Related
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
Ok guys (and gals)..
I personally have a rooted & rom'd Epic 4G. A coworker recently upgraded to their first smartphone, a Samsung Fascinate on Verizon.
Since they know nothing, they asked me to do a few things to the phone for them.
Here's what I've done so far..
Rooted (fully & confirmed) via One-Click Root. Originally tried rooting via steps found here and over on Android Central but it didn't seem to fully root. Some things would run that required root, but others wouldn't (Titanium Backup being one). Bottom line, phone is fully rooted now. Running the stock ED04 rom with no intent to change. This guy isn't a power user, just wants a few things beyond fully stock.
Issue 1 -
Next thing I wanted to do was get Clockwork Mod installed so they could do fully system backups. Tried installing the red Clockwork Mod via Odin found here which somewhat works, but the Backup/Restore functions aren't really operational. If you run a backup, it goes through like it worked, but then when you go to do a restore the first thing I noticed was all the dates on any backups made are set to January of 2000 for some reason. When selecting any of the backups present, it won't restore them. Thoughts? Link to a fully working CWM for ED04?
Issue 2 -
Wanted to flash a good kernel for him so I chose OTB Reloaded v1.6. Flashed via CWM, installed Voltage Control, and all that is working good. The only issue was that after flashing the kernel it screwed up the boot animation. Layered over top of the stock Galaxy S animation and then the Verizon one was the generic "ANDROID" animation. No huge deal, but it irritated me so I tried to fix it by flashing a "stock" Galaxy S boot animation found HERE. The issue now is there is no boot animation at all. After powering the phone on and getting the plain white text "Samsung" the screen goes completely black for a few seconds as the phone boots until you find yourself at the main screen. Any suggestions?
I've searched and looked around a bit but having trouble finding any clear info on either issue. Perhaps it's just me, but it seems like the Fascinate info and sections are very scattered and outdated?
Thanks in advance for any insight, help, tips, info, and/or fixes!!
I think by using this recovery, http://forum.xda-developers.com/showthread.php?t=942021, it should fix your problems.
Cool...thanks for the link. I'll give that one a shot and report back.
UPDATE: I think I might have found the procedure I was looking for. Can any one confirm if this will work?
http://forum.xda-developers.com/showthread.php?t=1238070
Greetings,
I beg tolerance and forgiveness of those much wiser and intelligent than I.
I need to restore my Fascinate back to the stock ROM that comes with the phone. it was running Froyo 2.2 when I got it.
I tried flashing Clockwork Recovery to my phone using Odin. I followed the instructions in several of the other threads (pretty simple).
Now, when my phone starts it defaults to recovery mode no matter what I do.
There are two options.
First the screen loads to...
"CwM Voodoo Lagfix Recovery v2.5.1.x" (I didn't realize I was putting this on my phone at the time).
If I go to apply sdcrard:update.zip --> Yes...--> "ClockworkMod Recovery v3.0.0.8"
At this point I am at a loss as to how to proceed.
The end state I am shooting for is to have a rooted phone with clockwork on it so I can make a backup of my phone before flashing a de-bloated touchwiz rom to my phone. Many thanks in advance!
follow the going back to stock section in this link. It will put you back to stock ed05 froyo.
http://forum.xda-developers.com/showthread.php?t=1238070
hi guys
I recently bought a 2nd hand Vibrant for a really good price.
As far as i see the Vibrant is already rooted with 2.2.1 Lidroid, and CWM installed.
The battery usage is amazing with this rom, but I still fancy to install some custom GB roms.
I have some questions:
1. I would like to check if I am already on GB bootloader, please guide me to check?
2. If I am not on GB bootloader, I know I must first install it.
I wonder if Vibrant has some stock GB firmwares like captivate does? The stock camera is a must for my case ><
Am i correct if I follow this method from here
http://forum.xda-developers.com/showthread.php?t=1156832
3.Or actually I can simply flash any custom GB roms directly from where I am (Lidorid 2)
THX
Okay you know if you're not gb bootloaders when you turn on ur phone there's weird rainbow lines
If not then you are
And if you are then yea you can flash any rom
Sent from my GT-I9000 using xda premium
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
j4371 said:
Let me confirm if you suggesting me to flash the GB roms?
If there's rainbows > froyo bootloader
if nothing > GB bootloader
So can i say actually Gb roms doesnt really need GB bootloader
as long as I am fine with the rainbows?
THX
Click to expand...
Click to collapse
I've run CM7, and CM9 (ICS) on Froyo boot loaders. For me it just makes the kernel screen flash and show again, then goes on to ROM booting. I'm running a Froyo boot loader right now.
Is lidroid a t959 rom or a t959v?
You need to have a t959 to be in the vibrant 3g section, otherwise you'll probably want the galaxy s 4g section.
Sent from my Sensation using Tapatalk 2
there is a Lidroid version for T959 - I have a Odin flash with it. I use it instead of JFD.
Want to know if you have the GB boot loaders? Easy -
Hold the Volume up button and the power button at the same time. If it goes to download mode....you got the GB bootloaders.
T959 Vibrant does not have Samsung 2.3 support. Samsung forgot about us after Froyo. There Froyo OTA upgrade bricked so many phones that they wont chance it again.
For 2.3 Gingerbread you will have to download a I9000 port found in our Development section. That said the ICS packages are very nice for Vibs too.
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Yup, you'll need to go back to stock. There are plenty of write-ups on how to do it.
Also, NEVER restore a 2.2 backup after you install 2.3 or higher. The file systems and partitions are different. Odin back to stock, install lidroid again, and then try to restore your backup.
j4371 said:
need help guys
A few hours ago, I was at work and bored.
I started to flash some GB roms without coming back to check this post.
The rom i used was phiremod-fusion-2.1.1.
As usual I nandroid my lidroid before doing anything.
Then I 3 wipes and flash the phiremod rom.
first time the flash was really quick and also rebooted itself.
But only this time I realise I have a newer CWM 5.xx version instead of my 2.xx version (Lidroid)
Ok, i wasn't panic, because i read some where before. It's prefectly fine for a cm7 if the first time it bootloop.
Then I pull battery, and boot into recovery again, to flash the 2nd time.
this time BAAM, prefect. I found myself with a 2.3.x cm7 mod rom.
but as soon as I found the camera apk is actually the MIUI one. I decided to nandroid back to Lidorid.
things turns ugly at this point, when i back to CWM i restored.
But only found some errors CWM said , but I remember CWM did say something like erasing boot.img before restoring.
After the resotre failed, I accidentally reboot my phone.
And now my vibrant only stuck at the typical black boot screen "Vibrant in the middle with samsung at the bottom.
I tried to boot back to recovery, but no luck.
right now I am telling myself i probably need to restore to stock.
Can my fellow xda members guide me the proper way to
1. boot CWM
2. download mode
Given the fact that I am not too sure about which bootloader I am on.
THX people!!
Click to expand...
Click to collapse
Get into download mode by while it's off, holding VOL-UP + Vol-DOWN and plugging in USB.
y vibrant revived!!
Thx everyone
After this, I am thinking to ask my colleagueto make one JIG for me.
I'd like to confirm it's same as SGS, i.e. 3 X 10kohm in series
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