Related
I used the odin stock TARs, incorrectly. I think they were supposed to be applied one at a time using the PDA button only, and in conjunction with the PIT file. I unfortunatly also used the PHONE and CSC buttons...which rendered my fascinate unable to connect to the cell network. so... does anybody have a TAR intended for use with the fascinate for the PHONE and CSC buttons? can anyone explain what these two buttons are? I DO HAVE several working stock fascinates with me, so can anyone point me in the direction of capturing correct ODIN tars from these phones for use on my broken phone? THANKS SO MUCH in advance!
Did you try redoing the Odin directions to get to stock?
andrewblanejr said:
I used the odin stock TARs, incorrectly. I think they were supposed to be applied one at a time using the PDA button only, and in conjunction with the PIT file. I unfortunatly also used the PHONE and CSC buttons...which rendered my fascinate unable to connect to the cell network. so... does anybody have a TAR intended for use with the fascinate for the PHONE and CSC buttons? can anyone explain what these two buttons are? I DO HAVE several working stock fascinates with me, so can anyone point me in the direction of capturing correct ODIN tars from these phones for use on my broken phone? THANKS SO MUCH in advance!
Click to expand...
Click to collapse
Sorry. You're SOL. This is why "DON'T USE THE PHONE BUTTON" is posted everywhere. If it was as simple as extracting modem.bin / bml12 from a good device, we would have done it many weeks ago.
There's nothing to be done at this point, you need to exchange the phone.
ilestdevil said:
Did you try redoing the Odin directions to get to stock?
Click to expand...
Click to collapse
Yup. I did. No go.
Odin: Do not use the phone button in odin
namebrandon said:
Sorry. You're SOL. This is why "DON'T USE THE PHONE BUTTON" is posted everywhere. If it was as simple as extracting modem.bin / bml12 from a good device, we would have done it many weeks ago.
There's nothing to be done at this point, you need to exchange the phone.
Click to expand...
Click to collapse
Right. So I do understand this is my fault, but i did not see such a warning in the Fascinate-specific or even ODIN specific articles that I found. There was only one article I found that said not to use the PHONE BUTTON, but i can't even remember where it was and i found it too late.
In some cases of non-fascinate (ie. Galaxy i9000 and older Samsung phones) articles there are specific instructions to actually use the PHONE BUTTON for modem.tar.
SO can the following threads (which are obviously very popular) be updated to reflect this warning and in the case of the more specific ODIN stock restore thread (fallingup/angel12), can we see an update that includes instructions on what to do with all 3 TARs and the 1 PIT?
I don't want to complain (luckily for me this was an extra destined-to-be-returned phone), but I do think that some very small post edits could help prevent other people from ruining their phones.
OH, and what about the CSC button, what does that do? and How do we back .TARs with ODIN? I have seen many people ask these questions, and very very few responses...anybody?
Best,
Andrew
Hi guys.
My phone has been having major signal issues, no signal or emergency calls only next to an exact same phone that has no problem. Talking to my provider, it appears to be the phone and I need to send it back for repair. Problem is, I have a different firmware on there. I obviously need to get it back to the stock optus rom it came with. I know computers and stuff, but im a bit lost in this area. I've done a lot of searching on here but can't seem to find a specific resolve to this issue.
I'll try and sum it up.
Currently running Litening Rom 5, which i flashed with odin. I found on here the link for the original optus branded rom (GT-I9100_OPS_I9100XWKE7_I9100XXKE4_I9100OPSKE4) but after downloading it I'm more lost. The 7zip file had the following files in it:
boot.bin, cache.img, factoryfs.img, hidden.img, modem.bin, param.lfs, sbl.bin and zimage.
I have no idea what to do with these. I've also read that CWM is another possible way to do all this. My rom has it so that might be possible. I'm not fussed about keeping any files, I was gonna do a factory reset before I send it away anyway. I wanna completely wipe my phone and get it back to exactly how it was, so when optus look at it, its how they sent it to me, especially with no yellow triangle on boot.
What should I do with these files? The other option I have is if I can get the rom dumped off a friends optus phone and simply put it onto mine. I know 2 friends with them, can I plug their phone into my PC and use the dump button in odin, or will I get the same files?
Other question I have are:
1) Will Optus know what version of the firmware came on the phone (XXKE7 or whatever) and therefore realise a possible older version is on there, causing suspicion?
2) Is it possible that custom firmwares can screw up my reception? Friends are running stock and they have no issue, though saying that, its still not as good signal as a Nokia.
If you've read this far, thank you very much, I really appreciate it. I'm just so lost, freaking out a bit, going a bit insane with the phone constantly not having signal and just low on time to sort it out. Any help would be appreciated. Thank you!
Hi.
First off, if you're already down to the .bin and .img files, you extracted too much.
The archive you downloaded should contain a .tar file - DO NOT extract this one! You need the .tar as .tar.
Then download an App called "Odin" (likely to be found in the very same thread where you found the firmware) and use that one to flash the .tar onto the phone.
Instructions for that are also in the thread where you found the firmware.
That should already solve most of your hazzle.
If I'm not mistaken, flashing your phone's kernel would case
Cause the binary flash counter to clock. And the phone does keep a record of how many custom kernels you have been through. So I would say if they wanted to know, they would be able to find out.
In that case, spend the 5 to 10 bucks on eBay for the USB jig that resets the counter.
I have one too, "works nicely" is an understatement
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
I had no idea about the kernel flash counter, but it sounds like it could be an issue. I saw those USB jigs, but though they were just a way to get into downloading mode if you'd somehow screwed up the normal way. Is that all they do, or much more?
TroyX87 said:
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
Click to expand...
Click to collapse
You're doing it wrong.
Intratech said:
You're doing it wrong.
Click to expand...
Click to collapse
You know what would be awesome? If you explained why. I have no idea why I'm doing it wrong. Did I download the wrong file? (didn't have many options). Or would it be better to get a dump from a friends phone that has the desired rom/kernel?
How do I know why you're doing it wrong? The files are self extracting, all you need to do is double click it and point to when you want the included tarball extracted. You will then have a single tarball which includes everything in a single package. This has all been covered in the tutorial.
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
TroyX87 said:
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
Click to expand...
Click to collapse
Where did you get the file from? Optus firmwares are in the carrier branded firmware thread in the dev forum so you can download a copy from there.
I grabbed the exe from your other thread, it had 5 different links and only 1 worked at the time.
But you know the worst part? I just figured it out. The exe extracted a .tar file, but in my rushing and stressed-ness, i didn't realise that was the one, it was a winrar file so i just thought it was compressed or something, like a zip.
My bad. I wont be flashing just yet, gonna replace my sim card first. I got used to the idea of wiping my phone and starting again, but now I realised how annoying that would be. Bought a USB jig too, just in case.
Appreciate your help, sorrying for being a n00b!
Ok everyone, this is an update from my post from a few months ago. If you didnt see it, I had accidentally bricked my Galaxy Mega while trying too root. I tried everything I could possibly think of. Im no expert, but I'm not a nooby either and I like to say that I know what I'm doing for the most part. So what I did was flash a sprint rom for the Mega. I did this based on a fix I did on a Galaxy S3 in the past. (Why I did this is too long of a story to get into here) Not trying to bash anyone who posted in my other thread, but there were alot of people saying that because I flashed rom that is not for US Cellular that I hard bricked the phone. I knew that they were wrong because I could still boot into recovery and download mode and I had been in this situation in the past. It is extremely difficult to "hard brick" a phone to where nothing can be recovered. So don't always believe the so called "experts" Anyway, the Sprint rom was no help. So I kinda gave up for a while. Today I thought I would give it another shot.
Ok, so what I did was flashed the stock 4.4.2 md5 file in Odin. This was my problem before. I couldnt find a stock US Cellular Rom.
Step 1. You need Odin 3.09 You can download it here http://odindownload.com/ (Make sure you download 3.09)
Step 2. Go to this thread: http://teamuscellular.com/Forum/topic/7085-r960-stock-442-rom-nf1-odin/ Download the stock rom and unzip it with a program like winrar or 7zip
Step 3 Flash with Odin (if you are not sure how to do that, there are plenty of tutorials on youtube, just be careful and make sure you know what you are doing)
Thats it guys. This fixed my problem. I am now working on finding a root for this device and will post it as soon as I find one.
Big thanks to http://teamuscellular.com/Forum/user/3187-bru-1-w4nje/ for uploading the file.
-Derrick-
Q&A for [Firmware][unofficial]1545OYUAMDK ODIN TAR
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware][unofficial]1545OYUAMDK ODIN TAR. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Update links plox
Update links. . . please?
I locked my bootloader the same day I received my Dev S4 back in 2013 and have read and re-read every post on XDA that has info about returning the firmware back to stock, it looks like this ODIN TAR should work, but I can't find a working DL link for it anywhere on the web. Samsung is of no help whatsoever, they just flat out will not help me because I've "modified the device". If this actually does not work, or even if it will work if I have my original aboot file, it'd be awsome if you could let me know and I'll stop checking this thread every month Thanks in advance!
I prob have the link somewhere, but the thing is we learned later on that you can only re-unlock your bootloader if you still have the aboot that came with your dev edition backed up somewhere
Surge1223 said:
I prob have the link somewhere, but the thing is we learned later on that you can only re-unlock your bootloader if you still have the aboot that came with your dev edition backed up somewhere
Click to expand...
Click to collapse
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
jas84701 said:
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
Click to expand...
Click to collapse
The one that's 2mb is likely a dd backup with padded zeros (good sign) problem is you have to be sure or you'll hard brick. I'd need to see the file, and even if we confirmed it's a dev edition aboot you would have to be 100 percent sure it's one from your phone originally.
jas84701 said:
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
Click to expand...
Click to collapse
Send me the 2MB file. I'll make it flashable in Odin for you.
Hi all,
I installed CM11 onto my S5830i (GB) and managed to get it all working. I had to install S5360_XXMK1 modem and a newer version of CWM to prevent the "Status 7" error. Anyway, it all worked and I had CM11 up and running. Unfortunately, I had to remove it, I couldn't click any links in the browser and the browser was slow as all buggery even on a fast wifi connection. So I fired up Odin and tried to put the stock firmware on (i don't have an original state backup, the phone came with a custom rom on it already). I got these files
CSC_S5830i_BTUMD1.tar.md5
MODEM_S5830i_XXMD1.tar.md5
PDA_S5830i_XXMD1.tar.md5
But something's messing up, after Odin does its thing and the phone restarts, I notice something on the screen during restart saying it failed to format the /data partition. When I let the phone boot up normally it just stays on the "Samsung" startup animation forever. If I go into samsung recovery and try to do a factory reset, this is what I see
Code:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
Data wipe complete.
Obviously, something's wrong there, can anyone tell me how to fix it pleeeeese, I'd be eternally grateful.
Thanks
NS
EDIT: I think the CM install may have messed around with my partitioning. I do not have a pit file for the phone (GB Version) and am reluctant to be using the re-partition option in Odin. I can find pit files online, but they're either not the correct version or the poster doesn't even say what version it is. I am just so lost and confused with all this.
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
ehsanotaku said:
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
Click to expand...
Click to collapse
Thanks but you were too technical. I have been to a lot of those pages you linked and it's not all obvious what's going on. You spoke about "base band", I have no idea what that is. I have no idea what RFS, MTD
are (file systems?), not do I know where to get a bootloader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do. I'll re-read the posts you linked to (I had already seen them) and see if something starts to make more sense.
For instance:
"Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11"
May as well have been in Klingon, I didn't understand a word of it.
EDIT:
I've reviewed those threads again. Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions. I need a pit file, there's no info anywhere on how to get that. So I've just done a general google and hopefully I've downloaded one (more info on that is needed in the tuts). And the bootloader is attached to the unbrick thread, but, is that the ONLY bootloader? Do I need a specific one for my region? Do I need a specific pit file for my region? All this info is not supplied anywhere, Newcomers are not going to know this stuff and it needs to be made clear in the tutorials. Most of the tuts have broken links (split fus for instance), so I'm not sure if the stuff I googled is actually the same. Absolute nightmare.
NicSure said:
You spoke about "base band", I have no idea what that is.
Click to expand...
Click to collapse
Please read the link was provided for your convenient. ( Absolutely suitable for beginners).
NicSure said:
I have no idea what RFS, MTD
are (file systems?)
Click to expand...
Click to collapse
"Robust File System" is more or less equivalent to your FAT/FAT32 of your PC ( Samsung file system Format,, not going to add "Journalling system" to the mix, since you are not a sport ,,FYI : You are supposed to know common terms such as MTD , RFS when you are massing with CM11 mate >> Read the first page thoroughly, before start experimenting with Cyanogen stuff,,,
MTD (Memory Technology Device) supports YAFFS2 as a file system residing on it and is considered some type of of Partition Map.
NicSure said:
not do I know where to get a boot loader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do
Click to expand...
Click to collapse
Again actually start reading this topic ( quite self explanatory).
NicSure said:
Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions.
Click to expand...
Click to collapse
This topic contains well made Wipe packages ( European version is compatible with your device, If you are reluctant to register though).
NicSure said:
I need a pit file, there's no info anywhere.
Click to expand...
Click to collapse
Again, Read the topic I mentioned above. You are on Cooperve device, so be aware of wrong file ( "cooperve_0623.pit" resided inside Odin3.v3.07.Cooperve folder) All of the related links already provided , Just take your time and read mate.
I'd already read the posts you linked to multiple times thank you. They may be "straight forward" to you, but I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly.
In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Also, why would changing the base band effect the file system? How could it cause physical damage to NAND memory. I'm confused. I assume you mean physical damage, because if not, why would it be ill-advised to change it if it could just be changed back with no ill-effects?
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
ehsanotaku said:
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
Click to expand...
Click to collapse
Firstly, I'm not complaining, I'm criticizing, there's a difference. I was critical of your language and terminology as it didn't match the links you posted. Also the level of technical talk you used toward a clear newbie who would obviously never understand it without clarification. If that offends you then I'm sorry, I'm just speaking my mind. Help offered, no matter how kindly or freely is useless if it cannot be understood. I generally take a very irritated approach to people who post links (with the implication that the information is freely available if you'd bother to look) in response to perfectly polite questions, especially when I'd already read ALL the posts you linked to before and had trouble with them, that is why I posted, to get a little more basic understanding, not be presented with links to material I'd already read and needed help with. Also, after some researching, with regard to the base-band, I think you're wrong, there's no way flashing a different base-band separately could effect the bootloader, no way at all. I seriously doubt it could even cause corruption, that's liek saying installing the incorrect driver for a graphics card on a PC could corrupt the file system, just no. So far I've flashed many many different MODEM types onto my phone to try to test this, in some caes the phone boots, in some cases it doesn't etc.. Not once has the phone failed to go into Odin flash mode, and if it can get to that, it can be restored. So based on research and some experimental evidence conducted to test your assertion, I'd have to say that my initial findings are that your assertion is probably incorrect.
Also I learn very quickly. My knowledge of the subject had increased dramatically from my first post to my second. I learned c++ in a day for example, and was posting similar newbie questions on programming forums to which I was later replying with a level of knowledge that wasn't consistent with my initial post. It's just me, sorry about that. And thanks for trying to help, but I got it myself.
NicSure said:
... I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly. In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Click to expand...
Click to collapse
Dear NicSure, I am in the same situation as yours, I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
thePanz said:
I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
Click to expand...
Click to collapse
Per your request/confirmation @ development section/twr topic i would resume troubleshooting .
What is your device variation (5830i/C/M/V/5839i ) ? Do you have any Nandroid back up left inside your SD card from your original stock firmware partitions ? Can you see your IMEI number , when you are dialing "*#06#" ? Your original stock CSC/PDA/MODEM you are coming from ? Your Region / Country / carrier you are staying with at the moment and please give me the Totoro Modem part you did flash to get into the CM11 ? and for addressing part of your primary queries , Odin 3.07 works very well with variation I mentioned above ( you could use 3.09 with no harm though , but not recommended ) . Pit file also must be relevant, otherwise you will hard brick your device in many cases I observed .