Related
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Hahaha I had that problem a few days ago, just flash back to stock with odin. Best to try a different rom....
Sent from my SGH-T959 using XDA App
Starting to think the phone might be bricked. Can't get into recovery mode or download mode. Always immediately comes back to the Vibrant screen. Pulled the battery. Didn't help.
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
DPCerberusBlaze said:
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
Click to expand...
Click to collapse
Thank you! That did the trick. I put the stock Froyo back on via Odin now and am back up again. Whew, Christmas is saved! Thanks.
Try Eugene Ginger Clone is pretty face...I'm currently running Team Whiskey Nero Beta 3...noticed a couple bugs nothing major
Sent from my SGH-T959 using XDA App
Ravynmagi said:
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Click to expand...
Click to collapse
You were trying to load a 2.1 nandroid restore onto a 2.2 kernal. Nandroid does not restore the kernal so you would have to install one separate from the nandoid if you want to try it again.
in order to restore your nandroid backup you would have to first flash a 2.1 ROM, preferably the one you are restoring from, whenever I am changing versions, 2.2 to 2.1, I always Odin back to JFD and build up from there.
Kernel flashing questions
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
tenbeau said:
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
Click to expand...
Click to collapse
Thanks button right next to the quote >.<
I'm used to the quote being on the left.
Anyway, you can flash just the kernel. Check the Development section. There are some out there (Eugene has a bunch as do others). Depending on how they packaged the kernel, you would either flash with CWM or through Odin. The different ROMs typically come with the kernel, so you could just flash a 2.1 ROM and then nandroid back to what you had, or flash just the kernel, then nandroid.
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
diceburna said:
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
Click to expand...
Click to collapse
Which rom specifically?
Also you shouldnt have to disable voodoo if you are coming from another voodoo rom.
have you tried reflashing the rom?
I got the same prob. Try to get back to stock T959UVJFD using odin and reflash.
Axura is nice but it shows many compatible troubles when trying with different kernels/mod.
I tried reflashing several times but no luck so far. And the previous rom I was using was the froyo rom for eclair the download zip file name is AXURA22VE...I'm thinkin I should probably have ODIN to stock Eclair, then update my phone to stock froyo before flashing this rom.
dont bother with stock froyo just odin to jfd then root install cwm and flash the rom
going to stock froyo includes the updated 3e recovery which can be circumvented but requires extra work on your part.
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
diceburna said:
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
Click to expand...
Click to collapse
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
nomadrider123 said:
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
Click to expand...
Click to collapse
same here
@op when did you download axura 2312? the D4A server went down a couple days ago and we are trying to restore all the files on the new site.
Redownloading 2312 will be not be possible at this point in time, i have posted a download for 2310 in the Axura development thread until the site is fully functional again. there isnt a very large difference between 2310 and 2312.
if you are still able to add files to your phone i would try to flash from CWM first otherwise if you cant jfd will be your only choice.
Hope this Helps
Thx guys I'm in the process of recovering from cwm now, tbh I haven't used ODIN before so before I try it hopefully my nandroid backup will restore everything. I downloaded the 2.3.1.2 rom I believe the day it came out.
the downloads on the d4a webiste are back up for the vibrant rom
http://devsforandroid.com/index.php?topic=23.0
Sweet I just finished dl'ing 2.3.1.3 hopefully it all works out. BTW I was able to easily restore my backup...flashin new rom now will update soon.
thanx men that really helps
All is well :-D I guess the old file I had was corrupted bc I flashed this rom w/ no problems at all...Thx
Flashed CM9 to experiment with it and see how it ran, prior to doing so made a backup of current setup (unnamed 2.2.1 w/ siyah kernel). After flashing to CM9 and playing around a bit i was going to revert back to my original setup. Tried flashing back and now I am unable to even get to CWM Recovery, or Download Mode. It will boot to the SGS2 screen and then just go black no matter what I do. It is still recognized in Odin so I was thinking I'm going to have to revert back to stock and just flash it back afterwards. Any ideas before I proceed?
AK40Nine said:
Flashed CM9 to experiment with it and see how it ran, prior to doing so made a backup of current setup (unnamed 2.2.1 w/ siyah kernel). After flashing to CM9 and playing around a bit i was going to revert back to my original setup. Tried flashing back and now I am unable to even get to CWM Recovery, or Download Mode. It will boot to the SGS2 screen and then just go black no matter what I do. It is still recognized in Odin so I was thinking I'm going to have to revert back to stock and just flash it back afterwards. Any ideas before I proceed?
Click to expand...
Click to collapse
Flash back to stock. Strange - you say you can't get into download mode, but Odin recognizes it?
Ok, finally got into DL mode and flashed a stock kernel from Entropy's post. Now i'm faced with it booting to the ATT splash screen and it just loops that screen infinitely. I'm still unable to access recovery mode to wipe data/cache or anything like that. This is becoming frustrating and I'm not quite able to wrap my head around why after flashing stock that I'm unable to boot into the phone beyond the splash screen. Am I using the wrong stock fw or something? Here's the link to the one i used.
http://forum.xda-developers.com/showthread.php?t=1286432
From my experience it's the wrong SPL/radio combo.
No matter what I do, I'm stuck up to that point.....I've tried a few different stock flash packages through Odin to no avail, same result every time. I know i'm probably doing something wrong or I'm missing something here, its not bricked I do know that so its not like i'm dead in the water here. Any ideas would be better than where I'm at currently.
BeenAndroidized said:
From my experience it's the wrong SPL/radio combo.
Click to expand...
Click to collapse
There is no SPL on the GSII, and a bad radio will only screw up calls/cell data.
To the OP - exactly how did you flash CM9? CWM or some kanged-up Odin build?
Through CWM, everything worked fine but when I was using CM9 my back button and serach button weren't working, probably erroneous to this situation. this is just messing me all up that I'm able to boot up til the splash and then it just loops it over and over, its making me think that the FW is having issues loading or something.
Problem solved finally. Something must have changed after this last flash attempt because now I was able to get into CWM of all things and recover my old backups. Nice little adventure that was. Thanks guys for the help!
Entropy512 said:
There is no SPL on the GSII, and a bad radio will only screw up calls/cell data.
To the OP - exactly how did you flash CM9? CWM or some kanged-up Odin build?
Click to expand...
Click to collapse
Understood. Coming from G1 I know it's different.
Sent from my SAMSUNG-SGH-I777 using XDA App
Does samsung kies still have a chance of bricking your vibrant? I just used odin to flash back to stock and now I want to go to 2.1> 2.2>2.3>4.0.
I wouldn't risk it........
http://forum.xda-developers.com/showthread.php?t=1464423
I got into cm7, and then i wiped data, cache, and tried to flash ics passion. After that, i kept getting boot looped and didnt have recovery so i had to use odin. Now im back at 2.1...what did i do wrong?
Get back to that point and when it bootloops, pull the battery, boot into recovery again and reflash ICS over itself.
From my guide
Once you are in recovery, scroll down to your folder and find the ICSv? (or whatever version you are wanting to flash) and flash it. First boot takes a long time just like before on CM7. Might also get into a bootloop like in CM7 too. If so, then do the same as before and reflash ICSv?, but this time you'll have to use the Volume-Down + Power (or if on Froyo Bootloaders the above key combo) to get into recovery. Boot up and you are good to go in you new ICS rom.
Click to expand...
Click to collapse
When you say that you didn't have recovery. Was that a custom recovery or you just saw the stock again? There should be no reason why you would not have recovery of some sort.
Agreed, pop your battery and return to cwm and flash, the kernel has updated, it should go now, listen to uncle wood.
and never use kies for anything!!!!!
Never kies
Go straight to 4.0. No need for in order. 2.1 is easiest to flash from anyways.
I've probably flashed hundreds of times now, test roms/kernel Worst case have to heimdall.
One time (n00b days) used Kies mini and it hard bricked me. Had to get jtagged riffbox.....
Sent from my SGH-T959 using Tapatalk 2
u will hard brick ur phone if u use kies ....from 2.1 go directly to cm7 from there use whichever u want .....
Yep .KIES can HB your mobile. I also updated via KIES from 2.1 --> 2.2 (OMG I didnt knew then.. Thanx goes to Woodrube for pointing that out.)
If you need to go to 2.2 there are always better way to than using KIES. this is a great thread which Now im using http://forum.xda-developers.com/showthread.php?t=1674519
tc
edit: No need to update to 2.2 brfore going to ICS. Its always better to flash back to stock before flashing ICS.
Never use kies, period. There are plenty of other options out there. Just in case you guys don't know about the EU bug, you should definitely read this if your planning to run ICS.http://forum.xda-developers.com/showthread.php?t=1580902. I'm currently running a 2.2 ROM until this bug is figured out.
Sent from my SGH-T959 using xda premium
Hello all, I want to install Clockworkmod on my Samsung Vibrant T959 so I can install a custom ICS ROM. I ran into some problems along the way. I can not seem to install CWM correctly. I had the phone under Froyo 2.2, kernel version 2.6.32.9, and build number froyo.uvkb5. After flashing the recovery by ROM Manager, I would still be stuck at the stock recovery. I have the correct files to download:update.zip. After clicking on "reinstall packages", the recovery said "replacing stock recovery with Clockworkmod recovery". The problem is that after that message, the phone restarts into the stock recovery. I tried it 4 times in a row, but I'm still stuck at the stock recovery. The system keeps saying that it will replace the stock recovery with the CWM recovery, but that did not happen with me. I would keep getting the same message when I click on "re install package". What am I missing that does not allow me to do this? Thanks all.
Are you on 2.1 eclair or 2.2 froyo?
I'm pretty sure you need to be on 2.1 but don't quote me.
Also, I believe there is an issue with the newer versions of ROM manager, recovery mismatch. (Again don't quote)
I haven't had to mess with that stuff in a long time. Either way I'm posting a link that will help you along. If you have any more questions just shoot.
http://forum.xda-developers.com/showthread.php?p=9375927
Paranoid, sitting in a deep sweat...
Thanks for the reply. Like I said in my last post, I am running at Froyo 2.2. I already bricked my phone for failing to downgrade to 2.1. I already rooted my phone, my problem is that I could not install CWM correctly by the stock rom. After the message states that it is replacing the stock rom, my phone goes back to stock with no changes.
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Your positive you dont have a 4g?
Sugartibbs said:
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Click to expand...
Click to collapse
You do not understand, I am having the problem that CWM could not install properly. When I chose "install packages" the steps went by and ended with "Replacing stock recovery with CWM recovery". Usually, that would jump straight into CWM recovery after it's installed. That did not happen to me, After installation, my phone restarted and booted back into stock recovery. I tried installing again but I always go back to stock recovery and not Clockworkmod recovery as I planned.
Ive never seen that error message, I know its frustrating, but the t959v 4g comes loaded with Froyo 2.2,the a 2.1 eclair odin will brick it.Just trying to help.
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
Paranoid, sitting in a deep sweat...
---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------
In the link I sent is the AIO toolbox download. There is a guide how to use it in this link. The DL links are dead in this one so get from previous.
Paranoid, sitting in a deep sweat...
IIRC the update.zip method does not work in Stock 2.2 because of the 2e and 3e recovery mismatch. If you to go to 2.1 Eclair, then you can use the update.zip method and then flash your ROM of choice after that. If you decide to stay on 2.2, you'll have to get the 3e method. It is in the Development section, so you'll just have to search 3e and it should come right up.
All this is provided you have a T959 (3g) and not a T959v (4g). Sorry but lately there have been many 4g users flashing our ROMs and then freaking out.
You can also find a bunch of files in my Repo thread stickied in the Dev section.
samsgun357 said:
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Maybe you'll get it now.
Good luck.
@Woody, thanks buddy.
I linked your repo thread in my previous post.
Edit: well the link isn't in my posts, must not have sent??? But here it is
http://forum.xda-developers.com/showthread.php?p=31279153
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
nfkod said:
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
^^ this is not true.
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
naturallight said:
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I have no idea what you are talking about?????
Paranoid, sitting in a deep sweat...
If you have the proper xda version of update zip on your sd...,, theres no need for a kernel flash.
I have the same exact issue as the original poster. 2.2 froyo and all. I even replaced my stock 3e recovery with the modded one, but I get the same issue. Says its flashing CW recovery but it always reboots and comes back with the stock recovery. What exactly are we doing wrong?
Follow steps in this guide, update.zip b is probably best but you need to Odin back to stock first.
http://forum.xda-developers.com/showthread.php?p=9375927
Alright so I managed to get CWM on my 2.2 Stock Vibrant and even got it permanently. What I did was download SGS Kernel Flasher and install it. Then I went the Samsung Vibrant Kernel Bible and found the stock kernel with Voodoo lagfix included that matched my phone (because the kernel has CWM built in) downloaded it, and placed it on the root of my card. Launched the app, backed up my current kernel and then flashed the new one. Everything went smooth and then my phone rebooted and was stuck on the Vibrant screen for 20 minutes. I was pretty sure I messed my phone up. Also it was talking to me which I didn't realize at first, because I was expecting my phone to be talking to me! Finally made out what it said and it said something along the lines of not enough space on the partition, closing... It was hard to understand because it was in a robotic voice. It eventually rebooted and loaded up like normal. Checked the about phone but saw nothing different. So I decided to reboot to recovery just to check and sure enough, CWM 2.5.1.3 comes up, and comes up every time Finally, now to figure out what to do to get on a jellybean ROM
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
samsgun357 said:
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
Click to expand...
Click to collapse
QFT. Just yesterday I ran into the same problem as reported by the OP and a few others. I HAD to downgrade to 2.1 via JFD Odin. Then flash the update.zip. I then just downloaded ROM Manager to get CWM working. However, I did see in some instructions that sometimes even though you know you have CWM installed, it will still default to stock recover. I simply applied the update.zip again and it eventually fixed itself. Not sure what that was about, but I did see it in some instructions, and I experienced it as well.
nfkod said:
the first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
great help dude.i fixed finaly."""""thanks"""""