[Q] Trouble Installing Blackhole 4.2? - Fascinate General

Ok, I'm having troubles flashing blackhole 4.2. I'll start off with where I am.
I'm rooted.
I have already flashed the EB01 modem.
I can also successfully enter the new red cwm.
I have a full working nandroid backup.
So I tried downloading the .zip for the standalone rom from sonofskywalker's post for blackhole 4.2. I placed the .zip on my sd card, but not in a folder. I booted into red. I wiped cache partition, wiped dalvic cache, and cleared data/factory reset. I selected install rom from sd. I then selected the blackhole .zip. It flashed, so I selected reboot system now. It brought up the samsung screen, then went black, then back to samsung logo, and finally back to red cwm. I've tried several times but I keep getting stuck in this boot loop. So I ended up restoring my nandroid .Does anybody have any suggestions? I also tried downloading it from rom manager. Same result. I thought it had something to do with still being on stock kernel. So I tried the standalone version. Is it still a kernel problem? If so could somebody please recommend a kernel to use with blackhole for eb01(preferrably not voodoo, but if it must be done). I also saw jt's bootanimation kernel in rom manager but haven't had the chance to try it yet. Any assistance is greatly appreciated. Again Thanks

You might try downloading again. It sounds like your download may have gotten screwed up. Check the md5 hash
Sent from my SCH-I500 using XDA App

I've tried downloading again from both rom mgr and the blackhole thread. I would check md5 hash but I don't know how or what it is.
Sent from my SCH-I500 using XDA App

Related

Flashed back to stock with odin, now force cloeses... Help Please

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

phone keeps booting back into recovery

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

[Q] Having problems with Baked Snack 1.6

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.

[Q] Fascinate Clockworkmod recovery Help?

Ok, so I rooted my fascinate using super one click root, and everything worked fine. Then I downloaded ROM manager, and went through the setup, selecting Flash ClockworkmMod Recovery as the first step. It says it was successfully flashed, and is showing ClockworkMod 2.5.1.0. The problem is, when I reboot into recovery to do a system backup, It pops up and says "Install from package." Then it trys to install an update, but it's gives me an error and says "failed to verify whole-file signature... installation aborted, and does not give me a backup option. I have tried several times, and can't get it to work right. I'm trying to get it backed up so I can install a ROM. What steps might I be overlooking, and what should I try next?
Thanks,
Anthony
You need to flash CWM with Odin first. See here or here, depending on what version you're on
Check your main area of ur sdcard for the update.zip. If that is there. It may have not downloaded correctly. Another way to get cwm recovery is by flashing it through odin. I did a complete odin restore to stock DL09 this morning. Then flashed the new cwm recovery through odin. Then I installed the proper superuser/busybox zip. Once that was done. I booted up to make sure everything was good. Then, I flashed the new DL30 froyo leak. Everything went perfect. Love having froyo finally! There r a few good threads in the development area.
Sent from my SCH-I500 using XDA App
The update.zip was in the root of my SD card, but it was not installing when I booted into recovery mode. I'm reading through the threads now, trying to figure out how to flash odin.
Ok, I just flashed clockwork with odin, and the phone rebooted. So I'm gonna fire it back up and see what kind of progress we've made.
What are you on? DL09, DJ05, or DI01?
Looks like it worked perfectly. Allowed me full access to the backup and recovery options with no errors. Thanks for all the help. Another step closer to getting off the stock kernel and ROM.
Kevin Gossett said:
What are you on? DL09, DJ05, or DI01?
Click to expand...
Click to collapse
It's on DL09.
Nevermind. I figured that part out. It's backing up now, so it looks like everything is working so far. Got DL09 Superclean running. Thanks again for all the help. I really appreciate it.
JKChad said:
Check your main area of ur sdcard for the update.zip. If that is there. It may have not downloaded correctly. Another way to get cwm recovery is by flashing it through odin. I did a complete odin restore to stock DL09 this morning. Then flashed the new cwm recovery through odin. Then I installed the proper superuser/busybox zip. Once that was done. I booted up to make sure everything was good. Then, I flashed the new DL30 froyo leak. Everything went perfect. Love having froyo finally! There r a few good threads in the development area.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I have a similar issue where after rooting and installing clockwork mod through odin, when I try to flash clockworkmod recovery from rom manager I keep getting "An error occurred while downloading your recovery"
I see that there is no update.zip on my sd card. What can I do to resolve this?

[Q] CM7 Nightlies Not Flashing

There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery

Categories

Resources