So Ive spent the last 3 hours trying to get Clockwork mod loaded on my stock, rooted Fascinate and I think all Ive done is manage to completely confuse myself more than I thought possible.
I should start off by saying Im a complete newbie at all of this and seeing things like "clockwork red vs green vs blue" doesnt really mean a whole lot to me.
I started off by trying to follow this thread in hopes of getting Froyo loaded. I was fine up through the "Installing Clockwork Mod" section. I was at first confused by the files that were mentioned as it seems as though the packages he refers to have since changed.
So what Ive tried thus far is booting into Download mode, loading ODIN chose the cwm-recovery-ALL.tar from here with the PDA button and hit start all seemed to go well.
My problems started occuring when I installed ROM manager and tried to backup the current ROM. When it booted into recovery mode, I got an error about failing "to verify whole-file signature".
I tried just continuing on in the tutorial and loaded the EB01 Froyo modem via ODIN, but still couldnt get to the point of loading the new custom rom as it gave the same error about the update.zip. Im hoping I didnt screw things up further by doing this.
Ive searched around and read I dont know how many forum threads since across a number of Android forums. Some saying you dont need the update.zip on the SD card, some saying you do. Ive also read some posts saying my phone should have booted into Clockwork "red" and I dont think Ive been able to do that yet. I think its only booting into blue (are these colors just referring to the text color?)
Ive since wiped my phone and tried again and still have had zero luck. Ive tried a couple other things including trying to the update.zip (which I assume is the "cwm-recovery-ALL.zip" that should be used?), but when I choose to apply the update.zip it now comes up with an icon that has the android robot with a yellow triangle with an exclamation mark in it.
Sooo frustrated at this point and any help would be greatly appreciated!!
ROM manager is incompatible with CWM and our phones currently. Everything you did up to installing it appeared right however.
Sent from my SCH-I500 using XDA Premium App
Ok, so what should be the next steps I take here? How does one backup the existing ROM (so I can revert back in case something goes wrong) and also load the new ROM without ROM manager?
Thanks again.
Use Odin to flash the recovery-All.tar file and then boot up your fascinate and after it boots turn it off again. Once it is off hold down both the volume up and volume down button at the same time. While you are holding those press and hold the power button and do not let go of the power button until you see the Samsung logo. When you see the Samsung logo let go of the power button first then let go of the volumes. At that point you should boot into Red CWM recovery. Try it and let me know how it goes.
Sent from my SCH-I500 using XDA Premium App
Related
Yes, I know...it's been posted many times before but I still haven't read a thread with my particular problems. Ok, so here goes....I have a locked Rogers Streak that I tried to flash to DJ_Steve's 1.4.6 using the sticky, but of course it didn't go so well so I ended up stuck at the Dell logo.
Next I tried a bunch of recovery img's via Fast_boot, but still no luck. So the current situation is that I can get to the recovery menu and I can Fast_boot:
1) I've Fast_boot'ed to Clockwork img, but when I choose option 2, I get a black screen.
2) I've Fast_boot'ed to 309 img, and tried to just straight update to official Dell 2.2 Streak_315_12332_00.pkg, but I get an error saying that it can't mount the SD card.
3) I've tried this fix as well: http://weethomas.wordpress.com/ And that did flash, I was stuck at the Dell log and when I try to flash the recovery img again, it does not flash option 2 in the recovery menu even after a factory reset.
4) I'm a little bit tired and a little bit drunk right now and I do not usually post anything at all (as you can tell from my stats, but I've been a member since the Atom Exec days and can search the posts ), I am kinda stuck right now so a little guidence would be great.
Thank you all!
Just flash the stock A1.6 and than 2.2. If this works, please leave xda devs cause it looks like you don´t know what to do and opens threats we have enough of them
hello guys, my 1st day with Vibrant, and android in general and i am in a soup.
i was trying different ROMs on my vibrant, 1st tried Axura's 2.1, then tried macnut R14 and was just about to try TW's Nero Beta when i saw an error at the start of the flashing, a white triangle with exclaimation mark and android robot beside it, i thought i bricked my phone but if i click any button it atleast goes into clockwork recovery, but if i try installing any ROM from zip file, it tries installing and gives following error
"Finding update package...
Opening update package...
verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
it happens with any ROM i try to install, even with update.zip file
oh by the way, if i choose "reboot system now" then it reboots fine wid macnut ROM as that was the last ROM that got properly flashed, how do i solve this issue?
I am sorry if this has been answered before but i am just too nervous to search much, please bear with me.
Had a very similar problem. Had installed (in this order, not sure if it makes any difference) Macnut 13, Axura 2.0.5, Macnut 14, Axura 2.06, 2.1 and errored when trying to install Nero B2. I could not install Nero, or any other 2.2 Rom even after going back to JFD and starting fresh, I even wiped internal/external SD cards and nothing. All I could do was return to JFD via download mode+odin, and then flash Bionix Fusion 1.2 . Thats all I could get to load. Not sure why this is happening, the roms weren't corrupt, I downloaded them several times to make sure (MacNut + Nero) and the previous ones worked without a hitch, but for some reason everything stopped working. Maybe if you can post some extra info we can find a solution, and maybe someone will throw some extra info in here or has a similar problem.
Find eugines froyo that don't brick and follow his instructions
Sent from my GT-I9000 using XDA App
@ op, it looks like you just need to download the rom again, and try to put the rom on the root of your sd (in no folders). I've had the same issue multiple times and those 2 things always seem to get it working.
Sent from my GT-I9000 using XDA App
I had the same problem and trying to flash another rom over top of it made it worse, get into download mode with the battery pull method then oden back to stock. Once back to stock just adb reboot recovery, reinstall packages (should bring you into clockwork) then flash an os.
Another method that seems to work well is as follows:
1) remove the battery
2) plug the phone into the computer
3) when the battery charging screen is showing hold down the vol up and vol down keys
4) with the vol keys pressed, press the power button, as soon as the screen goes black let go of the power button (KEEP THE VOL KEYS PRESSED TILL YOU SEE THE DOWNLOAD SCREEN)
5) when you are at the download screen let go of all buttons
6) smile, ODIN, reboot, take a deep breath
gdluck and if you have any more issues pm me
thanks for your inputs guys, but thankfully after flashing my vibrant with odin3 and original Tmo ROM, i guess its JFD, i could again get it back to factory state.
and after that I started the whole procedure again, rooting and flashing ROMs, and everything is working fine.
i guess (i am not sure, as i am a noob in this area) but after installinh macnut ROM my kernel was changed to GT9000 and that made it impossible to flash other ROMs, onve i got original vibrant kernel back with odin3, everything worked again.
im now on original T959 kernel, i hope that helps.
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
kero4 said:
Guys,
I have tried several roms and decided to odin back to 2.1, updated to 2.2 and just clean it up a bit and leave it as is for a while.
Everything went just fine, but yet again this damn clockwork recovery issue which I knew I would get but thought maybe it would be solved by now on rom managers side.
So, in rom manager, it shows that current recovery is 2.5.1.2 which matches the latest, however, when I reboot into recovery, I am still getting the standard 2.2 recovery console.
I tried searching but not sure what the issue is, of course I get the signature issue when I try to update package.
It's wierd that it's showing it's installed but it's not actually booting into the correct recovery console.
Thanks.
Click to expand...
Click to collapse
delete whatever update.zip you
http://forum.xda-developers.com/showthread.php?t=849028
get the 1 from there, reinstall packages twice and it should go to clockwork recovery
Okay, obviously option b would be better, however, will I have to reroot after if I use option B?
Nadda, same results, it's okay though, I'll live with it for now since I'll keep 2.2 with all the crud removed for now.
Please read that guide. You've missed some key points. I'd explain more, but I'm hanging with my kid.. Read the guide.
had the same problem i used this method and it worked for me
http://forum.xda-developers.com/showthread.php?t=833423&highlight=recovery
ok so yesterday i rooted my telus fascinate and i was going to isntall the MIUI rom. Following a guides instructions i installed rom manager and did a clockwork mod recovery, i then put the rom on my root file of my sd card and tried to install it through the "install rom from sd card option" on the app. Problem was i only got into the stock recovery mode and not the clockwork one it aslo gave me signature failures. I then followed the guide of this video:
http://http://www.youtube.com/watch?v=Q7xV0yE9ZcA
when i installed the kernel everything went fine but then after i got into CW recovery and installed the rom my phone booted and it just kept repeating the normal splash screen (it said galaxy I9000 instead) followed by a screen that said something like cryogenic mod. I got freaked out from here and tried to install stock kernels to get my phone running. As of right now my phone will boot but only stay on the splash screen. I can not access recovery mode. I really need some help, thanks.
these are some of the files i used:
the rom i used,
http://http://forum.xda-developers.com/showthread.php?t=1150045
the kernel i used,
http://http://forum.xda-developers.com/showthread.php?t=822756
thanks
the links are broken. Did you install a rom / kernal specifically for the telus fascinate?
i believe it could have been for the galaxy I9000,
ill try to fix the links btw
update*
i managed to get it into clockwork recovery mode by holding the dam buttons for a solid 5 minutes, after doing this i pressed factory reset, now my phone is stuck saying:
-- wiping data...
Formatting DATA
0_0' im not having a great day
http://forum.xda-developers.com/showthread.php?t=1227807Until I know what version miui and kernal you are trying to flash, it's hard to help. It definately sounds like your phone is soft bricked tho.
Edit* Here are some links you should read up on.
http://forum.xda-developers.com/showthread.php?t=923712
http://forum.xda-developers.com/showthread.php?t=1227807
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
brodydj said:
try to type this inot your browser:
http://forum.xda-developers.com/showthread.php?t=1150045
aswell as this:
http://forum.xda-developers.com/showthread.php?t=822756
it takes a little longer but i cant fix the links sorry.
So as of now i got i managed to wipe all of the data on my phone and i am in recovery mode, if i click reboot it does the same thing and stays on the boot screen. If i click the mod from the sd card it flashes from the normal model number screen to one saying cryogen mod. It then keeps going back and forth with a flash of a screen that has a bunch of commands on it for about 2 seconds
Click to expand...
Click to collapse
The rom you are trying to flash is for a i500 fascinate. I suggest taking the time to do alot of research before you turn the phone into an expensive paperweight. Read this link!!
http://forum.xda-developers.com/showthread.php?t=921285
K well i ran that rom and it works now but he only problem is i dont have any cell service, do you know how to fix that. I know that you are probably laughing at my mild retardism at this subject but i am a big noob. As for what you said in your previous reply is their an MIUI version for the fascinate from telus because i basically rooted my phone so i could get this rom.
thanks
Update*
i followed the instructions on the link you posted and chose the rom for MIUI I9000 as the one i was going to install but when i istall zip from sd it only says installed correctly and then when i reboot it keeps changing from the sgh-t959d to the galaxy s cyanogen screen
yea your boot looped now. I would run the rom that worked just install the compatible radio and kernal for it and you should get cell service back.
ok thanks i got all my cell service back and i got the MIUI rom to work. Now to just ry to remember all the apps i had
Your welcome...glad you got everything working!
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