I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
buggzero said:
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
Click to expand...
Click to collapse
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
buggzero said:
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
Click to expand...
Click to collapse
Your welcome and yes, you're completely back to stock and everything is gone. So you should be set. No, both methods work well and do the same. I know adb but still prefer the first method, works all the time is something goes wrong with voodoo or any lagfix.
I wouldn't say it's preferred to prevent those issues because you may still have them either way but its nice to have. You can make a backup with it so if anything goes wrong you have something to fall back on. Just makes things simpler.
Sent from my SGH-T959 using XDA App
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
buggzero said:
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's simple to disable voodoo. When you have voodoo installed you should have a voodoo folder in your internal SD card, if you don't them make one. Put a file called disable-lagfix in there with no extensions. A blank file with that name. Reboot and you'll hear the.process going through of removing voodoo. Then you can flash what ever you like without any problems. If you want voodoo back delete the disable-lagfix file or rename it to enable-lagfix. Simple.
Sent from my SGH-T959 using XDA App
thx for ur sharing...
i hv the same problem, it's fixed now...
Related
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
coasterman927 said:
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
Click to expand...
Click to collapse
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
silow said:
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
Click to expand...
Click to collapse
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
dasunsrule32 said:
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
Click to expand...
Click to collapse
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
Then odin flash this kernel:
http://forum.xda-developers.com/showthread.php?t=733792
If you are wanting a full-on restore to stock, then odin:
http://forum.xda-developers.com/showthread.php?t=734475
Good luck.
Moved to Q&A
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
The lastest release of Clockwork recovery is not a permanent flash. It is kept in an update.zip file on your internal sdcard which can be easily removed.
You can always follow the ODIN steps in the original link you posted. This will return the phone back to the way it was shipped. Note that it doesn't however wipe your internal sdcard.
If you want to keep your data intact flash only the kernel. Using the ODIN method will wipe your data (factory reset, however not your internal sdcard unless you check the repartition option).
If you are a One-Click root/lagfix type of person I wouldn't recommend using ODIN unless you had to resort to it.
post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
Needing some help with 3eRecovery. I understand every thread I've read on how to do these things, but it doesn't work the way everyone says. Explanation below.
____________________________________________
I'm definitely rooted... have superuser and test with Terminal Emulator. su works fine. Even tested root with Titanium Backup. It works.
Trying to install 3e recovery, to get CWM3, to get KA6+voodoo kernel. 3e recovery installer fails root check every time.
From what I've read, if you're already permanently rooted, the modified 3e recovery installer would stop checking for temporary root. This is clearly not the case here. I've even tried running SuperOneClick to shell-root the device, which it succeeds at, but this does not change any results from the 3e recovery installer.
I have even used Odin3 to start from scratch on the machine, taking it all one step at a time, back from the original Eclair ROM+KRNL, Kies upgrade to KA6, SuperOneClick.
oh, and yes, I've tried installing the KA6 stock+voodoo kernel through Odin. Odin says it succeeds, the phone reboots, but there is no difference. I've installed the Voodoo Control app, but it shows that there's no Ext4 conversion. Am I doing something wrong? Is my phone doing something weird?
I really wanna get rid of the rfs system. absolutely hating it. There are two images attached proving root and showing results of 3eRecovery
I'm obviously studying the XDA Vibrant Bible, but here's some other links I'm using:
http://forum.xda-developers.com/showthread.php?t=833423
http://forum.xda-developers.com/showthread.php?t=870480
Did you try reboooting into recovery to see if you have it properly installed?
definitely have... plus it fails at the temp root check, would it do that if the 3eRecovery were installed properly? I'd think it'd fail later.
and yes, I've tried installing CWM3 through Rom Manager a couple of times after attempting the 3eRecovery, and the "install package" choice repeats and repeats and repeats, I never see the CWM Recovery.
Is it telling you there's no more room in /system? Remove a bloat app like Slacker Radio to free up some space if you haven't already. Good luck!
Sent from my rough sketch of a Vibrant on a brick.
no... I saw that message once a while back, before I restored to original krnl and rom, the jfd one I think. but since I did that and started from scratch, this is the first problem I've run into.
Q: if I use the 512 pit file with the KA6+voodoo krnl tar found here (http://forum.xda-developers.com/showthread.php?t=870480) in Odin v.1.7, shouldn't that accomplish the same thing as cracking the recovery and using CWM to load up the zip version? when I try to use the Odin version, nothing changes? is that what you mean when you ask if my /system is full?
I'll remove some apps (i use Slacker) like Ads to Home, T-Mobile TV, etc. I'll let you know if Odin works any better. but I don't anticipate anything changing.
She issue here. CWM won't install, even after a supposed 3e flash.
-bZj
XDAapp
down8 said:
She issue here. CWM won't install, even after a supposed 3e flash.
-bZj
XDAapp
Click to expand...
Click to collapse
except mine won't even let me flash the 3e.
fail.
Did you enable usb debugging?
Sent from my SGH-T959 using XDA App
yep. absolutely.
Lol. I tried replying with just "yes," but there's a ten character minimum to posts. Ha (easily amused here)
Repartition choice in Odin
For others suffering this and other seemingly unfathomable problems with a Galaxy S phone... reset phone to official/full/original ROM+KRNL (JFD in my case) and use the re-partition choice in Odin. after I did that, I rerooted with SuperOneClick, installed a Terminal Emulator, and manually removed some of the bloatware that came with it.
Don't know which one of these fixed it, but the 3eRecovery installer worked after that... I downloaded the ROM Manager again, did the CWM that is included with that, had to click "reinstall packages" twice, but then it worked.
Thanks for the tip Droidificator. Don't know for sure if it's it, but I'm sure it didn't hurt.
___________________________________________________
lol... great irony in all of this is that Kies updated my phone to KB5 instead of KA6, so now I'm looking at using OCLF for the ext2 tools for now.
any advice on where to go from here to have the most efficiency out of this phone from the KB5?
make sure that a current version of busybox is installed. i had an issue with this when i ODIN'd back to stock and re-rooted. good luck with everything!
I have a major question. As of a week ago my phone suddenly began taking 20-30 minutes to boot. I'm not quite sure what caused it but one morning my phone booted to a black screen that only showed my toolbar at the top. After it randomly vibrating over a course of 20-30 minutes it finnaly showed my screen lock and wallpaper. Now it does this every time I boot!
I need to know if there is a way to fix it, for it's not only a nuisance but a safety issue. What if my phone were off and I needed to make an emergency call?
Phone Facts:
*Samsung Vibrant
*Firmware 2.2
*Not rooted, but at one time was
*Clockworkmod installed
The default answer is to use ODIN to get back to JFD... if you have issues THEN, well, let us know.
I have a guide in my signature with the files needed as well, going back to stock.
First, is this a known issue that can be solved with ODIN? Also, if I were to ODIN do I need to delete information on the phone or do I just get the stock files, download ODIN, and flash my phone?
This is not a known issue... which you know, because you searched before posting.
You should move any sensitive/important info to your pc and backup... you should not lose that data, but if you do, now you can't blame me.
Just use odin and the files from the guide.
So the data on my phone currently shouldn't interfere with the flash. Because I remeber hearing somewhere that old data from the android market and GPS can mess with the phone after it is flashed causing the GPS and market possibly to not work properly afterward. Is this correct?
Huh? Just ODIN the dang thing back to JFD already! When you do that, all data is erased except what is on your EXTERNAL SD (although this COULD get wiped, but is SHOULDN'T). Back up data on both your internal and external SD's to your computer that you don't want to lose, then follow s15274n's signature links to his tutorial on how to ODIN back to JFD and FOLLOW IT precisely and you will be fine.
EDIT: And when that works, and you're all back to normal again, don't forget to swing back here and THANK every post you can find by s15274n by clicking the thanks button.
I'll be sure to do that, THANK YOU both of you! Especially you s15274n for your wonderful tutorial. It worked like a charm, now all I have left is to replenish my apps and update my phone to 2.2. THANK YOU!!!!!!! No GPS issues, NO Android Market issues, NO issues at all! T-H-A-N-K Y-O-U!
^ Might I encourage you, BEFORE going to stock 2.2...
Maybe root with the update.zip in the guide and flash a 2.2 based ROM (THAT IS STABLE). Your phone will be better than stock 2.2 and you will have a lot more options.
Your call. Just know your phone would be better on Trigger, Zen or Project V than stock.
EDIT, of course I have a guide on that too
EDIT2, saw your post in the guide... also replied there.
Thanks but I think I'll stick with stock 2.2. However, I'm thinking of installing SetCPU but of course () I have a question before I attempt it. If I were to uninstall setCPU will the speed of my phone go back to original stock settings or will it stay with the custom settings I had set?
It would stay with the stock settings.
Sent from my SGH-T959 using XDA App
If you are rooting and flashing a kernel to overclock, why are you not using a rom?
Voodoo is better than overclocking/poorer battery in my opinion.
Agreed ^
Sent from my SGH-T959 using XDA App
odin to JFD and thy some other ROM
I have this SAME problem.. 20-30 mins to reboot.. and randomly vibrates while booting up. I just opened a thread about how I can unroot 2.2... you know, please help! I didn't do this until I rooted my 2.2 vibrant. Now i have no idea how to unroot.
Did you read the thread? Odin to jfd.
To answer your boot question LaxHoss it is most likely caused by a glitch in the samsung in vibrant. I came upon a list of glitches on the device a few days ago and discovered this issue. If you are using either the "password" or "pin" password locks on your phone and your phone takes a long time to boot then the screen lock is the cause of the boot issue... To correct simply go to:
Settings > Location and security > Set screen lock > (Then choose "pattern" or "none").
This is how I solved the boot issue for me.
However, for your root issue I would suggest to odin to stock and next time you root use "Z4root" or "Superoneclickroot". Just follow s15274n's guide to odin back to stock, it's real easy.
If going back to JFD, strongly encourage using the update.zip in the guide to root... your pc will think superoneclick is a virus. rageagainstthecage has exploits your pc will hate.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737