The structure of the PIT is defined below:-
Code:
Based on PIT u1_02_20110310_emmc_EXT4.pit
Partition Name LEN LEN in BLK OS Partition Physical Partition
GANG 00000000 0000 0
BOOT 00000000 0000 1
EFS 013FFFFF 00A0 0p1 4
SBL1 0013FFFF 000A 0p2 2
SBL2 0013FFFF 000A 0p3 3
PARAM 007FFFFF 0040 0p4 5
KERNEL 007FFFFF 0040 0p5 6
RECOVERY 007FFFFF 0040 0p6 7
CACHE 063FFFFF 0320 0p7 8
MODEM 00FFFFFF 0080 0p8 9
FACTORYFS 1FFFFFFF 1000 0p9 a
DATAFS 7FFFFFFF 4000 0p10 b
UMS 2E07FFFFF 1704000 0p11 c
HIDDEN 1FFFFFFF 1000 0p12 d
The offsets in the flash are as follows:-
Code:
Partition Name START
GANG 0x0000000000000000
BOOT 0x0000000000000000
PIT 0x0000000000004400
EFS 0x0000000000400000
SBL1 0x0000000001800000
SBL2 0x0000000001A00000
PARAM 0x0000000001c00000
KERNEL 0x0000000002400000
RECOVERY 0x0000000002C00000
CACHE 0x0000000003400000
MODEM 0x0000000009800000
FACTORYFS 0x000000000A800000
DATAFS 0x000000002A800000
UMS 0x00000000AA800000
HIDDEN 0x000000038B000000
SBL1 v SBL2 Explanation
The system (SBL) when downloading checks which SBL is active, this is done via a marker, in the GT-I9100 this is SNBL (GT-I9000 was OFNI, INFO in correct endian) and the SBL being downloaded is flashed to the opposite SBL partition, this is a safe guard and is how the 301k resistor on the ID pin can still enter DLM, it does not care which SBL is active, just some SBL can be executed.
Boot Sequence
iRBL > EBL > IBL > PBL > SBL
iRBL = iROM Bootloader (0x02000000)
EBL = Encrypted Bootloader (0x02021400)
IBL = Initial Bootloader (0x02023400)
PBL = Primitive Bootloader (0x4D300000)
SBL = Secondary Bootloader (0x4D400000)
thank you for share~~
hi Odia,
Many thanks for sharing, I can just blame myself not checking this tread before: I formatted my mmcblk0p2 partition->result: bricked phone, doesn't even show the galaxy or battery logo. On top of that, no download or factory reset mode.
What you are writing here gives me hope, that a JIG can help... I don't understand, why SBL2 doesn't come out with a button combination (or in normal download mode). Is there a documentation on SBL2 somewhere?
tamas970 said:
hi Odia,
Many thanks for sharing, I can just blame myself not checking this tread before: I formatted my mmcblk0p2 partition->result: bricked phone, doesn't even show the galaxy or battery logo. On top of that, no download or factory reset mode.
What you are writing here gives me hope, that a JIG can help... I don't understand, why SBL2 doesn't come out with a button combination (or in normal download mode). Is there a documentation on SBL2 somewhere?
Click to expand...
Click to collapse
Ouch, I hope you have at least updated the firmware once on your phone, if its from new and never flashed then 0p3 will also be empty and that is bad news for you. There is no real documentation on the SBLs, but I understand them, what are you thinking?
Odia said:
Ouch, I hope you have at least updated the firmware once on your phone, if its from new and never flashed then 0p3 will also be empty and that is bad news for you. There is no real documentation on the SBLs, but I understand them, what are you thinking?
Click to expand...
Click to collapse
Oucha. Only the kernel was flashed for rooting, I am heading to the local repair service, I hope they have a jtag.
on documentation I meant only infos, such as you mentioned, if the backup partition is populated with the right stuff or not...
tamas970 said:
on documentation I meant only infos, such as you mentioned, if the backup partition is populated with the right stuff or not...
Click to expand...
Click to collapse
The backup partition will be populated if you have updated the firmware at least once, but flashing just a kernel does not count.
Odia said:
The backup partition will be populated if you have updated the firmware at least once, but flashing just a kernel does not count.
Click to expand...
Click to collapse
Sad... I was hoping, that doing something in download mode already initiated the backup. I guess in the factory they directly flashed KE2 on it, but let's see what the service says...
I see the recovery (0p6) is also empty.
Thanks anyway!
tamas970 said:
I see the recovery (0p6) is also empty.
Click to expand...
Click to collapse
Yes, it seems not to be used at the moment.
Just a weird idea: is it possible, to put a bootloader on the microSD and boot from there?
tamas970 said:
Just a weird idea: is it possible, to put a bootloader on the microSD and boot from there?
Click to expand...
Click to collapse
Thats not as weird as you may think
Odia said:
Thats not as weird as you may think
Click to expand...
Click to collapse
I remember I had something similar with my old HTC Kaiser.
The question is how to convince the phone to look for bootloader elswhere
and how should the "rescue microSD" look like (is the bootloader enough or does it need a specific kernel/partitioning/file system).
Where does the external SD fit in your partition table?
tamas970 said:
Where does the external SD fit in your partition table?
Click to expand...
Click to collapse
External SD does not get referenced in the PIT so it was not written here, but you can find him @ 1p
Odia said:
External SD does not get referenced in the PIT so it was not written here, but you can find him @ 1p
Click to expand...
Click to collapse
I did some additional research, the JIG specifications say, that a "standard" 301kOhm USB JIG puts the booting procedure in "Factory mode 1", which hopefully means that the device looks for bootloaders on all partitions, incl microSD. I'll see soon...
I hope this is the right thread to post this.
What is data.img for file? It seem it make an hard reset if you flash it.
It contains most zeros.
Mackzen said:
I hope this is the right thread to post this.
What is data.img for file? It seem it make an hard reset if you flash it.
It contains most zeros.
Click to expand...
Click to collapse
Probably is the wrong place for your post, but I will try to help anyway.
Need some more information, like where did you get this file from?
Odia said:
Probably is the wrong place for your post, but I will try to help anyway.
Need some more information, like where did you get this file from?
Click to expand...
Click to collapse
it's from any "user_low_ship" rom from pda.tar .
http://forum.xda-developers.com/showpost.php?p=15009318&postcount=37
(this package even include an efs_xxxxx.tar) ?
I wrote it here because I thought we need an PIT file for Re-Partition.
Mackzen said:
it's from any "user_low_ship" rom from pda.tar .
http://forum.xda-developers.com/showpost.php?p=15009318&postcount=37
(this package even include an efs_xxxxx.tar) ?
I wrote it here because I thought we need an PIT file for Re-Partition.
Click to expand...
Click to collapse
Since the low packages are AKA a clean factory image they contain some empty filesystems which will erase the named partition e.g. data in this case, another example is cache.img in the CODE/PDA file bundle.
I can put a KE7 pit on my android 2.3.4 with KG2?
Where i can find it?
Because there are some lag in home screen.
mimstyle said:
I can put a KE7 pit on my android 2.3.4 with KG2?
Where i can find it?
Because there are some lag in home screen.
Click to expand...
Click to collapse
My car is getting lousy fuel economy, can someone tell me how to fit a new radio antenna to fix please?
Hacre said:
My car is getting lousy fuel economy, can someone tell me how to fit a new radio antenna to fix please?
Click to expand...
Click to collapse
LoL
Not possible to optimize this laggy home screen @!#£ ?
Related
i don't know how but a friend of mine killed his SGS2
when it boots he has a long red log that the phone can't open partitions
as i see it he needs a full flash with repartition but i can't find the pit (yes i know... all i find is threads about it)
iakovl said:
i don't know how but a friend of mine killed his SGS2
when it boots he has a long red log that the phone can't open partitions
as i see it he needs a full flash with repartition but i can't find the pit (yes i know... all i find is threads about it)
Click to expand...
Click to collapse
As always its on Samfirmware.com with the firmware . .samfirmware.com/ jje
I made this because the existing rom (package_us2.3.5.tar.md5) being distributed around the fourms isn't working right for devices like mine.
Your phone should be rooted prior to doing this.
Make sure you have the same device info as mine before proceeding. I will not be responsible if you decide to flash this to a device that does not match my own. You have been warned.
DOWNLOAD HERE: http://www.sendspace.com/file/1y2ogi
This is for the Samsung Galaxy Player 4.0 (USA) (YP-G1CWYXAA)
Model Number: YP-G1
Firmware Version: 2.3.5
Kernel version: 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build number: GINGERBREAD.UEKI8
Steps for flashing.
1.) Attach USB Cable and Put your device in Downloading mode (Hold Power + Vol Down)
2.) Download and run Odin 1.85
3.) Click on the button marked PDA and select the file named "yp-g1cwyxaa.tar" that you downloaded from the link above.
4.) Make sure that ONLY "Auto Reboot" and "F. Reset Time" are checked. (NO OTHER OPTION SHOULD BE CHECKED!!)
5.) Click on "Start" and wait for the process to finish. The process should take about a minute or two and finish with a green box saying "PASS!"
6.) When it has successfully finished, the device itself should reset. At this time you may unplug your USB cable.
7.) OPTIONAL: Press menu button > Settings > Privacy > Factory data reset (This will reboot your device, enter recovery mode, wipe all settings and reset everything to defaults, and then reboot your device once more automatically.)
8.) Enjoy your 100% working Samsung Galaxy Player 4.0 (YP-G1CWYXAA)
This is my first time doing something like this. I hope this works for all of you. Let me know if you have problems. Feel free to click the "Thanks" button if it works for you. =)
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
I downloaded and installed your stock rom and it worked perfectly. The clock works find and the widgets that weren't working before are now working.
The only step I skipped was step 7 because I wanted to keep my apps/data. And I'm certainly following step 8.
Thanks a lot for your effort Kwipper (and the thanks button was clicked).
I am happy to see that this is working. I am actually quite surprised with myself that I was able to do this. About 10 days ago, I didn't even have an android device, or know anything about the platform. =)
Don't be so modest. You've solved a problem that I've had for over a month now.
I'm curious how you did this. Did you use adb from your PC to run the 'dd' command? I ran the 'dd' command using the Terminal Emulator app. Maybe this is why my factory.rfs didn't work.
I did a bit of searching around the fourms and came across this post.
http://forum.xda-developers.com/showpost.php?p=15804185&postcount=15
Then I used a program called Cygwin. Used it to navigate over to where my files were stored and typed in these commands.
tar -H ustar -c factoryfs.rfs zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Then I flashed it using odin.
I also noticed that if you were using the previous "package_us2.3.5.tar.md5" file to restore from, the MD5 of my file would not match up, and Odin would give off an error. So I removed the .MD5 from the extension of my filename and it worked.
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Kwipper said:
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Click to expand...
Click to collapse
They are all right here: http://forum.xda-developers.com/showthread.php?p=20259805
Important: if you are going to flash this ROM, make sure you do NOT choose repartition in Odin with the PIT file. This only contains the /system and the kernel, so repartioning the whole device will make your device unable to boot past recovery. Still waiting for a full stock recovery ROM with all the partitions and can use the PIT file...
Kwipper said:
...
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
Click to expand...
Click to collapse
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Hmmm... Is there anyway to confirm if it's rooted or not? I suppose that if I remove the root and then reflash it using odin, it should remain unrooted right?
WT Ho said:
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Click to expand...
Click to collapse
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Kwipper said:
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Click to expand...
Click to collapse
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
WT Ho said:
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
Click to expand...
Click to collapse
Yeah, just imagine what it would be like to have your computer crash while you were flashing the bootloader!
Can you make a backup of that?
so i can test if it works, cause my device is bricked at the moment.
Woah there, careful what you post! unless you do a factory reset before dumping, the cache.rfs, dbdata.rfs, and data.rfs should NOT be included in a rom as they contain all your personal information!
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Tecardo said:
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Click to expand...
Click to collapse
I don't think you need data partition. In normal operation, you can format the /data partition clean and the system will recreate your new settings there.
For those of you that have used this, can you confirm that this removes root? I going to guess it does.
It's not really a problem since you can use super one click again, but I just wanted to be sure.
Thanks again for doing this, Kwipper.
hey i need to flash factoryrfs form odin. but im not sure how, any help?
minimeofctown said:
hey i need to flash factoryrfs form odin. but im not sure how, any help?
Click to expand...
Click to collapse
Tar it and then flash it with Odin just like how you flash a ROM.
Use terminal (or cygwin for Windows) :
cd (directory of factoryfs.rfs)
tar -H ustar -c factory.rfs > something.tar
Can you make such a ROM? I really think, it will work for me…
I don't know the Problem so i feed to flash the hole ROM
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
100% agree stay away from PIT unless you really know what you are doing .
jje
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
JJEgan said:
100% agree stay away from PIT unless you really know what you are doing .
jje
Click to expand...
Click to collapse
its only as a information, maybe somebody runs into the same problem..
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
PjotrFias said:
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
Click to expand...
Click to collapse
The why is generally that they use the wrong PIT files .
One of the stupid reasons why is going to forum xxxx downloading firmware from them then coming here to ask why has it broke my phone .
PIT mistakes for SG range are in the thousands not just the odd few .
jje
flashed a pit file and now my galaxy s2 is hard bricked
Hi
im new to xda. but having been trying to root my galaxy s2 I9100 through xda tutorials.
my problem started when i flashed a pit file with odin.and now i think its hard bricked. doesn't respond to anything, doesn't show on odin either. ive taken the battery out and have kept it like it for more than 6 hours, with no luck at all. but once i put in the battery to check it becomes hot. even bought a USB Jig and tried, nothing happened. please help as in my country we dont get warranty or we dont samsung service centers. I've tried so many ways to get my phone to life but have failed.. please help:crying:
Does the phone boot to download mode does Odin see the phone .
jje
JJEgan said:
Does the phone boot to download mode does Odin see the phone .
jje
Click to expand...
Click to collapse
nope nothing happens only gets hot..
boboschiyax said:
nope nothing happens only gets hot..
Click to expand...
Click to collapse
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
JJEgan said:
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
Click to expand...
Click to collapse
thanks but already did that. didn't work
boboschiyax said:
i think its hard bricked. doesn't respond to anything, doesn't show on odin either.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32367917
pleaaaaaaaaaase help me !!
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
i tried 4 pit files to repartition my samsung s3 i9300 but all the result is fault
my s3 now dead
please help me
i search google for all pit files of i9300 but no success
pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaase can anybody help me!!
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
NeilH1978 said:
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
It is possible because people usually think in terms of branding. Not aware different models may exist in different regions. Example the note gen1 has Korean and Chinese and US versions, each has a different model number.
XyRo7ec said:
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Click to expand...
Click to collapse
Here is the pit file for Note 3 SM-N9005 32gb varient.
HELP i think flashed the wrong .tar root file for my Galaxy J7 Pro
Hey man,
XDA doesn't trust me enough to let me make my own post and as I'm writing this I'm supposed to be studying for the 3 exams I will be having.
So,
I rooted my phone susing ODIN and the same root file a few months ago on Android 7.1 and it worked. I used it with TWRP recovery and everthing was fine.
Then the Android Oreo update was released for my phone, finally, and I hooked my phone up to my laptop and downloaded the firmware using Samsung's new Software called SmartThings.
Now I had stock ROM, but my device was recognized as rooted and modified, so couldn't use a few apps like Samsung Health and Pay. Then, without thinking, I put my phone in Download Mode and flashed the SAME .tar root file with ODIN, and now my phone won't boot to the pulsating Samsung logo and is stuck in the bootloader
wanted to say that Odin said PASS when .tar file was downloaded in the AP slot
In download mode,
Download Mode says:
Current Binary: Custom
System status: Official
FAP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0303)
I have access to STOCK recovery and download mode, and I've already tried factory resetting phone and wiping cache. I don't want to take more rash steps without someone knowledgeable guiding me. and I cant find any other forum to post on because I'm not a high enough member.
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
hi,
this morning i downloaded a i9305's stock rom in order to port it in my device (i9300) by using dsixda kitchen port tool. i ve flashed the edited rom and i got bootloop, then i tried to go to recovery i got black screen mixed with blue line (like a panic kernel). i pulled out the battery, flashed a stock rom by odin. the results are : touchscreen not responding, phone very slow to boot up
i tried everythings to restore it (factory reset, wipe dalvik cache, formated system, flashed original rom, full s/w with pit,pda,modem,csc....please help me
thanks
Allthough it is considered very risky try to flash stock fw with repartition ticked and pit file
Sent from my GT-I9300 using xda app-developers app
yes i know but any solution ?
Stay a way from pit files if it boots .
jje
so no response ?
no one can help me ?
You have asked got reply's tried most that can be advised all that is left is a paid for service repair .
jje
If you haven't tried already - I would repartition with pit first. (Make sure repartition is ticked)
If that fails then its possible the bootloader has been somewhat damaged. how far does the boot progress?
would need a sboot.bin that is within a tar file to flash via Odin - bit risky though!
edit
(can get sboot.bin.tar file from here http://forum.xda-developers.com/showthread.php?t=1916796
but that thread is for phone s that do not go into download mode)
but research, so you are conffident about what your doing
AbuYahya said:
If you haven't tried already - I would repartition with pit first. (Make sure repartition is ticked)
If that fails then its possible the bootloader has been somewhat damaged. how far does the boot progress?
would need a sbin file to flash via Odin - bit risky though!
Click to expand...
Click to collapse
where i can get sbin ?
edit: i ve tried this but no changes !
machu28 said:
where i can get sbin ?
Click to expand...
Click to collapse
Although I have flashed sboot.bin files on prev devices I have not done it on the SGS3.
I have left a clarification request on the aforementioned page
edit
there is also one post at this thread: http://forum.xda-developers.com/showthread.php?t=1918667&page=2
You're the second person I've heard that this happened to (Same screen corruption, touch not working afterwards), glad to know this wasn't related to my kernel. Seems that you have a wrong Melfas firmware going on on your device now.
machu28 said:
edit: i ve tried this but no changes !
Click to expand...
Click to collapse
if bootloaders and PIT with repartitioned and a stock ROM and Modem all together failed.
then likely need to to open phone to sort it out
------->know some experienced doing it or
------>service centre
possible hardware failure
AndreiLux said:
You're the second person I've heard that this happened to (Same screen corruption, touch not working afterwards), glad to know this wasn't related to my kernel. Seems that you have a wrong Melfas firmware going on on your device now.
Click to expand...
Click to collapse
any idea how to restore it ?
AbuYahya said:
if bootloaders and PIT with repartitioned and a stock ROM and Modem all together failed.
then likely need to to open phone to sort it out
------->know some experienced doing it or
------>service centre
possible hardware failure
Click to expand...
Click to collapse
isn't a problem of drivers binary ?
machu28 said:
where i can get sbin ?
edit: i ve tried this but no changes !
Click to expand...
Click to collapse
machu28 said:
isn't a problem of drivers binary ?
Click to expand...
Click to collapse
I'm not sure what your asking?
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
if your flashing is unsuccessful/failed on Odin, then you could try the SDcard technique
But personally I would send for warranty repair.
machu28 said:
any idea how to restore it ?
Click to expand...
Click to collapse
No, not right now, sorry. By the way this is now a hardware problem, you won't fix it through flashing anything.
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
Click to expand...
Click to collapse
Some things are hardware firmwares and have nothing to do with the ROM, the touchscreen is one of them.
AbuYahya said:
I'm not sure what your asking?
AFAIK most of the drivers are within kernel and some with in ROM.
so if you successfully flash it with Stock ROM (includes kernel and ROM and modem) then they return to stock .
if your flashing is unsuccessful/failed on Odin, then you could try the SDcard technique
But personally I would send for warranty repair.
Click to expand...
Click to collapse
yes send it for repair is my last option. unbelievable that software kills hardware !!
Some things are hardware firmwares and have nothing to do with the ROM, the touchscreen is one of them.
Click to expand...
Click to collapse
can i use "nand erase all" in odin ?
machu28 said:
can i use "nand erase all" in odin ?
Click to expand...
Click to collapse
No. The firmware isn't on the NAND.
So I bought a blue s3 gt-i9300 from ebay.co.uk and I received it with a boot loop problem.
It only gets into download mode (odin mode) and says CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: Samsung Official, SYSTEM STATUS STATUS: Official
It tried to flash a CW recovery but it keeps failing with NAND Write(start)... Fail.
Tried to flash a stock firmaware same NAND error.
Tried to do a repartition and nand erase with a pit file. It gets stuck at Erase...
I have adb installed but my device is not showing, although in odin it connects to my phone and windows shows my phone in the device manager.
I have tried with windows 8 on one computer and windows 7 on another. I have also changed the usb cable 2 times.
Is there anything else I should try or the only fix is a new mobo?
I am ready to pay for solving this problem through paypal. I can give you teamviewer access etc.
Please help me I am desperate...
new motherboard or read the forum this is a repetitive topic you have posted .
JJEgan said:
new motherboard or read the forum this is a repetitive topic you have posted .
Click to expand...
Click to collapse
Is this the only option? How much should they charge me for a mobo replacement?
milupas2 said:
Is this the only option? How much should they charge me for a mobo replacement?
Click to expand...
Click to collapse
I gave you two options .
JJEgan said:
I gave you two options .
Click to expand...
Click to collapse
Yes, but I do not know what else to try, I've read at least 100 topics with no results. I have posted everything I tried.
Could you please at least give me an estimative cost for emmc replacement if that is the only solution?
milupas2 said:
Yes, but I do not know what else to try, I've read at least 100 topics with no results. I have posted everything I tried.
Could you please at least give me an estimative cost for emmc replacement if that is the only solution?
Click to expand...
Click to collapse
you can try a rescue firmware here http://forum.xda-developers.com/showthread.php?t=1825272 make sure if you flash pit that it is correct. based on your internal storage.
ashraf sharif said:
you can try a rescue firmware here http://forum.xda-developers.com/showthread.php?t=1825272 make sure if you flash pit that it is correct. based on your internal storage.
Click to expand...
Click to collapse
with pit file: no pit partition found.
without pit file: Nand write start. . fail
with a pit named u1_02_20110310_emmc_EXT4 i get a different pit error, something like pit failed. (not the no pit partition found this time)
9634482 140
milupas2 said:
with pit file: no pit partition found.
without pit file: Nand write start. . fail
with a pit named u1_02_20110310_emmc_EXT4 i get a different pit error, something like pit failed. (not the no pit partition found this time)
Click to expand...
Click to collapse
can jtag fix this?
No, you have nand memory failure and require a new motherboard.