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.
Related
THIS THREAD IS NO LONGER RELEVANT AS IT IS FOR A DIFFERENT ISSUE FROM THE PAST... IT GOT BROUGHT BACK TO THE TOP. DONT CONFUSE THIS WITH THE 3E RECOVERY "ISSUE"
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Update from koush:
@clockworkmod Hey all, flashing recoveries through ROM Manager is busted. We hit a bandwidth/CPU quota on Google App engine.
If you are trying to flash Clockwork Recovery for the first time, it appears that a lot of users are having issues over the past 24 hours.
Normally, you would:
download Rom Manager
Click Flash Clockwork Recovery
it will ask for root privelages
you would select the Vibrant as your phone
after it downloaded CWR you would get a successful pop-up....
you could then click on reboot into recovery (and since it was the first time you would go to the stock recovery, click reinstall packages, and THEN you would go to Clockwork Recovery)....
well.... people can't seem to get there now. I am NOT having issues as I already have CWR. However, if you are, please download this file on your phones browser (just so you dont have to mount your phone to your pc.... which you can do if you prefer)
FILE DOWNLOAD HERE: View attachment update.zip
Move this file to the root of your internal memory. If you have any other update.zip file you can just overwrite it, or delete it prior to moving this file over, your choice....
NOW, go back to your stock recovery and press reintall packages.... you should go to CWR, if not, press to reinstall again... still no luck? blasphemy.
With all of that said, I need someone to post that this successfully works (it should, and you really can't lose anything)
I am contacting koush for an explanation of what's wrong....
i will check this out
everytime i boot into recovery and press reinstall packages my just restarts phone and i can't get into clockwork.
You generally have to tell it to reinstall packages twice.
^ that has not been the case for me.. but try it twice if if doesn't work the first time!
Yeah, it may depend on the ROM being run or something, but I've noticed it quite a bit.
yeah, something happened when rom manager updated in the last day where flashing recovery isnt compatable with galaxy s devices anymore. drove me freakin crazy cuz i just dl'ed nero and went to install and couldnt.
thank you again. +10 internets to u.
I started having an issue after flashing eugenes super kernel. I did a.clean install of axura and problem went away.
Powered by Axura
^ the rom would have nothing to do with it.
Koush has fixed this, it was server related.
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW (NORMAL STEPS STILL INCLUDED BELOW). I KNEW THIS WOULD BE A QUICK FIX FOR KOUSH!
As of 10mins ago i was having this problem.
But thanks to this post and installing the downloaded update I'm back up!
Rom manager gave me errors when flashing the clockwork recovery
so had to go to the update.zip and i'm now back!
Dont think rom manager in the market has been updated
[i was coming from a odin[ed] JFD stock.
hope this helps someone else!
Thanks... this works for me :\
I flashed to JL4 and had a freaking wifi boot loop and gotta go back to Eugene's does not brick ROM and found out can't install CWM via ROM manager
I don't know if its supposed to fix it, but even after flashing this Im still having issues with ROM manager. Get an error every time I try to update the recovery. Also, I can't remember the last time fix permissions actually worked (eclair maybe?).
Anyone else feel my pain?
This is a fix, and you trying to update the recovery is no different than those who have issues not even using my .zip....
I updated the op with a tweet from koush. He has a fix on his site too (might as well download it from here though?
I downloaded the new update, still can't get into clock work. When I hit reinstall packages it says ... E: error /cache/update.zip
(bad)
Installation aborted
Sent from my SGH-T959 using XDA App
^^^ I'm having the same problem as well right now.
reinstall off market and it works
I thought I was sunk until an hour of searching found this post. Thank you all so much!
I have after upgrade to K6 the error messeage:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I've try the update.zip from the 1st post,
reinstalled via market
update und select the Vibrant modell
everytime the same...
the phone is rooted via SuperOneClickv1.5.5-ShortFuse
Any help ?
None of this works because none of it addresses the real problem ,3E signature. Way to much trouble to go thru.
^ This thread was created when the Clockwork servers were down... it has absolutely nothing to do with 3e recovery... as that didnt even exist when this thread was created... hopefully others are not confused now that it was brought back to the top.
I didn't update it yet, because the thread was dead.
And to be fair the OP did have this:
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Click to expand...
Click to collapse
Hello,
I tried to recovery my phone by using Odin3 to install the stock 2.1 vibrant rom. I am using the rom from the official sticky about fixing a bricked phone.
Odin3 1.0 did not work and it would always freeze on a process even after trying it over and over again at least 5 times. So, I changed to use Odin3 1.7 which I found a link to on xda. This one installed successfully and went through the whole process and my phone rebooted. When it rebooted I saw the Samsung Vibrant Screen, then the T-Mobile screen then the Galaxy S screen fine like normal. But once it got passed the S screen a black screen would come up and all the button lights stay lit up and nothing happens for hours. I tried installing the rom several times, tried different links to the offical JFD stock rom, but everytime I try to install the same thing would happen. What do you recommend I should do to fix this problem?
wipe cache partitin , factory reset in rrecovery ?
Yes, I did. I wiped cache and data, but it still is is still stuck at the black screen.
Your using the JFD.tar in PDA and 512.pit in PIT and Repartition is NOT checked?
Yes, I made sure it was not checked and It was checked automatically the first time and I didn't realize that odin checks that automatically, so I unchecked it and did it a second time. The phone still gets stuck at the black screen with light up buttons.
I am trying the Eugene's Unofficial Froyo rom right now because what initially bricked my phone was installing 2.2 from Kies and that failing. When that failed I unplugged the phone and got the computer to phone icon screen and could no longer boot, so I went to install the stock rom.
The problem I am having with Eugene's Unofficial Froyo rom I am having now is that I have 0 space for applications and cannot install applicants even after doing a wipe and factory reset. Does this have to do with accidently setting it to re-partition and if so, how can I fix the no application storage issue so that I can install applications?
Thanks
I was thinking he designed this ROM just specifically to help bricked vibrants...I think you just use it as a means to reflash another ROM or back to stock or whatever.
I did what you had phone ! PC.. last night to my wife's phone....left it on that screen and plugged into pc with ODIN open..it showed a COM port so I flashed it like that and it boots right up.
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Hmmm...odin back to eugenes froyo & unmount ur internal sd & format...go ahead and remove ur microsd & sim also...& then try to odin just the. Tar for jfd no pit ...no repartition..try to use ka6 instead of a 2.1..
Sent from Bionix V powered Vibrant
flash back to JFD eclair from bible with 512 pit and repartition ticked .
just for record JFD.zip goes in to pda
ViralCipher said:
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Click to expand...
Click to collapse
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
jmcghee1973 said:
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
Click to expand...
Click to collapse
Yes, I rebooted after applying the disable lagfix, but it booted normally and didn't seem like it was doing the Linda thing....I wasn't sure if it worked or not. How would I know if it is back to using the RFS system?
I tried different roms and I had no luck. The KA6 Rom that flashes via odin installs fine, but it goes to the Recovery Screen the E3 one I think, and when it tries to mount DATA and other partitions it fails to do so, and somethings fail to be wiped. It doesn't boot.
When I run the JFD odin, when it goes to recovery for the first time it has one error where it fails to wipe DATA. Not sure if these are the reasons why I am having problems though.
I formated all partitions including the internal sdcard. Still no luck.
So far the only ROM that I got working is Eugene's 2.2..but I can't install applications with that one.
I tried installing the Bionix V Rom via ClockWork Recovery, but once it begins to Copy Files it errors out with an Error on line 13 and copy's out an error log. I posted a response to the thread about this ROM. I redownloaded to ensure it wasn't corrupted.
*****If you need more information on the EXACT Rom I installed prior to the brick here is the thread to the rom I installed. Maybe that will help you help me more ******
This is the rom I had before attempting to upgrade to Froyo:
http://forum.xda-developers.com/showthread.php?t=791478
I installed the Stock Recovery version.
Edit: I know this rom above is a kernal mod. I did flash the stock Vibrant kernel prior to installing the JFD ROM from this link: http://www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
bartek25 said:
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
Click to expand...
Click to collapse
When I install the JFD with or without repartition I get passed all the boot screens, but it screen goes black and buttons light up..Sorry if I am being a noob and missing something obvious...but I followed those instructions, and I did it multiple times as well.
FIXED!!!
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Ahhh see lagfix didnt disable..glad you got it working..
Thanks for your help. I now am using the Bionix-V Rom with the Dragon-Kernel Voodoo and let me tell you I love this phone even more now with this Rom. Loving the Gingerbread theme and it runs super fast. Stock is too slow for me lol Anyway, this is resolved no more offtopic posts lol...
ViralCipher said:
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Click to expand...
Click to collapse
would you please tell all the steps you did to make it work
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
I install the clockworkmod for set up the GTAB rom...
but now i want to return to the stock recovery...so how to uninstall clockworkmod?
thanks!
savage,
You install CWM to replace the stock recovery. Therefore, you have to re-install the
stock recovery. If you were using a stock rom like say 3588, you would just reinstall
the rom again and let it overwrite CWM.
But since I don't know what rom you are using, you need to check the source of
your rom, make sure it contains the stock recovery -- and then inquire of the issuer
of the rom whether or not you should re-install or do some other special procedure.
Rev
thanks！ Now i am using the VEGAn-Tab Build rom~
so what should i do next?
sorry for the confusion~
GTAB ROM is not granular enough - you running stock or a modded ROM? If so, which ROM?
I can reply for TNT Lite 4.3.0+ or gADAM 1.3.0+ - there's a script setup to go back to standard recovery. If you are running either of these, please see my first posts on those ROMs for instructions on what to do. Again, this is only if you are running TNT Lite or gADAM.
You can also attempt to flash standard recovery using a build 3588 standard recovery firmware image in PART3 here: http://forum.xda-developers.com/showthread.php?t=1005080
savage,
EDIT: roebeet answered you first so I'll just stand by and see what y'all do.
Good luck!
Rev
thanks！ Now i am using the VEGAn-Tab Build rom 5.1.1~
so what should i do next?
sorry for the confusion~
problem with installing CWM
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
yu203964 said:
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
Click to expand...
Click to collapse
If you got your tablet yesterday, then it probqbly had firmware 1.2.4349 on it, which is a 1.2 bootloader firmware. You tried installing a CWM made for a 1.1 bootloader. how much research did you do prior to modding? Seeing as you installed Z4root, I'd imagine that you didn't do much, as it's not needed at all to root your G-tab.
go to http://viewsonic-gtablet-for-dummies.webs.com/ and start reading at "START HERE" to get an idea of what your dealing with, and what you can and can't do...look through the entire site!
to get out of where you are now, and back to a workable base, follow the "CODE RED" instructions here: http://viewsonic-gtablet-for-dummies.webs.com/
Lastly...don't do anything else silly until you've read and understand all of the instructions on Goodintentions site...it's a GREAT resource and should be a pre-requisite for all new G-Tab owners.
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
This may be placebo more than anything, but when I was having problems, I went back to the EB01 stock with atlas as opposed to DL09 and then rooted manually to rooted stock using super one click before flashing the fixed CWM. Things worked great after that.
Also, if all else fails, flash CM7 7/4 and then upgrade from there... even though 7/17 should be fine, 7/4 was considered the jumping off point for a while.
pmanliu said:
Hi All, first time poster, long time lurker.
I previously had CM7 installed on my fascinate and that was the first time I ever rooted so it was a tad buggy and there were two CWM recoveries (JT’s red 2.5 & CWM 4.X fixed for CM7) installed. To get to JT’s I did the three finger salute, and to get to 4.X, I used long held the power button in CM7 and rebooted into recovery. Anyways I decided to right my wrongs and flash CM7 from scratch. I followed these instructions to the letter (started with Post #2 then moved onto post #1) ([http :// w w w .fascinateforums. c o m/forum/fascinate-rs-guides/2961-how-upgrade-cyanogenmod7.html[/url]) [sorry could not post links... please edit spaces for it to work], multiple times, and could not get it to work. If anyone could shed some advice, it would be greatly appreciated.
A brief overview of what I did.
1. Phone had CM7 Installed, w/ CWM4.0.1.0 and JT’s Red CWM 2.5… decided to reflash from the very beginning.
2. Downloaded DL09 & Atlas v2.2 PIT as defined in Post #2 in the instructions provided in the previous link.
3. Used odined, put DL09 in PDA, Atlasa v2.2 in PIT, checked off re-partition, and Started Odin. Success.
4. Did not turn on the phone, instead connected into Odin immediately after and flashed CWM4 that was fixed for CM7. Success
5. Used three finger method and got into blue CWM4.0.1.0
6. Wiped data three times… wiped cache three times… wiped Dalvik three times.
a.Note: While wiping data, it did not allow me to wipe “datadata” and skipped that part
b.Note: While wiping Dalvik, it said that it had wiped dalvik but the line to it mentioned a path not being found..?
7. Flashed the 7/17 build. Now the trouble begins…
a.Recovery says “Checking status of bml/mtd” then “installation complete.” Phone reboots into the SAMSUNG splash screen then to the SAMSUNG & CM7 splash screen. It never makes it to the skateborder screen and is just stuck on the SAMSUNG & CM7 screen.
b. How long am I supposed to wait here? I waited 10 minutes and it was still stuck… so I just battery pulled. Phone is restored to stock now (using steps 1-2).
I tried this method at least 3-4 times and it always gets stuck on the Samsung & CM7 Splash Screen and just stays there… I am probably doing something wrong but can’t catch it.
I also another method. In step 5, I also went to mount/storage in recovery and wiped /system in addition to wiping data/cache/dalvik. Afterwards I flash the 7/17 build and instead of it being stuck in Samsung & CM7 splash screen it was stuck in an infinite bootloop from SAMSUNG -> SAMSUNG & CM7 -> Recovery (for a quick second) and back to SAMSUNG. When it loops back to recovery it quickly says “Can’t mount” then “installation aborted” and then continues the infinite loop to Samsung => Samung/CM7, etc…
Currently i followed steps 1-2 above and got the phone back to stock and have been using it ever since like that. I miss CM7...
Any help would be greatly appreciated. This forum has provided a plethora of wealth, and I would love to contribute back one day.
Many thanks,
Pat
Click to expand...
Click to collapse
In step three of your post you have to fully reboot after flashing dl09 with the atlas pit file to convert all your files back to rfs before trying to install cm7...by pushing the dl09 w/atlas pit and not rebooting youre not fully completing the dl09 install so pretty much you just needed to reboot fully after flashing dl09 thats all.
If your sitting on a running dl09 now, then just do everything you did before minus the atlas pit and dl09...basically flash recovery...boot immediately into cwr and flash the same build using your same method...you probably won't have the data/data wiping problem anymore either!
Edit..you can also try the previous posters instructions as they have worked for me as well in fact every time I have to go back the eb01 file is what I use but most have no trouble with dl09
Sent from my SCH-I500 using XDA App
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
izzjkjoe said:
OMG im having the exact problem and for me that eb01 install did no difference i was also Stuck on SAMSUNG & Cm7 and by the way there is no 7/04 build because JT updated his site and there is none left
Click to expand...
Click to collapse
Have you tried booting up the phone after the initial first two steps (PDA +atlas 2.2 Pit)?
I'm at work and have not been able to try anything yet... will do when i get home in a hour
I have tried full reboot after flashing DL09 and it still doesnt work... gets me into a boot loop again. It did fix the wiping datadata issue but no luck with CM7...
I also tried EB01 without any luck.
Additionally i tried JT's 2.5 CWM (Red) and also a newer CWM 3.x...
none of these work. This is day 3 of my rooting problems... thanks for the replies, any more advice would be greatly appreciated...
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Just saw your post. Will give it a try now.
When i'm in a bootloop and it hits the recovery part of the loop, i was able to get the error message (via using a camcorder lol)
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
hope this helps,
many thanks
patrick
-----
edit:
tried your method to the dot. I get stuck on trying to flash CM7. Now instead of boot looping it just says
E: Error in /sdcard/cm7new/update-cm-7.1.0-fascinate-kang-0717-signed.zip
(status 7)
installation aborted.
i'm redownloading the update and will see if replacing it on the sd card will work. Otherwise...
-----
redownloaded & replaced the cm7 zip file on SD card. No success.
No luck w/ your method posted either...
Oi...
this is upsetting
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
efan450 said:
Download the recovery in the cm7 thread and repeat the same steps but use the recovery from the cm7 thread instead of 3-30 fix all and that should work
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
------
edit:
okay i decided to flash MIUI fascinate 1.7.15 instead of CM7 and see if that works.
Well MIUI is running, but the weird thing is i still get SAMSUNG/CM7 boot screen before the MIUI boot screen comes up...
i am so confused!
I went through that same nightmare trying to install MIUI. CM7 or MIUI would give me status 7, and sometimes CM7 would go through, but just bootloop like you mentioned.
I tried about everything, and the only thing that worked for me was to first flash the 7/4 CM7 release for CWM 4.x, then flash MIUI over that. With any luck, the same will work for you for newer CM7 releases.
Unfortunately, like someone mentioned, the file was removed for some reason or another. I've still got it, so I reuploaded it for you, but jt, if there was some particular reason it was removed, say the word and I'll delete this copy. Otherwise, it's probably best to keep it up for people with this issue.
So basically, wipe data/cache/etc., flash the 7/4 CM7 release. Get that running, then reboot into recovery from CM7. Don't use the three-button method. Then wipe again, and flash the zip for whatever release you want.
mediafire.com/?u1n0wcqbwpuvts2
Download that file and flash that...it's how I got in to cm7 for the first time from eb01...if you are still on miui you can flash this with the blue recovery, wipe all and install
Sent from my SCH-I500 using XDA App
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
pmanliu said:
Many thanks to both your help! It has been of great assistance.
I downloaded the CM7 file posted, and will flash tomorrow. MIUI is running on it's first shot, and i'm entranced by it (for the time being).
However i am liking CM7 better, although both have many similarities
Click to expand...
Click to collapse
No problem, glad to help. If you end up flashing it, give us an update. Hopefully it'll work that way.
I used Cyanogenmod for a while back when I was more into stock ROMs. On different devices, though. It wasn't bad. But I flashed MIUI a few days ago and haven't looked back since. It's a great ROM. MIUI or CM7 is your choice, and I haven't used CM7 enough to say much about it, but MIUI has my full support. I never thought I'd switch from UKB so easily.
efan450 said:
Try it again and record your steps exactly and post them and I'll try and see what went wrong...it could just be a corrupt download of one of your files or just a simple missed step. What build are you on and what rom are you trying to go to?
Edit: this is what I have done multiple time without a hitch
regardless of what build and rom your on..
-pull your battery
-odin official vzw EB01 (pda button only..just a reminder) and the atlas
2.2 pit file and check the repartition box (I use odin v.1.7, but it shouldn't matter) and let odin do it's thing
-install battery and fully boot and let it sit for a minute our two after it loads
-pull battery
-odin recovery jt's 3-30 fix all... (found in nitsuj's sticky in the development section under recoveries)
-insert battery
immediately three finger boot into recovery and wipe everything
-flash newest cm7 build..I can't remember the date (I used the 7/4 build to get on to cm7 but it has been removed but the latest on will work)
-reboot fully
-use power button menu and select reboot..recovery to get to new blue recovery
-Flash newest cm7 build (if applicable), gapps and or mtd kernel if desired without wiping
-reboot, and enjoy cm7
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So you never used jt's cm7 fix odin package?
Nope..I was able to go to cm7 with cwm3-30 fix all with no problem and I was able to go to it from otb's 3.x.x.x recovery...either way I've been back and fourth a few times but never had to use the 4.x.x.x. fixed recovery...maybe I'm just lucky but I know a few others have had success with those recoveries as well...you just flash it like normal...wipe everything and install the 7/17 build...reboot...and just make sure if you want to flash gapps or the glitch kernel you use the power button menu to reboot recovery...no three finger booting anymore.
Sent from my SCH-I500 using XDA App
Solution
pmanliu said:
Did that... just goes back into the bootloop from recovery => SAMSUNG => SAMSUNG/CM7 (not the skateborder screen) and gives me this errorr:
-- Installing
Finding update package
E: unknown value for path []
E: Can't mount
Installation aborted
Click to expand...
Click to collapse
I was getting the exact same thing.
Started after I flashed the glitch v12 kernel on top of nightly #29. No problems.
Then I used ROM Manager to download nightly #35
Rebooted into CWM 4.0.1.5 orange via power button
Navigated to CWM folder to find nightly #35 to install from zip
Selected to install, checked for BML/MTD, said complete, auto rebooted
Boot loop with the above quoted errors, never gets to skateboard logo
Tried adb solutions, not enough time to issue adb commands before reboot
three fingered into cwm4 dark blue, got the usual expected E: can't find errors
tried restoring nandroid backup, auto reboots, no change, same errors as in quote
three fingered into cwm4 dark blue, tried flashing nightly #35 from RM download, no change
3fgered back into cwm4 dblue, flashed nightly #29 from SD that I had previously direct downloaded from cm7 nightly website, phone checked bml/mtd status, auto-rebooted, completed install.
Phone booted up normal with cm7 kernel, nightly #29, Data had been wiped
Used power button to reboot into recovery 4.0.1.5 orange
restored nandroid backup, rebooted
all is good! bazinga.
What I've learned from this is that using ROM Manager to download nightlies is risky. It may work fine if you use ROM Manager to download, wipe, and install, but if it fails during any of those (which it seems to do frequently) you could be out of luck with a headache. Best practice seems to be to download nightly directly from the cm7 website or copy it from your computer to the SD card and reboot via the power button into recovery and install that known good copy you downloaded via the cm7 website in the browser or transfered from your computer to the SD card. ROM Manager does something weird. This has occurred to me 3 separate times with ROM manager and with different nightlies. Also, it is worth noting that jt does not support the Glitch kernel for use with CM7 nightlies and a lot of issues seem to stem from using it. It is amazing when it works, but seems to add a lot of risk. YMMV
Let me know if this has helped or if anyone has any questions. Sorry for it being long, just trying to be thorough as there was no info out there to help me when this happened so I hope I can be of help to someone else.