Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
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
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J
ok i was running com rom 1.2 then decided to try out the evil rom. so i did what you do normally and wiped everything. then when i flashed the evil rom everything force closed and would not save any setting so i went to re-wipe and noticed that now i'm unable to wipe datadata.
i'm pretty sure thats the problem so i've odined back to a stock ed01 which was suppossed to wipe all data and i wiped my sd card also then went to start all over and bam same crap happening. i also odined a new cwm and same crap again any help would be great cause i'm now lost
church101 said:
ok i was running com rom 1.2 then decided to try out the evil rom. so i did what you do normally and wiped everything. then when i flashed the evil rom everything force closed and would not save any setting so i went to re-wipe and noticed that now i'm unable to wipe datadata.
i'm pretty sure thats the problem so i've odined back to a stock ed01 which was suppossed to wipe all data and i wiped my sd card also then went to start all over and bam same crap happening. i also odined a new cwm and same crap again any help would be great cause i'm now lost
Click to expand...
Click to collapse
Place one of these packages on your SD card and flash it from recovery: http://forum.xda-developers.com/attachment.php?attachmentid=605463&d=1306198028 or: http://forum.xda-developers.com/attachment.php?attachmentid=605464&d=1306198028 The first link is if you are running a voodoo kernel. The second link is if you are running a non-voodoo kernel. Since you were using CR I'm assuming you were on voodoo and therefore you need to flash the first package. This is better than wiping.
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.