Good day to every one!
I want to repartition my GN with pit file.
The only reason is that wifi is dead every now and then. If you want to know more about this issue I have opened another thread:
http://forum.xda-developers.com/showthread.php?t=2157447
A friend at the end of the thread is telling me to repartition with pit file so I am considering giving it a try.
I know everything will be erased so I must back up everything but I must admit I'm a little bit worried!
I've never tried that before and I'm not sure of which pit file to use.
Has anyone done that?
I've found some links but they are not very clear to me...
Simply don't do it. Repartition won't help you with your wifi problem. But there is a "fat chance" to ruin your device.
Related
I posted this question in JM2 firmware thread but was wondering if anyone could confirm.
People flashing to JG5 reported having to use 512 PIT as 513 PIT didn't work for them.
I used 513 PIT to flash to JG1 from a stock firmware then followed what others recommended in the JG5 thread and used 512 PIT + repartition.
A few have reported that flashing without repartition worked if they used the previous PIT they used in a previous repartition.
Some have reported that they are on 513 PIT and have not had any problems flashing new firmware.
Is anyone able to confirm this.
I guess the question is:
a. Is 513 PIT better then 512 PIT. What is the difference if any?
b. If using 512 PIT repartition continue using this for all other builds without repartitioning just flash.
c. If using 513 PIT repartition continue using this for all other builds without repartitioning just flash.
d. If you want to go from 512 to 513 PIT then repartition as part of the flash process then stay with 513 PIT for future builds with no repartition.
Would be interesting to prove this theory.
Also would be good to have a standardised approach to flashing the firmware to decrease the confusion and assist others in doing a flash with less stress.
Click to expand...
Click to collapse
Would anyone like to comment.?
That's my question too.
the answer is here
http://forum.xda-developers.com/showpost.php?p=7325508&postcount=265
raspdeep said:
the answer is here
http://forum.xda-developers.com/showpost.php?p=7325508&postcount=265
Click to expand...
Click to collapse
Hey raspdeep.
I'm currently on JF3, rooted. Never flash any firmware or cook ROM yet, so this is the first. I'm trying to flash JM3. Should I use 512, with repartitioned ticked?
eaglesteve said:
Hey raspdeep.
I'm currently on JF3, rooted. Never flash any firmware or cook ROM yet, so this is the first. I'm trying to flash JM3. Should I use 512, with repartitioned ticked?
Click to expand...
Click to collapse
JM3? JM2 is the latest from what i know.. yes use 512 and check repartition.. if it doesnt work, uncheck repartition and try again.. im not sure why sometimes the ODIN software fail.. but the end results will not be affected
the difference is partition size change for dbdatafs and factoryfs.. one got enlarged, the other got reduced
And Who or What creates the pit files?
Maybe it would be helpful to know that.
Is it possible create a pit file with maximized App partition?
Reuse for it the 5-6 GB SDCARD partition place.
And instead the internal SDCARD Partition to use a big external SD CARD.
So we would have a internal 7 GB App Partition + max. external 32 GB SD CARD.
Is anyone willing to try my theory.
Flash back to JG1 using 512 PIT repartition then flash to JM2 using 512 PIT no repartition.
Flash back to JG1 using 513 PIT repartition then flash to JM2 using 513 PIT no repartition.
We would be proving no matter what PIT you used previously you do not have to repartition when flashing new firmware and that you can remain with the same PIT you originally used.
Remembering this could brick your phone and it not for the faint of heart.
Then again it might not be such a good idea. To much risk.
GAda said:
And Who or What creates the pit files?
Maybe it would be helpful to know that.
Is it possible create a pit file with maximized App partition?
Reuse for it the 5-6 GB SDCARD partition place.
And instead the internal SDCARD Partition to use a big external SD CARD.
So we would have a internal 7 GB App Partition + max. external 32 GB SD CARD.
Click to expand...
Click to collapse
The .pit file has got nothing to do with the internal SD card. The flash process doesn't access the internal SD card. It accesses the ROM which is different storage chip so what you are proposing is not possible unfortunately.
However, samsung has been made painfully aware of the lag/stalling issue and seeing the fix by mimocan, it is quite obviously a software issue and we can look forward to seeing it fixed in the future.
[email protected]_One: That will not brick your device. I may require a reflash with a different firmware but it will not brick your device. The firmware may not work but thats as bad as it gets.
Darkstriker said:
However, samsung has been made painfully aware of the lag/stalling issue and seeing the fix by mimocan, it is quite obviously a software issue and we can look forward to seeing it fixed in the future.
Click to expand...
Click to collapse
Hopefully this is a software issue and not a hardware issue. Time will tell.
Darkstriker said:
[email protected]_One: That will not brick your device. I may require a reflash with a different firmware but it will not brick your device. The firmware may not work but thats as bad as it gets.
Click to expand...
Click to collapse
Thanks just wasn't sure and didn't want anyone just going out and trying it.
Well it would seem to be a software issue because normal read/write speeds to the internal SD aren't very bad and we achieve double the points in benchmarks when using the slowest of microsd cards (class 2) so it is very likely a software issue.
Good point. I'm surprise they haven't tried to fix it knowing this to be true.
Maybe they know something we don't like damaging the components if the device runs to fast. Speed kills you know.
They have been made aware and the belgian department promised an official fix!
Sent from my GT-I9000 using XDA App
Ancient_One said:
Is anyone willing to try my theory.
Flash back to JG1 using 512 PIT repartition then flash to JM2 using 512 PIT no repartition.
Flash back to JG1 using 513 PIT repartition then flash to JM2 using 513 PIT no repartition.
We would be proving no matter what PIT you used previously you do not have to repartition when flashing new firmware and that you can remain with the same PIT you originally used.
Remembering this could brick your phone and it not for the faint of heart.
Then again it might not be such a good idea. To much risk.
Click to expand...
Click to collapse
When I flashed JM2 for the first time everything appeared to go well with the 513 PIT, but on rebooting I was left with a black screen after the initial boot animation.
Had to reflash using the 512 PIT and everything went as expected.
I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses
your phone is most likely toast, search around for similar problem, no one has been able to wipe or reset the internal sd card when this happens...its very frustrating, im on my second galaxy S because of this problem. the sooner you take it back the sooner you will have a new phone.
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'd love to hear if this actually works, i'm guessing it won't....I was told to try all kinds of different things including this....nothing worked. good luck.
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ya-no.
This will not work with this error code. Although, It has worked in the past with other errors.
I have a feeling I'm gonna have to get ANOTHER replacement....It probably won't be a DOA instant switch like last time though..augh....Loner-Phone, Here I come! :'(
I wonder...
Does Clockwork Recovery have a button combo? Much like regular recovery?
Jordiharrison said:
I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses
Click to expand...
Click to collapse
Hello
I had the same and i solved through the guide here:
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
But i think the problem really was that i have make an ext2 partition on sd-card.
I removed the sd-card during flashing.
Works !!!!
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked like a charm for me. Cheers
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked for me too. Thanks!
omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so i used this method to get my phone running again and it worked, which is why i said thanks. But the problem now is that i dont want to flash to jph and it keeps giving me the same error if i flash any other firmware.
Anyone know the soloution for this? All help appreciated thanks.
P.s I've been trying to flash back to lower firmwares so that i can update to froyo officially through kies.
Update:
Nobody seems to be helpful around here when i ask for help but thought id share with the people who have this problem in the future.
Try using a different pit file when flashing, as there are two types of pit files. If you need more details just pm me.
Hi Riverriz , what's jpc stand for?
Flashing JPC with repartition using 512 pit works!
My Internal SD working again just after flashing JPC, now go back to Doc's rom. Thanks.
guys what is JPC and how do you falsh with it im stuck with same issue any links ??
update: did this and the phone gets tsuck in a reboot loop tried two 512 .pit
Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?
I have problem like that on my galaxy tab. i didn't find answer on briefmobile,and i'm very afraid that i broke my device. so please, somebody, tell, how to solve this problem
Miggles said:
Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?
Click to expand...
Click to collapse
I am in a similar situation. Does anyone have any ideas how to fix this? I tried to install Doc's JPU rom with the CWM JPU kernel and now I seem to be chasing partitions that can't mount etc.
Thanks,
David
I eventually gave up on this - it wasn't going to fix itself regardless of what I did.
JPC with the 512 PIT worked for me. Now my I9000 is flying again.
Hey all,
Ive got a SGS from Optus in Australia but its unbranded. Currently I'm running JG4 rom.
I want to update to the JPO. Ive got the ROM. Ive got Odin and Ive got 3 pits.
Everything is fine, I just don't know which PIT to use. 512, 513 or 803. Could I just flash the rom over without a PIT? Should I repartition? This is the first time Ill be doing a flash.
Any help would be appreciated!
Advice from the experts
Hi,
The quickest and simplest is to go on the samfirmware.com site and register and log in. Everthing you'll need will be found there.
you will first want to flash with the 512 and repartition on.. i dont exactly remember which rom i think jm6 (samsfirmwares has the info on that)
and afterwards u flash the jpo with 813 pit and no repartition.
But yea just read the *info on the roms over there it explains the process.
Putting Pit file 813 without repartition checked is nonsense...
If this box unchecked, then ODIN will ignore Pit file.
At the end, I've never been able to flash whatever firmware with 813 pit file. All went very well with 512 one...
Sent from my GT-I9000 using XDA App
Just a quick question guys: what does re-partition really do and when should it be used ?
Prasad007 said:
Just a quick question guys: what does re-partition really do and when should it be used ?
Click to expand...
Click to collapse
It make the partition in different size. But so far i only use pit 512 for all firmware.
It works best.
You should only use them when you want to wipe you phone clean and need to re-partition the phone.
And yes you must tick the re-partition box to make it work. Else it don't use the pit file.
So samfirmware show wrong.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Yeah the pit doesn't really matter, stick with 512.
I'm trying to reflash 4.4.2 on my S4 Active with Odin, but have no idea which files go where, I can't find the original thread that had instructions on it, and everything I did find told me to click on a PA button, which I don't have. I just need to know which files to pick for PDA, Phone, CSC, and bootloader.
*Edit* Took a bit of digging, about an hour's worth, but I got the answer I needed off youtube.
So I played around with my Samsung galaxy S2 tablet.
Never done anything like this before and didnt read up on it enough.
I did not take a backup because I, to be honest, didnt think I would have to need that since the data on the device had no use for me.
Long story short.
Ive used nand erase in Odin without extrating the pit file.
So now its bricked and I need the pit file to get it back to where it was before.
Edit: 32gb model