trouble flashing CM9 to photon - Motorola Photon 4G

I'm having trouble flashing Joker's CM9 to my Photon. I followed the instructions here to root, unlock, and install clockworkmod to the phone. Then I followed Joker's instructions to install the ROM, as well as referencing this video.
After flashing the ROM, the phone sits on the red Motorola logo and doesn't go any further... I've waited about 10 minutes.
To review the steps I took to install the ROM:
1. Boot into recovery
2. Format /system
3. Factory reset
4. Reboot recovery
5. Flash joker's zip
6. Flash gapps
7. Reboot
8. Sits on Motorola logo
9. Repeat steps 1-7
10. Still sits on Motorola Logo
Any ideas? I'm sure there's something obvious here, but I'm not seeing it.
Thanks in advance!
Justin

Which rom were you coming from and which version of cwm were u using?
Sent from my MB855 using xda premium

Good questions. I came from the stock ROM. And I had used Rom Manager to update to the latest version of clockworkmod (5.0.2.8).

JustinHoMi said:
Good questions. I came from the stock ROM. And I had used Rom Manager to update to the latest version of clockworkmod (5.0.2.8).
Click to expand...
Click to collapse
The version is CWM that ROM Manager flashes isn't yet comparable with CM7, gonna have to go back to 5.0.2.7.
Sent from my 1.3 OC'd CM7.2 Electrify.

When you say it's not compatible with CM7, I assume that applies to CM9 also?

JustinHoMi said:
When you say it's not compatible with CM7, I assume that applies to CM9 also?
Click to expand...
Click to collapse
My bad, I meant CM9, not CM7. afaik CM7 flashes fine with it, I haven't heard/read any different.
Sent from my 1.3 OC'd CM7.2 Electrify.

Koush missed a few things in his cwm. For now use romracers cwm
Sent from my MB860 using XDA App

That was it. I flashed 5.0.2.7 and all is well. Thanks!

Related

[RESOLVED] [Q] Can't get recent Cyanogen Mod update to flash

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.

Having many problems with Fascinate

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!

[Q] Atrix 4G - ICS Codename

hellow dev...
please help me..
asking someting...
how can i install this rom? Atrix 4g ICS Codename..
you can see this http://cna.exynos.co/olympus/
it have update till 28.03.2012...
so when i install it...it come back to recovery...
im love ICS..
tq..please help me...
you have to choose one version, download and copy to your device
1. run recovery
2. wipe data, cache, dalvik
3. install zip from your device
4. reboot
i do step by step...still reboot recovery...
have u try it?
Did you install CWM? My buddy had the same problem with rebooting into recovery.
Sent from my MB860 using XDA
I tried flashing it and it does indeed just reboot to recovery. Have no idea why.
What it actually does is sits at boot logo screen, then reboots to recovery, so it actually bootloops once into recovery each time you try to boot it up.
CaelanT said:
I tried flashing it and it does indeed just reboot to recovery. Have no idea why.
What it actually does is sits at boot logo screen, then reboots to recovery, so it actually bootloops once into recovery each time you try to boot it up.
Click to expand...
Click to collapse
need the bins files and libcxxx from cm9 to stop reboot to recovery
stevendeb25 said:
need the bins files and libcxxx from cm9 to stop reboot to recovery
Click to expand...
Click to collapse
Cheers. I just tried flashing it to see if I got same issue as OP. Hopefully your comment will help him/her.
Sent from my MB860 using xda premium
need the bins files and libcxxx from cm9 ???
can i just take from cm9 source??
I got it booting using cm9 as base.
All you gotta do is delete app/framework from cm9 then push all app/framework of codename to see at least what the ui looks like and what options and features it has
Sent from my MB860 using XDA Premium App
rickriego replaced the bin/libs in the CNA zip with the ones from cm9 and posted a flashable zip over in the dev section for anyone interested.
I know there is a version using Jokersax's files but has anyone gotten it to work with Turl's files. The camera does not work with the newest jokersax as Rodriego uses, so I tried to use Turl's, and it just got stuck on the bootscreen. Thanks in advance.
fl1p1slander said:
I know there is a version using Jokersax's files but has anyone gotten it to work with Turl's files. The camera does not work with the newest jokersax as Rodriego uses, so I tried to use Turl's, and it just got stuck on the bootscreen. Thanks in advance.
Click to expand...
Click to collapse
same way, merge turls bin/lib folders into the zip using 7zip
stevendeb25 said:
same way, merge turls bin/lib folders into the zip using 7zip
Click to expand...
Click to collapse
Yeah I thought it would be pretty easy. I used winrar to move the folders to the cna rom zip but still stays on boot animation.
Thought I was going crazy bit other people could not make it work with turls1's files
ovitz said:
you have to choose one version, download and copy to your device
1. run recovery
2. wipe data, cache, dalvik
3. install zip from your device
4. reboot
Click to expand...
Click to collapse
No, the above WILL NOT WORK!!!
However, doing this will work:
get the nightly from
http://cna.exynos.co/olympus/
get the
beta 0.4.3
faux’s 1.0 kernel -outdated (ignore outdated, it´s the right one)
from
http://www.jokersax.com/developer-pages/jokersax/cyanogenmod-9-atrix/
get jokersax gapps v11
from
http://www.jokersax.com/developer-pages/jokersax/cm9-gapps/
in linux, using Q7Z, unzip the CNA nightly and replace the following folders by the ones from Joker´s beta 0.4.3:
bin
lib
xbin
Re-Zip. Be careful not to alter the zip structure or permissions.
In Recovery, flash your modded CNA.zip, THEN flash faux´s kernel, THEN flash gapps.
Enjoy

[Solved!/CWM] Unable to Enter Recovery (Showcase)

[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!

[Q] HELP! Can't Escape TWRP!

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

Categories

Resources