Related
I had zero problems when rooting and flashing my G1, but now with my Vibrant I am not sure what I did.
A few excellent stickies at the top but I seem to not be making any progress.
Here are the steps I took.
I had a stock Vibrant running 2.1
I downloaded ROM Manager, installed clockwork mod.
Did a backup of my current system ( was I supposed to do a clockwork AND nandroid?)
Downloaded and successfully installed a ROM called Blackhole 1.0
it runs ok but didn't give me the option to switch from 3G to EDGE data, and then I couldn't get internet access at all so i decided to restore my original stock vibrant system.
So I rebooted into recovery, selected restore (my phone won't go into recovery anymore for some reason) and waited, it took a while, then I rebooted (forgot to wipe), but it just got stuck on the Vibrant screen. So I booted into recovery mode again and wiped just user data not cache and rebooted, same thing stuck at Vibrant.
Now i keep hearing about something called ODIN, what I can tell it is some kind of flasher program for ROMS, nobody seems to give any kind of link or anything, is it greymarket or something?
So where am I now? I think the excellent noob guide needs to be updated a bit more.
My phone can get into download mode (whatever it is for i don't know) but it won't get into recovery mode anymore.
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
I have done the samething as you, coming from a nexus one it seemed easier to flash roms without worrying about downgrading kernels or what not. Recently I was on Nero froyo and flashed to a different rom, and tried to revert back but ended up stuck at the vibrant screen. Think it has something to do with voodoo lag.
Anyways I had to use Odin with the no brick froyo off ebproductions. Ran that and uploaded clockwork, reinstalled voodoo lag fix and was able to nandroid back to my Nero set up. Somewhat of a pain but once you've done it, no need to worry about bricking
xtone said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=771111
i think what happened to you is you flashed a 2.2 ROM then tried to revert back to 2.1 without doing the proper downgrading steps i.e. you did not flash a 2.1 kernel first.
but since you can get to download mode.. just flash stock JFD or JI6 through ODIN and you should be good.
good luck
Click to expand...
Click to collapse
So the steps that are in this page?
http://forum.xda-developers.com/showthread.php?t=734475
GreggoryD502 said:
Once you get back to stock don't give up on the 2.2 toms. Try axura or nero. They might have a few minor bugs but its way better then stock 2.1.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
Well as long as I can use Odin if I f-up royally like above then I might give it a shot.
Need to read about downgrading kernals or whatever. Might just wait for Cyanogen 6.1
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
thegreatcity said:
Just so you know, the backup utility in Rom Manager (clockwork) is really just shortcut to a nandroid backup.
The way I have things set up for backups, and this is just for my personal convenience, is as follows...
I have a stock JFD ODIN rom to flash in case anything goes wrong. (A lot of people here will tell you to flash this whenever flashing a new rom. It is safer, and cleaner to do it this way, but not absolutely necessary)
I make a nandroid of my last stable rom (I only keep one at a time cause the files are huge) and keep a backup of that on my PC.
I backup all my apps and a few other things (call logs, bookmarks, sms) through Titanium backup. If you get the pro version, you can load it up after flashing a new rom and have it automatically restore all your apps in one click (system settings can be dangerous to restore when going from rom to rom, so be careful with those.) I also keep a backup of this on my PC.
I will also occasionally backup both of the sd cards to the PC.
Maybe overkill, but you probably wont ever lose anything forever.
Click to expand...
Click to collapse
OK I will just do the long way from now on. I use this phone on AT&T, I was worried that I flushed $500 down the toilet but ever since i modded my first phone way back in the day i've been addicted.
Running Odin and my phone is in download mode, about to flash this b**ch.
wish me luck.
I flashed Odin on my phone to revert to stock. Re-Rooted it but now I can't flash Clockworkmod. Please help D:
use the update.zip posted here. You want B.
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
PrimeNemesis said:
I have rooted my Vibrant using ROM Manager/Flash CWM Recovery. (I'm running 2.2, Kernel 2.6.32.9, Build FROYO.UVKA6.) I used this method because no matter what folder on the external or internal sd card I could not use the 'reinstall packages' option on the reboot screen. Now, I'm trying to place the Bionx or Nero ROMs on my phone, but can't get anything to install no matter what I do.
I don't think I anything wrong with the root because I kept getting the same 'E:signature verification failed Installation aborted' message everyone else seems to be getting. I'm wondering if Samsung/T-Mo didn't put anything in to prevent rooting and adding new ROMs.
I have rebooted my phone multiple times and have not gotten any results. Along with ROM Manager, I have Busybox installed.
Please feel free to ask questions for more details. I'm a noob to rooting, so I definitely allow for the fact that I might have screwed something up and will need to start over.
PN
Click to expand...
Click to collapse
This is because you are now on 2.2. Samsung patched the exploit from 2.1 that allowed cwm recovery to be flashed. The best thing I can tell you to do since you have root would be to either
A) ODIN down to 2.1 ROM then root again, then install rom manager and from there you can install cwm recovery OR
B) Use this method I posted based on Supercurios voodoo kernels found here:
http://forums.t-mobile.com/t5/Samsung-Vibrant/on-steps-to-flash-Bionix-V-1-2/m-p/720803#M5807 (look for the answer marked solution - and because you have root skip ONLY that part and download the proper supercurio's zip not the tar).
Supercurio's vibrant kernels found here:
http://forum.xda-developers.com/showthread.php?t=870480
Do this before you try anything else, this is your quickest and least painful solution:
http://forum.xda-developers.com/showthread.php?t=833423
Then:
When you boot into recovery and hit Reinstall Packages, the phone might reboot back into recovery, Reinstall Packages again and it will take you to the mod recovery, no more sig. verification.
Congrats!
Thanks.....
roumenjr and mavsfan.
I was able to get the root done. I took roumenjr's suggestion and it worked once I figured out that I was placing the ROMs in the wrong folder.
Now running Bionix Obsidian v2.
oooops..............
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
sigmtndawg said:
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
Click to expand...
Click to collapse
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/showthread.php?t=1048380
To test root, simply open terminal emulator (free in market) and type "su" (no parentheses). It will notify you of a superuser request.
find an odin package for the baseband you want like EB01, EC01, ED01, etc (I use an all in one complete deodexed and debloated EB01 package myself) and the newest CWM 3. Odin them both, boot straight into cwm, wipe data/cache/dalvik, install the .zip rom of your choice from sd card and reboot phone. Should work fine, its the way I've done it and I've had few if any problems
edit: most roms like SuperClean, Evil, ComRom, etc are already rooted so there's no need to do anything special to gain root. the hardest part is flashing it correctly
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
sigmtndawg said:
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
Click to expand...
Click to collapse
Do not use ROM manager at all for anything on the fascinate.
The correct way to flash on fascinate: Download ROM .zip file and place on the root directory or your sd card. Boot into CWM and wipe data/cache/ dalvik cache (dalvik is under advanced) choose install zip from sd card. Install and reboot. First reboot will take 5-10 minutes, so be patient.
Hope this helps.
hi,
im trying to flash a custom rom onto my vibrant.
but i've got a question regarding the phone starting stage.
i got the phone from craigslist and it seems the phone is slightly modded:
-it's got a "overstock" logo when you first start up the phone.
-when i boot the phone using the pressing of two volume keys and power button, i get "clockworkmod recovery v2.5.1.3- voodoo lagfix" in red color.
What i want to ask is do I have to get rid of these mods first before i flash custom roms to prevent future problems? If so, how do i get rid of these mods?
if i dont have to get rid of these mods first, do i just follow this guide - http://forum.xda-developers.com/showthread.php?t=849028
also, i can flash custom roms without rooting right?
thanks
the phone is already rooted for you, to verify you should see the superuser app in your app drawer. Its a skulled android head. You can install any custom rom that already had voodoo enabled without disabling it. If you like you can disable it by going to the voodoo option and disabling it on the next boot. I wouldn't worry about it because most of these current roms have voodoo. What rom were you planning to flash?
hi thanks for the reply.
but i don't think my phone was rooted cuz there was no superuser logo.
so i did root it using the superoneclick method.
however, im in trouble now cause i accidentally formatted the internal sd thinking that'd disable the voodoo lagfix. (the guy i bought it from said he applied the lag fix- i wanted to disable it cause i'm trying to flash the team whiskey 1.3.1 and the site guideline said it'd brick my phone unelss i disable the lagfix- stupid i know)
But i did the phone backup using the rom manager and i restored, but my pics are still not there?
am i screwed here or can i recover somehow the pics from my phone using the backup file?
thanks!
convotutor said:
hi thanks for the reply.
but i don't think my phone was rooted cuz there was no superuser logo.
so i did root it using the superoneclick method.
however, im in trouble now cause i accidentally formatted the internal sd thinking that'd disable the voodoo lagfix. (the guy i bought it from said he applied the lag fix- i wanted to disable it cause i'm trying to flash the team whiskey 1.3.1 and the site guideline said it'd brick my phone unelss i disable the lagfix- stupid i know)
But i did the phone backup using the rom manager and i restored, but my pics are still not there?
am i screwed here or can i recover somehow the pics from my phone using the backup file?
thanks!
Click to expand...
Click to collapse
Find Vibrant Bible in the forum. Download stock rom, use ODIN to revert back to stock, Root, Install Rom manager, Clockwork Mod, Install Bionix 1.3 enjoy..
hey, is there any cwm recovery alone?
no custom kernel even philz kernel?
because the stock is way much better than philz kernel, and rom manager is installing the recovery but when i go throgh recovery mode, i see the stock one!
any help?
A few things:-
1) Don't use Rom Manager with the SGS2. At all. Ever.
2) Yes, you can install CWM independently of kernel. however, it will only be temporary/persist only until the next reboot, which is why you see it disappear. Just make life easy for yourself & pick a custom kernel that has CWM baked into it.
3) Don't use Rom Manager with the SGS2. At all. Ever. Rom Manager has a nasty habit of breaking CWRecovery with the SGS2 and/or causing bootloops. You might use it just fine for a little while, but before long, one or both of these things will happen to you if you continue to use it, and funnily enough (perversely even given how simple it is to do backups with CWRecovery), it seems to happen to people who don't have backups. Which creates obvious hassles for you if you have to start from scratch.
well thanks, so i have to stick with a custom kernel -_-
actually i didn't see any problem, but thanks for the advice!