Related
Downloads here: http://invisiblek.chickenkiller.com/pits/
Everything below this line is for historical significance, I've acquired what is needed here. Thanks!
==================================================================================
Hey guys, I'm from the VZW version of the device, but I'm trying to accumulate all of the PITs for each variant since they are all signed, they are all different. I'm doing this just in case they are needed by someone in the future, we won't have to scramble to find one.
Its quite a simple process, just need one command run from a root shell (adb or terminal emulator) then an upload of the file.
Command to run:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
You may upload /sdcard/out.pit to dropbox, mediafire, whatever.
I need a 32gb PIT. You may respond here or PM me, please include what size phone you have.
Thanks in advance!
FYI: A PIT is a partition information table, it basically tells Odin where to put things when you flash.
Pm'd you the 16gb
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Pm'd you the 16gb
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hmm, still don't have a PM from ya
It's the thought that counts right? =P
You can post here in the thread too, nothing is specific to your device or anything like that, no security risks here.
Weird. I know I hit submit....oh well. Here is the 16gb T999 pit file.
http://minus.com/mE5IIlBjE
You will need to unzip it.
Tried to attach it here but I'm on my phone and it wouldn't let me.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Weird. I know I hit submit....oh well. Here is the 16gb T999 pit file.
http://minus.com/mE5IIlBjE
You will need to unzip it.
Tried to attach it here but I'm on my phone and it wouldn't let me.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thank you!
invisiblek said:
Hmm, still don't have a PM from ya
It's the thought that counts right? =P
You can post here in the thread too, nothing is specific to your device or anything like that, no security risks here.
Click to expand...
Click to collapse
I didn't think it did. Was just thinking it'd be easier for you to keep track if it was in your pm's.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
I didn't think it did. Was just thinking it'd be easier for you to keep track if it was in your pm's.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
No worries, link in the OP with all the PITs I've gathered so far
Just missing the T-Mo 32gb and US Cellular
Cool! I completely missed that link!
Anyway, the other two are here, just a matter of getting them to come out and play!
Glad I could help btw.
And thanks for your work on it!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Cool! I completely missed that link!
Anyway, the other two are here, just a matter of getting them to come out and play!
Glad I could help btw.
And thanks for your work on it!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Do you still need the T-Mobile 32GB image?
T-Mobile T999 w/32GB file for you
Attached to this post is the pit file you asked for zipped.
I am running a Stock T-Mobile T999 32GB (IMM76D.T999UVALEM) with updated radio (T999UVLH2). The phone is rooted and partially de-bloated. Triangle Killer has been run.
Let me know if you need anything else.
ChitownWingMan said:
Attached to this post is the pit file you asked for zipped.
I am running a Stock T-Mobile T999 32GB (IMM76D.T999UVALEM) with updated radio (T999UVLH2). The phone is rooted and partially de-bloated. Triangle Killer has been run.
Let me know if you need anything else.
Click to expand...
Click to collapse
Awesome, thank you!
So what can these be used for?
stevessvt said:
So what can these be used for?
Click to expand...
Click to collapse
not to be an arse but...
http://lmgtfy.com/?q=what+is+a+pit+file+used+for
(ok, that was arse-ish, but seriously)
invisiblek said:
not to be an arse but...
http://lmgtfy.com/?q=what+is+a+pit+file+used+for
(ok, that was arse-ish, but seriously)
Click to expand...
Click to collapse
Yes, a little, but I lol'ed. But I thought that pit files would be pushed out by Samsung, like tar files. We can spit out our own pit files to reuse with Odin later if our partition tables get messed up?
stevessvt said:
But I thought that pit files would be pushed out by Samsung, like tar files. We can spit out our own pit files to reuse with Odin later if our partition tables get messed up?
Click to expand...
Click to collapse
I've not seen any come from Samsung, so I figured we could pull them from our devices and make our own collection.
Yes, it would help if partitions get messed up (although if that happens, you might be in worse shape than just needing a PIT.
A 32gb VZW user bricked his phone and got it JTAG'd back to life, but the person who JTAG'd it only had a 16gb image. So the partitions were messed up and he didn't have the full 32gb of space.
He was able to flash with the PIT from my 32gb VZW SGS3 and then flash a ROM and got all his space back.
Hey there I ran the line of code in the OP in a root shell in ADB and this file Ive attached is what it spit out. Its from a Rogers 16gb I747M. Hope you can make more out of it then me!! Have fun
I want to thank everybody involved in this project for the pit files :good:
Does somebody have "a working" T999 32Gb pit?
I tried the one posted on here but right away I knew it was not going to work ...all the other pits are 3-4 kb in size, the T999 32Gb is 240kb or am I missing something?
Before I get the " you shouldn't be using a pit..." I am trying to fix a 32Gb T999 that was Jtagged and was partitioned at some point with a 16Gb pit.
Thanks in advance!
This is amazing. We now have PIT files for the OG S3.
Now if we can get the LTE Version of the S3 TMo.
THIS should be stickied or something.
PIT Files are an underdog life saver. Just like what Invisiblek just said, lost his other 16 GB space, but with his PIT file, bam, back all of that 32GB.
BUMP!!!
ndwgs said:
This is amazing. We now have PIT files for the OG S3.
Now if we can get the LTE Version of the S3 TMo.
THIS should be stickied or something.
PIT Files are an underdog life saver. Just like what Invisiblek just said, lost his other 16 GB space, but with his PIT file, bam, back all of that 32GB.
BUMP!!!
Click to expand...
Click to collapse
I already have it if someone needs it.
Hey Doc,
Did you say you happen to have the S3 T999 32Gb pit?
I think the one on here was extracted with the wrong shell commands...so it's not going to work.
I tried modifying a 16Gb pit with pit magic but that didn't work either because I believe they are "signed" pits and pit magic trims off the signature.
Thanks!!
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
Dear Members...
those who want to restore I747 4.3 stock rom.
here is the link for that files...
https://www.mediafire.com/folder/w5czcxvufdiaw/I747UCUEMJB_ATTEMJB_4.3
:good:
Awesome
Sent from my SAMSUNG-SGH-I747 using Tapatalk
ashamsu said:
Dear Members...
those who want to restore I747 4.3 stock rom.
here is the link for that files...
https://www.mediafire.com/folder/w5czcxvufdiaw/I747UCUEMJB_ATTEMJB_4.3
:good:
Click to expand...
Click to collapse
Where did this come from?
Something not right. File size only 100MB?
Where did this come from?
I noticed when I followed the link it is a series of 100MB files. And 1 16 megabyte file. Something is not right about this one...also no explanation as to any details.
There is an Odin package for this on www.samsung-file.com but I don't know anything about that site and how reliable it is. It would be great if it was legit.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I've downloaded the files, and extracted them with 7zip. It's the same files on the website I referred to, www.samsung-file.com. I've extracted the system image and looked at the build.prop. From what I can tell it looks legit and has a build date of October 31, 2013. Unfortunately, the bootloader is where the danger lies. I don't know enough about what I'm doing to judge anything by it and am a little too chickens**t to try it out.
It's each individual file, not packaged in one tar? Hmm. Bootloader should be unimportant. Anyone needing to return to stock and needing to use this would most likely already have the mjb bootloader. No need to flash it again.
Its packaged in a tar. I just extracted it to poke around. It's actually 4 tars and a pit file. An ap, a bl, a csc, and a cp.
Sent from my GT-N5110 using Tapatalk
mrhaley30705 said:
It's each individual file, not packaged in one tar? Hmm. Bootloader should be unimportant. Anyone needing to return to stock and needing to use this would most likely already have the mjb bootloader. No need to flash it again.
Click to expand...
Click to collapse
As long as the files are in a folder or in an area on your computer all together, extracting them should make just one file. You typically do not see this with ROMs, it's mainly a media thing if you want to compress something really small but you keep the quality.
Dear Members...
the file i given here is original, that i used to one i747 which hangs at samsung logo.
Originally the file came with .md5 extention, i renamed to .tar format. Becauses in my computer md5 checksum takes more time before flashing in ODIN.
I will do this for all files, which is big in size.
And the important about this file is, it was taken from my support site. So users no need to worry....:good:
ashamsu said:
Dear Members...
the file i given here is original, that i used to one i747 which hangs at samsung logo.
Originally the file came with .md5 extention, i renamed to .tar format. Becauses in my computer md5 checksum takes more time before flashing in ODIN.
I will do this for all files, which is big in size.
And the important about this file is, it was taken from my support site. So users no need to worry....:good:
Click to expand...
Click to collapse
ok the phone is booting normally or the phone hangs at samsung logo?
and how do you flash ap, bl, cp files? a odin screenshot with files placed correctly would be helpful.
tejajuloori said:
ok the phone is booting normally or the phone hangs at samsung logo?
and how do you flash ap, bl, cp files? a odin screenshot with files placed correctly would be helpful.
Click to expand...
Click to collapse
Dear Member...
file selection is easy. See the attachment...
Use ODIN 3.09...
:good:
So to verify, one could use this without bootloaders and it would not trip warranty bit?
Sent from my LG-V500 using Tapatalk
Seeing the Odin 3.09 shot makes sense now. Thanks.
I used this tonight and it worked without a hitch...
I always liked using Odin to go back to stock every so often since I flash a lot. I don't know if or how this differs from the routine enewman put together to return to stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
lordmorphous said:
I used this tonight and it worked without a hitch...
I always liked using Odin to go back to stock every so often since I flash a lot. I don't know if or how this differs from the routine enewman put together to return to stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Do you know if this method trips the warranty bit? I'm trying to determine if in the future I wanted to go back to stock and grab the KitKat OTA, that this would be a viable method. I'm concerned the OTA might not work if the warranty bit is tripped.
Sent from my LG-V500 using Tapatalk
Carsus55 said:
Do you know if this method trips the warranty bit? I'm trying to determine if in the future I wanted to go back to stock and grab the KitKat OTA, that this would be a viable method. I'm concerned the OTA might not work if the warranty bit is tripped.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I don't know...I think my warranty bit was already tripped. How could I tell?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
lordmorphous said:
I don't know...I think my warranty bit was already tripped. How could I tell?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
You'd have to go in to download mode, then you would see an indicator...
Sent from my LG-V500 using Tapatalk
Carsus55 said:
You'd have to go in to download mode, then you would see an indicator...
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Mine says Warranty Bit: 1 both before and after flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk