After finally getting JPY on my SGS I'm now finally using it properly (Odin download). But it's already annoying me.
Market is constantly failing, downloads are slow to appear and sometimes start, sometimes decide they dont feel like downloading, some downloads pause and fail to restart.
Just tried it on my DesireHD and it works fine, even without my sim in and just using Wifi ... Please note SGS is on Wifi too ...
This phones software seems so so bad it's unreal?
EDIT: Searching for apps on market takes hours and constantly get retry issues. Is the Wifi on these hones so unstable or something?
hey.... first of all SMILE
i think you have just experienced a bad flash / ROM ... JPY in my opinion is very stable and fast... i have used it and had no issues what so ever and overall performance was good (without lagfix) the wifi connects is seconds of entering the street on my device...
when you flashed the ROM did you also do a full factory reset in recovery and did you use PIT file and RE PARTITION ???
if you didn't i suggest you do and try again.... or you could go for some custom ROM.
the latest stock/custom ROM is XWJS5 released only 1-2 weeks ago and that is good.
you could also install a lagfix to eliminate any lag..... dont get mad.... madness only causes more errors
Try XWJS5 ROM
How to
http://www.emoiz.com/how-to-install-android-froyo-2-2-1-xwjs5-rom-on-samsung-galaxy-s-i9000
@alien.46.uk
Glad that you finally got JPY on your device, first of all, you can't compare HTC desire or desire HD to this device when you get working right, you will understand what I mean in time.
This is your first flash, you need to make sure that your device has XEU as CSC, to do so you need to enter *#272*IMEI_Number# in dialer, if it's not XEU choose XEU and hit install, it will reboot changing to XEU.
The second thing is to get to Recovery Mode, that is Volume Up+Menu+PowerO On, choose wipe/factory reset and reboot.
The third is to clear Market cache, it's under Settings>Applications>Manage applications>All and choose Market, hit the button "clear data" and see how Market behaves.
All the symptoms that you've written in first post make me sure, that you should reflash the jpy again with wipe. This should help for your problems.
Not reinstalled yet, battled on and got everything installed, but might just start from scratch.
Do I have to start the whole process again because I assume my device is no longer rooted and I need to start again through the whole process?
Used the instant root software Ramad linked me to in another post. Is there a permanent root method?
EDIT: Im thinking this cuz my Superuser icon has gone and extended controls said my device wasn't rooted etc?
alien.46.uk said:
Not reinstalled yet, battled on and got everything installed, but might just start from scratch.
Do I have to start the whole process again because I assume my device is no longer rooted and I need to start again through the whole process?
Used the instant root software Ramad linked me to in another post. Is there a permanent root method?
EDIT: Im thinking this cuz my Superuser icon has gone and extended controls said my device wasn't rooted etc?
Click to expand...
Click to collapse
Try JS5, it's newer than JPY and more stable. If you're interested, here's a link to a package I made for my phone with the JS5 PDA, JPY CSC and JP5 modem (Vodafone UK stock modem). I've been running it on my phone for a while now and it works great: http://www.multiupload.com/Q1O3GP6AJP
You can root permanently with SuperOneClick
Good luck!
well if you shall start from scratch the move to js5. its better. then you flash a custom rom. that will make your phone faster. just make sure the rom support your country code.
you can doc rom kitchen to make a rom that working for you.
there is no reason to have a slow and buggy phone. all solutions is here.....
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
You have to root everytime you flash.
Before flashing check your CSC and see if it's XEU, the stock firmware of an unlocked Galaxy S for England is XEU.
Do a factory reset in recovery and flash using 803.pit or 512.pit, I use 803.pit, but both are good (you may only re-partition if your ROM is of three archives of tar.md5), after flashing do a factory reset again, clear Market data as I described earlier and then root (you have to reboot after rooting using super one click, or the phone will be laggy) and then install busybox.
Odin, 803.pit and 512.pit are here: http://www.multiupload.com/J3BOFW3S30
I think that there is no more to write about it, after so many posts and guides it should be crystal clear on how to make a Galaxy S ready for use by now.
Edit: to all the guys trying to recommend JS5 over JPY: This is his first use/flash of a Galaxy S, and he do live in England, the official firmware of Samsung for England is JPY with XEU as CSC.
The official firmware for Netherlands is JS5 with XEN as CSC, let him try to do it right before trying anything else.
one note.
you don't need to root if you choose a custom kernel or rom. they already fixed that.
use pit 512 or pit 513. stay away from pit 803. you should also only use a firmware with the 3 files. just to make the phone fresh and clean.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
DamianGto said:
one note.
you don't need to root if you choose a custom kernel or rom. they already fixed that.
use pit 512 or pit 513. stay away from pit 803. you should also only use a firmware with the 3 files. just to make the phone fresh and clean.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Click to expand...
Click to collapse
What are you talking about? How is it that 803 bad, and how is it that 513 is good, can you explain?
[Ramad] said:
What are you talking about? How is it that 803 bad, and how is it that 513 is good, can you explain?
Click to expand...
Click to collapse
all pit file change the partition on different way. many times pit 803 has made things working bad. 512 and 513 the best choice. pit 513 do have a little bigger system partition then pit 512.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
DamianGto said:
all pit file change the partition on different way. many times pit 803 has made things working bad. 512 and 513 the best choice. pit 513 do have a little bigger system partition then pit 512.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Click to expand...
Click to collapse
You know that the trading of ROM allocations are only happening between /system and /dbdata and all other allocations such as param, data, kernel etc are fixed:
512.pit: /dbdata=127MiB
513.pit: /dbdata=107MiB
803.pit: /dbdata=117MiB
What is interesting here is that 803.pit is offering the best balance between /system and /dbdata.
Why 803.pit is not popular is because all the lagfixes have been made to read and write data according to 512.pit partition table, later on the firmware DXJPE could only be flashed according to 513.pit partition table and further support for the 513.pit have been added, this is why using a 803.pit with a lagfix only brings problems for lagfix users.
if you think that....
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
DamianGto said:
if you think that....
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Click to expand...
Click to collapse
Please read here: http://forum.xda-developers.com/showthread.php?t=816449&page=2
The numbers of /system and /dbdata are not correct but that will give you an idea of what I think or what I know.
Good night
yes i know. i was there. lol.
but you try to say to use pit 803 when you also do write its not so good.
you blame all that make lagfix.
you also advice a user to use it even you know its don't work well.
so if you want to be able to use anything you like you stay away from pit-803.
this debate is over for me.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
DamianGto said:
but you try to say to use pit 803 when you also do write its not so good.
Click to expand...
Click to collapse
Where did I write this?
you blame all that make lagfix.
Click to expand...
Click to collapse
I did not blame anything, you did write why 803.pit is bad, I can't find where you gave a reason for that.
you also advice a user to use it even you know its don't work well.
Click to expand...
Click to collapse
Where did I write that it does not work well on a stock firmware?
this debate is over for me.
Click to expand...
Click to collapse
I can't call it a debate.
double post.
DamianGto said:
yes i know. i was there. lol.
but you try to say to use pit 803 when you also do write its not so good.
you blame all that make lagfix.
you also advice a user to use it even you know its don't work well.
Click to expand...
Click to collapse
Egh.
It might be over for you, but once again, you are acting like some coding god, who never has to prove claims of any type. You have proven nothing in this case or ANY case. Why is 803 bad exactly? What makes it so? And where are your basic statistics which show lots of people were having trouble?
If you can't prove it, just say "I can't prove it", and "I simply think it's true". But you don't need to treat everyone like crud to make your point seem more valid.
Auzy said:
Egh, I'm reporting you to an Op.
It might be over for you, but once again, you are acting like some coding god, who never has to prove claims of any type. You have proven nothing in this case or ANY case. Why is 803 bad exactly? What makes it so? And where are your basic statistics which show lots of people were having trouble?
If you can't prove it, just say "I can't prove it", and "I simply think it's true". But you don't need to treat everyone like crud to make your point seem more valid.
Click to expand...
Click to collapse
stop bugging me. try do something yourself.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Related
Hello guys I thought I'd make a little how to and make my first thread that really contributes to the XDA community, so here we go !
Please make sure you have access to 3 button mode(voldown+home+power) to get into download mode. If not please see this thread :
http://forum.xda-developers.com/showthread.php?t=785201 !
I'M NOT RESPONSIBLE IF YOUR BREAK YOUR PHONE, ALTHOUGH IT'S UNLIKELY YOUR TAKING THE RISK BY MODIFYING IT!
Instructions:
Step 1 -
Consider which Samsung ROM you want to have installed on your phone. Currently JPY is the fastest stock FroYo ROM from Samsung.
JPY 2.2.1 ROM : http://www.multiupload.com/UHJNT0K1F2
.RAR Password : samfirmware.com
ODIN Flashing Tool : http://www.multiupload.com/4JLU4QHUV7
Download these and your ready to go!
Step 2 -
Before flashing any roms, please disable any form of lagfix you are currently using!
Extract I9000XXJPY.rar and odin 1.3.rar
Start up odin1.3.exe
Now click on PDA and select the JPY.tar that you just extracted.
Place your phone into download mode and connect via USB.
You must start Odin before plugging your phone in! Odin is very temperamental.
Now flash your phone and you will reboot into the latest Samsung ROM.
Step 3 -
Now it's time to add some speed!
You will have to decide which kernel suits you most.
Using a super fast kernel with a lagfix will really improve the performance of your device. Converting Samsung's RFS Filesystem to much better EXT4 Filesystem should stop all the hang ups etc that you will encounter on your device. Supercurio's Voodoo LagFix converts partitions to EXT4. You will also have to option to convert to EXT4 with hardcore's kernel and most other kernels.
Do you want Overclock, Voodoo LagFix plus Voodoo Sound?
Then Trasig's kernel is for you :
http://forum.xda-developers.com/showthread.php?t=823300
Do you want a stable Kernel with a ton of features aimed at purely improving your phones speed?(NOW WITH VOODOO SOUND!
Then Hardcore's kernel is for you :
http://forum.xda-developers.com/showthread.php?t=822756
Would you like a kernel similar to harcore's with Overclock?
Laststufos kernel is for you :
http://forum.xda-developers.com/showthread.php?t=811660
Step 4 -
Now you have decided which kernel that suits your needs, Download it!
Now load up Odin, place the kernel's .tar in the PDA section, connect your phone in download mode and flash!
Step 5 -
Now your super fast kernel is installed, reboot into recovery (vol up+home+power)
If your on trasig's kernel, follow these instructions:
Select 'voodoo lagfix' under ClockworkMod Recovery
Select 'enable lagfix'
It's optional but for extra speed also select '/system lagfix on'
Now reboot!
DON'T BE ALARMED IF YOUR PHONE STARTS TALKING TO YOU.
The voice is just telling you that it's converting RFS to EXT4.
Just leave your phone be until it boots into Android.
If your on hardcore's kernel, follow these instructions:
Select 'advanced ULK features'
Select 'install superuser'
This will root your phone
Now go back and select speedmod then tweaks and enable the first four
Now go back and select lagfix
Select EXT4 and reboot
Your phone will ask you to backup and restore select yes and wait for reboot into android. This may take a while.
-Laststufo's instructions will be added later-
Step 6 -
Now we have kernels sorted out so they're ready for a super fast ROM.
Personally I have tried and tested and are a big fan of:
Darkys V9.0.2 -
http://forum.xda-developers.com/showthread.php?t=814091
Doc's & Stefunel's magical ROM Kitchen -
http://forum.xda-developers.com/showthread.php?t=817703
Darky's ROM is an all in one ROM that's been super optimised to make your phone fly.
Doc & Stefunel's kitchen gives to user the ability to build there ROM from scratch, you get to decide which features you want in your ROM. Also it too is super optimised!
Both of these ROMs are updated frequently so if any bugs are encountered you can be sure they will be fixed as soon as possible.
So know you've chosen which ROM to flash to your device, the next bit is easy.
Transfer the .zip ROM on to your internal storage
Now reboot into recovery(vol+up,home,power)
Select 'install zip from sdcard'
Select 'choose zip from sdcard'
Now navigate to the .zip that you just transferred to your device and select it
Your super fast ROM is now installing and this may take a while
After installation reboot
To enable overclock on compatible kernels use xan's excellent app, Voltage Control : http://forum.xda-developers.com/showthread.php?t=829731
Darky's ROM comes with it's own kernel, if you would like to stick with the kernel you chose in step 3, just follow the instructions again.
Step 7 -
Enjoy!
I have tried my best to make this guide almost noob proof, however if there's anything I've missed out or it doesn't make sense please tell me and I'll try my best to make it more suitable. As things progress I plan to update this post so please stay tuned.
Also if you like this post I'd appreciate if you clicked the thanks button
Dont forget that most OC kernels rely on Voltage Control at this moment
This is kinda sticky I think... Base steps for a new SGS users (who have some experience with Android though)
xan said:
Dont forget that most OC kernels rely on Voltage Control at this moment
Click to expand...
Click to collapse
Oops, thanks I'll add it in
Improvement
Maybe you could explain whats this Vodoos Lagfix ist all about? And maybe go into details, why ext4 is much better than the normal partition system samsung uses? Just a guess that would interest some new users.
Though you did a great job, woulda been a lot easier if i had this guide when i flashed my phone Anyway, Have a happy life.
Great Work!
I think no more details needed!
It would be hard to read!
Over the past 3 days that I've owned the device, i read many many guides, suggestions, forums etc!
Here i found everything that i would like to read at first so i didn't waste many hours on reading
You also need to add that if you load a customer ROM like Darkys, it will override your old kernal. Darkys ROM has kernal already in the package!
As a result 'advanced ULK features' is no longer there with Darkys ROM!
Its already there right above Seventh step
Excellent! Thanks so much for writing so clearly and succinctly. I have a problem:
I thought I flashed to JPY but my phone still shows JPA. I've done it both with and without the ODIN Pit file. I've rebooted a few times and even done factory wipe but it keeps showing JPA. Any ideas?
You might want to include that you do not want to have lag fix applied if your going from stock jpy to a custom rom and how to properly disable voodoo. Could save alot of headaches.
Sent from my GT-I9000 using XDA App
holgalee said:
Excellent! Thanks so much for writing so clearly and succinctly. I have a problem:
I thought I flashed to JPY but my phone still shows JPA. I've done it both with and without the ODIN Pit file. I've rebooted a few times and even done factory wipe but it keeps showing JPA. Any ideas?
Click to expand...
Click to collapse
as far as I know JPA has 803.pit BUT JPY has 512.pit.
did you tick the re-partition option in odin? if that still fails you need to flash first a stock eclair with 512.pit, like JM8 and the repart option ticked. then reflash JPY with repart option un-ticked.
Thanks for all the great comments guys, obviously as things move on(new kernels/new ROMs). I will try my best to keep this post updated as much as possible.
Samdroid_G_S said:
You might want to include that you do not want to have lag fix applied if your going from stock jpy to a custom rom and how to properly disable voodoo. Could save alot of headaches.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll do that later on today when I get back in the house This post will be edited over the next few days in order to make it a really simple guide and the only way it improves is due to the community telling me how to improve my post. So thanks!
Hello,
I did second step and it should reboot into the latest Samsung ROM but it is not! Phone is starting and showing that "S" , a few times goes vibro. After few minutes vibro goes three times at once and phone goes off. Touching screen lights up menu and back buttons. And more: if I left phone it vibrates time to time. Pressing and holding ON button repeating everything again.
Is it really only one file in Odin is needed? Only PDA? Is there no needed PIT file? Maybe there is more settings needed? Please need info how to back my phone. I did only second step! Thanks
Barcors said:
Hello,
I did second step and it should reboot into the latest Samsung ROM but it is not! Phone is starting and showing that "S" , a few times goes vibro. After few minutes vibro goes three times at once and phone goes off. Touching screen lights up menu and back buttons. And more: if I left phone it vibrates time to time. Pressing and holding ON button repeating everything again.
Is it really only one file in Odin is needed? Only PDA? Is there no needed PIT file? Maybe there is more settings needed? Please need info how to back my phone. I did only second step! Thanks
Click to expand...
Click to collapse
You could try adding 512.pit, but I decided to leave pit files out as they are no longer recommended by samfirmware.com
Sent from my GT-I9000 using XDA App
Great thread, thanks for this Paul!
A lot of thanks
Yes post is great and one of the clearest in the xda
Seems to be I am not a good geek because step fifth is not very clear for me. I mean explanation in recovery mode is not the very same like I have. I will give examples later on because I am on the road right now. And I would add general explanation for dumps how everything is an what for. For example: to have fastest sgs first you need flash it to stock rom, then flash an kernel, then do some tweaks in recovery mode, then again flash new suposed to be fastest rom. Something like this if I understood everything right. Sorry for beeing soo nooby I just want to help you and those new nobs who I am shure will appear.
Darkyy said:
Great thread, thanks for this Paul!
Click to expand...
Click to collapse
Haha thanks Darky ! Just thought I'd try to clear things up for everyone and stop all the pointless threads in development.
Sent from my GT-I9000 using XDA App
Thanks from me too
Voted to be on the portal (and should be a sticky)
Thanks. Nice guide
Glad to see everyones enjoying it I'll make a few edits and fine tune it tonight.
Sent from my GT-I9000 using XDA App
So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Update: Flashing to I9000XXJPU replaced the DBDATA. The file from samfirmware.com did the trick! Thanks for a great forum
This should resolve any issues you have with the DBDATA since the I9000XXJPU-rom creates a new DBDATA.
Open Odin and select 512 .PIT, and CSC, PDA, MODEM-files. Check Re-partition and don't touch any other settings.
Turn off your phone and put it in download mode by holding VOL DOWN+MENU+POWER.
Now just flash the phone with your ROM of choice. See here for correct flashing procedures: Flash Firmware and kernels using Odin
AFAIK you should only repartition if you have a lowlevel/full rom. Make sure you use the correct PIT either way.
Click to expand...
Click to collapse
Update 2: After reading feedback from several forum members it seems like it may be wise to just stick with 512 PIT for the time being.
dbdata
nooryani84 said:
So I tried flashing to XWJS3 in order to set my phone to PIT 803. As I understand i have to do this in order to flash it to XWJS5. After flashing with all 3 files i get this error in the recovery mode
How can I solve this?
Click to expand...
Click to collapse
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)
Thanks for the tip though as I find little documentation on that fix I think I'll flash to I9000XXJPU then XWJS3 with 803 => then XWJS5.... or can I skip the second step?
hehe sorry, I'm pretty new at this and have been reading a ton.
This is a fairly common issue. If you repartition your device (ie. run repartition with a new .PIT file) you change the partition sizes and therefore some of the old partitions become unavailable. In this case the partition that holds dbdata would have been changed and the old dbdata data was unavailable to the system. The fix is (a) flash a full ROM that contains all the components needed eg. JPU in this case, or (b) flash just the component you need eg. dbdata.rfs in this case. Either way would resolve the problem.
Hi,
i have the same Problem. After an unsuccessful flash (including a brain fart) with the JS5.
Flashing the I9000XXJPU with 512 pit and repart fixed the issue, i could start my phone again.
However, after that i flashed the JPY-PDA with 512 pit + repart i have the same "Can't mount DBDATA" error again :/
When i do a factory reset + reboot in this state, i get the Bootscreen with the Samsung S Logo, but then the screen just turns black and nothing happens.
Any suggestions how to fix this?
i had the same problem i would flash JPU with Repart and 512 all fixed then i would flash JS3 with repart and 803 and i get the same error then i went back to JPU then fixed then JS5 or JS3 i get the error back again. I do see dbdata.rfs being flashed as the last thing but still the error.
The only way i could get it to boot was when it showed the error i would scroll down the recovery console to wipe/clear data and then reboot and it worked fine booted to JS5. Hopefully thats works for you.
So in summary i flashed JS5 fine but had to do a wipe/clear data then reboot in the console but i dont know if it means there is still a problem but so far its working fine. My only issue is that i still have the old market and i cant see all the samsung apps like video editor etc.
Well, that is what i already tried. It starts into the samsung bootscreen after that but then it just force closes and i have to pull the battery.
I just flashed JPU again, the phone is in a working state atm. But i would like to upgrade it to the JPY, without the error obviously
//EDIT
Just tried it again, here is what i have done:
1. Flashed JPU with repart and 512 pit
2. Confirmed it was working.
3. Rebooted into recovery, did a factory reset + a wipe data
4. Rebooted again, confirmed its working
5. Flashed the JPY with repart and 512 pit
---> DBDATA error again :/
6. Factory reset + wipe cache
But after a reboot i only get force closes and a black screen.
Any suggestions?
Do i need to flash the JPY in a different way after i have successfully flashed the JPU?
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again
which pit file did you use ofr JPU to work with repart?
i think we are in the same boat we both have been on pit 512 and need to somehow get to pit 803
Copacaba said:
//EDIT²
Well, after i did start to actually use my brain it did work
I did flashed with JPU(3 Files), repart and a pit file.
So there is no actual reason to flash the JPY and AGAIN use a pit file + repart.
Its what i did when i flashed the JPY the first time (i came from 2.2 back then).
My phone is booting without any issues now, and i have JPY-JPY-JPY again
Click to expand...
Click to collapse
I forgot to mention that I did NOT use flash it with another PIT-file after the initial JPU flash + PIT. When I tried that appoach i got the same DBDATA-error. However I plan on flashing it with this I9000_XEN_I9000XWJS5 which includes all 3 files.
Download I9000_XEN_I9000XWJS5, see first post.
I'm interested to know if anyone has success with this method. Are there any benefits of changing the PIT file?
I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?
emmarbee said:
I was stuck at DBData error! Wiped the Cache/User data. But only after seeing this thread I came to know that there is no necessity for that
So for the people who are reading this thread with the dbdata problem. Here's my experience NO NEED TO WIPE USER DATA FOR DBDATA PROBLEM. To solve the dbData problem, I went to Darky resurrection and now I'm in Darky 9.2, though its good, I'm far more comfortable with stock rom for some reason.
Now I'm Totally confused on how to flash to JS5.
What should I do now?
Flash XEN JS5(3 files) + 803pit + repart ?
Click to expand...
Click to collapse
If you follow the instructions in the first post you will have to re-partition with a full stock rom such as JPU. This will erase all your user data/cache. Afterwards you can flash JS5 with just the PDA.
You may be able to flash/re-partition JS5 with 3 files and 803 pit, though I can't confirm if this is a full rom like JPU. If it is a full rom then I think you may be able to skip flashing JPU all together.
Someone more knowledgable than me would have to confirm this before I can recommend it though. To be on the safe side just flash JPU(3files)+512 PIT w/re-part first, then JS5(1 file) without re-part.
well stop using pit 803.
use 512 or 513.
samfirmware have a love for pit 803 but its most useless of them.
this has been up for discussion 100+ times and the fact is that pit 803 really sucks.
**DamianGTO Steam kernel. 350MB Ram. 500HZ. all ext2. Steam Rom. Js5**
Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.
Have a look at this :
http://forum.xda-developers.com/showthread.php?t=816449
The basic difference is the partition size of system and dbdata.
Auzy said:
Really Damian? Because on some threads people are saying the opposite.. In truth, I haven't seen any evidence that anyone has actually analysed the PIT files well enough (except maybe the Heimdell developer), to know whats going on, and I don't really recall him saying what was going on.
Click to expand...
Click to collapse
well i know it well. its looked into how it works.
the main thing is the different size of the partition. but many has different problem when using pit803.
it always works with pit 512, accept for one firmware. that need pit 513.
that's for the firmware is to big for pit 512.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards
miro666 said:
UFFF!
I can confirmed method on first post working, and very important is what write on gray:
If you're upgrading to a newer rom with 803 you must NOT re-partition again or you will end up with the same problem.
Thanks and Regards
Click to expand...
Click to collapse
Thanks for the feedback, I´ve updated the post. This problem annoyed the hell out of me, so I hope it saves people some of the frustration.
TechKidTarek said:
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below
P.s press the thanks button =)
Click to expand...
Click to collapse
This unbricked my phone. Thank you sir.
The dbdata File was flashed in Recovery Mode? Not in Downloadmode?
Hello folks,
I posted here recently about an issue I had when I loaned my brother my Vibrant running 2.2, and he accidently installed Voodoo 2.1 on it. It made a big mess of my phone, and I wasn't able to even boot up.
Working with several members of a few different Android forums, I got myself working using Eugene's No Brick ROM. My phone seems to be working fine, except that now the phone thinks it's Application Storage is 0.00kb left, when I know I have over 11GB on the internal SD. The feeling I've got from several people is that my stock kernel I reflashed is only seeing the space it's installed on, and not all the reformatted space that Voodoo has altered.
A few of the guys I talked to said I probably need to reset my phone with a FULL ODIN package (that includes boot.bin. sbl.bin movinand.bin) to reset the phone's internal SD back to the original format.
Does anyone know where I can find that full ODIN package?
Or if anyone else has any other ideas, please let me know.
The bootloaders won't help...just increase the chance of a hard brick. You probably will benefit from odin with the pit and tar with repartition checked for jfd.
Edit: fyi this will wipe your entire internal sd, so backup.
I have the same problem. Can you please point me to the download links and name of the pit and tar? Thank you.
http://forum.xda-developers.com/showthread.php?t=771111
everything you need is in there. Good luck.
Sdobron said:
The bootloaders won't help...just increase the chance of a hard brick.
Click to expand...
Click to collapse
My phone is a brick right now if I don't install a ROM with a bootloader on it (Eugene's No Brick ROM). That's the only way I can get it to boot up.
kgbros said:
http://forum.xda-developers.com/showthread.php?t=771111
everything you need is in there. Good luck.
Click to expand...
Click to collapse
Thanks, I've been looking at all the various stickied threads, and can't find what I am looking for, which is why I was asking for some help.
I was hoping someone could point me right to what I need. None of the ROMS I found in there are the complete ODIN packages.
You don't need a bootloader to correct this problem
I'm going to echo everybody else's statements, you don't need to flash any new bootloaders.
No offense OP, but I'm pretty sure you don't know what bootloaders are.
The Wikipedia page on bootloaders
Use 512.pit file and check repartition.
Some good info here as well
http://forum.xda-developers.com/showthread.php?t=848737
Read my previous post. This WILL fix your problem.
Thanks for your responses everyone,
Several times I've tried reflashing the stock ROM and PIT file (and selecting partition), and each time I've ended up with the same result - I get the T-Mobile and Galaxy S boot screens, and then the phone goes black and stays there.
The only way I can get my phone to boot up is using Eugene's No Brick ROM.
You can read more about my initial problem here.
Any help you can offer would be greatly appreciated.
You're supposed to flash eugene's then jfd with repartition checked. I've had the same exact brick before (my only legitimate soft brick) and this is the solution.
Edit: Have you been able to check your partitions in adb shell? Check mount and see if they are rfs or ext4.
Thanks Sdobron - I've done that many times, and after doing jfd (T959UVJFD) with a re-partition, I get the soft brick again.
If I check adb, my partition is rfs.
This is why I am so confused. It's like my phone shows no signs of why there should be an issue, and everything I try doesn't work.
Hi all,
I've just got my new i5800L, and I've already rooted it with z4root. Here are my qs:
What's all that of XXJPM and all that stuff? Which one should I use for mine? (actual one is I5800LVIJG7 (Eclair)).
Is there any way of doing a nandroid (full copy of the actual rom which can be flashed easily) so if I mess things up or want to get back to Eclair I'd just have to flash it back?
I guess that's all by now. Thank's in advance.
JPM is the latest froyo rom...you cant backup ur whole rom as if nw we dont have any alternative for this...check flashing guide in sticky and see vdos on youtube. ...happy flashing...
Sent from my GT-I5800 using XDA App
Thanks..
I've downloaded 2 files (2 diferent versions). One was a zip file with 3 files inside and the other one was a rar file with 4 .tar.md5 files. The zip i don't know how to apply it because odin will only take .tar or md5 files and in the other one I don't know what to do with all the .tar.md5 files. What should I do? :S
moikop said:
Thanks..
I've downloaded 2 files (2 diferent versions). One was a zip file with 3 files inside and the other one was a rar file with 4 .tar.md5 files. The zip i don't know how to apply it because odin will only take .tar or md5 files and in the other one I don't know what to do with all the .tar.md5 files. What should I do? :S
Click to expand...
Click to collapse
Take a look at rudolf895 youtube channel
http://www.youtube.com/rudolf895
All you need to know is on his Videos
Hope this helps
Thanks, now it's booting (on the samsung screen). I think it worked. But now it's "orangeized" XD. I'll keep looking for the right tar XD
PD: is it ok if it takes a while on the "samsung" (the one with the glow, after the GT-I5800l screen) screen? cause it's past a few minutes and still on that screen and I'm starting to panic XD
EDIT: It's been more that 15 minutes since it's stuck at that screen. What should I do? Please, second day with it and already screw it XD
Flash the JPM firmware...you shud get it as a tar package...a single file...
but sometimes u will have 4 files
1. bootloader
2. pda
3. csc
4. phone
dont ever flash the bootloader file in odin with pda csc n phone tar files...because the risk of bricking goes high...
just flash the 3 remainin files...n when ur fone has booted...just do a hard reset
katkoriaarpan said:
Flash the JPM firmware...you shud get it as a tar package...a single file...
but sometimes u will have 4 files
1. bootloader
2. pda
3. csc
4. phone
dont ever flash the bootloader file in odin with pda csc n phone tar files...because the risk of bricking goes high...
just flash the 3 remainin files...n when ur fone has booted...just do a hard reset
Click to expand...
Click to collapse
Great, now it works again! Thank you a lot. And now I finally understand how odin works :-D
which custom rom do you guys recomend?
Don't forget the i5800L is different from the i5800, but the only difference is the 3G antenna frequency. If you install JPM you MIGHT have 3G connection problems, or then again you might not. You MOST LIKELY will see a battery life decrease because of this issue. If you want really badly to have Froyo (android 2.2) you can flash a JPM ROM. If you want your battery to last a couple of days, either wait for an american release of froyo, or keep your Eclair version.
I have a i5800L from VIVO, originally with JG7 as well. When I installed JPF (previous froyo release) I had issues with the 3G network, when I flashed Kyrillos custom JPM ROM i also had problems. When I flashed Lestatious custom JPF ROM I didn't have problems, and when I flashed clean JPM i didn't have problems either.
So really, its a question of luck.. although let me tell you, my battery lasted way way longer on the original JG7 firmware than any other release (including the JK1 Eclair, said to be the best Eclair released before froyo).
Remember though, if flashing separately (not as one package), avoid flashing the BOOT file or BOOTLOADER. Flashing this increases the chance of bricking your phone. Not flashing it decreases the change by 1000000000000 times.
IonAphis said:
You MOST LIKELY will see a battery life decrease because of this issue. If you want really badly to have Froyo (android 2.2) you can flash a JPM ROM. If you want your battery to last a couple of days, either wait for an american release of froyo, or keep your Eclair version.
Click to expand...
Click to collapse
Yeah, I can see that. I'm with Kryllos v3.3 and the battery only lasts like about 16 hours :S. I guess I'll go back to I5800LVIJG7 (The one which it came with).
IonAphis said:
Remember though, if flashing separately (not as one package), avoid flashing the BOOT file or BOOTLOADER. Flashing this increases the chance of bricking your phone. Not flashing it decreases the change by 1000000000000 times.
Click to expand...
Click to collapse
About that, if I flash the bootloader (with all the others too, of course), and it upgrades ok, then there's no problem, right? I mean, if I try to downgrade again, it'll work fine? (Yes, before I read the comment telling me not to flash the bootloader, I did it and it was successfull. But now I don't know if it'd make it fail when I'll downgrade to I5800LVIJG7 :S)
It's not about upgrading or downgrading. When you flash, pratically all the memory on your phone gets erased, which means you can upgrade or downgrade at will with no problems.
The problem is, when you flash a bootloader, and say, for example, you have a power outage, or your computer decides to give more resources to your MSN or winamp you have running on the background (or whatever else), or even there is a problem with your cable connection or a spike in power, or whatever other mishap that can occur, the bootloader might not be able to transfer successfully. If that happens, you won't be able to boot your phone. If you flash everything except the bootloader and something happens, you will be able to at least go back into download mode and reflash the files needed.
Basically the bootloader tells your phone to start. If that gets corrupted, it simply won't. If you avoid flashing this and even if the transfer gets corrupted, you can always do the process again by going into download mode (which is installed along with the bootloader)
Great, thank you so much
moikop said:
Great, thank you so much
Click to expand...
Click to collapse
So when you were running on Kyrillos' ROM, did you have any connections problems with the 3G band?? thank you for your answer
fedee13 said:
So when you were running on Kyrillos' ROM, did you have any connections problems with the 3G band?? thank you for your answer
Click to expand...
Click to collapse
No, I haven't. I'm now in Kyrillos v5.7 and it goes great (battery consumption, performance, etc)
Remember to backup your IMEI so we may have one less "help my imie is 000000000" thread.
Sent from my GT-I5800 using XDA App
moikop said:
No, I haven't. I'm now in Kyrillos v5.7 and it goes great (battery consumption, performance, etc)
Click to expand...
Click to collapse
Fantastic! thank you very much Now it's time to learn how to do it haha
dilzo said:
Remember to backup your IMEI so we may have one less "help my imie is 000000000" thread.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
How do i do that??
fedee13 said:
Fantastic! thank you very much Now it's time to learn how to do it haha
How do i do that??
Click to expand...
Click to collapse
Go to terminal emulator and type this..
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Wait for few seconds. Then copy efs.rfs from sdcard to pc and keep it safe.
arunmcops said:
Go to terminal emulator and type this..
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Wait for few seconds. Then copy efs.rfs from sdcard to pc and keep it safe.
Click to expand...
Click to collapse
I'm sorry but where I find this "terminal emulator", I'm new at this.
Thanks in advance!
fedee13 said:
I'm sorry but where I find this "terminal emulator", I'm new at this.
Thanks in advance!
Click to expand...
Click to collapse
Market dude......
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
you custom flashed??
what do u mean u custom flashed??
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
tibosee said:
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Click to expand...
Click to collapse
Can you send me a link with a rom which has this please?
Here i had the same problem when I tried to flash my first rom. Just tried to flash on another computer and guess what... Successfully done!
Sent from my GT-I9100 using Tapatalk 2
smalmagal said:
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
Click to expand...
Click to collapse
Yes I factory reset a STOCK ICS ROM .. please can you assist in what I need to do.. Which PIT file and which ROM Shall I try to flash with.. please assist.. Many thanks..
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
read the whole tut again it tells you why since you have to move partition tables.
Yes...it's a rather small deal anyway...there are 64gb SD card after all.
mkohman said:
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
Click to expand...
Click to collapse
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
nipuna said:
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
Click to expand...
Click to collapse
Thanks for your assitance bro.. I will live with it. .I don't mind loosing 3 gb .. Already got 32GB SD card so no issue. Just happy its all back up and running really.. Big thanks to the German brother you the man
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
prabhu1980 said:
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
Click to expand...
Click to collapse
I actually followed his guide and repartioned manually and only lost about one Gbyte vs using the pit file and losing over 3 G bytes. Took a lot of trial and error though
Sent from my GT-N7000 using Tapatalk 2
RE:
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
can you contact entropy before sending your unit to samsung??
entropy is looking, if im not mistaken, for a purely stock bricked note... kindly pm him
zairui said:
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
Click to expand...
Click to collapse
Not necessary to use the 3gb regain patch.
There's a 1gb or 2gb regain patch also. And it's enough.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
Though so many ppl told u alrd, i just want to say, in any case, when u r in ICS alrd, it is totally prohibited to do factory reset through CWM with samsung ICS original kernel.
When u need to wipe or factory reset, make sure u r on a safe kernel like speedmod or notecore.
If u want to recover ur note, just use the pit file method. It works.
Make sure u use the correct patch of 16gb or 32gb, depends on ur note.
Always try from the smallest patch, so u won't loose so many storage.
Anyway, latest CriskeloROm with speedmod is the best for battery life nd performance.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
I'm having the same issue now.
I did wipe data / factory reset with stock ICS kernel and I think, I bricked the Note.
I didn't know there were such issue.
I couldn't find a ROM with 3 files (code.md5, modem.md5 and csc.md5).
Please kindly guide me where to find such ROM.
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
anubis1126 said:
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
Click to expand...
Click to collapse
So we dont need 3 files ROM?