OK, so it has been a while since I have had to flash recoveries etc... Anyway, I Odin'ed back to stock today because I had to go to the Verizon store to talk about my replacement phone so I wanted to have it unrooted. Anyway, now I am trying to get CM7 back on for the time being but I can't get in to CWM. I tried pushing the cwm_recovery_all tar file via ODIN and when I do the three finger boot, it still brings me to the stock recovery and when I hit apply update.zip it fails.
What the heck am I doing wrong? I figured I could just get recovery on there and not have to worry about "rooting" since all the ROM's have that built in anyway.
Any help is appreciated!
Nevermind, I think I figured it out
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Kevin Gossett said:
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Click to expand...
Click to collapse
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
xceebeex said:
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
Click to expand...
Click to collapse
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
efan450 said:
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
My point is that I was able to boot in to red recovery (2.5.1.x) BEFORE flashing any custom kernel. I understand that CM7 has a kernel built in, but I was able to boot in to both the red recovery and jt's cwm 4 fix (4.0.1.0) before flashing any ROMs/Kernels. I wasn't even rooted (flashing CM7 is what rooted me).
After re-reading what he wrote, the way he says it is correct. I must have read it wrong the first time. So I apologize for saying "Nope." For some reason I read it as if he was saying I had to flash a custom kernel before being able to boot in to any recovery. He is just saying that you can't let the phone fully boot after pushed the recovery (which is what I ended up doing in my steps).
Sorry for the confusion.
No problem...glad you didn't take offense I'm just nearly thinking of all the noobs that are just getting into this kind if stuff and when they read the thread they might be misinformed...
that being said I've been on cm7 for a while and I know not to flash with anything other than the included recovery, I can confirm power button menu gets you to the new blue recovery but if you three finger salute it (done on accident just out of habit) you will get to an older recovery! In my case the old red one....Weird having both on the phone simultaneously, but it's no prob as long as we only use the new recovery to flash anything.
Sent from my SCH-I500 using XDA App
Related
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
RepAZ said:
So i updated OTA to 2.2 and then rooted my Fascinate. Now I'm trying to flash a new rom using Rom Manager but whenever I try to install a rom or reboot into recovery i get the error
And then it puts me in Stock Android Recovery. Any ideas on why this is happening and how I can fix it? Thanks
Click to expand...
Click to collapse
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
phonefiend said:
The consensus seems to be not to use ROM manager and to ODIN Clockwork Recovery Manager. Unfortunately there seems to be a little mentioned bug where CWM won't stay after the 1st time you reboot and I can't find a solution to this yet.
Click to expand...
Click to collapse
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
islandtime said:
CWM will stay after you boot but you need to change your kernel. After you boot stock kernel overwrites cwm. Definately use odin to flash cwm, boot to recovery, should be red, flash custom kernel. I use JT's undervolted voodoo. If you voodoo itll take a little while to boot while voodoo converts your system.
Click to expand...
Click to collapse
What I meant to say is what you said above: you can boot into CWM right after you flash it, but if you restart again it will go into stock recovery.
fitti28 said:
Island beat me to it but he is exactly correct. I kept the stock kernel at first but i had to ODIN CWM 2 times as the first time it was blue but after 2nd time it was red. But the best way is to flash a custom Kernel which will keep it red
Click to expand...
Click to collapse
I've ODIN'd CWM multiple times but it still gets overwritten with the stock recovery. I'd like to stick with the stock ED01 kernel but can't find any ZIPs to flash this kernel via CWM.
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I can't find anything on that, can you point me to the thread you followed?
Allmaechtig said:
You need to get the 3e recovery and put in /system/bin/ I had the same thing happen to me.. look up 3e recovery. It a common problem when the Galaxy S is updated to 2.2. Once you put the recovery file into the /system/bin/ you can flash CWM and it will all be good
Good Luck
PM me & let me know how it goes
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
imnuts said:
No, what is needed to get into CWM is you need to flash CWM via Odin. Take the battery out when going into download mode. After flashing, unplug the USB cable and put the battery back in. When you go to start the phone, boot straight into recovery. The stock kernel reflashes recovery on every boot, so if you boot the phone normally, the phone will continue to have stock recovery. Once in CWM, flash a custom kernel and you'll be set as the custom kernels don't reflash recovery on boot.
Click to expand...
Click to collapse
This is unfortunate because I used to run a version of CWM just fine with the stock EB01 kernel. With the current CWMs I finally found a way to get it to work with the stock kernel: rename /system/etc/install-recovery.sh.
got it working yay
BlackHoleSlam said:
got it working yay
Click to expand...
Click to collapse
Tell us how.
i just waited some time and placed the debinged rom from adrenylne on my sd card then used the 3-30 tar and put my self in red voodoo flashed a different kernel theme then rom and all is good
Ok, so I'm kinda new to the whole rooting, recovery, etc, but after successfully rooting my phone last week, I felt like trying to do something simple like putting on Community Rom or a different boot-up animation. I followed this thread for Community Rom:
http://forum.xda-developers.com/showthread.php?t=1053567
Which then references other links to download the files necessary to flash the Community Rom to the Fascinate. Problem is, I cannot get 'Update.zip' from this link:
http://forum.xda-developers.com/showthread.php?t=1046855
The update.zip link goes to a 404 not found page, so I can't finish the rest of this.
What I have done so far is installed ODIN on my PC and flashed Clockworkmod, though its not the same one I see referenced on XDA....the filename is
"cwm-recovery-ALL-3-30-FIX". Would this make an difference at all? I got it on my phone and it works when I boot into recovery, but it gives the stock blue screen and not the CWM screen (which I understand should be red) and I guess this is because I don't have Update.zip or something, so I can't flash anything using CWM at the moment.
I did find an 'update.zip' file somewhere (I really don't remember where now), and I put this on the root of my sdcard, but when I go into record and select 'Apply sdcard/update.zip' it shows that it's trying to do something (a progress bar moves across the screen very quickly), but then I get a triangle with an exclamation mark inside and the Android underneath it and nothing else happens. I left it for at least 5 mins and still nothing happened. The only way I can get back to the phone normally is to pull the battery out, put it back in and reboot the phone from the stock recovery.
Can someone help me out? Do I have a crap 'Update.zip' file and if so where do I get a good one from?
My specs for my phone are:
Hardware ver. I500.04
Firmware ver. 2.2.1
Basband ver. S:i500.04 V.ED01
Kernal ver. 2.6.32.9
Build number: SCH-I500.ED01
Odin the CWM recovery, boot to recovery, flash CommROM. That's all you need to do
Sent from my SCH-I500 using XDA App
Ok, I guess I'm kinda confused now. I already have CWM on my phone. Are you saying that I should use Odin to put the version of CWM on from here and I won't need update.zip?
Update.zip is not needed, the cwm replaces the stock recovery in the phones flash memory
Sent from my SCH-I500 using XDA Premium App
You already have cwm on your phone and the recovery 3-30 file is fine, download comm rom and it put on the root of your phones sd card (ie.not in a folder)...if you download it right from your phone it will be in a file that your downloads will be in..most likely tapatalk download, download, or downloads... the point is you want to be able to find it easily.boot into recovery and
Do a factory data reset, also wipe cache, and go to advanced and wipe dalvik cache . After doing those three things locate the comm rom file and install..reboot and enjoy!
If you did odin recovery and then did not flash anything the stock kernel will re write recovery and you will have to re-odin recovery again...so if I were you I would....odin recovery...put the batt back in, three finger boot into cwm flash your rom and or kernel and done
Sent from my SCH-I500 using XDA App
efan450 said:
You already have cwm on your phone and the recovery 3-30 file is fine, download comm rom and it put on the root of your phones sd card (ie.not in a folder)...if you download it right from your phone it will be in a file that your downloads will be in..most likely tapatalk download, download, or downloads... the point is you want to be able to find it easily.boot into recovery and
Do a factory data reset, also wipe cache, and go to advanced and wipe dalvik cache . After doing those three things locate the comm rom file and install..reboot and enjoy!
If you did odin recovery and then did not flash anything the stock kernel will re write recovery and you will have to re-odin recovery again...so if I were you I would....odin recovery...put the batt back in, three finger boot into cwm flash your rom and or kernel and done
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Maybe that's what happened then, I used Odin to put CWM on, but didn't flash anything after that. I'll go ahead and try again and see what happens.
So, why does everyone say you need update.zip all the time after you Odin CWM on the phone?
toledospod said:
Maybe that's what happened then, I used Odin to put CWM on, but didn't flash anything after that. I'll go ahead and try again and see what happens.
So, why does everyone say you need update.zip all the time after you Odin CWM on the phone?
Click to expand...
Click to collapse
You use to have to use update.zip but that is not the case anymore...and since you didn't flash anything after recovery you will have to re-do it, so if u did not already download the com rom file you will have to boot up...download comm rom...(i recommend the one with the otb kernel because you can overclock and undervolt with the voltage control app), pull the batt, odin recovery...that 3-30 recovery file is what works for me, put the batt back in and boot directly into recovery at this point I would suggest going to backup and restore and doing a nandroid back up btw power button is accept and menu button is go back...this willsave your phone exactly like it is now just in case things get screwy you will have a point to go back to ( but do not try to restore that back up in the future with out first disabling the voo doo lag fix) after your nandroid is done ,wipe data/cache/dalvik, navigate to wherever your comm rom zip is...install reboot and done...this process will take a few minutes and it's important to be patient...if you are fully stock as if right now you will hear a robotic lady saying stuff as your phone boots up...this is all normal and what you want to hear..once it reboots you can start playing around and setting it up the way you like it
One more suggestion is to use titanium backup and back up all of your apps prior to flashing and after your flash just restore all the apps...not data..i also export all of my contacts to the sd card not g mail cause I've lost contacts before so I just export to sd..flash and import them..that's what works for me...good luck..happy flashing!
Sent from my SCH-I500 using XDA App
Thanks efan, that worked perfectly this time. I now have Comm Rom on my phone and like you said, didn't need update.zip at all.
Edited as I thought I was having problems after with Android Market, but its fine now.
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
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!
Last week I flashed LD3 for my Galaxy S2 i777. Today I was going to flash CM9. Every time I tried to boot into recovery it just started the phone.
I figured I could use mobile odin to flash a new kernel and it would fix it. Like an idiot I used a Gingerbread kernel on my phone running an ICS rom. So of course my phone froze on the "Galaxy S2" screen.
I couldn't boot into recovery and freaked out because I couldn't boot into dl either. I ordered a jig but kept fiddling in the meantime. I found that if I hook my phone to the USB, wait for the battery charging icon, take the battery out, then hold the down button it would boot into dl mode. Then I had to put the battery back in before I clicked continue or else it just reset.
Ok, so got into DL mode. I grabbed the stock rom and kernel from XDA site and flashed them with Odin. http://forum.xda-developers.com/showthread.php?t=1286432 (can't post links yet).
The phone starts and setup mode begins. It shows the android figure and says click it. Now all kinds of errors pop up telling me different google services weren't working and force close. When you click the android figure it goes to setup wizard screen but nothing happens (except more android service errors).
Can someone help me out here? I've been at it 5 hours and searched this forum high and low. My thought is there are some ICS elements left behind in there it is trying to load, but I could be way off.
I still can't boot into recovery mode, just DL.
PenguinSpark said:
Last week I flashed LD3 for my Galaxy S2 i777. Today I was going to flash CM9. Every time I tried to boot into recovery it just started the phone.
I figured I could use mobile odin to flash a new kernel and it would fix it. Like an idiot I used a Gingerbread kernel on my phone running an ICS rom. So of course my phone froze on the "Galaxy S2" screen.
I couldn't boot into recovery and freaked out because I couldn't boot into dl either. I ordered a jig but kept fiddling in the meantime. I found that if I hook my phone to the USB, wait for the battery charging icon, take the battery out, then hold the down button it would boot into dl mode. Then I had to put the battery back in before I clicked continue or else it just reset.
Ok, so got into DL mode. I grabbed the stock rom and kernel from XDA site and flashed them with Odin. http://forum.xda-developers.com/showthread.php?t=1286432 (can't post links yet).
The phone starts and setup mode begins. It shows the android figure and says click it. Now all kinds of errors pop up telling me different google services weren't working and force close. When you click the android figure it goes to setup wizard screen but nothing happens (except more android service errors).
Can someone help me out here? I've been at it 5 hours and searched this forum high and low. My thought is there are some ICS elements left behind in there it is trying to load, but I could be way off.
I still can't boot into recovery mode, just DL.
Click to expand...
Click to collapse
Did you do a full wipe before flashing the stock rom and kernel?
I did not do a full wipe. How can I go about that without logging into recovery? I'm googling that now but if you have linkage I would appreciate it.
mattdm said:
Did you do a full wipe before flashing the stock rom and kernel?
Click to expand...
Click to collapse
dont need to wipe when using Odin/Heimdall.
To OP:
there is only factory recovery, no CWM, you could always just flash a kernal from the DEV section, get CWM, flash CM9.
If I flash another kernel wouldn't I still have the same problem? I'll go ahead and give it a shot. Any you recommend for any reason or other?
PenguinSpark said:
If I flash another kernel wouldn't I still have the same problem? I'll go ahead and give it a shot. Any you recommend for any reason or other?
Click to expand...
Click to collapse
So let me get the straight...you're on unrooted stock right now? If that's true, you should:
1. Do a factory reset from settings.
2. Use Odin to flash the Stock with Root package.
3. Use Mobile Odin to flash either Entropy's DD or Siyah.
4. Use CWM to flash what you want after that.
PenguinSpark said:
If I flash another kernel wouldn't I still have the same problem? I'll go ahead and give it a shot. Any you recommend for any reason or other?
Click to expand...
Click to collapse
recovery is in kernal. If you flash a kernal from the DEV section you'll get CWM recovery, then you can flash your CM9 that you wanted, after a wipe data/factory reset.
MotoMudder77 said:
recovery is in kernal. If you flash a kernal from the DEV section you'll get CWM recovery, then you can flash your CM9 that you wanted, after a wipe data/factory reset.
Click to expand...
Click to collapse
Yes, but if he flashes said kernel with Odin, it'll trip his flash counter. I'm just telling him the safe way to do it, Mobile Odin.
I've already tripped my counter. I have a jig that will be here tomorrow so I can use it to reset the counter.
I can't use mobile odin because I can't log into my phone. I can only use desktop Odin.
All the files I am digging up look like .zip made for cwm. Could someone help guide me towards a kernel I can flash from desktop?
PenguinSpark said:
I've already tripped my counter. I have a jig that will be here tomorrow so I can use it to reset the counter.
I can't use mobile odin because I can't log into my phone. I can only use desktop Odin.
All the files I am digging up look like .zip made for cwm. Could someone help guide me towards a kernel I can flash from desktop?
Click to expand...
Click to collapse
Either Entropy's DD or Siyah. You can open the zip and extract the zimage; the zimage is the kernel.
I just tried using Syiah:
http://forum.xda-developers.com/showthread.php?t=1367800&highlight=cf-root
I still get this message:
"The process android.process.acore has stopped unexpectedly. please try again"
I can't get past the setup screen.
And I still can't access recovery.
PenguinSpark said:
I just tried using Syiah:
http://forum.xda-developers.com/showthread.php?t=1367800&highlight=cf-root
I still get this message:
"The process android.process.acore has stopped unexpectedly. please try again"
I can't get past the setup screen.
Click to expand...
Click to collapse
you flashed siyah kernal, booted into recovery, wiped data, and reflashed and are still getting this?
I can't boot to recovery
PenguinSpark said:
I can't boot to recovery
Click to expand...
Click to collapse
Flash the return to stock package from Odin again. Something must have gone wrong with it the first time.
well thats wierd. Sorry man but are you doing it right?
vol down and power. hold it untill the screen flashes twice.
I flashed stock 3 times now. I couldn't get into recovery before this (manually or with rom manager) and still can't. It starts like its going into recovery then just resets and loads normally.
Down is for dl mode, up is recovery.
I think the lack of ability to boot into recovery and the android service errors may be related.
PenguinSpark said:
I flashed stock 3 times now. I couldn't get into recovery before this (manually or with rom manager) and still can't. It starts like its going into recovery then just resets and loads normally.
Down is for dl mode, up is recovery.
I think the lack of ability to boot into recovery and the android service errors may be related.
Click to expand...
Click to collapse
Forget recovery. You shouldn't be worrying about recovery until after you get your phone booting.
New thought: maybe your download of the stock package is corrupted. Try to download it on your computer again. Download the one with root. If that fixes it, you can go use Mobile Odin to flash the Siyah kernel.
To get into recovery hold down both volume up, volume down, and power button and don't let go until recovery comes up.
Sent from my SAMSUNG-SGH-I777 using XDA
I have been using the rooted. The fully stock won't dl. This started because I flashed a gb kernel instead of ics. Maybe I should try flashing an ics kernel instead of stock gb?