I am going to switch my service from att to t mobile. Can I odin, a t mobile stock Rom on the att phone? I want to have wifi calling on it. I believe all the hardware is the same and it should work. I just want to make sure. Thanks in advance.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I did the opposite. I put a T-Mobile note 2 onto the AT&T network. I asked if I could put an AT&T rom in the T-Mobile phone and I was told it "could" cause compatibility issues. I went ahead and put the matching T-Mobile software in the phone.
Of course you should see what the more experienced folks have to say. I have been curious myself. I've been thinking about trying an AT&T rom in the phone. They did say the hardware is pretty much the same, but that it could cause issues with the factory installed software that remains even after a rom install.
Hopefully we hear from someone soon.
---------- Post added at 08:19 PM ---------- Previous post was at 08:08 PM ----------
I found the post. It was for the SGS III I was playing with, my wife has it now. Hope this helps.
Check this post.
I know I can flash t mobile roms via cwm or twrp. But I want to use odin to change modem and everything. Basically make it a stock t mobile phone. It is for my wife, and stock is fine.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I have an AT&T Note 2 running T-Mobile stock rom.
You can't flash the T-Mobile radio to the AT&T phone but, mine is working every well with this setup.
Did you flash via recovery? Or Odin?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Micronads said:
Did you flash via recovery? Or Odin?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ODIN. I had to take out parts of the original ROM that I knew would make it fail via ODIN upon install.
Sent from my SGH-T889
tooter1 said:
ODIN. I had to take out parts of the original ROM that I knew would make it fail via ODIN upon install.
Click to expand...
Click to collapse
I know this is an old thread, but how do you do this? I've got an AT&T phone that I would like to load the stock T-Mobile build on. I've got a .md5 file for ODIN. Is it as simple as untar-ing the file, deleting the modem image, then retar-ing it and generating the .md5 file?
An additional complication is that I've enabled all of the radios using a Qualcomm utility.
chris.arney said:
I know this is an old thread, but how do you do this? I've got an AT&T phone that I would like to load the stock T-Mobile build on. I've got a .md5 file for ODIN. Is it as simple as untar-ing the file, deleting the modem image, then retar-ing it and generating the .md5 file?
An additional complication is that I've enabled all of the radios using a Qualcomm utility.
Click to expand...
Click to collapse
I need to look and see if I can remember the files to remove. I know I did a trial and error thing and I can't seem to find my saved stock ROM. I'll keep looking for it though.
I assume it was the modem file, but I don't know for sure. The bigger question I have is how to re-create the ODIN file. I untar-ed a stock T-Mobile image from this thread. I deleted the modem.bin file, and tried to retar it according to the instructions here. I tried flashing it, but it's been "flashing" the boot image for over an hour. I'm about to reboot it, and try something else. Maybe tar-ing up each individual image, and flashing them one at a time? I don't understand why ODIN won't let me flash a .img or .bin file, but it'll allow a .tar that contains a .img or .bin? I'm hoping I haven't bricked it!
chris.arney said:
I know this is an old thread, but how do you do this? I've got an AT&T phone that I would like to load the stock T-Mobile build on. I've got a .md5 file for ODIN. Is it as simple as untar-ing the file, deleting the modem image, then retar-ing it and generating the .md5 file?
An additional complication is that I've enabled all of the radios using a Qualcomm utility.
Click to expand...
Click to collapse
chris.arney said:
I assume it was the modem file, but I don't know for sure. The bigger question I have is how to re-create the ODIN file. I untar-ed a stock T-Mobile image from this thread. I deleted the modem.bin file, and tried to retar it according to the instructions here. I tried flashing it, but it's been "flashing" the boot image for over an hour. I'm about to reboot it, and try something else. Maybe tar-ing up each individual image, and flashing them one at a time? I don't understand why ODIN won't let me flash a .img or .bin file, but it'll allow a .tar that contains a .img or .bin? I'm hoping I haven't bricked it!
Click to expand...
Click to collapse
What happened with the process? I can't seem to find my old file(s) that I flashed, must have deleted it since I haven't had that phone in quite some time.
What I did was, I started to delete files within the ROM like modem, tz, hidden etc. until it fully booted.
Sorry I couldn't be more useful about this. I should have put it in my response thread on how I did flashing process.
Related
I'm pretty good when to comes to rooting, I just odin to stock and upgraded to
latest (MD5), but I didn't take into consideration that there's not a pre-rooted tar file out, I really hate to odin back to UVLC to root and then upgrade... anyone have any idea how to root it?
There's a rooted file already ..
Sent from my SGH-T999 using xda premium
re: root
Mr_Jay_jay said:
I'm pretty good when to comes to rooting, I just odin to stock and upgraded to
latest (MD5), but I didn't take into consideration that there's not a pre-rooted tar file out, I really hate to odin back to UVLC to root and then upgrade... anyone have any idea how to root it?
Click to expand...
Click to collapse
This new upgrade is pre-rooted.
No need to root it at all.
Here is the direct download link for the new Samsung Galaxy S3 T999 Official 4.1.2 stock rooted Jellybean rom:
- http://www.androidfilehost.com/?fid=22946563261203914
Just flash it using cwm or twrp like any other zipfile rom.
Good luck!
Misterjunky said:
This new upgrade is pre-rooted.
No need to root it at all.
Here is the direct download link for the new Samsung Galaxy S3 T999 Official 4.1.2 stock rooted Jellybean rom:
- http://www.androidfilehost.com/?fid=22946563261203914
Just flash it using cwm or twrp like any other zipfile rom.
Good luck!
Click to expand...
Click to collapse
That's the thing.. I'm pure stock.. I don't have a recovery, I tried to odin a recovery, but it wont stick since I'm not rooted...
re: sure way to root the first time.
Mr_Jay_jay said:
That's the thing.. I'm pure stock.. I don't have a recovery, I tried to odin a recovery, but it wont stick since I'm not rooted...
Click to expand...
Click to collapse
Here is a step by step guide:
Easy and sure way to root your phone - Here is s step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benefit of being rooted.
Download the stock-rooted Samsung Galaxy S3 Jellybean v4.1.1 T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to take a long time on first boot, this is normal so you must be very patient!!!)
Good Luck!
Misterjunky said:
This new upgrade is pre-rooted.
No need to root it at all.
Here is the direct download link for the new Samsung Galaxy S3 T999 Official 4.1.2 stock rooted Jellybean rom:
- http://www.androidfilehost.com/?fid=22946563261203914
Just flash it using cwm or twrp like any other zipfile rom.
Good luck!
Click to expand...
Click to collapse
Hello curious i used that file from that link but the update is good but the baseband version is still t999UVDLJC any idea how i can get onto the new baseband version. My build is new JZ054K.T999UVDMD5 but baseband is old still.
re: baseband
indnracn2 said:
Hello curious i used that file from that link but the update is good but the baseband version is still t999UVDLJC any idea how i can get onto the new baseband version. My build is new JZ054K.T999UVDMD5 but baseband is old still.
Click to expand...
Click to collapse
The reason is that Jody (the developer) removed the new RADIO/MODEM image
from the rom so everyone including those people who have AT&T Unlocked phones
can use the rom.
If you want the original baseband/modem/radio cwm/twrp flashable zipfile here
is the UVDMD5 Radio/Baseband Download Link - http://db.tt/RgrCGufl
Only flash this if you have a Samsung Galaxy S3 T999 device and you have Tmobile service.
You can root same way as all prevouse stock ROMs. Install custom recovery with Odin and then flash superuser in recovery.
Sent from my SGH-T999 using xda app-developers app
Except for one thing. After odin flashing recovery you cannot let the device restart. Everytime you boot up it checks for correct recovery and if its not there it rewrites it.
Sent from my SGH-T999 using xda premium
re: root
DocHoliday77 said:
Except for one thing. After odin flashing recovery you cannot let the device restart. Everytime you boot up it checks for correct recovery and if its not there it rewrites it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
That's one of the main reasons I always suggest NOT to odin flash the stock T999 4.1.2 tar rom
but instead flash the cwm/twrp T999 pre-rooted deoxidized 4.1.2 rom which Jody setup for us.
People should have been warned about what you said before they allowed the OTA update to
upgrade their phones unless they don't want root access and want their phone to be pure stock.
Misterjunky said:
That's one of the main reasons I always suggest NOT to odin flash the stock T999 4.1.2 tar rom
but instead flash the cwm/twrp T999 pre-rooted deoxidized 4.1.2 rom which Jody setup for us.
People should have been warned about what you said before they allowed the OTA update to
upgrade their phones unless they don't want root access and want their phone to be pure stock.
Click to expand...
Click to collapse
Its all been covered pretty thoroughly, and all folks need to do is read! I know its asking an awful lot for some.
I haven't looked at jovys but there are two files that cause the recovery rewrite, and if he didnt remove them his rom will do the same.
If I remember right they are:
Install-recovery.sh
Recovery-on-boot.p
The second is wrong im pretty sure, but its something similar. Check my firmware thread and it should be there.
Hope that helps.
Sent from my SGH-T999 using xda premium
Misterjunky said:
That's one of the main reasons I always suggest NOT to odin flash the stock T999 4.1.2 tar rom
but instead flash the cwm/twrp T999 pre-rooted deoxidized 4.1.2 rom which Jody setup for us.
People should have been warned about what you said before they allowed the OTA update to
upgrade their phones unless they don't want root access and want their phone to be pure stock.
Click to expand...
Click to collapse
Still need to Odin stock to get the updated bootloader/rpm/tz. Unless you want to flash them yourself. That's why everyone suggests root66.
re: root66
DocHoliday77 said:
Its all been covered pretty thoroughly, and all folks need to do is read! I know its asking an awful lot for some.
I haven't looked at jovys but there are two files that cause the recovery rewrite, and if he didnt remove them his rom will do the same.
If I remember right they are:
Install-recovery.sh
Recovery-on-boot.p
The second is wrong im pretty sure, but its something similar. Check my firmware thread and it should be there.
Hope that helps.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I was just looking in your "Firmware/OTAs T999(V) Official, Leaked & Root66 FW & OTA Updates" thread
and downloaded the "root66_TMO_T999UVDMD5.7z" which is the pre-rooted Odin flash 4.1.2 firmware.
The reason I downloaded it is that I just want to have a odin flash rooted backup of 4.1.2 in case I need it in the future.
I wanted to ask if this firmware includes the modem/radio in the TAR file?
If it does, what is the filename of the modem/radio file? (I need to remove it).
My phone is an Unlocked AT&T I747 Galaxy S3 which I am using with Tmobile service and
I do not want to flash the modem/radio since it will not work with my phone.
Thanks.
Misterjunky said:
I was just looking in your "Firmware/OTAs T999(V) Official, Leaked & Root66 FW & OTA Updates" thread
and downloaded the "root66_TMO_T999UVDMD5.7z" which is the pre-rooted Odin flash 4.1.2 firmware.
The reason I downloaded it is that I just want to have a odin flash rooted backup of 4.1.2 in case I need it in the future.
I wanted to ask if this firmware includes the modem/radio in the TAR file?
If it does, what is the filename of the modem/radio file? (I need to remove it).
My phone is an Unlocked AT&T I747 Galaxy S3 which I am using with Tmobile service and
I do not want to flash the modem/radio since it will not work with my phone.
Thanks.
Click to expand...
Click to collapse
Modem is NON-HLOS.bin. Can't remove it, because the md5 check will fail.
Maybe ask mrrobinson if he can give you any pointers on how to remove it correctly. The steps he uses to create root66 would likely work to remove the modem as well.
Do you have the same partition layout as us? If not, dont use any of the firmware. If so you can always flash it and then flash your correct radio after.
Sent from my SGH-T999 using xda premium
re: md5
Aerowinder said:
Modem is NON-HLOS.bin. Can't remove it, because the md5 check will fail.
Click to expand...
Click to collapse
What if I remove the .MD5 from the filename ?
I don't think that Odin requires the .MD5 extension, I know I have Odin flashed
roms a while back which did not have an MD5.
---------- Post added at 08:14 PM ---------- Previous post was at 08:07 PM ----------
DocHoliday77 said:
Maybe ask mrrobinson if he can give you any pointers on how to remove it correctly. The steps he uses to create root66 would likely work to remove the modem as well.
Do you have the same partition layout as us? If not, dont use any of the firmware. If so you can always flash it and then flash your correct radio after.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am sure I have the same partition layout, I am using the cwm/twrp flashable zipfile of the pre-rooted UVDMD5 T999 4.1.2 rom.
Before I got the Unlocked AT&T Galaxy S3 I had the galaxy S2 which I used with AT&T network and flashed the
root66 Odin flash roms before and had no problems, but since I am with Tmobile now I need to remove the radio file.
Since I am with Tmobile now, I never odin flashed roms due to the fact that they all contain the radio file.
Mobile Odin will flash without the md5 extension. Cant remember for sure with pc odin. I may try it later tonight to see for sure. You can also deselect the modem when flashing via M.O. in case you didnt know, though
I am also pretty sure you have the same layout as the t999. I appreciate you taking the time to do it in a way that is safe and wont brick!
I do think you would be ok to flash the full fw though, just make sure you have a copy of the correct modem and flash it right after.
Ill let you know for sure about the md5 after I get home and try it out.
Sent from my SGH-T999 using xda premium
re: modem
DocHoliday77 said:
Mobile Odin will flash without the md5 extension. Cant remember for sure with pc odin. I may try it later tonight to see for sure. You can also deselect the modem when flashing via M.O. in case you didnt know, though
I am also pretty sure you have the same layout as the t999. I appreciate you taking the time to do it in a way that is safe and wont brick!
I do think you would be ok to flash the full fw though, just make sure you have a copy of the correct modem and flash it right after.
Ill let you know for sure about the md5 after I get home and try it out.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks, I just wanted to save a few steps and not have to flash the AT&T stock modem if I don't have to.
Hey man, didnt want to leave you hanging. Im not going to get to try odining without the md5 tonight. Definitely tomorrow though. Just has got too late too fast and my eyes are crossing from lack of sleep!
Ill get on everything by early afternoon for sure.
Sorry if ive kept you waiting on me for anything. But I haven't forgotten!
Sent from my SGH-T999 using xda premium
I rooted it had a ton of apps on it and I just couldn't leave it alone. I couldn't figure out why I rooted it and then my Shealth quit working. So, I decided to install a different rom. Which I assume was back to factory. Well then I didn't have the dual window feature and couldn't get it on there either. So, tried to flash another rom. Well that didn't work now it just says Galaxy S4 and stuck there. 2 of the roms that I try to flash won't even work for some reason. This is TMobile.
One of them is this: ! SGH-M919-TMB-M919UVUAMDL That one didn't work.
Did this one: I9500_Omega_v3.0_X.....
I don't know where to start or begin now. Been trying to fix this for the last 6 hours and it is 5:00 am in the morning. I am going to have to sleep on this one.
Isnt is for Tmobile US versions??
You screwed up by flashing i9500 Rom man. May be u made softbrick before which leaves u option to go back to stock by odin but after u flash international rom you are screwed totally.
Sent from my SGH-M919 using xda premium
---------- Post added at 11:40 AM ---------- Previous post was at 11:36 AM ----------
Its hard bricked now.
Power off first and try pressing power +home + volume down button ; see if u can reboot into download mode.
Sent from my SGH-M919 using xda premium
bikrame said:
Isnt is for Tmobile US versions??
You screwed up by flashing i9500 Rom man. May be u made softbrick before which leaves u option to go back to stock by odin but after u flash international rom you are screwed totally.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Oh Great. I thought the 9500 was the us version. So what is the US version. I can still get into recovery so I would assume i can still flash another rom.
I see it is the 9505. That is what I get with no sleep.
Outrung2 said:
Oh Great. I thought the 9500 was the us version. So what is the US version. I can still get into recovery so I would assume i can still flash another rom.
Click to expand...
Click to collapse
If you still can reboot into recovery wipe system data and chche and delvik too. Then flash any rom from our section saying for M919 (tmobile is that even att and sprint willl not work ).
You are on good shape if u can reboot into recovery.
Sent from my SGH-M919 using xda premium
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
IF Its tmobile US version; BE CAREFULL DONT FLASH ANY ROMS FROM ATT SPRINT OR VERIZON. THEY ARE NOT SAME .
Sent from my SGH-M919 using xda premium
bikrame said:
If you still can reboot into recovery wipe system data and chche and delvik too. Then flash any rom from our section saying for M919 (tmobile is that even att and sprint willl not work ).
You are on good shape if u can reboot into recovery.
Sent from my SGH-M919 using xda premium
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
IF Its tmobile US version; BE CAREFULL DONT FLASH ANY ROMS FROM ATT SPRINT OR VERIZON. THEY ARE NOT SAME .
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Thats kinda how this started. I downloaded one for tmobile. Every time I ran it though it said bad. Not sure why. SGH-M919-TMB-M919UVUAMDL.ZIP
Do you have a better link to a tmobile one?
Flash this one
http://forum.xda-developers.com/showthread.php?t=2274795
May be its not flashable.
The one I gave is stock but rooted.
Sent from my SGH-M919 using xda premium
What carrier are you with?
Sent from my SGH-M919 using xda app-developers app
You probably installed the I9500 ROM and soft bricked the device. the same thing happened to me a few months ago with my s3. go to samsung-updates.com and install the SGH-M919 stock rom. then, go to download mode and flash that ROM with odin. the same thing happened to me when i was a noob with ROMs. a soft brick is actually quite easy to recover from. at least it wasnt a hard brick.
bikrame said:
Flash this one
http://forum.xda-developers.com/showthread.php?t=2274795
May be its not flashable.
The one I gave is stock but rooted.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
This is exactly what I need. However the download on that page is not working.
I am still having trouble. I have no idea why. I have rooted every phone that I had with no problem. But this should be so simple and it's not
When I first rooted Shealth stopped working. Then I was going to just forget about it. But it was something that I wanted to use. So after a few days I decided I wanted it to work. I didn't see that anyone else had this problem. So I downloaded what I thought was the US version but guess it was not. I installed this new rom. Well now I had 2 problems. No multi window and still my shealth didn't work.
Then I thought oh crap I forgot to do a wipe. So I did a wipe and re-ran the rom. Well that is where I got stuck. I can not get passed the S4 Screen still. I can get into recovery, flash the rom (the rom flashes in like 1min which sure does seem fast). I then reboot and get right back to the s4 screen. Can't get passed it.
So here is my question. These tar files that I keep downloading. They are all zip files. If I wanted to flash them via odin as one told me to do I can't because it is a zip. Am I supposed to unpack this or change the extension from zip to tar?
Been without my phone for almost 24 hours and driving me nuts. At this point I would be glad just to see a working phone.
If it is the stock tar file you need to unzip it. The tar will be in the zip file. It will have an extension of tar.md5 if memory serves.
Sounds like you lost system files. If you can still get into stock recovery, then reformat system and then flash a stock rom. From there, you'll have to reroot.
Atmazzz said:
If it is the stock tar file you need to unzip it. The tar will be in the zip file. It will have an extension of tar.md5 if memory serves.
Click to expand...
Click to collapse
Ok I downloaded a stock rom and unzipped it. I then did a search for tar and it couldn't find it. I couldn't find it manually either. So now I am converting the whole zip file to a tar. Gonna take a while for 1.6 gigs
Outrung2 said:
Ok I downloaded a stock rom and unzipped it. I then did a search for tar and it couldn't find it. I couldn't find it manually either. So now I am converting the whole zip file to a tar. Gonna take a while for 1.6 gigs
Click to expand...
Click to collapse
You shouldn't have to do that. Do you have a link to what you downloaded?
Atmazzz said:
You shouldn't have to do that. Do you have a link to what you downloaded?
Click to expand...
Click to collapse
I have so many but I am going to look them up and post them here in a minute. This is the one that I am downloading now. It actually completed but when I opened it, it came back with some errors so I am guessing it just didn't download right. I will get the links for the others in a few min.
http://forum.xda-developers.com/showthread.php?t=2274795
Here are some of the other ones.
http://forum.xda-developers.com/showthread.php?p=40962344&highlight=uvuamdl+4+2+2#post40962344
http://forum.xda-developers.com/showthread.php?t=2258628
I chose this one on there: Download UVUAMDL Official TAR
Jason
Outrung2 said:
I have so many but I am going to look them up and post them here in a minute. This is the one that I am downloading now. It actually completed but when I opened it, it came back with some errors so I am guessing it just didn't download right. I will get the links for the others in a few min.
http://forum.xda-developers.com/showthread.php?t=2274795
Click to expand...
Click to collapse
Outrung2 said:
Here are some of the other ones.
http://forum.xda-developers.com/showthread.php?p=40962344&highlight=uvuamdl+4+2+2#post40962344
http://forum.xda-developers.com/showthread.php?t=2258628
I chose this one on there: Download UVUAMDL Official TAR
Jason
Click to expand...
Click to collapse
OK, your first two links are custom Roms you flash in recovery. You don't unzip those. The last one, k0nane's thread, that's the stock firmware. Unzip and use Odin to install it.
Atmazzz said:
OK, your first two links are custom Roms you flash in recovery. You don't unzip those. The last one, k0nane's thread, that's the stock firmware. Unzip and use Odin to install it.
Click to expand...
Click to collapse
Well that is my problem. The last 2 wouldn't flash on there. I don't understand why. Let me try the one you said to do through Odin.
When I click to open so I can unzip that file I get this from winrar. ! B:\Users\Jasons\Downloads\ModdedUAMDL_v2.zip: Unexpected end of archive
I am assuming it just didn't download right so doing it again.
Outrung2 said:
When I click to open so I can unzip that file I get this from winrar. ! B:\Users\Jasons\Downloads\ModdedUAMDL_v2.zip: Unexpected end of archive
I am assuming it just didn't download right so doing it again.
Click to expand...
Click to collapse
If its saying modded, that's not the one you flash in Odin. That's a custom ROM. For Odin, its the one in k0nane's thread. The last link you posted.
With me not reading about Samsung latest OTA locked bootloader , I rooted my phone, installed TWRP and updated SU, them I am stuck at a soft brick at the download mod, I have tried every possible way with ODIN to no luck, I always kept booting to the damn download mod, then accidentally I was able to flash this pit file to bypass the stuck download mod and was able to boot normally
All you need is ODIN and the attached pit file,
1. Download attached file and unzip it
2. Run ODIN
3. Click on pit
4. Loacate the unziped SGS-I337_16GB.pit file and load it
5. Click start, phone will reboot when when compelete
6. Done
Thought to share my findings
Good Luck Don't forget to Hit the Thanks Button
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
scott14719 said:
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
Click to expand...
Click to collapse
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
iB4STiD said:
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
Click to expand...
Click to collapse
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
nkhater said:
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you tell me where the original information came from (a link)?
scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
scott14719 said:
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
Click to expand...
Click to collapse
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I added some Ninja edit info to my last post...
nkhater said:
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
i say fire up odin and try to downgrade to amdl :good:
iB4STiD said:
i say fire up odin and try to downgrade to amdl :good:
Click to expand...
Click to collapse
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
scott14719 said:
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
Click to expand...
Click to collapse
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
iB4STiD said:
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
Click to expand...
Click to collapse
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
scott14719 said:
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
Click to expand...
Click to collapse
ya, wiping cache in stock recovery, will kick the phone out of bootloop
iB4STiD said:
ya, wiping cache in stock recovery, will kick the phone out of bootloop
Click to expand...
Click to collapse
And here is another example of someone getting out of a bootloop through Download (ODIN) mode:
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
Possibly, Odin triggered a similar reaction.
Actually, the original thread i pulled that post out of sounds very similar to what happened to the OP in this post.
Take a look at the OP of this post to see what I mean:
http://forum.xda-developers.com/showthread.php?t=2398336
So, I think my theory is correct. The PIT file never actually flashed, it was the interaction between ODIN and D/L mode that overcame the bootloop.
But hey, feel free to keep messing around with the PIT file because you never know...
I wonder where op went...
Sent from my SGH-I337 using xda premium
orlandoxpolice said:
I wonder where op went...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
OP was sleeping and just woke up will reply shortly
Sent from my GT-N7105 using xda app-developers app
scott14719 said:
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
Click to expand...
Click to collapse
Sorry if this off topic but what's stopping someone from wiping the bootloader partition and flashing the MDL firmware?
I'm not sure if this would be done via a PIT file, ADB script or some other method but in general isn't this the path of last resistance for achieving root/bootloader access?
scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Here is the link
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
I use the Sprint SlimBean ROM and I had no issues with it on my SCH-S960L. I had no issues with my mobile connection except for the fact that it it took some time to connect to mobile data services or even required a restart or Airplane mode toggled. This along with it sometimes did not switch between 3G and LTE when it should. Because of this I attempted to flash a newer Sprint Galaxy S3 modem. This completely disestablished any connection to services. It has 0 bars and cannot make calls, send texts, or use data. I have tried to reflash the ROM but of course, it did not help at all.
Now in the light of hope, I made a backup of the efs and firmware folders before flashing. I'm not sure how I can fix my issue with this but it was suggested to do so before flashing.
My baseband version was S960LWYAMD6. While I could reflash the old modem, (with help) I would prefer a better modem. (if there are any)
Any help is appreciated.
With best regards,
SirBenjamin
Well this just may be your day. Apparently chxnugs just posted the Modem for your particular device HERE. I would update PRL / Profile first just to see if that will help. Also have you tried ##72786# ?
prboy1969 said:
Well this just may be your day. Apparently chxnugs just posted the Modem for your particular device HERE. I would update PRL / Profile first just to see if that will help. Also have you tried ##72786# ?
Click to expand...
Click to collapse
chxnugs said:
i know this is sprint galaxy s3 section, but the straight talk s3 is basically the same phone and there is no section for it.
if you own this particular model, then you would know that its pure hell trying to find ANY files. this is the stock MD6 modem.bin ripped from my phone. ive seen people ask for this modem because they flashed the MD4 modem in hopes of getting their MSL and/or for the benefits of being able to use the 16-digit password. (which reminds me.. i have read of ways to port the 16-digit password from a .dll file in the phone? i have done loads of searching, but the password is NO WHERE to be found) and needed the stock modem. so for anyone that needs it here it is.
hopefully us ST S3 users will eventually gather up all the odin files to completely restore our phones when needed
Click to expand...
Click to collapse
I tried to flash the file chxnugs provided. I used both Mobile Odin and replaced the modem file in another flashable ZIP. Neither of them worked and I still get 0 bars/unknown baseband.
Honestly I have no idea what to do to fix this but it needs to work.
Again I say, all help is appreciated.
ok i extracted a fresh modem.bin straight from my phone. let me know if it works
Oh and just asking.. have you extracted the .bin file from the zip and tried it
Sent from my SCH-S960L using Tapatalk
chxnugs said:
Oh and just asking.. have you extracted the .bin file from the zip and tried it
Sent from my SCH-S960L using Tapatalk
Click to expand...
Click to collapse
chxnugs said:
ok i extracted a fresh modem.bin straight from my phone. let me know if it works
Click to expand...
Click to collapse
I got the same results. I extracted the .bin but renamed it to NON-HLOS.bin since Mobile Odin would not accept it as modem.bin. Am I flashing this wrong?
Sent from my SCH-S960L using Tapatalk
Did you try any of my other suggestions form post #2 ?
im sure your trying to flash it under phone section.. i managed to try to make a flashable CWM version. maybe you can try that and let me know if it works
prboy19648801865 said:
Did you try any of my other suggestions form post #2 ?
Click to expand...
Click to collapse
chxnugs said:
im sure your trying to flash it under phone section.. i managed to try to make a flashable CWM version. maybe you can try that and let me know if it works
Click to expand...
Click to collapse
Proby, I tried to do the other things you suggested. I can't update the PRL/Profile since I'm on a custom ROM. That is unless there is another way. I did not understand what you meant with the number you mentioned. If you wanted me to call that it did nothing.
As for chx, unfortunately it still did not fix it. This quick little modem update is turning into a nightmare. Not only that, but no sound plays, the microphone does not work, and DSP Manager crashes whenever I try to play media.
I really appreciate both of your support though.
Yay! I used Mobile Odin Pro and flashed a file from another thread. It may have been the file or using Mobile Odin Pro since it downloaded the correct driver. I appreciate all of your help, though.
Sent from my SPH-L710 using Tapatalk
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
jester12345 said:
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can someone post a pit file for me?
Look in the general section.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2609871
messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.
Zen Arcade said:
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.
Click to expand...
Click to collapse
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.
messerchmidt said:
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.
Click to expand...
Click to collapse
Did the stock rom work?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do
Which non-stock rom? After flashing it are you able to get into recovery mode? Does this rom by any chance flash a modem.bin?
If a stock rom loads ok, chances are your pit mapping is OK.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
messerchmidt said:
yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do
Click to expand...
Click to collapse
Sounds to me like ur definitely not giving the roms enough time on the boot. Some could take 5-7 minutes for initial boot. The fact that stock works and EVERY OTHER ROM here doesn't... leads me to believe this. Patience is virtue
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
also, someone at your skill level should not be messing with partitions; you are just asking for a brick..
Not to mention the likely requirement of fully wiping the internal storage of the device...
Arbitrarily changing frameworks back and forth without wiping the file structure first will give you problems on boot...(boot loops)...
Additionally....once the rom is flashed...it may help to immediately go to recovery and wipe the device caches and data again...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
listen to greg; he is an authority on re-partitioning and bricking! :victory:
wase4711 said:
listen to greg; he is an authority on re-partitioning and bricking! :victory:
Click to expand...
Click to collapse
ok i will try again and keep you posted
got it working after several tires, running the 4.3 jedi x2
:good: