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?
Related
My internal SD failed about 5 minutes after the latest update and so I started trying to flash new roms/pit combinations like a madman. This led me to the Q&A subforum, where I found this thread:
http://forum.xda-developers.com/showthread.php?t=892534
Where:
Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
I did this and followed every instruction, it works perfectly. My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Also, thanks so much to Encrypted1024 for finding this.
Why didn't you just send it back to Bell and get your new phone + $100?
I have a launch Bell i9000m that refuses to die. I've flashed via CWM and Odin many times, but it's still fine. I'd actually be happy if it died so I can get the $100 credit and a new phone....
sr3yas said:
My phone went from the DBdata recovery error and unable to mount filesystem -> Darky's Rom 7.7 with all the working bands.
I urge everyone with a failed bell phone to try this, it's amazing.
Click to expand...
Click to collapse
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.
wang1chung said:
sorry, but dbdata errors in recovery are not the major sdcard issue that is not recoverable from. dbdata errors are recoverable via flashing, same with st10/11.
unless someone with an mmcblk0p1 issue wants to try this, i highly doubt it will work.
Click to expand...
Click to collapse
I just tried it with my mmcblk0p1 error, and it doesn't work.
jentech said:
I just tried it with my mmcblk0p1 error, and it doesn't work.
Click to expand...
Click to collapse
Agreed. I just hit my second phone with that error and haven't seen any solution to recover from it. Dead = dead.
We need to get very clear on this board between what is a truly dead phone due to sd card issues vs what is recoverable (no comment on how sucky it is to experience a recoverable issue tho).
The thing is, that I've installed CM7 (the one, that is uploaded here in a topic), and now I would like to go back to 2.2.1 . Now, I did this: flashed XWJS3 with 512.pit and re-partition enabled using odin. After flash, it took me to the basic recovery menu as it used to, and displayed some errors, some notifications etc... I ignored it, because it always does this... Then tried to reboot, and it booted, and after animation screen has gone black, two touch-buttons lit up. And it didn't want to go on. I did the whole stuff again, same. I'm stuck, plz help me guys to get it working. Thanks!
Can you use download mod?? Pls pm to me if you cant
flash jpc with repartition
then flash whatever u want...
i fell subject to same sort of issue and after hours of googling found the issue to be a fault with the Internal SD Card and my fix was as follows in my thread
http://forum.xda-developers.com/showthread.php?t=910076
gbohm, JPC is 2.2 isnt it?
Sparco, you wrote, I should flash 2.1
Would any of you be so kind, and give the exact one?
The exact name and .pit I need from samfirmware.com THX!
2.1 XJWM9 rom says after flashing: E: Cant mount /dev/block/stl11
94kram01 said:
gbohm, JPC is 2.2 isnt it?
Sparco, you wrote, I should flash 2.1
Would any of you be so kind, and give the exact one?
The exact name and .pit I need from samfirmware.com THX!
2.1 XJWM9 rom says after flashing: E: Cant mount /dev/block/stl11
Click to expand...
Click to collapse
You flashed the wrong repartition with jpc from samfw nothing can go wrong then flash whatever without reparition....
Oh btw wrong subforum isn't it?
Sent from my A101IT using Tapatalk
Is this for sure the right pit does it say use pit? Or just one file no pit?
Just flash the one i told you jpc with repartition and report back happened before isn't a problem we will get it working again don't be afraid
Sent from my A101IT using Tapatalk
Okay, firstly, thanks!
I managed to find out, that any rom, that has all the files (so is really a full rom, not only update) (cache.rfs dbdata.rfs [<- this one was missing for me] factoryfs.rfs modem.bin param.lfs zImage) has to be flashed first when stuff is messed up like in my case. After that, it's going to repair itsself, and then any rom is flashable
94kram01 said:
Okay, firstly, thanks!
I managed to find out, that any rom, that has all the files (so is really a full rom, not only update) (cache.rfs dbdata.rfs [<- this one was missing for me] factoryfs.rfs modem.bin param.lfs zImage) has to be flashed first when stuff is messed up like in my case. After that, it's going to repair itsself, and then any rom is flashable
Click to expand...
Click to collapse
Yes exactly jpc is such a full release
Sent from my A101IT using Tapatalk
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!
I tried to upgrade from jpy to jvp with odin, I used the correct settings in odin but the levels get stuck in factory fs, I still have the download mode and the connection is good but nothing seems to happen. I tried again and again and it does the same everythime, any idea?
Sounds like you had a lagfix on JPY.
The only thing you can really do is pull the plug, and hope you can get back into download mode.
Flash a 3 file firmware with a 512 pit and re-partition.
Download JVP from this thread, it's a 3 file firmware.
http://forum.xda-developers.com/showthread.php?t=1102881
Thanks, actually I managed to solve the problem by reinstalling jpy without repartition, it changed my kernel to the default one as I had speedmod and and then I upgraded to jvp with repartition....thanks again for your help.
cgo372 said:
Thanks, actually I managed to solve the problem by reinstalling jpy without repartition, it changed my kernel to the default one as I had speedmod and and then I upgraded to jvp with repartition....thanks again for your help.
Click to expand...
Click to collapse
I have had this issue a number of times when flashing stock Gb firmwares, it will not flash when using .pit file for some reason..
But not selecting .pit and deselecting Repartition seems to work fine.
I have been running XXJVP for a good few days without any issues!
The other day I followed the thread
Root_Method_Rev_B/11_Bootloader_Using_Combo_Firmware
This is a root method for the s7 and s7 edge on bootloader 11 (B) phones using the combination firmware. I really dont think it will do much but I will post it and maybe someone will do something with it Downloads...
forum.xda-developers.com
and though it works it is super buggy and constant crashes after reflashing several times. SO I wish to return the phone to complete stock. Is there a way to do this? I have read over several post about this and I just get errors or varying results no matter what method/rom I try to use.
panowolf said:
The other day I followed the thread
Root_Method_Rev_B/11_Bootloader_Using_Combo_Firmware
This is a root method for the s7 and s7 edge on bootloader 11 (B) phones using the combination firmware. I really dont think it will do much but I will post it and maybe someone will do something with it Downloads...
forum.xda-developers.com
and though it works it is super buggy and constant crashes after reflashing several times. SO I wish to return the phone to complete stock. Is there a way to do this? I have read over several post about this and I just get errors or varying results no matter what method/rom I try to use.
Click to expand...
Click to collapse
What version of Odin are you using, and what firmware are you trying to flash?
Have you tried a different USB cable?
Generally flashing Samsung devices works pretty much the same. If you're returning to stock from a custom ROM or otherwise want to wipe data, use the CSC_xxxxx instead of HOME_CSC_xxxxx file in the CSC slot. Data doesn't mix and match well, so if you didn't wipe after coming from a custom ROM or other firmware, that could be the reason for the instability.
V0latyle said:
What version of Odin are you using, and what firmware are you trying to flash?
Have you tried a different USB cable?
Generally flashing Samsung devices works pretty much the same. If you're returning to stock from a custom ROM or otherwise want to wipe data, use the CSC_xxxxx instead of HOME_CSC_xxxxx file in the CSC slot. Data doesn't mix and match well, so if you didn't wipe after coming from a custom ROM or other firmware, that could be the reason for the instability.
Click to expand...
Click to collapse
I've tried several ODIN versions. 3.12,3.13, 3.14, 2 different modified versions and it seems to be the same.
I have tried 3 different cables, no change.
I have tried using the normal CSC and HOME_CSC but I still return errors.
I can flash the combination firmware and the stock MM rom listed in the original post but no matter what other post I try to follow I can not get any to take. How can I get rid of this combination firmware and return to stock completely?
panowolf said:
I've tried several ODIN versions. 3.12,3.13, 3.14, 2 different modified versions and it seems to be the same.
I have tried 3 different cables, no change.
I have tried using the normal CSC and HOME_CSC but I still return errors.
I can flash the combination firmware and the stock MM rom listed in the original post but no matter what other post I try to follow I can not get any to take. How can I get rid of this combination firmware and return to stock completely?
Click to expand...
Click to collapse
I think what you need to do is re-partition the device using the factory PIT file that's located in the CSC package. In the Odin options tab, check the NAND Erase and Re-Partition boxes, then in the PIT tab, select the PIT file you extracted from the CSC_xxxx.tar
DO NOT check Re-Partition without using the PIT file. Make sure you're using the correct firmware for your device as this could result in a brick.
V0latyle said:
I think what you need to do is re-partition the device using the factory PIT file that's located in the CSC package. In the Odin options tab, check the NAND Erase and Re-Partition boxes, then in the PIT tab, select the PIT file you extracted from the CSC_xxxx.tar
DO NOT check Re-Partition without using the PIT file. Make sure you're using the correct firmware for your device as this could result in a brick.
Click to expand...
Click to collapse
Where should I get the PIT file from? Any particular site/rom file?
panowolf said:
Where should I get the PIT file from? Any particular site/rom file?
Click to expand...
Click to collapse
As I stated above, it should be in the CSC file.
Well, after many many hours of trying what seems like countless roms/files I have finally got it back to stock Oreo but the lag and stability is horrible. It is pretty much unusable, music apps crash/stutter, Playstore takes about 3 minutes to start up and can't even be scrolled through, returning to the home screen takes about 2 minutes as you watch each and every element load in one at a time including the wallpaper. I think the phone is trash now? I'm on B/11 (G935VVRSBCTC1) if that helps with any suggestions.
panowolf said:
Well, after many many hours of trying what seems like countless roms/files I have finally got it back to stock Oreo but the lag and stability is horrible. It is pretty much unusable, music apps crash/stutter, Playstore takes about 3 minutes to start up and can't even be scrolled through, returning to the home screen takes about 2 minutes as you watch each and every element load in one at a time including the wallpaper. I think the phone is trash now? I'm on B/11 (G935VVRSBCTC1) if that helps with any suggestions.
Click to expand...
Click to collapse
did you flash stock with odin?
Sorry for the late reply. Yes, I got the rom from samfw and flashed with Odin. Then I tried using Smart switch to update it and it was all successful but the phone is still fairly jittery. It's not as bad as it was on the combo rom but music apps still stutter and the system overall is pretty laggy.
Side note: The phone ran like new prior to flashing the combo rom.
jrkruse said:
did you flash stock with odin?
Click to expand...
Click to collapse
panowolf said:
Sorry for the late reply. Yes, I got the rom from samfw and flashed with Odin. Then I tried using Smart switch to update it and it was all successful but the phone is still fairly jittery. It's not as bad as it was on the combo rom but music apps still stutter and the system overall is pretty laggy.
Side note: The phone ran like new prior to flashing the combo rom.
Click to expand...
Click to collapse
You need to extract the pit file from the stock firmware regular CSC file and load it in the pit tab in odin along with the other files and you need to flash regular CSC not home CSC
jrkruse said:
You need to extract the pit file from the stock firmware regular CSC file and load it in the pit tab in odin along with the other files and you need to flash regular CSC not home CSC
Click to expand...
Click to collapse
I did. I'll try it again Monday and see if it makes any difference. I appreciate the help.
panowolf said:
I did. I'll try it again Monday and see if it makes any difference. I appreciate the help.
Click to expand...
Click to collapse
it sounds like you didnt wipe data so reboot too stock recovery and wipe data
I think it's running about as good as it's going to. I reflashed the stock Oreo firmware and extracted the pit, nand erase, re-partitioned, wiped data /cache. Still a bit jittery but it'll do. Just need it to play music while at work.
Thanks for the advice.