I've tried many different roms, actually all that are available for the gt-s5660 and iv noticed that i can only use roms flashable from cwm recovery. My phone is the gt-s5660m and the baseband is unique. My phone cant run Asia or Europe firmwares so I was wondering, why do some roms preserve the baseband and others will change it?
All you have to do is to open up the "One Package" tarball with 7-Zip, and delete the amss file in it to remove the baseband.
In fact, you should only have system.rfs and maybe boot.img in there. Avoid flashing bootloaders for not reason.
Check out my partition thread for more info.
So your saying that if I just delete the amss file my baseband will be preserved no matter what rom I flash hypothetically?
turner2914 said:
So your saying that if I just delete the amss file my baseband will be preserved no matter what rom I flash hypothetically?
Click to expand...
Click to collapse
Yes, the baseband will not be replaced because thats in the amss file, so it wont be flashed
Sent from my GT-S5660 using xda premium
thabk you very much this was extremely helpful
Sent from my GT-S5660M using XDA App
I have deleted the amss file but how do I repackage it into a .tar? Because i tried to use 7zip and it made the .tar but when i went to flash it with odin, it was stuck on loading the boot.
turner2914 said:
I have deleted the amss file but how do I repackage it into a .tar? Because i tried to use 7zip and it made the .tar but when i went to flash it with odin, it was stuck on loading the boot.
Click to expand...
Click to collapse
Ccouldnt you open the .tar and delete the amss file inside??
Sent from my GT-S5660 using xda premium
voetbalremco said:
Ccouldnt you open the .tar and delete the amss file inside??
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
my friend you cant do that.if you want to pack a package flash will odin,you need to use the command “tar -cf” on a linux os
Sent from my GT-S5660
Oh well i guess im out of luck because I dont have linux
Sent from my GT-S5660M using XDA App
You can package with Cygwin and the tar command included under Windows with no problem. Actually, both my stock ROM backup and Odin-flashable releases of ArpegGioMod were done like that.
czkwg8: Odin doesn't like tarballs created by 7-Zip, or WinRar, or WinZip (probably has to do with missing/incorrect file system permissions stored in the archive), but I never had problems with using those to remove files from an existing and valid archive.
Darkshado said:
You can package with Cygwin and the tar command included under Windows with no problem. Actually, both my stock ROM backup and Odin-flashable releases of ArpegGioMod were done like that.
czkwg8: Odin doesn't like tarballs created by 7-Zip, or WinRar, or WinZip (probably has to do with missing/incorrect file system permissions stored in the archive), but I never had problems with using those to remove files from an existing and valid archive.
Click to expand...
Click to collapse
so sorry,maybe i should use 7-zip to delete files instead of winrar……
Sent from my GT-S5660
Darkshado said:
All you have to do is to open up the "One Package" tarball with 7-Zip, and delete the amss file in it to remove the baseband.
In fact, you should only have system.rfs and maybe boot.img in there. Avoid flashing bootloaders for not reason.
Check out my partition thread for more info.
Click to expand...
Click to collapse
I realize that this post is off topic, and I offer my deepest appologies... But when you mentioned "tarball", this is what i thought of...
http://www.latenightwithjimmyfallon...song-about-the-oil-spill-balls-in-your-mouth/
While the version i saw was done a capella by jimmy on the Engadget Show back when Joshua Topolsky was chief editor at Engadget, this version illustrates it nicely.
remove amss file in zip
I am trying to flash CyanogenMod 9 (ICS) on my Gio (S5660M)
How would I remove the amss file if it is meant to flash in CWM?
I opened up the zip file and couldn't find the amss file.
no need, just flash, you only delete if you use odin because it changes baseband from 5660M to 5660 but cwm doesnt
well, I went ahead and flashed it but bricked my phone. Fortunately, I found a way to get back into download mode. Close call there, I guess I'll just stick with Arpeggio for now.
You probably didn't brick, just dropped into infinite loop. If I am not mistaken, your phone is 5660M so not all ROMs are compatible with your phone. Try to check the posts, some people mod the ROMs for M and other versions of Gio, some are already compatible. But check first and ask if you are not sure.
DeviantSun said:
You probably didn't brick, just dropped into infinite loop. If I am not mistaken, your phone is 5660M so not all ROMs are compatible with your phone. Try to check the posts, some people mod the ROMs for M and other versions of Gio, some are already compatible. But check first and ask if you are not sure.
Click to expand...
Click to collapse
you have to go into recovery, clear data and cache, then flash rom, and before you reboot normally, you have to clear data and cache one more time for it to work
i learned that the hard way as i had the infinite loop my first few times
DeviantSun said:
You probably didn't brick, just dropped into infinite loop. If I am not mistaken, your phone is 5660M so not all ROMs are compatible with your phone. Try to check the posts, some people mod the ROMs for M and other versions of Gio, some are already compatible. But check first and ask if you are not sure.
Click to expand...
Click to collapse
Well, it only showed the word Samsung then the screen turned black. It didn't even get to the boot animation. I'm pretty sure it was bricked because I couldn't get into recovery. I can't find any ICS roms that work for S5660M. Only Arpreggio.
Success!
I searched around and found out that it does work on 5660M. I just had to wipe after I flash the CM. I thought it bricked again because the screen turned black before the boot animation. I waited for a minute and then the cyanogen mod boot screen came up! It works now thanks for everyone's help!
no problem man thats what xda is for
Sent from my GT-S5660 using xda premium
edit: and what do you mean by search around to find out you have to wipe after o: my post says that and it was from july 1
Related
I have read that some people prefer to use Mobile Odin Pro to flash roms, kernels and such in place of CWM. I know how to use it when the files are in the tar format but I am wondering if there is a way to flash roms that are in the zip format and made for CWM? Am I missing something or did I misunderstand what I read?
Thanks in advance.
Sent from my SPH-D710 using xda premium
unfortunately if its in zip I believe its only through cwm. just like regular odin.
OK, so the roms have to be in the tar format. Is there a way to repack the zip into a tar that can be flashed via Mobile Odin Pro?
Sent from my SPH-D710 using xda premium
Not really sure about this but if you use root explorer and press and hold on a file it will give you an option to convert to tar file or something like that. Idk if that would work or not but just happened to notice it last night.
Sent from my SPH-D710 using XDA App
although rootexplorer does format it into tar it won't flash via odin or mobile odin. the only way I know of is to have a linux partition on your computer. other than having linux it won't work. it may be in tar format but it needs to know where to put those file in which place. and just converting it to tar doesn't work. I have even tried putting a pit file in with the files in a tar and it didn't work.
OK, that's what I thought but I figured I'd ask. Thanks for your answers.
Sent from my SPH-D710 using xda premium
no worries man. anytime. I don't know everything but what I do know I'll gladly share
patrao_n said:
unfortunately if its in zip I believe its only through cwm. just like regular odin.
Click to expand...
Click to collapse
lol thats not true.. yes .zips are made for cwm, but if you notice in mobile odin pro it can actually open certain types of files and extract the different parts of it to flash such as kernel, modem, etc. etc. this is how i flashed a zip through mobile odin pro, however for whatever reason gave me issues with the modem.. on ICS, I had to flash rogue fb17 kernel to get cwm back, then flashed the fb21 modem through cwm. either way, there is a way to extract the files from the .zip to be flashed in mobile odin.. there is a setting in the app that says open and extract the files.. have a look see! besides all that, I love mobile odin and prefer to use it when possible over using cwm anyday..
well I do not doubt that you used it. however I have many roms in. zip format. when I try to use the extract feature the only ones I can extract from are the. tar and tar.md5 files. maybe I'm messing up or something.
I have tried to open zip files using the method you suggested and it's like it doesn't see the zip file in the directory I put it in.
Sent from my SPH-D710 using xda premium
when I do it I look in the directory and it only sees the tar files I have of the stock tars I have in the same directory. I have looked into it on chainfires thread and it makes no mention from what I have seen of flashing rom zips.
Check out the video on this page
http://www.madteam.co/2012/02/11/mobile-odin-now-supports-galaxy5/
I think he's flashing a full rom.
mgd76 said:
Check out the video on this page
http://www.madteam.co/2012/02/11/mobile-odin-now-supports-galaxy5/
I think he's flashing a full rom.
Click to expand...
Click to collapse
ya it is a full rom. but its in tar format. I was under the impression from the other poster in here zip were flashable too. I realize that what cwm is for. I have used mobile odin many times. and I'm almost positive it does not flash zips. just figured if he did it he might want to share.
hmmm
My plan was to only use m.o. to flash, (after root via 2c) so I'll have to figure this out...
patrao_n said:
although rootexplorer does format it into tar it won't flash via odin or mobile odin. the only way I know of is to have a linux partition on your computer. other than having linux it won't work. it may be in tar format but it needs to know where to put those file in which place. and just converting it to tar doesn't work. I have even tried putting a pit file in with the files in a tar and it didn't work.
Click to expand...
Click to collapse
could you explain how to do this in linux?
Thanks!
i dont know how to do it in linux. i just know when i googled gow to do it all tge tutorials said linux was needed. sorry man
firemedic624 said:
I have read that some people prefer to use Mobile Odin Pro to flash roms, kernels and such in place of CWM. I know how to use it when the files are in the tar format but I am wondering if there is a way to flash roms that are in the zip format and made for CWM? Am I missing something or did I misunderstand what I read?
Thanks in advance.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I could flash my kernel using 'zImage' file using Mobile ODIN.
TLR Version. Don't. If it was meant for CWM use it in CWM.
I don't think you guys are going to have any luck with that. When (Mobile) odin flashes a tar file it is flashing a factoryfs.img. When CWM flashes a zip it copies the files over.
You could, in theory*, convert the flash-able zip into a flash-able tar by moving the files in the zip into a proper factoryfs.img or a system.img... but its not really an easy task and you're VERY likely to end up with a (almost**) permanent brick and or paperweight.
So just don't. You can flash Kernels and full system restores tars with it, but other than that, I wouldn't play with it.
* I say in theory because I'm not gonna test it. I don't see why I wouldn't, but there is no reason to risk anything.
**You could probably unbrick it with a JTAG, but that is a whole different mess.
Clearing cache before flashing
I'm a beginner. My last cell phone was very old and could only make calls, and I jumped into the s3 because I heard it's a good phone.
I've figured out how to root it and unlock it, and I have installed mobile odin pro. I copy the zipped rom directly to my phone and start mobile odin pro, which asks me if I want to unzip the rom and install it. Well, yes, I do. So it goes about doing its thing, reboots, and fails. I have tried installing three different roms with the same result each time.
My question is this: will mobile odin pro automatically clear the cache, the darvik cache and so on? Or should I do this manually from within the mobile odin pro app before flashing the rom?
Any help will be much appreciated
If you have an s2 this is not the forum for you. Just a heads up. Anything flashable from this s2 forum will wreck your phone
sent from my BAD A$$ Epic touch
Seem to have gotten myself in another bind :/
Ok, so I flashed a ICS ROM and as usual I want to flash something else(I admit its a bad addiction! ). Unfortunately, my OEM cable isnt working and so odin can't recognize the phone!
SO I have mobile odin installed but I need the correct files. Never had to use it until now, I thought I had a correct kernel/recovery to flash but it says "partition not recognized"
So please mind that I will have to download the files DIRECTLY from my phone. I will seriously LOVE anyone who can help me out
Go to the wiki, found in the sticky section, you're looking for el26 kernel with cwm tar file. In mobile Odin, click kernel and find the file. Check md5 and go. During reboot, Press and hold volume up and power till you get to cwm. Do your wipes and flashing there. Good luck!
Sent from my SPH-D710 using Tapatalk 2
thegoodrat said:
Seem to have gotten myself in another bind :/
Ok, so I flashed a ICS ROM and as usual I want to flash something else(I admit its a bad addiction! ). Unfortunately, my OEM cable isnt working and so odin can't recognize the phone!
SO I have mobile odin installed but I need the correct files. Never had to use it until now, I thought I had a correct kernel/recovery to flash but it says "partition not recognized"
So please mind that I will have to download the files DIRECTLY from my phone. I will seriously LOVE anyone who can help me out
Click to expand...
Click to collapse
Assuming you are using something from the OneClick thread, you need to unpack the file first, either double-click the .exe in windows to unpack or use zarchiver on android. The resulting file can be use with Mobile ODIN using Open File.
Here's the el26 cwm kernel
http://db.tt/jUNENJGl
Sent from my SPH-D710 using Tapatalk
thegoodrat said:
So please mind that I will have to download the files DIRECTLY from my phone. I will seriously LOVE anyone who can help me out
Click to expand...
Click to collapse
There are several apps like Wifi File Browser that you can install on your phone that will allow you to transfer files back and forth from your pc/phone if necessary. Really nice to use too.
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 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.
my tab GT P5210 10.1 wifi
is rebooting showing only samsung galaxy tab 3
is there anyway to fix it?
i have tried 4 stock roms
and prerooted firmware too but no luck
does any one have this pit file???
GT-P5210_EUR_XX_20130523.pit
I'm trying to get you that file and I'll post a link if I get it.
Isn't the pit already set for stock roms? Of the four you say you used, were they official like from Samfirmware?
Also did odin say they were successful?
Sent from my GT-P5210 using XDA Premium HD app
Benzoman said:
I'm trying to get you that file and I'll post a link if I get it.
Isn't the pit already set for stock roms? Of the four you say you used, were they official like from Samfirmware?
Also did odin say they were successful?
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
yes all stock roms were from samfirmware and flashing went smooth with odin
um pretty sure its not the rom problem
its partition problem
so thats why i was looking for pit file
or do you have this kernel file?
3.4.34-601491
[email protected] #1???
pit file is available here
http://www.dlgsm.com/index.php?dir=..._4.2.2/P5210ZHUAMH1_P5210ZZHAMH1_P5210ZHUAMH1
but unfortunatly um unable to download from this site
I'm not positive of the reliability of the source so use at your own risk!
Unzip the file to get the .pit had to zip it to upload it here.
Hope this helps. Took forever to find this file without having to pay for it.
Sent from my GT-P5210 using XDA Premium HD app
thx
but u sent for p5200
and um looking for p5210
The gt-p5210 pit seems to be impossible to find unless you speak farsi and want to pay a site in Iran for it.
But dont give up hope. I have a couple feelers of there and maybe I'll get a bite for you.
In the mean time you just might want to give the 5200 pit a shot. Cant hurt too much being you're in a bootloop already.
But of course I must say do it at you own risk.
Sent from my GT-P5210 using XDA Premium HD app
yes i have tried that pit too u sent
did'nt work
do u have kernel file ?
or seperated files
BOOTLOADER_P5210ZHUAMH1_1246052_REV00_user_low_ship.tar.md5
CSC_ZZH_P5210ZZHAMH1_1246052_REV00_user_low_ship.tar.md5
GT-P5210_EUR_XX_20130523.pit
PLATFORM_P5210ZHUAMH1_1246052_REV00_user_low_ship.tar.md5
like they have on their site
Found anything?????
Sheeda Talli said:
Found anything?????
Click to expand...
Click to collapse
Sorry nothing yet.
Sent from my GT-P5210 using XDA Premium HD app
Any news on how you fixed your problem, and if you have pit file?
On PIT File
Sheeda Talli said:
does any one have this pit file???
GT-P5210_EUR_XX_20130523.pit
Click to expand...
Click to collapse
mohali256 said:
Any news on how you fixed your problem, and if you have pit file?
Click to expand...
Click to collapse
according to this thread http://forum.xda-developers.com/showthread.php?t=2643970 post #3 by user @r2d23cpo
this should be the pit file. see attachment rename GT-P5210_EUR_XX_20130523.pit.txt to GT-P5210_EUR_XX_20130523.pit
m
@mohali256
You have not mention why you need the pit. The pit mention before was grabed from P5210 using the following command in terminal or adb:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
once you execute, go to your Sdcard folder and look for out.pit.
This is a command many Samsung devices share. I am confidece that the output is correct. But no one has confirmed using it succefully.
In any case I sugest you use that command your self to get your own pit and compare with the one I posted in my original post.
r2d23cpo said:
@mohali256
You have not mention why you need the pit. The pit mention before was grabed from P5210 using the following command in terminal or adb:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
once you execute, go to your Sdcard folder and look for out.pit.
This is a command many Samsung devices share. I am confidece that the output is correct. But no one has confirmed using it succefully.
In any case I sugest you use that command your self to get your own pit and compare with the one I posted in my original post.
Click to expand...
Click to collapse
R2,
yup, i pulled this file from my own tab gt-p5210. did that the day you posted the command :good:
i just avoid the pit file approach if i can help it.
m
@moonbutt
4.4.2 Is a troubled game! You never can be sure what is going on if you change things in system!.
In a worst case a loop-boot can be as result of Lock boot failing dm-verify!
Google suggest Manufacturers to start enforcing on a limited population for testing!. Who knows maybe that is the root cause!
Just as some Galaxy S4, that got screw by Samsung!!!!. Bad weather is coming!
I been adding libraries.ko to mount my wireless hard drive. The libraries do not survive for long and they get purge of \system in short time. New Installed KO's never survive a reboot!
Even compiling the kernel act weird. I can not select all libraries. If I go and edit .config manually, when I execute make, a script revert back what I had change so that the lib.ko do not get build!!!
I have not double check but the wifi symbol at then top keep showing the something is downloading!
This make me think? Did you guys did not forgot to disable OTA updates?
Did you ever get this to work?
I have tried the pit file and different stock versions of the OS but I still keep getting a reset after the Galaxy Tab 3 screen and then it like acts like it's going into recovery and even if i have twrp it'll show it for a brief second and then reboot again.
I am about ready to throw this stupid thing in the recycling bin.
sorry to bother... i just tried to upgrade my Tab 3, and now it is stuck in an endless boot loop.
i've tried flashing my tablet with Odin 3.07 with the factory image, a pre-rooted image and also cyanogenmod 12.1 - all have appeared to be successful, but the result is the same - boot loop.
i've also gone through loading the 3 images on the MicroSD card and installing them via recovery mode. i was careful to wipe the data and cache partitions prior.
still, endless boot loop. i'd really rather not recycle this device... if anyone can help, it would be greatly appreciated!
thanks!
just a heads up. i was able to fix my Tab today.
this video shows all the steps outlined. basically, install TWRP, clear all the partitions (on the internal storage), install your image.
https://www.youtube.com/watch?v=lflnn850jRw