Related
I have a huge problem.
I rooted my wife's (yea...my wife's...) Fascinate last night. The root method I used worked like a charm. I installed ROM Manager. Again...no problem. Flashed ClockWork Mod no problem as well. I selected "reboot to recovery" to do a nandroid as I've done on numerous other phones. In fact, ALL of this I've done on numerous times on half a dozen different phones.
When it rebooted, instead of it being in Nandroid, it was in the regular stock recovery. My stomach sank...lol
It would just reboot...that's it. Is there a loop with the fascinate? How do I get out of it if so?
At one point, the phone wouldn't do ANYTHING...all that would happen when I plugged it in was a little computer and cell phone would pop up on the screen. No recovery, no nothing. So, after lots of digging and reading, I found the files here that I thought I'd need to reflash the system using odin. I got the /system file, the kernal and the recovery. I flashed the kernal...worked perfectly. Flashed the recovery...again, perfect (and recovery is back but still in a reboot loop...) When I try the .tar.md5 system file, it says md5 is invalid so I changed it to a straight .tar file and it worked all the way up to the very end, then it stops. That's it.
I just need the phone to work again for my wife. I don't care if I even flash a new custom rom (which I can't fine one of that works!) or if it's just simply restoring the stock system files.
ANY AND ALL HELP GREATLY appreciated, guys. Thanks!!
To get to cwm, you have to select "apply update.zip" from stock recovery. This is how fascinate and a few other galaxy s cwm works. Also don't ever delete the update.zip file from sd card.
But to start out....
Step 1: Start with Odin:
http://forum.xda-developers.com/showthread.php?t=782204
A. Flash system and pit together
B. Flash kernel
C. Flash recovery
*Important note: in Odin, always use PDA!!!! Using phone will cause huge issues.
Step 2: Flash cwm:
http://dl.dropbox.com/u/458252/CWMrecovery.tar
*note: this is an Odin file, again flash using PDA
Your phone will end up stock, rooted and with cwm.
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Rooting aside if you want to just fix it, I can help you with that. Nothing more though. Interested?
Sent from my SCH-I500 using XDA App
rmp5s said:
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Click to expand...
Click to collapse
What do you mean for the "stupid fast replies"?
tats_06 said:
What do you mean for the "stupid fast replies"?
Click to expand...
Click to collapse
I think he means that your replies were just as fast as geeknik's kernel. The only other interpretation is that although your replies were quite quick, unfortunately they were also stupid. But thats obviously not true, so it must be the former. ;-P
Sent from my SCH-I500 using XDA App
I think some of us are showing our ages, "stupid" is the new "awesome."
Sent from my SCH-I500 using XDA App
Hey dont worry i had same problem
http://www.mobilephonenews.info/and...fascinate-restore-is-it-really-that-easy.html go here and follow instructions!!!
then update phone manually to get latest update!! might take a few times or many times because it failed to get update many times but eventually youll get it!!
goodluck
Sherwood, in his case he needs all Odin files, not just system.
Fallingup was first to put this up, credit to his post!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin%...in3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin%...System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin%...covery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin%...00-VZW-pit.pit
Yea...I mean it's almost stupid how fast I got good, meaningful, educated replies.
In other words, you guys kick ass. Thanks again!!
similiar issue, please help me out.
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
aabfalter said:
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
Click to expand...
Click to collapse
sam problem here, i can get to cwm recoery and thats it. someone please help
justin94 said:
sam problem here, i can get to cwm recoery and thats it. someone please help
Click to expand...
Click to collapse
I had the same problem when I flashed the non-voodoo over voodoo and spent hours trying to fix the boot loop. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=782204 but still running into the boot loop (recovery mode) then I flashed with the file from here via ODIN http://adrynalyne.us/files/kernels/DI01package3.tar.md5 and it restored my phone back to factory. From there you would have to do the root procedure again. Hope this helps.
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
The update.zip to get to clockwork??
http://sharesend.com/g2jbl
First time I've ever hosted a file so let me know it if works lol.
Sent from my SCH-I500 using XDA App
This could be one of the rosiest phone ever to unbrick, unless you are a noon of coarse.
Sent from my DROIDX using XDA App
tswtech2 said:
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
Click to expand...
Click to collapse
There is no update.zip method to unbrick. You will need to re-download a working copy of Odin or figure out how to make Odin work to do a factory restore with it.
Download the di01 complete package and use pda in odin to restore it.
http://forum.xda-developers.com/showthread.php?t=867648
borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?
Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.
thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet
no problem. it should work out good.
mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!
BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help
mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def
Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..
I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App
You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App
adrynalyne's di01 odin package covers a multitude of sins.
upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
I'll give that a shot, thanks!
Sent from my HTC Glacier using XDA App
k20matt said:
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
Click to expand...
Click to collapse
IT WORKED! Thanks again!
How did it work? Share what you did.
Same thing happened to me yesterday.
Check the clockwork/download/mirror1.kanged.net/recoveries folder on your SD card. Is there a .img file in there called recovery-clockwork-2.5.1.4-glacier.img? If it's not in there that's why you can't flash it, because it can't find the file.
Not sure why the file was missing from the folder.. but thats what it turned out to be.
You should be able to download the image from: http://phones.crackflashers.com/glacier/recoveries/glacier-cwm3src-2.img
Or you can get the file already named correctly out of this zip: http://goo.gl/nZJ7U
But you'll have to dig for it to find it.
then rename it to exactly "recovery-clockwork-2.5.1.4-glacier.img" and put it in the folder. It should work then.
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
OptLynx said:
How did it work? Share what you did.
Click to expand...
Click to collapse
I just flashed ice glacier, went to rom manager, select all clockworkmod recoveries, select 2.5.1.4, and that's that
Sent from my HTC Glacier using XDA App
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Well I had the problem and went through the steps i described above to get it to work... So not sure.
Oh and it didn't say no legacy recoveries found, it said there was an error trying to flash. But it's working fine for me now after I out the img in that folder... so up to you guys if you want to try it.
Sent from my HTC Glacier using XDA App
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
its not just you, everyone is getting this error. Youll need to flash cwm 3 through fastboot or terminal emulator if you want to go to CM7 or MIUI until TrueBlue_Drew gets it fixed and releases an update.
Skunk2 DC said:
IT WORKED! Thanks again!
Click to expand...
Click to collapse
No Problem. Glad it worked. it was the only way i knew.
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Actually I am not sure what you are talking about OptLynx. What shortsloolbus said is 100% correct. If you are missing the image or it is in the wrong place it does not give you the "no legacy recoveries found" error. It will just say "error flashing recovery". And the reason it worked when people switched to a old Ice glacier rom is because IG isnt running the latest Rom Manager that has now changed the location of where it keeps the recovery images.
See my thread here for the new zip that places everything in the correct place. http://goo.gl/O5SlI
Whats up guys I have a Sprint Tab. It's not working anymore.
First off, I'm not an expert, or even half way expert. But I do follow walk through instructions well.
Initially, I was using the tab with GB 2.3 rooted and pretty much stock.
After a while I decided to put Cyanogenmod on it to improve my tab experience. It worked for about a month and a half, and then I ran into some problems with it. It started to reboot and get stuck at the boot screen and got no further. I tried upgrading to a newer build of Cyanogenmod but that kept getting stuck too. After trying different builds and a whole bunch of other things I realized that it wasn't going to work.
I figured it was an issue with Cyanogenmod and CWM.
Anyway, I decided to sell the tab and get a Galaxy S3 so I wanted to return it to stock.
I tried Heimdall one-click and Odin to get it back to stock. Guess what? No success.
The Tab initially had the Sprint Splash screen. And it is sitting here next to me stuck at the samsung screen just looping. Pretty useless.
What is the problem? Again I am far from an expert, I do NOT know what to try next.
Any suggestions?
Hey,
Your Tab did not work after new build is probably because of incorrect 'upgrade' procedures. The early CM9 build was based on a non-MTD partition system. The later build is based on an MTD partition system. You would need to restock to GB 2.3.3 going from a Non-MTD to an MTD rom.
Now that you want to re-stock, you will need
CDMA stock ROM 2.3.3 (preferable than the 2.3.5 or 6)
correct .pit file
dbdata.rfs
Flash the CDMA stock ROM while re-partition with the .pit file you have. (re-partition is a MUST going from ICS back to stock 2.3.3).
Once you are done flashing and re-partition, do a factory reset data wipe, cache wipe, dalvik wipe. see if you can do those successfully. If you get a mounting error message (most likely you will, and you will still be stuck at SAMSUNG boot loop), proceed.
Flash separately a dbdata.rfs from the CDMA stock rom you have (extract it from the ROM package and create a separate .tar for flashing or you can search in XDA). Reboot back to recovery and do another all wipes. This should take care of your problem (Hopefully).
you can do all those using heimdall or ODIN.
I hope this helps.
ill try that, thanks. But one thing.... I know you said improper installation of CM9 could cause this. But how come out of the blue it happened and not the first time I did the installation of it?
I definitely remember all the steps at least 9-10 times before I did the upgrade. So I don't think I missed anything at all. Maybe I did, maybe I didn't .
Not sure what to make of it.
ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?
throwback1718 said:
ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?
Click to expand...
Click to collapse
Try this. Follow the link provided.
http://forum.xda-developers.com/showpost.php?p=27096519&postcount=2
Make sure you tab isn't plugged into a dock, u had major problems trying to flash that way. Sometimes u can't even have it plugged into a charger.
Sent from my ADR6425LVW using Tapatalk 2
Hey guys,
Every time I try flashing a different rom via TWRP, I keep getting an error that says "unable to open zip". I've tried 3 different roms and I am getting the same error. I've even tried using CWR and it's the same deal. Can anyone lend a hand?
Checksum
Start with the basics. Download the app md5 checker and verify that your download is %100 perfect.
Klark_Kent86 said:
Hey guys,
Every time I try flashing a different rom via TWRP, I keep getting an error that says "unable to open zip". I've tried 3 different roms and I am getting the same error. I've even tried using CWR and it's the same deal. Can anyone lend a hand?
Click to expand...
Click to collapse
Couple questions......are you downloading the zips via phone or computer? Also, are you trying to flash these from the internal storage or ext sd card? If you are trying to flash via internal storage move them to ext sd card and try flashing.
Klark_Kent86 said:
Hey guys,
Every time I try flashing a different rom via TWRP, I keep getting an error that says "unable to open zip". I've tried 3 different roms and I am getting the same error. I've even tried using CWR and it's the same deal. Can anyone lend a hand?
Click to expand...
Click to collapse
Have you renamed the file? I found that renaming the file can break the md5 checksum. If that is the case try renaming the file to something simple with NO spaces in the name. This has fixed a few backups that were not working for me. Good luck. Don't know if this will help.