My samsung fascinate has VooDoo on it. I did not put it there, I am not comfortable with ADB shell and the commands that go with it. Its a D101 that HAS to run at 800Mhz with Voodoo (Not the 1.2 the specific voodoo is) at 1.2 nothing runs and constantly redraws the homescreen.
I tried the automatic uninstaller, and the red recovery stays to haunt. I've tried other kernels while disabling Voodoo.
My phone was running fine up until recently where it would have random reboots and have trouble booting back up.
I came across flashing back to stock with ODIN. the system file went over fine, and I even did the stock kernel and (PIT)
i Just flashed them all through ODIN.
The phone boots up fine to the main screen, where then I get the error message about a UID ? (Sounds dirty) it says to wipe data or my phone will have inconsistencies. Then gives me a button that says "feeling lucky"
Message as follows "UIDs on the system are inconsistent, you need to wipe your data partion or your device will be unstable" Only button to click is I'm feeling Lucky
everything force closes, red voodoo still shows up in recovery. What am I missing or doing wrong?
I bought this phone this way and like i said i know NOTHING about ADB or all those commands, etc.
Can somebody help me out? I'd even gladly send it to a trusted member for repair with a donation, of course.. until then I'm using my OLD bb curve
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
make sure you use the pda option in odin and not the phone..aparantly using the phone option can really screw things up
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
BrianWM said:
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
Click to expand...
Click to collapse
are you disabling voodoo before flashing these new kernels?
Powell730 said:
are you disabling voodoo before flashing these new kernels?
Click to expand...
Click to collapse
Yes, VooDoo is disabled.
BrianWM said:
Yes, VooDoo is disabled.
Click to expand...
Click to collapse
so did you use the odin files and flash it via PDA in odin? if so, did that revert you to total stock? i believe those .md5 files contain the stock recovery.
EDIT:
do you know what version of voodoo you're using?
http://forum.xda-developers.com/showthread.php?t=804784
that guide should help you, if you're using voodoo 5 there is a guide there that specifcally says "if you're still getting the red voodoo menu flash this file then flash a nonvoodoo kernel." check that article out by ady if you havent already.
flash voodoo boot right into recovery. adb shell into the device and type
cat /voodoo/partition_tables/fascinate > /dev/block/mmcblk0
And then reflash everything with Odin.
Also one of adrynalyne's di01 packages doesnt flash recovery. So either flash my dj05 or go to adrynalyne's cwm odin thread and flash a regular update.zip cwm tar.
Sent from my SCH-I500 using XDA App
A proper, 100% full Odin tar will replace everything on the phone, including voodoo, and the partitions that it formatted as ext4 will now be RFS again. Since the full DJ05s and DL09s came out I use it as a first resort instead of a last resort. Flash the full tar, CWM, the kernel, then nandroid and I am good to go in about 15 minutes.
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
ivorycruncher said:
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
Click to expand...
Click to collapse
Presentation is everything, thanks for the info!
Related
So i tried dj05 rom with voodoo kernel: jt's clean .5 rom and 11/29 voodoo 5 and dj05 modem
i got an fc hell so i went back to cwm(red) recovery and wiped data and cache and then odined di01 modem and then nanded back to my previous rom
i guess irc users told me my problem was i didnt turn off voodoo first before nand restore but it was too late my rom restored with no apps but with 4 or 5 apps including settings, market and camera plus the TW launcher so i tried odin to stock and still the same. so i formatted cache, data, system, and boot >> odined again and this time my phone loops back to recovery.
so i tried to flash a di01 stock rom found somwhere in the forums from jt (when di01 1st came out) and still the same. tried nand and same and odin also still the same IDK WHAT TO DO NOW
Flash clockworkmod with Odin and start from there. Look at the removing voodoo completely thread in the fascinate dev forum. Try that. Then flash a custom rom and kernel and hope things work from there.
Edit: I remember reading in IRC that nandroid in the green cwm is broken. So the nandroid backups your probably trying to restore aren't going to work right. After you do the remove voodoo completely thing look for the thread with the stock nandroid images. And give that a whirl.
Sent from my SCH-I500 using XDA App
Hey guys, new rooter here, hopefully somebody can help me out...
So I was running stock DL18 Eclair, decided to flash Baked Snack 1.6 (babystep.zip).
I rooted, installed Clockwork Recovery, made a backup and everything, as well as backed up with Titanium backup.
I loaded babystep.zip onto my sdcard and flashed using Clockwork. Install was successful, but when I rebooted the phone it hangs on the Samsung loading screen. I tried reflashing, to no avail. I also tried step2.zip, another kernel version of baked snack, no go.
So then I tried reflashing my backup from clockwork recovery. That didn't work either, same problem, just hangs on the Samsung screen.
Does anybody have any advice, or did I brick my phone and now I have to do a factory reset using odin?
anti09 said:
Hey guys, new rooter here, hopefully somebody can help me out...
So I was running stock DL18 Eclair, decided to flash Baked Snack 1.6 (babystep.zip).
I rooted, installed Clockwork Recovery, made a backup and everything, as well as backed up with Titanium backup.
I loaded babystep.zip onto my sdcard and flashed using Clockwork. Install was successful, but when I rebooted the phone it hangs on the Samsung loading screen. I tried reflashing, to no avail. I also tried step2.zip, another kernel version of baked snack, no go.
So then I tried reflashing my backup from clockwork recovery. That didn't work either, same problem, just hangs on the Samsung screen.
Does anybody have any advice, or did I brick my phone and now I have to do a factory reset using odin?
Click to expand...
Click to collapse
How long did you give it on the first boot? Sometimes the first bootup takes a really long time.
Worst case, just do an odin restore with DI18 and then restore with your clockwork backup. Would take like 15 min and you'd be right back to where you were.
How long is really long? I probably gave it a good 5 minutes before restarting.
And I was on my way to doing a factory reset with odin now... where do I insert the .pit into odin? I don't see a pit section
I'm not too familiar with Baked Snack.. is that the kernel file or the rom that you were flashing? Or does it only need the one .zip file?
Sent from my SPH-D700 using XDA App
Baked Snack is a kernel only, it uses the stock Dl18 rom.
Honestly by this point I'm just trying to do a factory restore, cause after re-flashing with my clockwork recovery (which also didn't work) I can't even access my sdcard anymore.
Odin recognizes my phone but I don't see anywhere to insert the .pit file... I'm using Odin Multi Downloader 4.3, is that the right program?
Edit: If somebody felt like helping me over AIM, it would be much appreciated! S/n is anticrombie0909
I dont know what you are using but u should be usind odin3 v1.61 and the pit file goes right above the pda but you dont need the pit file. Just use the tar file and make sure its the approp. Size. Depending on what stock rom you downloaded it should at least be 255mb. And insert the rom in pda section and make sure only reboot is the only thing checked.
Sent from my Evo killer!
Can someone please link me to that version of odin? And why don't I need the .pit file? Finally, do I need to reflash the entire ROM, or only the kernel?
Odin MultiDownloader is an older tool than Odin3 that really isn't meant to be used with our phones. Use Odin3 1.61.
And you should be able to get by without a pit as long as your partitions are still properly partitioned.
Ok, so I managed to do a factory restore using odin, back to stock.
I tried reflashing baked snack again, but it looks like it's hanging on the Samsung screen again... here's exactly what I did, step by step.
1. Wiped my phone, clean Dl18 stock install.
2. Installed Rom Manager, flashed clockworkmod install. Loaded babysteps.zip (the kernel file) onto sdcard.
3. Ran clockwork manager, picked "select file from sdcard," flashed the kernel, which was successful.
4. Went back to clockwork manager's main menu, selected "reboot phone."
Once again, it's hanging on the Samsung loading screen. I've let it sit for about ten minutes now, no change. What am I doing wrong?
You're flashing babysteps, which doesn't work with all phones. Do something a little more mild. Also there is a rom, you know, and the kernel runs better with his custom rom.
Sent from my SPH-D700 using Tapatalk
So should I try something like worksforall.zip? Or should I just go ahead and install the whole bakedsnack1.6 rom + kernel combo? And if I do the latter, is it the same process (load onto sdcard, go to clockworkmod, install and reboot)?
be careful with it. I did works for all and then rebooted to do step 2 and mine hung samsungmobile.com screen. It took me about a week to fix it as i was having checksum errors, odin screwups, driver issues, clockwork problems, boot problems. Any problem that could happen happened to me. Im currently fixed and restoring my nandroid after using odin, im probably gonna wait for a better build and i suggest you do the same, but it would be probably easier for you to fix yours than me to fix mine
So I ended up installing the entire Baked Snack 1.6 kernel + rom, which seems to be working great now. Thanks for your help everyone, this thread can be deleted.
Okay, so I flash the Froyo ROM to my phone and I think I forgot to disable Voodoo... well it was hanging on the SAMSUNG splash and wouldn't ever load, so I tried to restore a previous backup using Clockwork... and now it only boots into stock recovery mode. I tried returning to stock, and now it only boots into stock recovery without even booting into CWM.
What do I do?
edit: Nevermind, I flashed CWM back in... I still can't get my phone out of stock recovery looping...
I've also tried wipe data/factory reset plus cache wipe... went into Odin and flashed the stock files using the PIT/PDA and now it still boots into manual mode... even after restoring CWM and flashing my restores.
At this point, forget about your backups. Especially if they were Voodoo backups. Flash the DJ05 or DL09 Odin stock, get the green CWM update.zip on there and then flash DL30 via CWM.
I'm not sure if I have the DL09 Odin stock... I'll have to get those and give it a try.
DeezNotes said:
At this point, forget about your backups. Especially if they were Voodoo backups. Flash the DJ05 or DL09 Odin stock, get the green CWM update.zip on there and then flash DL30 via CWM.
Click to expand...
Click to collapse
Yeah if you didn't back up with green cwm, probably going to have to get red back eventually, then you'll be able to restore any old back ups
Sent from my Eris using XDA App
Okay, I went to the Odin Restore files thread to get my restore files, so those are the ones I used. I'm not sure where to get the others, so I'll walk you through what I did.
1) Followed tutorial to return to Verizon stock.
2) Reboot phone, does not boot into anything but manual mode.
3) Flash CWM to access CWM.
4) ???
Okay, so new error. I found the stock DL09 Odin files and flashed them. Now my phone endlessly reboots with the "Wipe Data" over and over again. I need my phone working by tomorrow so that I can call my job as there's a blizzard here and I won't be able to get in.
I finally got it. I used Adryn's flash back to DI01 in order to restore my phone. Thanks anyway all.
Where did you find that stock restore for odin, I have the same issue.
im having same issue...any help would be great
I was getting this issue the other day. The only way I could fix it was as suggested... DJ05 flash with odin.
I was previously running a full stock phone, unrooted, with the OTA DL07 update. I flashed the stock DL30 rom leak, by flashing CWMRecovery_DJ05_DL09.tar.md5 via odin, then applying update.zip (not the new one). Once in clockwork recover, I tried to apply the new_cwm.zip, but I got large zoomed in blue text that I couldn't read, and nothing really happened.
After a few reboots, I learned that I the DL09 I got OTA, somehow restores the recover, and I have to use odin every time before I plan on getting into clockwork. Anyways, I eventually just decided to ignore the new_cwm.zip, and just flash the DL30.zip via the old cwm. It worked, I ran DL30 for a few days, but today I wanted to wipe battery stats, but I can't get back into cwm.
I can't flash CWMRecovery_DJ05_DL09.tar.md5 anymore, it fails, and then my phone won't boot, until I flash Stock-i500-VZW-Recovery.tar.md5, upon which I can boot my phone up normally.
So my question is, how can I get cwm back? And should I use the old update.zip I've been using, or should I replace it with the new_cwm.zip?
Download ROM Manager from the market, install cwm through it. Then reboot into recovery (do a nandroid backup), Wipe data, install DL30 rom, reboot, go back into cwm, flash the new_cwm.
Ok .. I am not sure if this is the right area or not .. but I have been tring to install the DL30 onto my fascinate but it will go to a blue screen and when I choose update.zip it will tell me failed to
open /sdcard/update.zip no such file or directory?
Signature verification failed installation aborted .. any ideas how to make this work?
Thanks for you help in advance
kscheryl said:
Ok .. I am not sure if this is the right area or not .. but I have been tring to install the DL30 onto my fascinate but it will go to a blue screen and when I choose update.zip it will tell me failed to
open /sdcard/update.zip no such file or directory?
Signature verification failed installation aborted .. any ideas how to make this work?
Thanks for you help in advance
Click to expand...
Click to collapse
download rom manager from the market and use it to install cwm
thefunkbot said:
Download ROM Manager from the market, install cwm through it. Then reboot into recovery (do a nandroid backup), Wipe data, install DL30 rom, reboot, go back into cwm, flash the new_cwm.
Click to expand...
Click to collapse
Just tried, when I launched ROM Manager, it said Current was 2.5.0.4, Latest was 2.5.1.0. I clicked flash, it downloaded, and Current changed to 2.5.0.4. I clicked reboot into recovery, phone reboots, default recover comes up, starts to apply update.zip, and the signature fails.
Same here ... even when I use rom manager with the CWM it is still coming up with the signature error. It is only going to the blue screen not the green screen but it is also not allowing me to install the update either. Help!
Dunno why so many folks are having issues...but make sure you have root and dj05 or dl09. Download rom manager and new_cwm. Flash recovery while selecting your phone in rom manager. Then reboot in recovery from rom manager install new dl30 and then new_cwm. If you cant reboot from rom manager, do it manually and select update.zip to get to cwm
Ps...make sure you never had voodoo or it is niw disablef...one of the two.
thefunkbot said:
download rom manager from the market and use it to install cwm
Click to expand...
Click to collapse
That doesnt work to just do it through rom manager when your on dl09... your confusing people by telling them that. To get into cwr you have to flash it with odin, boot into stock recovery, do the update.zip, then boot into cwr. You cant let the phone boot into the os until you get to cwr and do all your flashing. Dl09 has something built in that makes it not work the way it used to. What you are saying is the original instructions for dl30, but have since been modified like i said... its somewhere in this forum,
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Right, the problem is that I'm already running DL30, and I can't flash the clockwork recovery for dl09/dj05 via odin, it fails and my phone won't boot until I flash the stock recovery via odin. Anything I try through rom manager simply fails the signature verification.
Sent from my SCH-I500 using XDA App
I have the exact same problem as OP, I tried to flash DL30.zip and the new_cwm.zip. DL30.zip flashed like a charm, but for some reason after i flashed new_cwm.zip, I'm not able to get into cwm at all, it just sends me to stock recovery.
Heres the thing, whether your on dl09 or dl30 (which is still dl09) you cant let the phone reach the os between flashing cw and applying update.zip, and then booting into cwr. So the only way is to flash cw via odin, stock recovery update.zip, cwr. Another way would be to get back to dj05, this shouldnt have the built in recovery reset, and dl30 is compatible with it.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
ziggy484 said:
Heres the thing, whether your on dl09 or dl30 (which is still dl09) you cant let the phone reach the os between flashing cw and applying update.zip, and then booting into cwr. So the only way is to flash cw via odin, stock recovery update.zip, cwr. Another way would be to get back to dj05, this shouldnt have the built in recovery reset, and dl30 is compatible with it.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Click to expand...
Click to collapse
What you are trying to say is if I flash the DL09 cwm via ODIN to my DL30, I would be able to get into cwm?
Avelnan said:
What you are trying to say is if I flash the DL09 cwm via ODIN to my DL30, I would be able to get into cwm?
Click to expand...
Click to collapse
No... first of all you need the new cw that works with froyo if you plan on using it while on froyo, then you still have to follow the steps in my previous post because your still dl09. If you are on froyo why do you need cw right now?
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
ziggy484 said:
No... first of all you need the new cw that works with froyo if you plan on using it while on froyo, then you still have to follow the steps in my previous post because your still dl09. If you are on froyo why do you need cw right now?
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Click to expand...
Click to collapse
Because after I flashed DL30 all my apps were still there, even though I strictly remember wiping my phone clean. Also I want to flash Blackhole 4.0.1 rom. I just want those apps gone because they seem to cause problems, apparently after wiping EVERYTHING is still there
Avelnan said:
Because after I flashed DL30 all my apps were still there, even though I strictly remember wiping my phone clean. Also I want to flash Blackhole 4.0.1 rom. I just want those apps gone because they seem to cause problems, apparently after wiping EVERYTHING is still there
Click to expand...
Click to collapse
You could just uninstall the apps through task manager... and then you need the new cwm to flash more roms, again follow the steps i previously posted to get to cwr
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
ziggy484 said:
You could just uninstall the apps through task manager... and then you need the new cwm to flash more roms, again follow the steps i previously posted to get to cwr
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Click to expand...
Click to collapse
So I DO have to flash the DL09 CWM via ODIN. Where can I get this file, and ODIN?
Avelnan said:
So I DO have to flash the DL09 CWM via ODIN. Where can I get this file, and ODIN?
Click to expand...
Click to collapse
search this site for both, there are links everywhere
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
ziggy484 said:
search this site for both, there are links everywhere
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
Click to expand...
Click to collapse
That's what I tried to do before I even started this thread, as I said in my original post. The DL09 cwm will not flash via oden. It fails. And then my phone just shows a computer/phone icon, and refuses to boot.
I have to flash the stock recovery via odin to get my phone working again.
And the reason I need cwm if i'm already running DL30, is twofold. I'd like to switch roms, AND I need to wipe my battery stats.
Dewmgaze said:
That's what I tried to do before I even started this thread, as I said in my original post. The DL09 cwm will not flash via oden. It fails. And then my phone just shows a computer/phone icon, and refuses to boot.
I have to flash the stock recovery via odin to get my phone working again.
And the reason I need cwm if i'm already running DL30, is twofold. I'd like to switch roms, AND I need to wipe my battery stats.
Click to expand...
Click to collapse
Same here bro.
Dewmgaze said:
That's what I tried to do before I even started this thread, as I said in my original post. The DL09 cwm will not flash via oden. It fails. And then my phone just shows a computer/phone icon, and refuses to boot.
I have to flash the stock recovery via odin to get my phone working again.
And the reason I need cwm if i'm already running DL30, is twofold. I'd like to switch roms, AND I need to wipe my battery stats.
Click to expand...
Click to collapse
Have you tried getting to dl09 via odin before flashing the dl09 cw? And once you get to dl30 you need the new cw to do anymore flashing while on froyo. try flashing stock dl09 (not di01) then flash dl09 cw, then stock recovery update zip, then flash dl30, then flash new cw, then reboot. Do one after the other without booting into the os at all. Once your on froyo you still wont be able to just hold the buttons and get to cw i dont think... you may have to do it the hard way like i just explained.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
[RED-CWM] (not orange)
Alright sick of scanning 3 different threads trying to help people with the new Clockwork manager I decided to write up this guide. This was tested from stock, I flashed back to stock to test both these methods, and they should work for everyone.
Stock versions tested: DI01 (stock), DJ05 (stock), odin method works flawlessly on these versions. cwm was not replaced by sammy kernel.
Stock DL09 will remove cwm on reboot, install a different kernel adryn's should work, pick your poison here: http://forum.xda-developers.com/showthread.php?t=915709 flashed cwm via odin. install kernel, then rebooted, if you get stock recovery flash via odin one more time.
Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, http://dl.dropbox.com/u/2056318/update.zip on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)
To get to stock use adrynalyne's DI01 package get it here: http://forum.xda-developers.com/showthread.php?t=867648 flash via odin.
First I would like to thank jt1134 for fixing up the new cwm get your perferred version here: http://forum.xda-developers.com/showthread.php?t=942021
Odin method (preferred method stock users do this one!)
1. Alright let’s do this, head over to jt’s original post and download the cwm-recovery-ALL odin:
2. Plug phone into PC and turn off phone
3. Pull battery in phone and then press the down volume button
4. Open odin on PC and press PDA load cwm-recovery-ALL.tar, DON’T MESS WITH ANY OTHER SETTING! Then hit the start button.
5. Boot into recovery (cwm) do this by holding both volume keys plus the power button till you see Samsung screen, you can let go then.
6. Congrats your done now install your custom roms, kernels, radios, and other various things!
Clockwork manager method (only if you have cwm installed already)
1. Copy new cwm-recovery-ALL.zip to root of SD card. (do not need to rename!)
2. Boot into recovery
3. Choose install zip from sdcard
4. Choose cwm-recovery-ALL.zip
5. Reboot your phone and delete update.zip from root of SD card, and recovery-update.zip from clockworkmod folder.
The cwm should be red, and should say voodoo no matter if you have a voodoo kernel or not.
Rom manager will not boot your phone to recovery, install a new shutdown menu that includes boot to recovery or do a manual boot to recovery.
The new clockwork manager installs to the boot partition of the phone that's why you no longer need the update.zip file. Do not flash the cwm from Rom manager, it’s not needed folks, and will put your phone into an endless boot. The cwm jt gave us is customized for our phones.
Post your questions here I will be happy to answer them.
Below I attacked the clockwork manager files, plus odin3 v1.3 but visit jt's OP and give him a thanks, I'm just the translator, hes got plenty of other crap to do rather than test this out.
I am not responsible for any bricked, broken, or abducted phones.
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
vlucchetti said:
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
Click to expand...
Click to collapse
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Takafiji said:
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Click to expand...
Click to collapse
Seriously thinking of deleting ROM Manager altogether. I did dl Adryn's revised ROM Mgr but may switch to doing everything through cwm.
I think the slight delay after the double samsung flash is the program working through blue in the background so it jumps right to red afterward.
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
lfrench0 said:
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
no prob thats what we're here for.
any custom kernel built for dj09 will work. only use a kernel for your raidio/rom version ie: dI01, dj05, dj09, dl30, ebo1 etc...
Hey Takafiji,
I posted a similar thread over at Android Central about the same time as yours here at xda. I discovered this ability to boot directly to red cwm, and I put together the how-to thread and everything was great until I booted to recovery one time and saw stock blue (2e) recovery. I played around with different options, but couldn't completely get rid of blue recovery. I decided to do some research in jt1134's thread and saw the link to yours and read everything here. I have tried every method in your thread and jt1134's thread and I keep running into the same problem. I can install the new cwm just fine and I can keep booting directly into red cwm just fine until.........I flash a new ROM. I can flash themes, patches, add-ons no problem, still able to boot to red cwm. As soon as I flash a new ROM, I boot to stock blue recovery. The only ROM I have been flashing is Adrynalyne's superclean 2.4. I read in jt1134's post that flashing a stock kernel will revert you back to stock blue recovery. The kernel in Adrynalyne's sc 2.4 is the farthest from stock we can currently get in nonvoodoo EB01. My guess is we will not be able to boot directly to the new red cwm on nonvoodoo until the devs get their hands on the source code and we get some custom nonvoodoo kernels. Any thoughts? Thanks
landshark68 said:
Hey Takafiji, Any thoughts? Thanks
Click to expand...
Click to collapse
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Takafiji said:
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Click to expand...
Click to collapse
I got rid of Rom Manager as soon as we got the long press power button menu with recovery in it. The only ways I boot to recovery are long press power and holding volume down, volume up, and power buttons.
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Takafiji said:
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Click to expand...
Click to collapse
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
landshark68 said:
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
Click to expand...
Click to collapse
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Takafiji said:
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Click to expand...
Click to collapse
No problem. I'm just going to keep going through blue recovery to get to red cwm until we get some custom nonvoodoo kernels. I updated my OP to advise everyone there on nonvoodoo to put update.zip back on the root of their sd card and do the same for now. Thanks again for the brainstorming and ideas.
EDIT- Also to let you know, yes I already tried flashing back to DI01 then to EB01. We are definitely thinking along the same lines.
Well now I'm totally gorked up. I followed Zacisblack's method with your addition of doing the ODIN install first. Now when I get blue recovery and hit apply sdcard:update.zip I go to green cwm. Trying to figure out a solution to that now.
EDIT - fixed that problem. Fortunately I still had a copy of the cwm_froyo.tar
I also have the same issue when flashing a new rom. It always goes to blue recovery.What I have to do every time is in blue cwm go to apply sdcard/update.zip which gets me in green cwm. Then I go to choose zip and scroll down to clockwork and choose cwm-recovery-all and flash it again then scroll down to update.zip and flash it then i go to applysdcard/update.zip and flash that then i reboot. Then next time i boot into recovery it always goes straight to red cwm. Sounds like a pain (and sometimes it is) but in reality it only takes like 5 minutes. I wish i didn't have to do that every time i flash a new rom but thats just part of my routine now as its what works for me.
I might not have to do all of those to get back to red but thats the way i originally got red cwm on my phone from a great write up on jt's thread (sorry but don't remember who did the write up). Maybe I'll experiment with just flashing one of those zip's next time i flash a rom to see if there's a faster way.
But I would really like it if there was a way to just always go to red cwm with a new rom instead of going thru all that.
Fantastic tutorial! Just what I was looking for! Thanks a million!!
Thanks Takafiji! I had just installed the Superclean v2.6 non voodoo and got the stock blue (2e) recovery as well. I tried to apply the update.zip and it took me to orange. I read your original post and it worked wonderfully!
Takafiji Quote from OP:
"Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, <drop box link to update.zip> on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)"
...now, if I could just figure out why Google Voice can't seem to find my contacts, i.e. voice command "Call Mark Davis", nothing found and defaults to looking on the web.
My phone won't even update the app. When I try it d/l's, starts then aborts saying it isn't properly signed. Guess I'll stay with Adrynalyne's modified one for now.
I used ODIN to flash the new-CWM, but it always seems to boot into blue recovery. Using update.zip gets me into green, which seems to work fine for flashing roms. I've occasionally seen red recovery, but when using update.zip takes me right back to green.
Am I doing anything wrong here?
Thanks for the write-up I flashed recovery with ODIN
In read recovery and working great
again THANKS for the writeup