Im running into problems with Cyanogen Mod 7 I can't get it to install. I choose the zip in cwm and it sits there for a sec then gives me either a bunch of errors or a status 7. Its like the zip is corrupt. I tried re downloading it with no luck. I tried installing the 7 04 build and it just bootloops or doesn't work. I installed the june 19 build just fine though. Anyone else having problems? I got ukb to work just fine too
EDIT: Has been resolved. Thanks everyone for your kindness to my noobness
Have u tey to flash custom recovery tht jt list in his op then flash from tht 1
Sent from my I500 using XDA App
Yeah I've tried to do it from there too. I actually got the 7/04 build to flash. Then when I try to flash the 7/13 one it gives me a status7.
shakeandscream said:
Yeah I've tried to do it from there too. I actually got the 7/04 build to flash. Then when I try to flash the 7/13 one it gives me a status7.
Click to expand...
Click to collapse
i ran into the same thing. If your already on 7/04 go into orange recovery, wipe cache and dalvik and it should work. If not try flashing one of the OTB kernals, rebooting then go to recovery and try to flash.
Orange recovery? Like do I use the recovery that I already have or should I download rom manager on 7/04 and flash that recovery because if that's not the case and I use the one I already have it won't work cause I tried it. :\
shakeandscream said:
Orange recovery? Like do I use the recovery that I already have or should I download rom manager on 7/04 and flash that recovery because if that's not the case and I use the one I already have it won't work cause I tried it. :\
Click to expand...
Click to collapse
Once you have 7/4 test, you should go to Recovery via the reboot menu or adb reboot recovery.. DON'T use the power & vol- 7 vol+ method..
Also do not use rom manager with the fascinate period.
bobthesalesclerk said:
Also do not use rom manager with the fascinate period.
Click to expand...
Click to collapse
Until jt's commits get official CyanogenMod support - once that happens new CM7 nightlies will be posted to ROM Manager and the CM7 version of ROM Manager will work 100% for the Fasc.
Another Fascinating post by my XDA app...
it's frustrating I know.. make sure you are on 7/04 build. When you flash CM7, instead of the red recovery, you should get the orange recovery. You can only flash 7/13 build from the orange recovery. Wipe cache/dalvik and you should be able to flash 7/13 without any problem.
If you are getting bootloop from 7/04, that's because you did not wipe data on red recovery before you flashed 7/04. Go back to the red recovery, wipe data, and flash 7/04 again. Flash 7/04 fully on orange recovery, reboot recovery, flash 7/13 after wiping cache/dalvik, profit.
edit-moved to Q&A
So how do I get orange recovery? Cause when I flash 7/04 I still have my old recovery
Sent from my SCH-I500 using XDA App
After you boot 7/4 cm7, you want to get into recovery by holding power button, selecting reboot, then recovery. Or open a terminal and type su <return> reboot recovery <return>.
After you are on cm7 my experience is never do 3 button recovery or it will hose everything that you have achieved to this point.
ej
Okay well I got it installed. What I did was install 7/04 build, then I went into Rom Manager and chose the recovery I had installed or whatever. Then I rebooted into recovery and it was orange. Then I installed it just fine. I am now running on the 7/13 update Thanks everyone for your help, took me a bit to figure out but I got it.
Related
I was sent a Fascinate as a Droid Incredible replacement. I was able to root it without a hitch but now my CWM can't mount anything. Won't mount anything can't bring up any logs. I am using the CM7 Clockwork and my phone is now bricked and I'm tired of using Odin to restore it and root it again then flash CWM and CM7, I lose all my games and free apps which I have to download again.
What am I doing wrong?
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
skafan2 said:
Also, are you using atlas.pit when odining to stock? After doing what does the phone stop working entirely (IE does the phone boot up CM7 and then brick, or can it not load CM7 at all)? Can you run stock without your phone breaking?
Click to expand...
Click to collapse
Yeah. I can work on stock just great.
What is the best rooting method to use if I plan on using CM7?
What I do is use Super One Click to root (http://forum.xda-developers.com/showthread.php?t=803682), then flash the custom CM7 CWM, and then flash CM7 in the custom recovery after wiping data, cache, and dalvik.
Use the CM7 from here: http://forum.xda-developers.com/showthread.php?t=1190668
Do I use the recovery in that thread? I've been using that one as well. I will re download the rom then.
Yes. Here are the exact steps from that thread after rooting with SuperOneClick:
Start with a rooted device (do not ask us how to do this).
Flash ClockworkMod Recovery attached to this post.
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Wipe Data! Seriously! Do it!
Install the ROM zip from sdcard
Install gapps package linked here (http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps)
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Yeah. It's stuck at the logo. I reboot into recovery and I get the log errors. That's 6 Odin resets today.
Make sure you use atlas.pit when restoring to stock. If you are following those directions exactly, all I can say at this point is to try another ROM (maybe MIUI or OMGB) and see if that works, unless another poster wants to take a stab at this.
Yeah, I'm using the atlas 2.2.pit
I had it working yesterday but only if I flashed the rom using the orange recovery through ROM Manager. I might try that again.
Hyphnx said:
Alright. Let me try that again now. I just put the Nightly #8 on my SDCARD
Flashed it through the recovery, it's at the Samsung logo now. I am going to leave it there for a bit and see if that changes.
Click to expand...
Click to collapse
I think the nightly might be your problem?...my $.02...and there are a lot of extra steps but it works for me if I really can't get cm7 to load (I've done this more then once)
Odin eb01 with the atlas 2.2pit and reboot fully when odin is done.
Pull battery...Odin cwm 3/30 fix all..and when that's done, install battery and 3 finger salute into recovery....wipe everything and flash com rom 2.0 and reboot.
This is where you may have to try different recoveries, putting com rom on your phone gives you root, recovery and voodoo. So from here if your recovery doesn't properly flash cm7 you can simply pull the battery re odin a different recovery and try again, as long as you don't try to reboot the phone.
Make sure you are using the 7/17 build from, jt's pretty much official cm7 Thread, not the nightly. even if this is not what you want it should properly get you to mtd format, so another rom on an mtd build can just be flash the good old way.
I've had the cwm4.x.x.x work fine and then today it would not work after I flash a different kernel with out wiping anything...oops! I've had 3/30 fix all cwm give me the best results but even today would not work.
What did work was using the com rom recovery to flash times infinity's purple recovery zip...reboot recovery into the purple one, and then wipe everything and flash cm7 7/17...ugh finally! Once I was there just power button menu... reboot recovery to install gapps, and glitch. You could at this point wipe cache and dalvik and flash nightly if you wanted...hope some of this helps.
Sent from my SCH-I500 using XDA App
I've had the same problem tryin to flash all mtd based roms...it always sticks at the samsung logo when I three finger back to recovery. I get the error logs aswell...**** sucks lol. That's odining ed05, fully boot, odin cwm 4 fix for cm7, boot recovery, wipe data,cache, dalvick, install rom.zip, all for a samsung logo and log error lol. So instead of spending 5hrs trying to flash a rom, I spent 10min and flashed power wash ed05, works great!
[SCH-I500, Android 4.0.4, IcyGlitch V14 B6]
[EDIT: Solved! Bug within Gummy v1 on Showcase and Mezmerize. Configure ROM Manager and reboot recovery for workaround.]
Here's the short version: In Gummy v1.0.0, using the power menu, I am unable to enter recovery. According to Droidstyle's guide, using the 3 finger method is not to be done once on ICS, as it will cause bootloops. "adb reboot recovery" will not work either.
Alrighty, here's what I've done so far to my Showcase from CSpire:
1. Restored my stock ODIN file, which is EI20.
2. ODIN'ed CWM4 Fixed for CM7
3. 3-fingered into recovery
4. Installed ICS Hacksung Build 2
5. Installed ICS Gummy and GApps 3/17
6. Used for about 2-3 weeks, with a few tweaks.
7. Attempted to nandroid, unable to enter recovery.
So, I'm not sure if I should re-flash recovery via ODIN/Heimdall, attempt to replace the recovery.img via shell, or if there's a different method.
Does anyone have an idea about how to fix this problem?
th
Akkeresu said:
[SCH-I500, Android 4.0.4, IcyGlitch V14 B6]
Here's the short version: In Gummy v1.0.0, using the power menu, I am unable to enter recovery. According to Droidstyle's guide, using the 3 finger method is not to be done once on ICS, as it will cause bootloops. "adb reboot recovery" will not work either.
Alrighty, here's what I've done so far to my Showcase from CSpire:
1. Restored my stock ODIN file, which is EI20.
2. ODIN'ed CWM4 Fixed for CM7
3. 3-fingered into recovery
4. Installed ICS Hacksung Build 2
5. Installed ICS Gummy and GApps 3/17
6. Used for about 2-3 weeks, with a few tweaks.
7. Attempted to nandroid, unable to enter recovery.
So, I'm not sure if I should re-flash recovery via ODIN/Heimdall, attempt to replace the recovery.img via shell, or if there's a different method.
Does anyone have an idea about how to fix this problem?
Click to expand...
Click to collapse
did you try selecting the reboot option instead of recovery in the power menu? they were mislabled on gummy the last time I was using that rom.
Nope. Rebooting with Reboot, Recovery, and Bootloader all yield a standard reboot sequence.
Akkeresu said:
Nope. Rebooting with Reboot, Recovery, and Bootloader all yield a standard reboot sequence.
Click to expand...
Click to collapse
That's a known issue on Gummy for showcase and mesmerize. I can't figure it out.... :-( people have been working around it by using ROM manager to get to recovery.
Sent from my Glitched AOKP Unicorn.
imo make the switch to aokp!!!
Stephen.k.spear said:
That's a known issue on Gummy for showcase and mesmerize. I can't figure it out.... :-( people have been working around it by using ROM manager to get to recovery.
Sent from my Glitched AOKP Unicorn.
Click to expand...
Click to collapse
That did the trick. I did have to click the Flash Recovery Button, , select the Showcase and tell it to use CWM v3.x+
Maybe it's something about the scripting? When I get some time, I'll turn on some logging and see if I can locate a difference between the normal recovery reboot attempt and the ROM Manager reboot.
I was attempting to use Supercharger V6, but couldn't make it stick because I was unable to clear Dalvik. Thanks a bunch!
Akkeresu said:
Nope. Rebooting with Reboot, Recovery, and Bootloader all yield a standard reboot sequence.
Click to expand...
Click to collapse
I'll definitely give it a try now that I can get into recovery and make a backup. My good friend from Canada just recently dropped Build 32, I think, onto his own Faci, so I'll see how it runs on my Show. Thanks for the help dude!
I can't escape TWRP!
My setup is this:
ROM: THS build 10
Kernel: ICYGlitch v14
Recovery: TWRP (included with ICYGlitch)
Recently, I wanted to flash ParanoidAndroid. I rebooted into TWRP via the power menu, made a backup, and tried to flash. It gave the error E: signature verification failed. Later, I tried turning off signature verification, but then it gave me another error. I then tried to flash cwm4_fixed_for_cm7, but it gave me the same error. Then I tried flashing the recovery through ODIN. It said it succeeded, but it still loads TWRP as the recovery. Help! I can't escape!
P.S. I know my way around the Fascinate, I'm not a complete noob.
try flashing cm7, then back to ICS, ...if all else fails odin back to stock start over.
Maybe
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
MultipleMonomials said:
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Click to expand...
Click to collapse
flash a older version of glitch that still utilizes cwm recovery. check my kernels section of the guide.
That would work except for the fact that I cannot flash anything from TWRP.
MultipleMonomials said:
That would work except for the fact that I cannot flash anything from TWRP.
Click to expand...
Click to collapse
odin cwm4 fixed for cm7, then three finger and flash away.
Wait. Doesn't three-fingering on a MTD filesystem bootloop you?
at this point just odin back to stock and start over
shelby04861 said:
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Sent from my SCH-I500 using Tapatalk
I figured it out. I was able to flash an older version of Glitch with CWM recovery.
How did you flash an older version of glitch in cwm if you were stuck in twrp? I though you couldnt flash anything. I am confused???
Sent from my SCH-I500 using Tapatalk
Sorry. I meant TWRP. Here is the procedure that I used. I don't know if it is necessary, but it worked.
1. make a nandroid
2. restore to stock
3. ODIN cwm
4. install THS build 1
5. install THS 10 (substitute whatever ROM you're using)
6. install newest Glitch (with TWRP)
7. restore nandroid
8. install older, CWM glitch
I think this works because nandroids don't restore the recovery partition.
I was having instability with the older Glitch version, so I flashed the newer version again, and I can still flash stuff.
Okay. I got it now. I thought the whole reason you didn't want to start over was because you didn't have a backup of your current setup. That is why people were saying that you were going to have to start over.
Glad it worked out.
Sent from my SCH-I500 using Tapatalk
I really don't know who to credit for this, so if your reading this Credits to you! Koush & CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
09/30/12 (Mainly a JellyBean reference)
Easily switch between ROMS and the different partition layouts!
Reboot to recovery and flash cwm4-fix, power the phone down (might need to pull battery) and three finger back into recovery!
Wipe data, flash chosen GB,ICS, or any partion JB ROM from any order! (ie: downgrade or upgrade)
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
cwm4-repack no asserts Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)(Allows force flashing)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
cwm6_recovery Contents:
Latest source built CWM Based 6.0.1.0 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
cwm4-repack no asserts 5.83 MB - 06/27/12
cwm6-recovery (JB) - 5.15 MB - 07/29/2012
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Click to expand...
Click to collapse
If you download, power off, three finger and flash cwm4-repack and reboot it should break the boot loop and continue booting your ROM (However sometimes when updating the recovery it will automatically reboot to recovery, reboot now if this happens). Assuming ICS...
Also if you power down, three finger, do nothing and reboot, your phone will actually reboot! Assuming you already flashed cwm4-repack...
Not to sound dirty but I was three fingering all day while doing yard work...
Back n forth from CM7,CM9 & AOKP Based!
notta said:
I really don't know who to credit for this, so if your reading this Credits to you! CM obviously too!
I repacked CWM4 & CWM5 to solve the three finger recovery loop dilemma...
Flash cwm4-repack after each ROM flash to solve the three finger boot loop issue.
If you three fingered and need to flash a CM7 based ROM, you can simply wipe data and proceed to flash. If you need to flash a CM9 based ROM, simply flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM9 ROM. (Always Remember to flash cwm4-repack directly after to break the recovery loop..)
When you reboot it may take you to recovery, just choose reboot now and your ROM should continue booting!
With these two zips and your chosen ROM, you should be able to flash on the go again without fear or break your existing install!
Update:
It seems most of the newer CM7 builds will require the same procedure as flashing a CM9 ROM.. (flash aokp-cm9-recovery first, then go to advanced/reboot recovery to reboot to the updated recovery. From there wipe and flash your chosen CM7 rom...)(Always Remember to flash cwm4-repack directly after to break the recovery loop..)
I have not tested any of the above combinations with twrp! Use at your own Risk! I also recall twrp having something about an injection feature of some kind that may be useful for that...
cwm4-repack Contents:
Repacked CWM4 fixed for CM7 (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery Contents:
Latest source built CWM Based 5.5.0.4 Recovery (Flashes Recovery only)(Does not affect ROM recovery)
aokp-cm9-recovery 4.50 MB - 06/06/12
cwm4-repack 5.83 MB - 06/06/12
Click to expand...
Click to collapse
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Nice dude! that's nice to keep on the Sd card.
Sent from my Glitched AOKP Unicorn.
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
tetrismonkey said:
will be sure to keep these on my sd card had to go back to stock to get out of the that boot loop it was horrible when i close my eyes i can still see images touchwiz
Click to expand...
Click to collapse
The horror...
Sent from my Glitched AOKP Unicorn.
sageDieu said:
so what about saving yourself from a loop? like if I download this and then three finger into recovery. then flash this, what happens?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
jmac9 said:
This is great....thanks. I'll give this a try on TWRP later (when I have access to ODIN just in case).
Click to expand...
Click to collapse
So am I to assume all is well with both scenarios...
notta said:
So am I to assume all is well with both scenarios...
Click to expand...
Click to collapse
Sorry....never went back to twrp. With the new devil kernal, I've been playing too much to want to try anything different. On a side note, I went back to the glitch kernal this morning (experiment) and had issues with trying to get the Rom to load and then actually had to go the three fingered route. This worked great once I followed your directions EXACTLY!
Note to anyone else.....if you are flashing a Rom that requires gapps, make sure you flash the cwm-4 repack right after the Rom....BEFORE the gapps. Loop doesn't break if you try to slip the gapps in there too soon I found.
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
SeatownGST said:
WOW this will be super helpful.
what does it take to compile roms to be installed via CWM 4 or CWM 5 ?
Click to expand...
Click to collapse
Not sure exactly what your asking but typically you would compile cm7 for cwm4 and cm9 for cwm5!
Or the answer for exactly how I read this:
A computer, some time and some knowledge...
notta said:
06/27/12
How to use these to upgrade from stock/rooted stock to ICS Rom of choice!
If pure stock you obviously need a CWM recovery installed so odin/heimdall cwm all or cwm4 fix!
Reboot recovery
wipe data
flash cwm4fix-no_assert
reboot
wait until samsung logo blinks, then pull battery
three finger into recovery
wipe again to be safe
install ICS Rom of choice
It will reboot twice, once to update recovery and proceed installing and once more when it's done!
Click to expand...
Click to collapse
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
SotYPL said:
It doesn't work for latest AOKP. Bootloops on samsung logo after flashing rom. I've had to go back and do it like always (CM9 b2 first).
Click to expand...
Click to collapse
Well, my apologies for mis-leading. However I did just repeat the above steps exactly, coming from Geewiz EH03 to a today built build 40! Perhaps a limitation against pure stock?
If this was stock and you are put in the position again, you could try flashing a non stock kernel after a odin/heimdall of cwm of course! I suppose this could be an issue... Maybe?
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
so, I've been searching around and apparently haven't found the right search term.
Why does the 3 finger boot screw things up in cwm 5?
How does one cold start into the recovery? I finally got ics on my trusty fascinate.
Click to expand...
Click to collapse
I'm not really sure! I was going to attempt a look but a short search came up empty for some older sources.
Speaking of, they need a smiley that is bashing his head against a wall in shame..
Clearly, Credits for this go to Koush! (And queue the above mentioned smiley)
notta said:
Not to sound dirty but I was three fingering all day while doing yard work...
Click to expand...
Click to collapse
LMAO!! Nice! And good guide btw, I still have no idea why three fingering does that :/
Sent from my SCH-I500(Fascinate)
It seems with the recovery wipe repack method, i get all the way to the point of the rom booting up, but it will just sit there and play the boot animation over and over and over.... how long is it supposed to take? I'm beginning to think i'm going to have to odin... ugh!
notta, you needta update this to cwm6 for jb, please & ty
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
+1
Sent from my A500 using xda app-developers app
ztotherad said:
notta, you needta update this to cwm6 for jb, please & ty
Click to expand...
Click to collapse
lifeofcoding said:
+1
Click to expand...
Click to collapse
Technically it isn't needed! CWM4 is all I have been using for JB so far. Works perfect to break the 3 finger curse and also to downgrade the recovery for better JB flashing in some scenario's.
Truth be told I only need heimdall now once in a blue moon and that is always because of something I'm trying. :silly:
I still posted it though as I figure it may come in handy at some point or at least have an odin/heimdall alternative. In OP for those in seeking...
Also while getting this together for you guys, I noticed the files in the OP are pushing close to a 1,000 downloads. Yet only 9 people have thanked me.
Has this not been useful? Just Curious...
My Atrix 4G is unlocked and I have perma CWM installed, used it for a long time with GB pudding and I wanted to try out a CM7 based ROM.
I've been trying to install MROM with no success at bootup it just stays on the Motorola Logo with the Unlocked. I thought maybe it was doing something and left it for 10 mins with no change.
Any suggestions on what other things I could do? I've tried clearing the cache/dalvik and wiping data/factory reset before installing.
Thanks,
LF4
Try wipe factory after install rom
Sent from my Atrix 4G using xda premium
Go to mounts and wipe system and osh. Flash rom. Will probably sit at boot.... Pull battery and flash rom again without wiping anything then should work
I tried factory wipe after the install.
Also formatted system/osh installing reboot and installing again.
No luck on either one. I was selecting install from zip and would navigate to the zip file downloaded from the link on the xda dev post here. Which is what I thought was the correct way of doing things.
The install takes about 10 seconds before it says it's complete and the boot I'm not sure how long to expect it before I need to pull the power and try again.
Are you sure you downloaded the correct zip file? Should be around 100 MB or so but seems if install is done in 10 seconds that you only have downloaded the kernel or something like that.
You can get MROM at montuori's website here
take the latest build (not the update, the normal version so without *-update.zip)
jorno88 said:
Are you sure you downloaded the correct zip file? Should be around 100 MB or so but seems if install is done in 10 seconds that you only have downloaded the kernel or something like that.
You can get MROM at montuori's website here
take the latest build (not the update, the normal version so without *-update.zip)
Click to expand...
Click to collapse
Yeah that is why I mentioned it only takes a few seconds to install. I did download the full Atrix-MROM-20121111.zip which is 119MB in file size. MD5sum is correct so the file isn't corrupted.
I've tried all different combinations to get this installed. I was running pudding 4.5.91 would that affect the install of MROM?
Might be time to upgrade your recovery. Last version for official clockworkmod no touch mode is 5.0.2.0, touch version is 5.8.1.8 (http://www.clockworkmod.com/rommanager)
jorno88 said:
Might be time to upgrade your recovery. Last version for official clockworkmod no touch mode is 5.0.2.0, touch version is 5.8.1.8 (http://www.clockworkmod.com/rommanager)
Click to expand...
Click to collapse
Thats what I was thinking. So I can just RSD flash the recovery-clockwork img to upgrade it do you suggest the touch or no touch CWM?
flashing a recovery when your bootloader is unlocked is done via fastboot.
i use the touch version myself and am happy with it.
to flash rom you type
moto-fastboot erase recovery
moto-fastboot flash recovery <recoveryname>.zip
make sure you have the motorola fastboot and drivers, to enter fastboot you can either use "adb reboot fastboot" or boot phone with volume down key pressed, when fastboot appears press volume up
stay as far away from rsd if it's not necessary.
My CWM was too old to flash it so I had to update it first then things worked great. Thanks for the help and suggestions I didn't know recovery zips were based on different versions.
Congrats man