Ok, I am currently using the Samsung Galaxy S Fascinate from Telus. I did some research and i figured I might as well root it. I did that successfully and that's where i should've stopped. I thought I was able to download the mod CyanogenMod but that was a failure. I have no idea what any of the technical terms mean (modem, kernal, how to open random files ie .tar, .rar .md5, flashing, etc). I tried to follow the Guide on http://forum.xda-developers.com/showthread.php?t=923712. I got to step 5, and tried to download the .exe file but then installation failed. I am able to get into download mode and recovery mode but my phone won't reboot past that. Did I just break it..? Any help is appreciated but small simple steps are also appreciated
i'm looking to do the same thing but i'm not sure if i should be flashing the initial ROM (or where to find it) or a nightly
i'm no expert for sure but it sounds like you aren't totally screwed if you can get to recovery or download...not sure if you can just try reflashing the ROM (.zip)again from recovery in order to fix the problem (don't see in the guide where to use a .exe) but you can at least recover to stock using odin...just use step 2 in that guide...again no expert but this is what i have sorted out reading around here trying to figure out how i want to proceed
I have tried many things and yes sorry, the CM I used was in a .zip file, not .exe, my fault. I have attemped to go back to stock mod using that step 2 and those files provided but everytime odin fails. It's looking bad.
StruggletoSucceed said:
I have tried many things and yes sorry, the CM I used was in a .zip file, not .exe, my fault. I have attemped to go back to stock mod using that step 2 and those files provided but everytime odin fails. It's looking bad.
Click to expand...
Click to collapse
You should at least be able to go back to STOCK ROM by following Step 2.
If you are failing in ODIN, make sure the files were downloaded correctly. Using 7zip, try to view the files to verify they are OK. Also, be sure to place each file in the correct section.
Good luck!
Unfortunately, it still fails. 7zip says everything is fine but there is one thing i noticed, the file I'm supposed to place into the "phone" slot is under a WinRar file whereas the rest are a .md5 (or .pit in pit). Would this be a problem.. and how would I fix it?
StruggletoSucceed said:
Unfortunately, it still fails. 7zip says everything is fine but there is one thing i noticed, the file I'm supposed to place into the "phone" slot is under a WinRar file whereas the rest are a .md5 (or .pit in pit). Would this be a problem.. and how would I fix it?
Click to expand...
Click to collapse
Err.. if the file is a .rar, you need to uncompress first!
Odin only takes .tar or .tar.md5 or .pit files !!
Hmm.. fail. How would I uncompress a WinRar file?
The file name ends in .tar but when I go to properties, the file type says WinRar..
StruggletoSucceed said:
Hmm.. fail. How would I uncompress a WinRar file?
The file name ends in .tar but when I go to properties, the file type says WinRar..
Click to expand...
Click to collapse
I use a free program called 7Zip. It's best, IMHO. It can uncompress/compress lots of different formats.. http://www.7-zip.org/
Once you have 7Zip installed, find the file with Windows Explorer, then right-click the file and select "Open Archive".. if you can view the contents, then that means the file is good.
Which file are you having problem? If the file already has .tar extension, then you don't need to uncompress. Only do so it's a .zip, .rar or .7z
Thank you for telling me to use 7Zip. I was using WinRar before and that automatically changed a file into an extension Odin couldn't use. So now I have all my files in eaither .tar or .md5 but Odin is still failing at
<ID:0/007> cache.rfs
<ID:0/007> modem.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Everything is in the correct box and Odin is opened before I plugged in my phone
StruggletoSucceed said:
Thank you for telling me to use 7Zip. I was using WinRar before and that automatically changed a file into an extension Odin couldn't use. So now I have all my files in eaither .tar or .md5 but Odin is still failing at
<ID:0/007> cache.rfs
<ID:0/007> modem.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Everything is in the correct box and Odin is opened before I plugged in my phone
Click to expand...
Click to collapse
I have a Fascinate, but ODIN should work the same. I just downloaded the .zip file you mentioned in your 1st post and unzipped and checked all the files. They seem OK. Have you verified each file is OK?
Do you know which file is it failing? Also, the ODIN included in that .zip file is quite old.. only V1.0. Try this version v1.83 (uncompress first).
Also, did you check the "Repartition" checkbox in ODIN? And put the .pit file in the PIT section?
You sir, are my hero. This is the first time I've seen my home screen in a week!! I would hit that thank you button a thousand times. Although it did delete my Titanium Backup and unrooted my phone, it works!
Any advice towards if I attempt to "flash" a new Mod again?
Would the fact that I tried to flash CM7 (which I understand is Gingerbread) and the kernal it has me downloading is Froyo be a factor? Where would I get a replacement kernal?
StruggletoSucceed said:
You sir, are my hero. This is the first time I've seen my home screen in a week!! I would hit that thank you button a thousand times. Although it did delete my Titanium Backup and unrooted my phone, it works!
Any advice towards if I attempt to "flash" a new Mod again?
Would the fact that I tried to flash CM7 (which I understand is Gingerbread) and the kernal it has me downloading is Froyo be a factor? Where would I get a replacement kernal?
Click to expand...
Click to collapse
I'm so glad I could help! That image you flashed through ODIN is the stock, so it's probably not rooted.
Now that you know how to restore to original stock, you can experiment more. But always remember to read the instructions carefully..
Installing CM7 is a bit more complicated, specially for people who never done it before. I'm not even sure if CM7 or other MTD based ROMs can be installed on a Telus, but I'll do some research. I'm running JT's vanilla Gingerbread myself and it's a great ROM. If you want, I'll tell you how tomorrow..
Well thanks to you, I successfully installed CM7 on my telus following this new guide - http://forum.xda-developers.com/showthread.php?t=1115090 - (with a couple restoring back to original), the only problem now is that i'm unable to get service. It says if I can't then just flash back to original and try again. I did that a few times but same outcome, no service (or 3g). I also noticed my home button no longer works.. that might be a problem too but I'm sure it's just a bug. Any extra assistance is always appreciated!
StruggletoSucceed said:
Well thanks to you, I successfully installed CM7 on my telus following this new guide - http://forum.xda-developers.com/showthread.php?t=1115090 - (with a couple restoring back to original), the only problem now is that i'm unable to get service. It says if I can't then just flash back to original and try again. I did that a few times but same outcome, no service (or 3g). I also noticed my home button no longer works.. that might be a problem too but I'm sure it's just a bug. Any extra assistance is always appreciated!
Click to expand...
Click to collapse
Did you wipe Data & Devik Cache when installing CM7?
In my experience, sometimes, you can fix the Wifi/3G issues by toggling Airplane mode, wait a bit and try again. You don't have service at all or is the signal icon just white instead of green? Also, maybe try 1st with just installing the stock CM7 without the glitch kernel..
Yes, i wiped my system, dada and cache (which the instructions said). Toggling airplane mode didn't fix anything unfortunately. When i looked into mobile services available, my phone can only pick up a rodgers signal (which my sim card cannot not connect to it for obvious reasons). Once I downloaded CM7, the guide says that CM7 has a default kernal already in place so i believe i don't have the glitch kernel running. My screen shows 3/4 white bars but no signal or mobile internet.
StruggletoSucceed said:
Yes, i wiped my system, dada and cache (which the instructions said). Toggling airplane mode didn't fix anything unfortunately. When i looked into mobile services available, my phone can only pick up a rodgers signal (which my sim card cannot not connect to it for obvious reasons). Once I downloaded CM7, the guide says that CM7 has a default kernal already in place so i believe i don't have the glitch kernel running. My screen shows 3/4 white bars but no signal or mobile internet.
Click to expand...
Click to collapse
you may need to flash the stock TElus modem back...some of the guides here have a link to the file in it...srry don't have a link to it
moosehead11 said:
you may need to flash the stock TElus modem back...some of the guides here have a link to the file in it...srry don't have a link to it
Click to expand...
Click to collapse
That would make sense but once i install CM7, if I go into recovery mode my power (aka enter) button doesn't function so once CM7 is flashed, i can't flash anything from there.
StruggletoSucceed said:
That would make sense but once i install CM7, if I go into recovery mode my power (aka enter) button doesn't function so once CM7 is flashed, i can't flash anything from there.
Click to expand...
Click to collapse
You can still boot into CWM, but either using ADB, type: adb reboot recovery on a command prompt, assuming you have ADB working..
If not, another way to get into CWM is by using ROM Manager, which is included by default in CM7.
Like I said, I have a Verizon Fascinate, so I don't really know anything about a Telus Fascinate.
Best of luck...
neozen21 said:
You can still boot into CWM, but either using ADB, type: adb reboot recovery on a command prompt, assuming you have ADB working..
If not, another way to get into CWM is by using ROM Manager, which is included by default in CM7.
Like I said, I have a Verizon Fascinate, so I don't really know anything about a Telus Fascinate.
Best of luck...
Click to expand...
Click to collapse
would any stock telus modem (where ever i would find one) work properly on CM7 or would there be a certain model/version that's needed? I'm so close to getting this >.<
StruggletoSucceed said:
would any stock telus modem (where ever i would find one) work properly on CM7 or would there be a certain model/version that's needed? I'm so close to getting this >.<
Click to expand...
Click to collapse
OK. Here is the thing.. As far as I know, CM7 doesn't flash a modem, so when you restored to stock TLJL3, that's the modem that you still have. You can verify by going into Settings, then About Phone. The Baseband version is your modem version. What does it say? What about the Kernel? What's the kernel version? And what version of CM7 did you flash? is it the latest nightly?
Also, when you flashed CM7, you didn't flash another kernel right?
Last thign, although unlikely, I've heard people here having success after reflash CM7 again, after wiping DATA and Dalvik cache..
I've attached the TLJL3 Tulus modem here just in case, flash it in CWM
Related
This thread has a similar issue to what im having, but ive branched off elsewhere...
http://forum.xda-developers.com/showthread.php?t=883944&highlight=Rom+Manager+partition+recover
The story: Ive had a rooted vibrant for a while. Im no linux noob, either. I was having some issues so i decided to try Darky's Toxic rom...worked GREAT! I made a clockwork backup...now i felt it safe to start to play.
I was having media scanner issues...so i decided to repartition my storage spaces (and to get rid of the avatar movie)...but i used ROM manager...clearly by mistake. whoops.
So after MUCH trouble with boot looping...i was able to ODIN to Eugene's Froyo that doesnt brick. The STOCK rom wouldnt give me video...just hung after the Galaxy S boot seq. Im assuming thats a voodoo issue?
Anyway...able to get Eugene's on there...and i was smart and made a back up of both storage spots. I reloaded CWR, and tried to restore to the backup of Toxic i made with no luck. Matter of fact, i cant get any other ROM to load that ive tried.
Any suggestions to get my restore point back up and running? I thought about trying to go stock...but like i said, i couldnt get to stock through ODIN.
Couple of Ideas........ I am assuming you can get into download and recovery.
If you can get into recovery, clear cache, wipe dalvik then, pull battery and get into download, then try odin back to stock, remember to check repartition.
Or try Heimdall, sometimes it works when Odin does not. But if you can get into download then, there is a way (or some combo of ways) to get you back to stock. Just be patient and logical......... you will get it..........good luck
I CAN get into download and recovery...and was able to get CWR back on...thankfully.
I have tried every combo of wipes i can think of.
If i flash to true stock 2.1...i get black screen with lit buttons.
If i flash to Eugene's...i can boot into a ROM build with no internal storage, therefore no way to install apps.
I just came across this and tried it...with no new results.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Click to expand...
Click to collapse
I'll try your suggestion now...thanks!
Still no luck. Same thing...black screen, with lit buttons.
Did i officially brick this thing?! haha...i thought it barely possible with the vibrant.
I tried flashing the JI6 rom too....still no go.
Anything?
When you Odin to stock, what tar are you using? When you repartition, do you use the pit file?
I suggest that you use the JFD Odin image and repartition using 512.pit. I have also heard of some people having more success with Odin when they dont have an SD card or SIM card in the phone (this may be an old wives tale.) Good luck.
Same problem
I had this exact issue two days ago and after many attempts with Odin, like you, the only ROM I could load was Eugene's. Re-Partitioning with Odin had no affect, stock wouldn't work and wiping everything had no affect. With Eugene's it would show no space for apps and wouldn't hold any settings if the phone was rebooted. It seems that clockwork mod is actually removing the apps partition and no tool I could find would actually recreate it. I searched quite a bit and found several posts all with the same issue and in every case they had to replace the phone. Luckily I am still under warranty so T-Mobile is replacing it. I don't know if the Clockwork Mod developer has a thread on here, but that "feature" needs some work or it needs to be removed.
kadashti said:
When you Odin to stock, what tar are you using? When you repartition, do you use the pit file?
I suggest that you use the JFD Odin image and repartition using 512.pit. I have also heard of some people having more success with Odin when they dont have an SD card or SIM card in the phone (this may be an old wives tale.) Good luck.
Click to expand...
Click to collapse
Yes, ive used both the vanilla JFD tmo tar, and the JI6 tar. Neither worked. Triend both the 512 and the 513 PIT file. 512 for the first HUNDRED times...then 513 for the hell of it, since at this point, i was getting nowhere.
And thanks pamulli, thats what im basically resigning to..i just needed to hear it from another person.
REMINDER: It is as easy as fat fingering the keyboard to totally screw your phone. Click carefully!
Hello,
I've tried before, and was unsuccessful. I am on a small regional carrier and when flashing MIUI, my 3g or 1x data connection does not work and reception is very very poor due to being on a verizon radio. I have accuired my carreirs ODIN files, but running linux I use Heimdall. However, I've extracted the files and have the modem.bin file. When I flash this over my MIUI ROM, and try to reboot, I get some wiered error where MIUI wont even boot up. I don't remember the error and am at work currently(which is the reason for the spelling errors also, sorry).
My proccess is:
1. Install MIUI from stock
2. Boot and install Glitch V12
3. Flash new modem.bin through Heimdall using Atlas 2.2.1 pit file(a pit file is required correct?)
Am I doing something wrong? Is the correct way
1. Flash Phone to stock with carriers radio
2. Install MIUI
3. Yada Yada
Everything works currently but data, I have to connect to WIFI. Any suggestions for me?
I'm not positive because i'm on Verizon and have never had to do this but I believe using the pit file when you flash the modem is your problem..try doing everything you said in the same order but when it comes to the part about flashing the modem do not use the pit file that is used only when you repartition, so no needed for that
Sent from my SCH-I500 using XDA App
Correct me if I'm wrong(probably am), but don't you have to populate the .pit file portion in order for odin to flash?
Sent me alink to the modem.bin i will prepare a cwm flashable zip for you.
That would be awsome demetris, it'll be about 2 hours before I will be able to do that as I am currently at work. I'll post it up here soon. Thank you
kyleco said:
Correct me if I'm wrong(probably am), but don't you have to populate the .pit file portion in order for odin to flash?
Click to expand...
Click to collapse
nope you don't have to populate the pit section to flash..you just need to use the pda button only, (never the phone button) if you were using an official VZW rom.tar and you wanted to repartition, then you would use the pit section but unless your repartitioning, it's not a requirement for Odin to flash, and would actually cause problems using a pit file with out an official VZW.tar...which is why I think you were having the issues trying to flash a modem with a pit file.
Edit: i'm sorry I just realized the instructions I just gave were for Odin and you're using heimdal...or wait...are you using Odin or heimdal?? I would wait for the previous posters cwm zip, because i'm unsure of heimdal's exact instructions, unless you are using Odin? but I still think your problems stems from using the pit with the modem
Sent from my SCH-I500 using XDA App
I am using Heimdall, and now that I am at my laptop, you do have to load a .pit file in order to add a partion portion(such as a modem) here is the modem.bin file demetris. I really appreciate the .zip file man! I'm hoping this helps me. Now I just need to find a way to push my carriers prl file to my phone so it stops pushing to verizon update.
Demetris, if you know how to make a .zip for a prl file, here is the .prl for my also.
I owe you one for this,
Thanks everyone!
What fascinate you got there, it seems modem is bigger than galaxy s family,
i think is the verizon cdma and i need to know where that modem lies in the partition.
Anyway i made one with the stantard bml12 partition that all galaxy s modems are i hope is the same on cdma
Here it is:
http://www.multiupload.com/AL7IBCDKMB
Flash it with CWM.
If you need an odin one just ask
I've got the version version of the fascinate. I500. I'll give this zip a try. Thanks again
I got into a boot loop and could not stop it. I put it into download mode and tried to odin but the computer won't see the phone. I don't know what else to try. I used odin to go back to stock one time when I had froyo.
Please help!
If you can get into download mode then you're not bricked. Try either a different driver or a different USB cord.
I was able to get into Odin once more. It showed pass and the phone reset but it got stuck at the Vibrant screen. Does this have anything to do with the bootloaders since I was on ICS using Gingerbread bootloaders?
Also, I notice that once Odin starts, the progress bar on the phone goes very fast and finishes in about 3 seconds and the phone reboots. Odin shows passed. This is when it just stays on the Vibrant screen.
m4r10 said:
I was able to get into Odin once more. It showed pass and the phone reset but it got stuck at the Vibrant screen. Does this have anything to do with the bootloaders since I was on ICS using Gingerbread bootloaders?
Click to expand...
Click to collapse
It shouldn't since you can us GB bootloaders with Froyo ROMs. Did you follow N00B's guide and use the stock 512 PIT and JFD tar files provided? I've seen a 513 PIT file that didn't do anything for me, so I'd stick with the 512 version.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Give N00B (and me ) if that helps at all.
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
m4r10 said:
Also, I notice that once Odin starts, the progress bar on the phone goes very fast and finishes in about 3 seconds and the phone reboots. Odin shows passed. This is when it just stays on the Vibrant screen.
Click to expand...
Click to collapse
What files are you using? The flash should take a little over a 1 minute or so since you're applying an approximately 200 meg file (stock file) to your phone.
Grab both those files (.pit and .tar) from N00B's guide and try it.
kaiser_bun said:
It shouldn't since you can us GB bootloaders with Froyo ROMs. Did you follow N00B's guide and use the stock 512 PIT and JFD tar files provided? I've seen a 513 PIT file that didn't do anything for me, so I'd stick with the 512 version.
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Give N00B (and me ) if that helps at all.
---------- Post added at 02:18 PM ---------- Previous post was at 02:14 PM ----------
What files are you using? The flash should take a little over a 1 minute or so since you're applying an approximately 200 meg file (stock file) to your phone.
Grab both those files (.pit and .tar) from N00B's guide and try it.
Click to expand...
Click to collapse
Followed the NOOB guide to the T my man. I'm using the 512 file. I've checked the MD5 checksum of all three files. Now I can get started and see the progress bar on the phone but hangs every time. First a bright green screen and now a blue screen. Odin shows stuck on modem.bin process.
m4r10 said:
Also, I notice that once Odin starts, the progress bar on the phone goes very fast and finishes in about 3 seconds and the phone reboots. Odin shows passed. This is when it just stays on the Vibrant screen.
Click to expand...
Click to collapse
Not trying to be a smarta$$ or anything but I would double check that you pulled out the bootloader.md5.tar from the PDA and put in the correct files to get back to JFD. I agree with Kaiser that is should take 1+ mins to full flash. Bootloader flashes are more like the time frame that you are talking about.
I also think that you may have a bad download if you are applying the correct files. Try the AIO Toolbox in the Dev section. It have the drivers, Odin 1.8 (I think) and the proper Pit/Tar files for JFD. Also the very last post Adamanda posted an earlier version of Odin that you could try too.
m4r10 said:
Followed the NOOB guide to the T my man. I'm using the 512 file. I've checked the MD5 checksum of all three files. Now I can get started and see the progress bar on the phone but hangs every time. First a bright green screen and now a blue screen. Odin shows stuck on modem.bin process.
Click to expand...
Click to collapse
Wouldn't hurt to grab the files from Wood's guide, and make sure to use the new version of Odin.
I'm guessing since you already done an odin flash before you already did this, but maybe try re-installing the correct Windows drivers for the Vibrant:
http://forum.xda-developers.com/showthread.php?t=728929
One thing to note on the drivers (I had to at least) is that you may need to disable Digital Signature Verification in Windows. Get to the Windows Safe Mode Screen (while booting windows, keep pressing F8), then select Disable Digital Signature Verification. Windows can block the drivers otherwise.
Something else would be putting the PIT and TAR files in the same directory you have the Odin executable. Not sure if you still have to, but it was recommended way back when and I still do it to this day whenever I go back to stock.
A last ditch would be running Odin as an administrator, but you really shouldn't have to do that.
All the files have been verified and I click on the pit button and choose the pit file downloaded and then click on PDA and choose the appropiate 512 TAR file. I click start and get into the process. It just hangs at different points all the time. This last time it made it to factoryfs.rfs process and my phone got a blue screen. I'm gonna give a different version of Odin a try.
Kind of sucks but I have heard of this before. Only thing that I can recall is that the user just kept trying to get it to pass and he maybe did it 8 times before it got all the way through. His was like yours and it would hang on different parts in the process here and there. I'll see if I can find that thread and link it for you.
Woodrube said:
Kind of sucks but I have heard of this before. Only thing that I can recall is that the user just kept trying to get it to pass and he maybe did it 8 times before it got all the way through. His was like yours and it would hang on different parts in the process here and there. I'll see if I can find that thread and link it for you.
Click to expand...
Click to collapse
Thanks. I'll keep trying
Should I try clicking the dump box, phone EFS clear box or phone bottloader box? Or will this erase my files?
Looks like you might have a bad download. Try to Toolbox I listed above. Much better than piece-mealing files together. Nice all-in-one package.
Here is that thread btw about being stuck at points in Odin.
m4r10 said:
Should I try clicking the dump box or the phone EFS clear box? Or will this erase my files?
Click to expand...
Click to collapse
NO!!! Don't clear your EFS. Will kill your ability to call or get/send data. Will lose your IMIE and you'll be forced to Odin anyways.
Woodrube said:
Looks like you might have a bad download. Try to Toolbox I listed above. Much better than piece-mealing files together. Nice all-in-one package.
Here is that thread btw about being stuck at points in Odin.
NO!!! Don't clear your EFS. Will kill your ability to call or get/send data. Will lose your IMIE and you'll be forced to Odin anyways.
Click to expand...
Click to collapse
How am I gonna use this AIO toolbox if I can't get into the phone and put it on debugging mode. I've never used this program
m4r10 said:
How am I gonna use this AIO toolbox if I can't get into the phone and put it on debugging mode. I've never used this program
Click to expand...
Click to collapse
Odin/Download Mode doesn't use USB Debugging, only Mass Storage/MTP uses that.
Download the Toolbox and the .Net files (if you don't already have it-most PCs do nowdays). Install it, Open and hit Flash to Stock. It will open the included version of Odin, browse for the files it comes with re: the Pit and Tar/PDA files and hit Run like you do in regular everyday Odin.
m4r10 said:
All the files have been verified and I click on the pit button and choose the pit file downloaded and then click on PDA and choose the appropiate 512 TAR file. I click start and get into the process. It just hangs at different points all the time. This last time it made it to factoryfs.rfs process and my phone got a blue screen. I'm gonna give a different version of Odin a try.
Click to expand...
Click to collapse
This is a dumb suggestion, but just trying to get the simple stuff out of the way. You're unzipping the 512 pit and only selecting the .pit file for PIT part of Odin, right? I don't think Odin will let you select another file type anyway, but just checking... And the bigger .tar file that you'd get just stays as a .tar when you select it for PDA.
All 3 of those boxes for Odin should be checked (partition, reset, and whatever the other one is).
I've really only had Odin hang on me when I didn't have the drivers installed, when I needed to do the Digital Signature step, and when I was trying to use an older version so here's hoping a few retries work. Like I said earlier, for ****s and giggles run Odin as an Administrator too.
kaiser_bun said:
This is a dumb suggestion, but just trying to get the simple stuff out of the way. You're unzipping the 512 pit and only selecting the .pit file for PIT part of Odin, right? I don't think Odin will let you select another file type anyway, but just checking... And the bigger .tar file that you'd get just stays as a .tar when you select it for PDA.
All 3 of those boxes for Odin should be checked (partition, reset, and whatever the other one is).
I've really only had Odin hang on me when I didn't have the drivers installed, when I needed to do the Digital Signature step, and when I was trying to use an older version so here's hoping a few retries work. Like I said earlier, for ****s and giggles run Odin as an Administrator too.
Click to expand...
Click to collapse
Yea I checked all that. I think the first time I used an unzipped file for the .tar. That's why it finished so quick. I was supposed to use the .tar file without unzipping. This is probably what f-ed everything up.
I'm still trying to bring it back to life. Still get into download mode but nothing else. Not even Vibrant screen anymore!
Ok. I've tried 3 different versions of Odin, downloaded both the pit and tar files several times, and tried with odin flashable roms like bionixfishmanmod and The process still hangs at factoryfs.rfs.
Does anyone have any other tricks to try? I'm all out of ideas.
And every time Odin hangs, The screen on my phone changes from the download screen to a full screen of a random color at which point I have to reset into download mode and start the process over again. I've gone through the process over 100 times now.
Did you install the device drivers and disable the digital signatures in Windows that I mentioned before?
You could also try other USB ports if you haven't.
Hello all,
I'm hoping someone can advise me with the following problem. I bought a unlocked S3 in Belgium (no branding, network locks etc), and the other day I noticed the latest firmware I9300XXBLFB on http://forum.xda-developers.com/showthread.php?t=1646610
As I use OSX I found out that I needed to use Heimdall to flash it.
I download the ROM, unzipped it, then I renamed the tar.md5 to .tar extracted that which gave me the following files:
boot.img
cache.img
hidden.img
modem.bin
recovery.img
system.img
Now the problem began with the PIT... I required one, and stupidly went off to google in search of an S3 .pit file.... which I found
So I selected the .pit, added the files to their relevant partition, and flashed....
Upon rebooting the phone had updated, however there was no factory reset, everything I had previously was there (to my surprise), but the system info showed the correct rom, baseband, blah blah.
Yesterday I noticed I could not access any internet services. Say I open GMail app, and tried to open a mail, it closed the app after a number of seconds (without displaying the mail contents btw).... no error, just back to the main screen.
I also had problems using 3G or WiFi... nether was stable.
So I reflashed yesterday evening.. at which point I found out how to read in my own .pit file off the phone... but of course I've flashed someone else's previously. I did an MD5 sum on the one I extracted off my phone, and also on the one I downloaded off the net and they still matched.
Still I had the same problems, so I thought perhaps I should drop down a ROM version.
I grabbed a zip file with I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 and proceeded to flash it.
Now the phone won't fully boot, it just sits in the Samsung animation and the blue LED pulsing.
I'm guessing I've stuffed up the PIT... the big question is now, what the hell should I do.
FYI I can still get to recovery mode and Odin mode.
Any help / advice would be really appreciated guys.
All the best and thanks in a advance
PS: I just this minute reflashed using Heimdall the I9300XXBLFB. Now it boots up, on first boot it said Updating Android optimsing applications 1/65 and proceeded thru to the point it asks me which language I want... this normal??
kuntstubble said:
Hello all,
I'm hoping someone can advise me with the following problem. I bought a unlocked S3 in Belgium (no branding, network locks etc), and the other day I noticed the latest firmware I9300XXBLFB on http://forum.xda-developers.com/showthread.php?t=1646610
As I use OSX I found out that I needed to use Heimdall to flash it.
I download the ROM, unzipped it, then I renamed the tar.md5 to .tar extracted that which gave me the following files:
boot.img
cache.img
hidden.img
modem.bin
recovery.img
system.img
Now the problem began with the PIT... I required one, and stupidly went off to google in search of an S3 .pit file.... which I found
So I selected the .pit, added the files to their relevant partition, and flashed....
Upon rebooting the phone had updated, however there was no factory reset, everything I had previously was there (to my surprise), but the system info showed the correct rom, baseband, blah blah.
Yesterday I noticed I could not access any internet services. Say I open GMail app, and tried to open a mail, it closed the app after a number of seconds (without displaying the mail contents btw).... no error, just back to the main screen.
I also had problems using 3G or WiFi... nether was stable.
So I reflashed yesterday evening.. at which point I found out how to read in my own .pit file off the phone... but of course I've flashed someone else's previously. I did an MD5 sum on the one I extracted off my phone, and also on the one I downloaded off the net and they still matched.
Still I had the same problems, so I thought perhaps I should drop down a ROM version.
I grabbed a zip file with I9300XXALF2_I9300OXAALF2_I9300XXLF2_HOME.tar.md5 and proceeded to flash it.
Now the phone won't fully boot, it just sits in the Samsung animation and the blue LED pulsing.
I'm guessing I've stuffed up the PIT... the big question is now, what the hell should I do.
FYI I can still get to recovery mode and Odin mode.
Any help / advice would be really appreciated guys.
All the best and thanks in a advance
Click to expand...
Click to collapse
UNZIP THE DOWNLOADED ROM ONCE FROM .RAR TO .TAR/MD5 FILE. AND PUT THE SINGLE .TAR FILE IN PDA SECTION IN ODIN AND FLASH IT. Really, start to read before you do anything
the instructions don;t mention requiring a pit, also, why remane .tar.md5 to .tar when the instructions say "Click PDA and select *.tar.md5". seeing as you can still connect with odin, you onlt have a soft brick and you can still use odin and flash something properly.
gee2012 said:
UNZIP THE DOWNLOADED ROM ONCE FROM .RAR TO .TAR/MD5 FILE. AND PUT THE SINGLE .TAR FILE IN PDA SECTION IN ODIN AND FLASH IT. Really, start to read before you do anything
Click to expand...
Click to collapse
Erm, think you need to read first... I said I use Heimdall because I'm on OSX.
OrbNRG said:
the instructions don;t mention requiring a pit, also, why remane .tar.md5 to .tar when the instructions say "Click PDA and select *.tar.md5". seeing as you can still connect with odin, you onlt have a soft brick and you can still use odin and flash something properly.
Click to expand...
Click to collapse
Once again, I'm using Heimdall not Odin. I'm on OSX not Windows.
Secondly the tar.md5 file is a tar file containing all the components that make the ROM.
kuntstubble said:
Erm, think you need to read first... I said I use Heimdall because I'm on OSX.
Click to expand...
Click to collapse
Oke, my bad. I don`t use heimdal so can`t help you.
Go to recovery (power on with pressing VOL-UP + HOME + POWER when the phone is off) and do a factory reset / wipe data.
This wasn't caused by using a .PIT, though: never use a .PIT ever again, never ever.
HellcatDroid said:
Go to recovery (power on with pressing VOL-UP + HOME + POWER when the phone is off) and do a factory reset / wipe data.
This wasn't caused by using a .PIT, though: never use a .PIT ever again, never ever.
Click to expand...
Click to collapse
Done that also, made no difference :-(
I don't care which ROM I recover correctly but I do want to get the phone working LOL
Use a windows pc and stop using mac?
Its really easy to fix your problem via Odin....
U can use usb jig to unbrick ur phone,and in the future,use odin for all the flashing on ur s3..
Sent from my GT-I9300 using xda app-developers app
pedja381 said:
U can use usb jig to unbrick ur phone,and in the future,use odin for all the flashing on ur s3..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Stupid reply USB Jig does not unbrick a phone .
ODIN how can the OP use Odin and why would you think its better than Heimdall ??? .
jje
OK the phone is running, but it's bizarre ...
Basically I'm connected to my WiFi signal, and Chrome works 100%... but the normal browser does'nt... just hangs, then closes.
GMail if I open it I can see all the mails, if I click on one, it just sits there with the circle going round, then closes, although if I scrolll thru all mails it does load more... very strange.
Seems any default apps that where installed have connection issues... It's really pi**ing me off....
Anyone?
BTW: *#1234# reports:
AP: I9300XXBLFB
CP: I93000XXLFB
CSC: I9300OXABLFB
It doesn't matter if you change .tar.md5 to .tar i always do it to.
What was the name of the pit you flashed?
Hi,
I downloaded GalaxyS3RootMac which contained a file called
s3pit.pit
MD5 (s3pit.pit) = c67ccbe3628793a9f0dba761c15e0896
Thats the one I used ... stupidly ... so I guess I overwrote mine own one...
I had this exact same thing with browser. That was caused eather from wrong csc or that I mistakenly flashed the firmware using phone field in odin and not pda. Try to change your csc to something else using *#272*IMEI#. That wipes the phone.
Tried what you recommend but still same problem
I choose BTC btw
It previously was on KOR
Sent from my GT-I9300 using xda premium
People read the damn topic before posting.
Usb jig is for accessing download mode, which he can do just fine without.
The phone is softbricked, not soft-hardbricked.
I've never used Heimdall but afaik it has caused issues in the past.
Is anyone you know using Windows or can you install Windows as Bootcamp on your Mac?
If so, please try again with Odin, but factoryreset your phone before and after.
Please also confirm you're actually on hardware i9300 or i9300T, not e.g. i9308
Sent from my GT-I9300 using xda premium
d4fseeker said:
People read the damn topic before posting.
Usb jig is for accessing download mode, which he can do just fine without.
The phone is softbricked, not soft-hardbricked.
I've never used Heimdall but afaik it has caused issues in the past.
Is anyone you know using Windows or can you install Windows as Bootcamp on your Mac?
If so, please try again with Odin, but factoryreset your phone before and after.
Please also confirm you're actually on hardware i9300 or i9300T, not e.g. i9308
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hi, well you're completely correct I could go bootcamp although I prefer not to. If all else fails I'll do it that way. Sadly today I can't get my hands on a Windows system to use.
The phone is a Benelux model I believe (bought from Mobistar), under that battery it says i9300 from what I remember.
Cheers for the logical response
I got exactly the same problem as the OP with the S3, a Macbook Air on Lion, and Heimdall yesterday. I was frustrated but ended up trying Odin on a Windows 7 virtual machine to re-flash a stock firmware. It went through perfectly and I was saved.
Hi guys, I've been flashing different roms lately on my sgs3 international with no problems until today. I tried to flash a particular rom using TWRP which failed. I restored a nandroid backup with no problems, and wondered if the flashing fail was because TWRP needed updating, so i downloaded the latest version and flashed it via Odin, which seemed to go ok, until the phone tried to reboot and got stuck at the 'Samsung Galaxy SIII GT-1300' screen, and wouldn't get any further. I tried a few more times to boot it but it was a no-go. I removed the battery and left it out for an hour or two and retried, nothing. I downloaded CWM recovery, with the intention of replacing TWRP, but Odin refuses to see the .tar file, no matter where I put it. It still sees the new TWRP.tar file though. I downloaded a stock Sammy rom, Odin wont see it. Ive tried Odin versions 1.85 and 3.09, but no-go.
I've scoured XDA, and the net for hours, but it all stops with Odin not seeing any .tar files. I'm all out of ideas guys. Can somebody please help me with this?
Many thanks, Dave
Zigg49 said:
Hi guys, I've been flashing different roms lately on my sgs3 international with no problems until today. I tried to flash a particular rom using TWRP which failed. I restored a nandroid backup with no problems, and wondered if the flashing fail was because TWRP needed updating, so i downloaded the latest version and flashed it via Odin, which seemed to go ok, until the phone tried to reboot and got stuck at the 'Samsung Galaxy SIII GT-1300' screen, and wouldn't get any further. I tried a few more times to boot it but it was a no-go. I removed the battery and left it out for an hour or two and retried, nothing. I downloaded CWM recovery, with the intention of replacing TWRP, but Odin refuses to see the .tar file, no matter where I put it. It still sees the new TWRP.tar file though. I downloaded a stock Sammy rom, Odin wont see it. Ive tried Odin versions 1.85 and 3.09, but no-go.
I've scoured XDA, and the net for hours, but it all stops with Odin not seeing any .tar files. I'm all out of ideas guys. Can somebody please help me with this?
Many thanks, Dave
Click to expand...
Click to collapse
Try running Odin in administrator mode and placing .tar file on your desktop and delete the twrp file first so Odin definitely can't see it.
tallman43 said:
Apart from the trouble you are having with Odin you say you tried to boot it a few more times but failed. Did you mean it failed to boot into a rom or boot into twrp or both.
Click to expand...
Click to collapse
Both, actually. I can get into download mode, but nothing else. Thanks for replying so quickly.
Zigg49 said:
Both, actually. I can get into download mode, but nothing else. Thanks for replying so quickly.
Click to expand...
Click to collapse
I thought so sorry i didn't read you post correctly have you tried my suggestion above I edited my post.
tallman43 said:
I thought so sorry i didn't read you post correctly have you tried my suggestion above I edited my post.
Click to expand...
Click to collapse
Trouble is, I can only launch Odin directly from the rar file I downloaded for some reason. It doesn't want to install itself, or give me a shortcut to be able to run it as admin.
Zigg49 said:
Trouble is, I can only launch Odin directly from the rar file I downloaded for some reason. It doesn't want to install itself, or give me a shortcut to be able to run it as admin.
Click to expand...
Click to collapse
Also, I have deleted the TWRP file, but it didn't make any diffrence. (wasn't in admin admittedly).
Off to bed now. Thanks for taking the time to help, hopefully You, or someone else will have solved it by tomorrow
That why its not working you need to extract it from the rar file with 7z or similar unzip program
tallman43 said:
That why its not working you need to extract it from the rar file with 7z or similar unzip program
Click to expand...
Click to collapse
Sorry for not getting back to you sooner, I've been out all day.
But, and don't think I'm arguing here, how come it saw the TWRP .tar file, and let me flash it? I've always had to launch Odin in this way, and it's never let me down before. That being said, I will try and manage a permanent install, and hope it does the trick, thanks.
Zigg49 said:
Sorry for not getting back to you sooner, I've been out all day.
But, and don't think I'm arguing here, how come it saw the TWRP .tar file, and let me flash it? I've always had to launch Odin in this way, and it's never let me down before. That being said, I will try and manage a permanent install, and hope it does the trick, thanks.
Click to expand...
Click to collapse
So, this is what I did. Don't ask me why, it was more an act of desperation than anything else, was unpack the CWM onto my desktop and lo and behold, Odin started to play and recognised the unpacked .md5 file, how weird is that? I've read in the past, about folk who have mistakingly unpacked the .rar file, and then Odin not doing its thing, but never the other way round!
Ok, so good news, right? Err, nope, 'cos even after I managed to flash CWM, the phone still wouldn't boot!
Soooooo....remember the stock sammy rom I mentioned? Well, I did the same thing with that ie. unpacked the .rar and flashed the .md5 file, and, long story short, it went in, albeit after what seemed like a very long writing process. So here I am with a working phone again, although I realise now that it was a Vodaphone file, and my phone is unrooted, but, hey, it's working .
All I have to do now is re-root it, and flash a rom of my choice.....what could possibly go wrong? (cue maniacal laughter)
Zigg49 said:
So, this is what I did. Don't ask me why, it was more an act of desperation than anything else, was unpack the CWM onto my desktop and lo and behold, Odin started to play and recognised the unpacked .md5 file, how weird is that? I've read in the past, about folk who have mistakingly unpacked the .rar file, and then Odin not doing its thing, but never the other way round!
Ok, so good news, right? Err, nope, 'cos even after I managed to flash CWM, the phone still wouldn't boot!
Soooooo....remember the stock sammy rom I mentioned? Well, I did the same thing with that ie. unpacked the .rar and flashed the .md5 file, and, long story short, it went in, albeit after what seemed like a very long writing process. So here I am with a working phone again, although I realise now that it was a Vodaphone file, and my phone is unrooted, but, hey, it's working .
All I have to do now is re-root it, and flash a rom of my choice.....what could possibly go wrong? (cue maniacal laughter)
Click to expand...
Click to collapse
Glad to see you got it working but it's not weird at all you could have saved yourself alot of trouble by saying in your first post that your files where originally in .rar format. It is normal procedure to unpack .rar files for them to work in programs and especially for them to work in Odin so that it can recognize them.
tallman43 said:
Glad to see you got it working but it's not weird at all you could have saved yourself alot of trouble by saying in your first post that your files where originally in .rar format. It is normal procedure to unpack .rar files for them to work in programs and especially for them to work in Odin so that it can recognize them.
Click to expand...
Click to collapse
Ahh, ok . But I've always just directed Odin to the .rar file, and never had this problem before. Oh well, you live and learn, eh?
Thanks for your help:good: