Hey I found a wonderful .tar file that will help anyone trying to get to EB01. You can go from any version with root and CWM included. Hope this helps.
http://www.droidforums.net/forum/sa...roms-w-root-new-clockwork-updated-2-11-a.html
I'm just the messenger. I did nothing for this except find it. Didn't see this around here....hopefully I don't get scolded.
This seems fairly solid. I'm already up to the newest version of SuperClean (or else I would use this), but I'm thinking I'll use this to get my friend's SGS up to speed. Can't believe This guy's got an Odin file for 3 different EB01 builds. That's pretty awesome.
I've been rocking his stock deodexed Odin for a couple of days now. Great, easy package.
Of course I would see this after going back to DL09 then back up to EB01 the "long way" and setting everything back up. lol Thanks for the link. Should save me a lot of time in the future.
I went for the stock version for my first try with eb01, but might try the others soon. I also was surprised there was no mention of this odin option anywhere here.
I'm thinking of going with the deodexed version but if I do that, does that mean all my apps have to be deodexed in order to install them? I'm absolutely ignorant about it.
This is a good way to fix the DBData issue that a lot of us are experiencing.
I just got a warranty replacement today so finding this made everything so easy, thank you so much
Sent from my SCH-I500 using XDA App
Worked great. Very easy way to install froyo.
Yea I agree it's so simple. Hopefully more people wanting froyo see this. Go thank this dude!
Yeah this was great. No need to transfer the rom to the sd card and use cwm. Very streamlined and the deodexed rom runs fantastic (just had to remove a few extra items, like DRM stuff)
i keep getting an error 0 transfer failed or something like that any ideas?
<osm> all threads completed. ( succeed 0/ failed 0)
is the error i get
Thanks for this life saver!
Rav try re-downloading it...it's possible your file is. corrupt.
i did that still same error, only thing i can think of is i was using a different cable than what came with the phone, going to try it again with the factor cable.
Trying to download via my phone. Are the links dead? Also I'm thinking it would be easy to replace sc 2.1 with 2.4 and future versions in the package?
Sent from my Samsung Fascinate using XDA App
I ran the deodexed version and then restored from titanium backup. Every thing went very smoothly. But I was getting a lot of force closes until I cleared the cache.
I also got rid of the Included swype and installed the swype beta which works much better.
The all in one package is about as ready as it gets.
Sent from my SCH-I500 using XDA App
so i got the update done and everything installed now my problem is i have no internet says 3g is on but i get connections errors on any thing like FB or words with friends.
any reason why it would just all the sudden stop working
Does this still have widgets and touchwiz like in the dl30 Rom?
Sent from my SCH-I500 using XDA App
Related
For the past few weeks Ive been getting error message when using Clockwork Mod Rom Manager, under 'Download ROM" "Error Occured while processing the ROM List!" when trying to download a ROM under SonofSkywalker3. Im running Eugene's Ginger Clone now but also had that problem under NeroV3. I was running Macnut R14 a fews weeks ago and it worked fine. So I dont think its the ROM. Anyone else been having that problem? Is there a fix? See attached pic. Thanks.
Are you using voodoo?
Sent from my Nero powered Vibrant
I'm using Voodoo, and getting the same error
Are your trying to flash a rom or mod? If so, why don't your just put the .zip in the root of you're SD card to flash from there with cwr?
I've never used the option that you're trying to use.
Sent from my SGH-T959 using XDA App
Gopena said:
I'm using Voodoo, and getting the same error
Click to expand...
Click to collapse
If you have the recovery option in the power menu use that.
Sent from my Nero powered Vibrant
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
I think you guys are missing the point. Skywalker has a bunch of stuff to download thru rom manager. But its been showing an error for a few weeks. Not sure what's up with it. He uploaded it to rom manager so it could all be in one place.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
I guess this question should be raised to the developer.
Not using Voodoo with Gingerclone but did use it with Nero. Anyways, Voodoo is disabled.
Im not flashing a ROM, but pieces from the ROM. I just want to get some of the goodies that Sonofskywalker has like Widgets and Wallpapers. Skywalker offers Ala Carte options instead of downloading an entire ROM.
I'm having the exact same problem. I been looking everwhere to fix this problem,but so far found nothing. I'm running Axura 2.2.5.7 rom. I'm not sure if its the roms. I odin back to stock and downloaded Skywalker Black hole 1.2 beta and some other goodies download went fine at frist. I trying going back in rom manager to get some more goodies and got an error "Error while processing rom list" I am a rom manager premuim user. Help Please!!!
I have the same problem. Trying to pull up any ROM list will result in the same error.
Sent from my SGH-T959 using XDA App
To Clarify, this feature worked in Nero Beta 3, and Nero V1.
Going to try reinstalling Rom Manager
Running Nero V3 with SBGB and Voodoo
Been having the same issue with Nero v3. And I can confirm that for the first several days of v3 it was working fine, and then it went kuput. I know I'm only adding to list of people looking for a fix, but at the very least want to let the OP know they're not alone with this issue. I don't believe it is ROM specific.
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
quest4fire said:
Thanks SonofSkywalker. Really appreciate it. Love your work. I'm busy right now but hopefully I can find time to do a logcat in a couple days.
Click to expand...
Click to collapse
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
quest4fire said:
Update: I read the logcat and it was showing my Vibrant as a Fascinate in CWM and it there was definitely an error with downloading. So I decided to restore my backups I had of Macnut R14 and Nero to see if I could download your ROM and was unable to, same error message. Then my phone got corrupted because of restoring the backups. I Odin back to stock 2.1 JFD and now I am able to download your ROM in CWM. So I dont think its a CWM issue. Unfortunately I lost my logcat because i had it inside my phone, was using a Logcat app from the market because I was having trouble getting my ADB server starting.
Click to expand...
Click to collapse
sonofskywalker3 said:
I do have a few things i've picked up over the past week, because i'm aware of the problem, but not how to fix it.
1. Some people have reported that by using odin to revert to stock they can then get rom manager working.
2. rom manager does successfully download my manifest, but it errors out while trying to process it.
3. it's nothing wrong with my manifest, because i have changed all the entries for the vibrant over to fascinate and the fascinate reads it fine
4. I have tried contacting koush, but haven't gotten any help.
This info leads me to two possible conclusions:
1. It's a problem with something in some custom roms (including Blackhole) that prevents rom manager from using something it needs to read the javascript on the vibrant
2. It's a problem with the rom manager software, either the version you have, or just on the vibrant in general.
some info that might help me fix this:
1. if anyone can get me a logcat of while the problem happens, i may be able to see what the issue is
2. if someone can tell me the rom manager version, it may be an older one and i can post the latest from the fascinate, which might help.
also i'm going to try to release a 2.0 beta based on JL5 later this week which may or may not fix these issue. and i'm going to continue to hope for help from koush.
Click to expand...
Click to collapse
I'm using Rom Manager 3.0.0.7 and can't get into any roms. Not sure how to get a logcat, but once I figure it out, I will send it your way
I had the same issue and I was able to get Rom Manager working again by performing the following steps:
1) Clear the cache from the Rom Manager app (under Settings/Applications/Manage Applications)
2) From within Rom Manager run "Fix Permissions"
3) Reboot (which you're prompted to do when the "Fix Permissions" step is completed anyway)
This has worked for me twice.
Good Luck
Tried to flash a custom ROM for the 15th time or so, with the same result. E: Can't Symlink /system/bin/su
Failure at line 16
Have researched this error, thought I had it figured out. Obviously not. Feel like an idiot. I never had any problems loading custom ROM's on 2.1.
BTW, I am rooted thru S1Click, have backed up thru nandroid and Titanium, have installed 3e custom recovery, everything I have read I could be doing wrong I have changed. I have tried different makers- Bionix, Axura, Eugene, all with hte same errors, so I know it's not just the ROM file.
What am I doing wrong here?
I don't know.. but let's save everyone the trouble of answering this and let you odin back to stock.
It might be something you flashed etc..
tried that too. tried loading these ROM's right after rooting and adding ROM manager. It's just weird that know one can answer a specific problem like "failure at line 16". Surprised there isn't an answer to look up based on the Line 16 error.
I'm not pointing any fingers, because I don't know the answer either. Just know that if you you give me one of the basic replies, like try ODIN to stock, I've probably tried it.
What are you odining to? I've always had success going to back to jfd. Doesn't seem to be any issues with rooting or rom manager.
Trigger + Overstock = Awesomeness
yep. Odining to jfd.
One thing is that I always install 2.2 via mini-kies before attempting to install custom ROM. Reason being that for whatever reason, the super one click just does not want to install on 2.1. Could that be part of the problem?
Here's what I do and it works every time for me.
1. Odin to jfd
2. Root then install rom manager
3. Flash clockwork recovery
4. Download rom of choice to internal sd
5. Flash rom thru clockwork
6. Enjoy
That has never failed me.
Trigger + Overstock = Awesomeness
Check This Out....Tell me If It Helped You
http://forum.xda-developers.com/showthread.php?t=848737
I did it. FINALLY.
Loaded Simply Honey 2.5, and this thing is FAST and awesome. Such a cool ROM. I was so pumped when it actually worked. Thanks for all the help, guys. And all the great developers that put in hte time and work to make our phones what they should be. Good job, guys.
Glad you got it working. The first flash is pretty awesome.
Trigger + Overstock = Awesomeness
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
This is the safest way and the best way.
Hello, all!
I've purchased a vibrant for my wife over the weekend (i'm on sensation), and have several questions.
The guy i bought it from did a hard-reset supposedly, and said that it reverted it back to the stock android build. Seemed weird, but the first thing i did was update it via kies mini to the froyo build. It's been working fine, except for the camera started messing up last night. Going into black screens, showing "camera failed" errors. It also takes some time (2-3 secs of black screen) to process a picture after it has been taken. I don't remember it doing that on the stock build. I did update it to the latest firmware.
Should i root the phone and flash a different rom? (which rom would you recommend?) A short google search revealed a lot of people having slow-downs after the froyo update.
Appreciate your help!
just to follow-up. wife's been having problems with the music player app hanging, then the phone shut down while she was installing something.... i'm going to wipe everything first to see if it helps any, but will end up rooting it and flashing something else, most likely.
Before rooting make sure you odin back to stock 2.1. That should het rid of the problems
Sent from my SGH-T959 using xda premium
Definitely do what the above poster suggested. Go to the development section and get the AIO toolbox. It has everything you need to get back to stock and get you rooted. If your looking for a good stable rom I'd recommend bi-winning v3. Good luck.
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
RussianBear said:
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
Click to expand...
Click to collapse
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
dseldown said:
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
Click to expand...
Click to collapse
Wow, didn't know this. Will delete kies asap. btw, this rom that i've flashed has a custom kernel (bionix? + voodoo). i did a backup of the stock rom via recovery. do i need to flash the stock kernel first before rolling back to stock?
hereeny said:
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
Click to expand...
Click to collapse
thank you, will check it out!
Project-V is a Great 2.2 ROM, I made a few themes for it too: Blar and WP7 Style
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.