Well, I was previously running Comm rom, and i decided to switch to CM7 7/13
This didn't go so well. I Odin'd DL09 with atlas and repartitioned then installed Cmw and still Status 7 when I try to install. Then I tried installing 7/4 and it would just say something like "Checking BML" Or something, i forgot... and it would just reboot into cwm. I was running JT's cwm fix, and i tried with cwm all... I don't know what to do. Now my fascinate won't install comm rom, and every rom install just leads up to booting up in cwm.. no samsung logo.. Help??
Edit: Phone is now in "Manual mode"
i guess samsung recovery? but it wont boot. It just reboots into the same recovery after i press "reboot system now"
please? :'(
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
xwhofarted said:
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
Click to expand...
Click to collapse
That's the thing... It wont boot to anything i install on it.. But it sure as hell boots to ANY cwm i install... and it also boots to normal recovery in the absence of a cwm....
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
jamespweb1503 said:
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
Click to expand...
Click to collapse
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
efan450 said:
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I love you <3
Related
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
alemondemon said:
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
Click to expand...
Click to collapse
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
I have same thing, but I cant get the phone to show in download mode to odin anything
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Edit: Just tried to do a restore and the MD5 Sums don't match. I've had to do Odin reset three times today.
I think I might do Vodoo and try to restore that way. I will report back.
alemondemon said:
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
Click to expand...
Click to collapse
No I don't think its omfgb related cause I've never ran that rom but I do think it has something to do with all the different recoveries we have floating around and so many different builds with different formats things are bound to get screwed up...my problem came from forgetting to wipe before flashing a different kernel and got me stuck in a boot loop.
Sent from my SCH-I500 using XDA App
I've had this problem ever since I got my Fascinate and tried to get CM7 on it. (2 days ago) I was always able to flash new builds just fine if I managed to get into the orange recovery and not the CM7 one. I believe the one I used was the one on ROM Manager.
This is kinda upsetting...
Hyphnx said:
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Click to expand...
Click to collapse
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
efan450 said:
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We are having problems with the recovery he posted in his post.
Tried CWM-Recovery-All, turned my phone into muffed up phone. UGH!
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Hyphnx said:
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Click to expand...
Click to collapse
So what rom are you running now?
Sent from my SCH-I500 using XDA App
efan450 said:
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
alemondemon said:
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
Click to expand...
Click to collapse
Yup...boot into the otb 3x.x.x recovery and flash the times infinity.zip and then select reboot recovery while in cwm and it should go from the otb one to the times infinity one...at that point wipe everything and flash cm7 build 7/17..not the nightly....once your on the mtd build you can flash the nightly if you wanted
From the power button menu
Sent from my SCH-I500 using XDA App
Edit: I suppose you could just odin times infinity's recovery...I just happened to have the zip on my sd handy so thats why I did it that way...it was that recovery that worked so you could odin it if you wanted it's in the link you posted try flashing it from ti's recovery..I just got there a little differently
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
humblewarfare said:
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
Click to expand...
Click to collapse
unfortunately a boot loop normally requires odin...use the eb01 tar and the atlas 2.2pit and your phone will be back up and running
From there I would flash com rom and reboot then if you wanna take a stab at cm7...try and flash it with the com rom recovery...if it doesn't work you can just try odin'ing different recoveries as long as you don't let the phone boot fully you can simply pull the battery and try to odin a different recovery.try the one from com rom, the 3-30 fix all, ti's recovery, or jt's fixed recovery...I don't know where I got the file but I also have a recovery named fixed 3 x.x for cm7 but I came remember where I got it.it is important that you let eb01 sit for a few minutes after booting and also let com rom sit for a few minutes after flashing also...I just skipped all the setup stuff to get the main screen and then pulled the battery and started flashing
Sent from my SCH-I500 using XDA App
humblewarfare said:
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
Click to expand...
Click to collapse
I'm running vista home edition...if it matters and I'm using odin v.1.7 try the samsung generic drivers also.but once I'm on cm7 my pc says it doesn't recognize my phone but if I put it in download mode and hook up odin recognizes it...so I'm not sure on that one
Sent from my SCH-I500 using XDA App
alemondemon said:
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
Click to expand...
Click to collapse
Try holding the down button while you plug into your wall charger then just move it to your pc...if that doesn't work...clean the contacts with rubbing alcohol...with the phone off.at worse case there is a jig you can manually force download mode...you can buy or make them
Sent from my SCH-I500 using XDA App
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!
Here is the story
Last week I was running Cm10 port with datadata without any issues. In a bad time I saw a new kernel version and I flashed that. After flash I got boot loop so I tried to go into recovery but to add to my bad luck recovery didn't work. So I thought Odin is the only option now. I odin back to stock and phone started working. Now time comes for more bad things to me
Day 1
I installed the CWR and tried to install SLIM 4.2 which was on my SD card. Install went fine and system booted. I soon as I booted I saw my SD card got formatted and I lost my IMEI with EFS folfer empty. I tried to restore EFS from backup but it didnt work so I odin back to JFD which gave my IMEI back. I tried slim again and same thing, again lost IMEI.
I thought lets try with different kernel, I flashed subzero kernel and rebooted into recovery again. Flashed zip and all went fine. Rebooted system after flash but system again went back to recovery. Flashed zip 2-3 time but same recovery again and again( Like a recovery loop)
Here I odin back to JFD and also flashed gingerbread bootloaders to make my life easy.
Day 2
Downloaded biwinning redux v1 which is 2.2.1 ROM. Install went smooth and I was able to use it.
Now I got new red recovery and it automatically enabled voodoo.
Here I tried to install HellyBean and got status 7 error. So I tried to flash devil intial package but status 7 again. So I flashed icy glitchy kernel and install went fine.
As soon as I reboot system all I had was small orange bar at the bottom and nothing else.
It was like I only have kernel but no system. Rebooted into recovery and flashed files again. Still same thing. So I flashed initial package on top of icy glitch and again install went fine. Phone got recovery loop again.
Damm...ODIN back to JFD and installed biwinning redux again as nothing else seems to be working for me.
Day 3
ODIN back to JFD and flashed icy glich kernel.
Flashed latest CM9 build. As soon as I flashed it, phone rebooted twice with some fast scrolling text. After that it keeps on rebooting and seems like its trying to find some file as I can see some red exclamation sign when it reboots.
Odin devil kernel tar file and flashed files again. But after cm9 files I just get black screen, waited for 10 minutes and nothing.
I odin again to JFD and restored nandroid of biwinning.
So I am again on 2.2.1 rom and seems like I am stuck on it.
Please suggest me what should I do....and I have already tried more then what I told.
Right now I am on biwinning redux v1(2.2.1 rom) with vodoo enabled and Gingerbread bootloaders
Go back to stock, flash straight from stock one of CM9 nightlies and then you will be able to flash to JB
Sent from my SGH-T959 using xda app-developers app
mikka06 said:
Go back to stock, flash straight from stock one of CM9 nightlies and then you will be able to flash to JB
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Already tried that. Phone keeps rebooting after flash...script keeps looking for something and gives me loop.
You have to flash twice from stock to CM9. After that you should be good
Sent from my SGH-T959 using xda app-developers app
mikka06 said:
You have to flash twice from stock to CM9. After that you should be good
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Can you please please give me step by step instructions from stock. I just dont want to odin again...already did like 10 times and now I am at breaking point.
Ok, so flash back to stock. Reroot your phone,so under recovery hit "reinstall packages" (once or twice, i always have to do it twice). Once you're in the new recovery flash any of CM9 nightlies. You will have some bootloops due to the recovery mismatch. Don't panic, take out the battery, put it back and go again in the recovery (vol up+vol down+power button if you're on froyo bootloaders or vol down+power button for gb bootloaders). Once you're in the recovery flash CM9. Once on ICS you should flash JB.
mikka06 said:
Ok, so flash back to stock. Reroot your phone,so under recovery hit "reinstall packages" (once or twice, i always have to do it twice). Once you're in the new recovery flash any of CM9 nightlies. You will have some bootloops due to the recovery mismatch. Don't panic, take out the battery, put it back and go again in the recovery (vol up+vol down+power button if you're on froyo bootloaders or vol down+power button for gb bootloaders). Once you're in the recovery flash CM9. Once on ICS you should flash JB.
Click to expand...
Click to collapse
Trying ..thanks
Update : Everything went smooth. I am on Slim Bean now
So the problem was when I got bootloops with cm9 , I was odin back but instead I had to reboot into recovery and flash again without changing any kernel. When I was getting bootloops I was installing kernel again.
Thank you for all the help
Haha good times .
Sent from my SGH-T959 using xda premium
I flashed Devil kernel over my Paranoid Android 2.18 rom, and it booted into devil recovery, with lots of errors. It wouldn't let me flash my previous rom, so I restored a previous jb "boot" [recovery] from a nandroid [advanced restore], then it went into a bootloop.
I tried heimdall, flashing the cwm boot.img from the parandoid android rom [extracted from .zip], still got the recovery bootloop. Then I tried repartitioning with atlas2.2.pit, and thought I was out of the woods when it booted into cwm 6.x recovery.
Then I wiped data and flashed my PA rom again, and this time I had a black screen [yes I know it's hard to see a black screen on SAMOLED screens, but it was dark and I could see the screen coming on and off] bootloop. No SAMSUNG logo, just the screen turning off and on again.
Download mode didn't work until I took out the battery, so I'm gonna try Odin. only thing is I have to reboot into windows since I use linux, but I'm wondering if anyone knows what happened here?
lucky I have a recent TiBa..
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
bbrad said:
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yeah I got it fixed by odining eh03 then CWM and flashing jb ROM..
The problem was I didn't have access to Odin right away so I was trying to fix it with cwm.