I recently bought a fascinate which is currently running the stock DI01 ware. I have rooted the device using ADB (from cyanogenmod wiki) and have installed clockworkmod recovery using ADB (from the *nix directions here http://forum.xda-developers.com/showthread.php?t=788099).
From my understanding to install DJ05 I need to:
1. Install Heimdall and issue this command to flash dj05 radio while fascinate is in download mode.
Code:
heimdall flash --verbose --modem modem.bin
2. In clockworkmod recovery: wipe data/factory reset, wipe cache partition, then wipe dalvik cache under the advanced options.
3. In clockworkmod recovery: Flash dj05 rom and kernel. I am planning to install jt's super clean dj05 v0.9 and jt's dj05 voodoo5 kernel.
I have scraped up all this info from various posts around this forum and some others and was wondering if this is the correct method. Particularly I am uncertain of using Heimdall to flash dj05 radio. I am also weary of wiping the data and caches.
Any input on these issues would be wonderful and thanks for all the great help this forum has already provided for me.
Im guessing you have access to a computer, So why not use Odin? It will make your life much simpler
There are a few roll up sticky threads that will guide your way to dj05 awesomeness.
ps next time asking questions use the general section.
Well I'm using linux so Odin isn't an option for me, from what I have read heimdall should be capable of anything Odin is. I already have heimdall installed and just wanted confirmation of the heimdall command to flash the radio, and I am also unsure of wiping the dalvik cache.
oh sorry buddy.... I wished I could answer that for you. Just be patient and I'm sure someone techy enough will be able to answer your question.
Good luck.
I guess my problem was that I couldn't get my computer to detect my fascinate in download mode, so I couldn't get heimdall to work right. However, instead of holding the button combo to get into download mode, I used adb to reboot the phone into download mode which ended up working (thanks to some threads in I9000).
After fixing a force close menu popup loop by clearing the caches again, I think I successfully installed jt's super clean rom and voodoo kernel. I have to say that I am loving it, it's very dicey. Definitely loving not having 3 pages of pre-installed apps that can't be removed, and I also noticed the maps app shows me exactly at my house instead of a half mile down the road. Thanks again to this forum and sorry I posted this in the wrong section.
Related
I flashed my fascinate back to stock with odin and now when i boot up i just get a ton of force closes and they keep coming up and wont let me continue. Any help would be appreciated. Thanks
You should have posted this in the General section.
Now, what did you flash to stock from? Were you using voodoo beforehand?
IME, FC hell after an odin restore is due to the PIT file not being used.
Open Odin
Go back into Download Mode on your phone.
Hit the PIT button and select the PIT file you downloaded from the OP of the odin topic.
Hit the PDA button and select the "system" tar you downloaded from teh OP of the odin topic.
Hit Start.
Wait for it to finish (system takes a bit).
Reboot into recovery and wipe data/cache.
Sorry for posting in the wrong section and i was on vodoo and removed it and flashed a differernt rom was most recently on the zinc rom. i also tried to re run odin with pit and still force closeing. thanks for the help so far
swerve12 said:
Sorry for posting in the wrong section and i was on vodoo and removed it and flashed a differernt rom was most recently on the zinc rom. i also tried to re run odin with pit and still force closeing. thanks for the help so far
Click to expand...
Click to collapse
Only other thing I can think of off the top of my head is wiping data/cache from both Stock and CWM recovery. You could also try wiping dalvik cache (CWM-advanced) or nuking the contents of dbdata...but that requires either adb or root access and a phone that isn't constantly fc'ing on you.
Have you tried restoring a nandroid backup?
If he was on vodoo then he write have to flash back to a vodoo kernel and then make the disable lagfix folder and reboot. Then revert to stock kernel right?
Sent from my SCH-I500 using XDA App
I think that a good question here would be whether or not you had voodoo installed. Tell us what you are/where running so we can diagnose and help u work through the problem. No worries though, this can be fixed.
Sent from my SCH-I500 using XDA App
ok so orignally flashed vodoo and when it was first put out then i (what i thought was) removed vodoo and flashed the Zinc V2.1.3 Fascinate Rom then i went from that to Blackhole Version 1.2 Rom after i flashed to blackhole and before i did any restore of apps i had 0 internal mem left and couldnt figure out why so i decieded to run odin to put the phone back to 100% stock and now all fc's
I had the same issue today, to gix it I booted to recovery and did "factory reset" it wiped the data and no issues since. I have also changed to the atupid fast kernel instead of voodoo. Hope it helps. I suggest you try it...
Sent from my fascinating fascinate
Ive been working on putting Dj05 and super clean on my fascinate tonight and followed some of the basic steps that i have found around here. started with rooting, cwm and flashed dj05 modem with odin.
Then when i restarted it booted into stock recovery and the dj05stock.zip that i renamed update.zip gave me an error. beyond that i got stuck in a force close loop. I then followed instructions on flashing factory setting back onto the phone, and when i rebooted i still got force close loop, but was able to get to settings>privacy>factory data reset... and no more force close now.
However... under phone info baseband version says dj05 but build number says dh12... im a bit of a noob at this and im not sure where im at in this process and where i should go from here. any help is greatly appreciated!! Thanks in advance!
Edit: to make things more fun, apparently the texts i send out are showing up blank on the receivers end...
Why did you rename the dj05 file to update.zip? Update.zip is your CWM file, never mess with that. You will need to reflash CWM, and then you can flash the dj05 file from within CWM
Edit: also, this kind if thread should be posted in the General section, not Development.
I will see if i can help.
First you should not have renamed to update zip. The update zip is what gets you into recovery.
Since you did the modem already you just need to flash, through recovery, you dj05 kernel, then your super clean rom.
Somehow you will need to rename your file back to its original name and leave the original update zip in place so you can get to recovery to flash the other files.
I hope this helps.
Sent from my stupidfast fascinate through xda app.
SMS and probably more are now broken because you have only flashed the modem and nothing else. You need to finish with the kernal and ROM
Thanks for the replies, I changed dj05 to update.zip as i was following a guide i found... i found it a bit odd myself.
Once in stock recovery, select "apply: update.zip" and this will take you into cwm. Then in cwm select "install from sd card", find your dj05 update and select it
Awesome i got cwm installed properly and got dj05 on... now same process in cwm for super clean?
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!
[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
Yes i have already searched the forums but there are no instructions to install Overcome v1.1.3. can anyone guide me ?
samsung-tab said:
Yes i have already searched the forums but there are no instructions to install Overcome v1.1.3. can anyone guide me ?
Click to expand...
Click to collapse
If you have already read the Overcome thread there is instructions how to install it. Thot its messy in the 1st post. Hehe
In order to install the rom. You can use clockworkmod or odin to install.
1) CWM is to be install into your tab & flash the rom via in recovery mode. The rom is stall inside your sdcard(the removable)
2) For Odin, its an app on your computer. You flash the rom via odin from your computer with your tab in usb connection (in debug mode)
Personally, I followed these Instructions here: http://www.droid-den.com/phone-guides/phone-guide-install-custom-modaco-rom-and-kernel-on-samsung-galaxy-tab-guide to install Modaco Kernel with ext4 conversion and CWM, and simply replaced the Modaco Rom in the instructions with Overcome v1.1.3 full. Worked a treat. With the new Overcome v1.2.0, just use the full install zip (don't forget to wipe everything including dalvik cache in clockwork, and don't forget to make backups!) and you will get the Overcome Kernel aswell, which is sweet.
All of this will get you upgraded to having CWM, ext4 Filesystem, and the Rom.
I would also suggest doing a RotoBackup first, always good to have a backup of original software etc.
I started off by flashing the euro 1.4GHz OC kernel with Heimdall which included Clockwork recovery, it seemed the safest option as opposed to using the bootstrap off of the market. Then flashed overcome 1.1.3 via clockwork.
any link for Overcome v1.1.3 download ?
Just get 1.2.1. Its the latest and greatest.
many thanks to all of you didnt knew too easy
Can Overcome be installed on a Korean Tab? Model number SHW-M180S?
Thanks for any help!!!
corodius said:
With the new Overcome v1.2.0, just use the full install zip (don't forget to wipe everything including dalvik cache in clockwork, and don't forget to make backups!) and you will get the Overcome Kernel aswell, which is sweet.
Click to expand...
Click to collapse
If you are coming from 1.1.x then IIRC you can just use the upgrade zip rather than the full wipe zip. I did this last night and it is fine.