Related
Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.
Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.
CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.
Thanks given.
Do you know of any method I can do to fix this
You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.
You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.
I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.
Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.
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.
I gained root access through superoneclick gingerbreak. It gave me the superuser app and i downloaded rom manager but whenever i try to get to clockwork recovery mode it keeps going to samsung recovery. No matter how many times I hit re-install packages it goes back to the samsung recovery. What did I do wrong? Should I have gained root another way? Should I try to flash back to 2.1? Please help I'm so frustrated.
first off dont use gingerbreak. Just odin back to stock and then root by installing the update package twice and after twice ur recovery should turn blue to green.
here follow this, use the eclair root guide:
http://forum.xda-developers.com/showthread.php?p=9375927
Rsuave419 said:
I gained root access through superoneclick gingerbreak. It gave me the superuser app and i downloaded rom manager but whenever i try to get to clockwork recovery mode it keeps going to samsung recovery. No matter how many times I hit re-install packages it goes back to the samsung recovery. What did I do wrong? Should I have gained root another way? Should I try to flash back to 2.1? Please help I'm so frustrated.
Click to expand...
Click to collapse
no modded 3e recovery..so it will keep going to Stock recovery. You need to do what movie said or flash a voodoo kernel or flash a modded 3e recovery.
Interestingly enough I have the same problem, 100% rooted, super user access no issue, busy box installed, root manager installed.
I upgraded the 2.1 to 2.2 from the kies mini software.
I have been doing a ton of reading and would like to start flashing roms, etc etc.
Through titanium backup, I have un-installed a large mount of apps and have not suffered any problems as of yet, but would like to try some custom roms.
My question is, since I uninstalled alot of things, only apps that are bloatware, and since I can't get my clockwork recovery console to take affect, do I have to follow post #2?
Is this link the right one taken out of the link from post #2
http://forum.xda-developers.com/showthread.php?t=1047087
Is this the final and correct link, since I do not store data on my phone, and all contacts are on my sim card, and really haven't done any customizations to anything really, can I just odin back and not back anything up? All I use my phone for is calls, txt's and internet, I don't bookmark anything, I don't save txts and call logs mean nothing to me?
I assume I will have to re-root my phone again and do the same procedures, etc etc.
Also as a side note, I am a minimalist type of person, that's why I use linux at home, no windows of any kind (I'll do this procedure at work). Any roms out there that can handle my needs of simply calls, txt'ing and internet without all the other stuff? I don't use GPS, I don't facebook or social network, I don't play games on my phone. I do need however, the use of the camera and video recorder.
Thanks.
I would just follow my advice and odin back to stock its really easy and safe to do. Well if the only apps u have left are bloatware and u dont save anything else i guess u wont need to back anything up before odin. Well the thing its alot easier to root 2.1 then 2.2.
Once ur at 2.1 just do the root process of installing update package twice and after twice ur recovery will turn from blue to green.
follow this guide
http://forum.xda-developers.com/showthread.php?p=9375927
the eclair guide
heres the steps for download mode just in case:
power off phone
pull out battery
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
So, is this the right link from the guide you posted, it's amazing, I read so many things today that It's easy to get a little well, brain farty, ya know.
http://forum.xda-developers.com/showthread.php?t=1047087
Also, I have the kies mini drivers installed, that's how I updated from 2.1 to 2.2 so I assume those will work fine?
BTW, this is the coolest community, props to all involved!!!
Now, I edited my post I think while you were replying, any rom suggestions for a simple user who likes minimal applications but just a well running phone that's not clogged to the gills with stuff?
good noob friendly rom is bionix 1.3.1!
movieaddict said:
good noob friendly rom is bionix 1.3.1!
Click to expand...
Click to collapse
Yep, that seems to be the consensus, thank you
Guys,
A huge thanks, odin'd back to 2.1, rooted, removed the bloatware I didn't want, gonna make a nandroid back, then proceed on to bionix.
I can understand how first time users can get nervous but once done, the process really is not that hard, just takes patience and making sure everything is prep'd before doing so.
I hope I can now help others if you guys don't beat me to it first
My only question is this: when I create my nandroid backup, where does it go and do I need to save it somewhere just in case like a usb key or something along those lines or does it reside on the phone. Only asking cause I have not yet done this step
U can always make a extra backup and store them on ur ext sd
Sent from my SGH-T959 using XDA Premium App
Okay, so I assume the backup, made from rom manager "backup current rom" gets stored to the internal memory on the phone?
Any special settings or it just does it's thing, should be smaller than normal as I removed quite a bit of junk and stuff.
i did what you said and i still cant get into clockwork recovery screen! i went back to stock rom, reinstalled packages twice and i still have samsung recovery. i know i have root because i get the super user asking me to give clockwork root access!
So I assume you odin'd back to 2.1, rooted have installed titanimum backup and busy box, rom manager, tapped the flash clockworkmod recovery, then "reboot in recovery" choose update. I rebooted via the rom manager menu, not via the phone itself. I had to update twice immediately, didn't reboot and do it again. I saw it installing and it kinda hung, then used the volume down to update again, and was completed.
Also after installing titanium there was an update for super user, which I also installed as well. Did you do this? Not sure if it has any bearing but thought it was worth mentioning.
It worked seamlessly for me, I had to update twice, then purple turned to green and all is well.
Can you post your steps you took to get back to 2.1, how you rooted, etc etc?
It's kinda fresh in my mind as I only did it about 2 hours ago.
my screw up after i flashed clockwork and rebooted i didnt apply package. all is good now. thx for all the info!
Anytime, I found the process to be quite interesting and taught me alot and also removed my fear of installing new roms and such.
Make sure to create your backup through rom manager. When you do, it will reboot into clockwordrecovery and show you the progress, didn't take that long for mine but I removed alot of nonesense from 2.1. This will be your emergency fall back, you might know this already but just making sure, as I am quite a noob at this point ROFL!
Enjoy
ps - I still can't decide on a new rom, I'm so fussy about stuff, ugh.
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?