Related
So I tried to flash the rom of my galaxy tab.
I first flashed it to JM6, everything fine
Then to JMA, everything fine
Then to JMF, and the tab did not reboot, it went into recovery mode.
I tried rebooting again, it got stuck at Samsung logo, I went to recovery mode and wiped data and rebooted again and it again was stuck at the Samsung logo, I tried doing this 3-4 times and it was always stuck at samsung logo.
I tried flashing it again and no luck.
Then I tried flashing a different rom, the JHA from Roto, and odin failed.
Now my tab has picture I havent seen anywhere else, A phone picture - A PC picture and in between there is a yellow triangle with ! in it.
I can not go to download mode, can not go to recovery mode!
Stuck like this, can anyone help?
ok so when I have the phone+yellow exclamation+computer pics, i used odin to flash it again, and it did flash!
after the flash the screen became the normal download mode, i rebooted and it got stuck again at samsung logo, i did the wipe data thing on recovery mode but it still does not boot, gets stuck at samsung logo.
help please
solved !
went back to base rom jm6, pit csc pda modem files, did boot
then flashed again to jma
now using jma
dont know which rom i should use now, cause jmf did not reboot
Hello everyone,
I have the same problem since yesterday, after wanting to do things too fast. I have a french Tab bought from SFR.
Coming from Roto JME V4, i flashed OC Kernel v2, all fine.
Then when modaco's ext4 kernel drop, i flashed it and did the ext4 conversion : all fine.
On top of that i tried to flash new OC Kernel v6 for ext4, i ended up with freezing home after analysing storage, just like others.
Here's what i did wrong : i didn't backup recovery with CKW has i should have, i tried to flash JME V4 again, thinking it would wipe and i would have started all over again, no matter.
So here i am, odin flash didn't end well, i restart the tab and i have this frightening logo.
Now i would have liked doing like you, flash with odin while this logo's on, but i think the battery's out : whatever i do, tab keeps alterning logo/black screen(like off)/logo/black screen/logo, while pluged ; doesn't show anything if not plugged ; odin can't see anything.
Has anybody got an idea? Just let me know if you need more info (no logcat or screenshot though).
Thanks in advance. Regards,
FF
It sounds like you've probably both had a problem a lot of us have experienced in the past because the JM series ROMS after JM6 do not include dbdata.rfs and this often causes Tabs to error when you enter the recovery console after a flash (or hang at the Samsung logo if you don't go into the recovery console). The way to solve this is either to make sure that the ROM you flash includes dbdata.rfs or flash the dbdata.rfs file from JM6 with Heimdal after you have flashed another ROM. If you look in the topic for the JMG ROM you'll see a number of posts about this and there's a link posted on page 3 to a stock JMG ROM that includes the dbdata.rfs from JM6 and can be flashed straight with Odin.
Hello everyone,
I'm still with the same problem, the Tab don't seem to charge while plugged in, it keeps alternating showing the logo then nothing like the tab's off.
Odin can't see anything as the Tab just keeps turning on & off.
What do you think? screwed? go to shop and play the idiot to get a new tab?
Thanks.
FF
JayJayaa said:
solved !
went back to base rom jm6, pit csc pda modem files, did boot
then flashed again to jma
now using jma
dont know which rom i should use now, cause jmf did not reboot
Click to expand...
Click to collapse
where can I download jm6?
Samfirmware.com
Sent from my GT-P1000 using XDA App
hope u got this fixed man
bdl1969 said:
It sounds like you've probably both had a problem a lot of us have experienced in the past because the JM series ROMS after JM6 do not include dbdata.rfs and this often causes Tabs to error when you enter the recovery console after a flash (or hang at the Samsung logo if you don't go into the recovery console). The way to solve this is either to make sure that the ROM you flash includes dbdata.rfs or flash the dbdata.rfs file from JM6 with Heimdal after you have flashed another ROM. If you look in the topic for the JMG ROM you'll see a number of posts about this and there's a link posted on page 3 to a stock JMG ROM that includes the dbdata.rfs from JM6 and can be flashed straight with Odin.
Click to expand...
Click to collapse
hi! can u give me a link for this exact thread u're refering to! as i searched it on the forum and could not find it! i too have a tab with the same problem! itjust hangs at samsung logo! but no issues with the bootloader! it came to me this way! i think the dbdata.rfs is missing! as i tried flashing a older rom too but didn't fix the issue!
WBR
ReyTech.
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?
i would love to flash up to JVU but being Canadian i am using the PDA and CSC sections on odin from the KG3 firmware, and the PHONE section is on JVR, which has been great,
so if i flash with odin and JVU in the PHONE section as well as KG3 in CSC and PDA, will it still work well?
i have all the files downloaded and am waiting not-so-patiently to hit go,
I'm running JW1 PDA with KG3 PHONE and CSC.
lgsshedden is running JVU PDA with KG3 PHONE. Not sure about the CSC.
It will work, the Canadian i9000m is pretty much identical to the international i9000 so just keep the KG3 CSC.
Do I only need to keep the csc for the dual band networks to work or do I need csc and pda?
Sent from my GT-I9000 using XDA App
Sorry, I misread what you wanted to do.
I've been using the CSC and PHONE from KG3 with the PDA from JW1 (and will do the same when I update it to JVU).
You want to keep the KG3 code (PDA) and the CSC and only want to use the JVU modem (PHONE). I'm curious...what does that give you?
I think it should work, I used KG3 modem with JVT, CM7, Onescosmic ICS Alpha's and now Team Hacksung ICS CM9 builds (currently 13). No problem with any of them, and signal as usual
not sure if this will help you, im on cm9 when i flash jvu modem i end up with no service. on bell.
okay so i tried to flash with JVU as PDA and KG3 on PHONE and CSC, and with a 512 .pit and re partition and all and when i hit go on odin it freezes after a few seconds, i have tried with both odin 1.7 and 1.82, what would cause it to freeze? i have also tried without the .pit and no re partition
Like others said, KG3 works with pretty much any build you want.
And dont worry about the CSC, it you have the wrong one installed the only downside is you can't update your phone with KIES. That is something you dont care about anyhow if you are flashing your own ROMs.
carmanj16 said:
okay so i tried to flash with JVU as PDA and KG3 on PHONE and CSC, and with a 512 .pit and re partition and all and when i hit go on odin it freezes after a few seconds, i have tried with both odin 1.7 and 1.82, what would cause it to freeze? i have also tried without the .pit and no re partition
Click to expand...
Click to collapse
Is it actually freezing or just taking a while to flash?
When I flashed JW1 as PDA and KG3 for PHONE and CSC, it took a couple of minutes to complete the flash process (Odin 1.82).
Try different USB ports and see if that makes any difference.
It starts then windows says it stops responding, and I am kinda wary of letting it go for more than a minute that way without just closing it,
Sent from my GT-I9000 using XDA App
Hi. I'll try to be as detailed as possible.
I have been using the Lollipop 5.0.1 I9505XXUHOA7 German ROM that got leaked early last month, and have just had a few niggling issues, like no silent mode.
So, I looked at SamMobile yesterday and found that there are later versions of Lollipop for the S4 that fixed things like silent mode. I obtained I9505XXUHOB7.
However, when using Odin to flash it to my phone, each and every time, it has gotten to the very end of system.img.ext4 (takes about 5 minutes), and then fails at the very end. I've tried a number of things including a different cable and different USB ports, flashing a new recovery and trying to reboot through that, and even obtaining the CSB_signed_Fusion3_EUR_0325_V2.pit file to Re-partition. At this stage, I don't care if I lose files. I keep most stuff backed up. Just really want my phone to be up and running again, and not too sure what to do.
When I flashed the I9505XXUHOA7, it came with Bootloader, PDA, Phone and CSC to use within Odin, whereas any of the newer ROMs don't seem to have anything but the .tar.md5 file to use in PDA.
Any help would be greatly appreciated. Thanks very much.
Mate, when you download the file in Sammobile you only get 1 .tar file.. it comes with everything.. not like the leaked OA7
1. try using the latest odin 10.6 i think, AP to flash Firmware
2. Reinstall drivers to your PC
3. Or try to redownload a firmware again.. latest is OC6... it might be a bad download too..
4. Refrain using .pit file.... no good at all! Specially for official firmware...
I always brick my phone before and i had no issues flashing diff firmwares from diff country
Did you try flashing the OA7 again? The leaked OA7 (4 files + pit) is a service firmware and should fix issues like these (just to make it running again). After success, you should try an other firmware f.e. OB8 (maybe a bad download?)
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.