Related
Hello,
Bit of a droid noob here. I forced my Galaxy S to update to 2.2.1 today through Kies. It wouldn't work at first so I had to erase the M off of the model number in the registry to make it work (I think thats where my problem started).
Now my phone just reboots at the samsung screen or if it is plugged into USB it shows a star on the screen. I am able to get into download mode and use Odin, but even after flashing with a stock ROM from samfirmwares it still boot loops.
Help.
Thanks.
Oh, I think I am in the wrong forum. Q and A would be more appropriate. Sorry...
Okay, been messing around a bit more. Tried to load a different 2.2.1 ROM and now it turns on and flashes the Galaxy S screen and turns off. Not sure if it is getting better or worse.
did you had any lagfix activated while updating? if so, try to a factory reset through recovery mode.
No, I had no mods. It was a stock Bell rom updated through Kies. I managed to boot into recovery mode and it said something about can't mount sd card.
Encrypted1024 said:
No, I had no mods. It was a stock Bell rom updated through Kies. I managed to boot into recovery mode and it said something about can't mount sd card.
Click to expand...
Click to collapse
I've just encountered this problem myself (I guess misery loves company Lets see if we can resolve this.
What was the 2.2.1 ROM that you flashed that allowed you to get back into recovery?
What's the specific error msg you're getting when you're in recovery?
Well, I have flashed so many ROMs today trying to fix it, what I can tell you is this: JL2 gives the best results. It gets to the S screen with JL2. I think JL2 lets you get to recovery mode, if not then JH2. Speedmod seems to format the sdcard but doesn't seem to fix the issue.
I am getting this error from recovery mode:
E:Can't/b mount /devlock/stl10
Some people say they have fixed this with various flashes and reflashes and repartition combos. I have had no luck so far.
Apparently there is a way to restore the partiation, but I am not there yet.
Oh, the 2.2.1 ROM I tried was JPU_Complete_Flash_by_Virnik
Most likely the internal SD is dead and you'll have to send the phone in for repairs...
Mine just died (again) too. Same problem.
I just got my i9000m back from repair today... Updated to the official Bell for fun and then tried to go back to jh2 for recovery 2e and now my phone continuously loops at the first GalaxyS screen. I tried to flash many other versions with same results... Tried odin 1.7 and that didn't help. Tried various combinations of re-partition and different versions and nothing is working. Any idea?
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.
P.S. I was using Odin 1.7 all day and switched to 1.3 in the end. I was using 1.3 when I got it working. Just thought I would add that.
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
Encrypted, you are the man! I followed everything you posted and now I'm back up and running!
Encrypted1024 said:
I am getting this error from recovery mode:
E:Can't/b mount /devlock/stl10
Click to expand...
Click to collapse
Ahh.. That's where we differ. I'm glad you recovered from your error (too bad it happened to begin with). I'm getting the "E:Can't mount /dev/block/mmcblk0" error msg which I am fairly certain means I'm toast. Nothing working so far. I think I'll be testing the new return & $100 credit policy today.
I have seen similar posts where the steps I used helped with your error too. I would give them a try just to see.
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
This worked for me, there was some talk earlier of a bounty, so I donated 5 bucks (it's all I have right now) to childsplay charity through text in your name
gtg2 said:
Ahh.. That's where we differ. I'm glad you recovered from your error (too bad it happened to begin with). I'm getting the "E:Can't mount /dev/block/mmcblk0" error msg which I am fairly certain means I'm toast. Nothing working so far. I think I'll be testing the new return & $100 credit policy today.
Click to expand...
Click to collapse
On the phone I sent out I was able to get both errors depending on the firmware/kernel. Wish JL2 was out then.
Sent from my GT-I9000 using XDA App
sr3yas said:
This worked for me, there was some talk earlier of a bounty, so I donated 5 bucks (it's all I have right now) to childsplay charity through text in your name
Click to expand...
Click to collapse
Awesome! Thanks!
I was having similar issue and your post helped Thanks!
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
When flashing with Odin do you have checked Repartition? Do that and it should work.
Sent from my GT-I9000 using XDA App
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
This works! You are THE man!
I have checked other similar threads before posting, but I couldn't find anything helpful.
I had a stock 2.1 Eclair then updated to FroYo through Kies a couple of days ago (firmware JPA). Then I applied the voodoo lagfix through Odin and everything was working fine. Today I tried to install CF-Root using Odin. It went fine and my phone rebooted but then it went into a blank screen after the booting animation/sound.
I CAN boot into both recovery and download modes but I'm a little bit confused on what to do now. Should I flash a new firmware or is there any thing else that I could do to fix this. And if I have to flash a new firmware, which version do you recommend (I prefer stock 2.2.1 Samsung firmware, preferably ones for the Middle East so they would have Arabic support).
Thanks in advance
Just a little update. I flashed a new firmware (XWJPA), it went fine and rebooted then came up with the recovery menu with an error message that the /dev/block/stl10 can't be mounted. I tried to wipe stored data (not internal SD card) and rebooted it. Now it goes into the same blank screen but keeps vibrating randomly!!
Any suggestions?
your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...
azzledazzle said:
your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...
Click to expand...
Click to collapse
Can anyone confirm which one has dbdata, JM5 or JM8? I currently have a very slow internet connection and downloading both would take a lot of time.
Also could anyone explain the reason it got corrupted?
Thanks for your help
I flashed JM5 and now my phone boots fine again. Later I tried to flash JS5 but I got the same problem again! What am I doing wrong? And which is the latest stable firmware that I should flash to?
Don't tick repartition in odin when you upgrade to JS5
Thanks for the quick reply. The update went fine
I've been trying to reflash my Bell Galaxy S from not booting up without success. I have tried Odin and Heimdall no less then 10 times with different suggestions in this forum. And I went from getting the "Can't mount /dev/block/mmcblk0p1" when the phone first loop boot to not booting at all after first Odin, then to "Can't mount /dev/block/stl10" - "Can't mount /dev/block/mmcblk0p1" after another Odin.
After many Odin and Heimdall flashes now all I got is just a round inanimated "sun-ray" with the usb cable plugged-in or the Samsung splash screen without the usb cable.
I don't want to proceed further because I think the solutions I got from other posts are not specific enough for my situation.
I have read in many posts that you MUST disable lagfix before flashing with Odin or Heimdall. This I did not do because my phone started to loop-boot with the lagfix enabled.
Someone even mentioned here you can't flash your Galaxy too many times as every flash is registered in the phone, or you will void your warranty.....
My phone: Bell Samsung Galaxy S GT-I9000M. Updated from Eclair to Froyo via Kies. I do not know the exact Froyo version but my mental image of the "About phone" info screen seems to agree with UGJK3. Rooted and lagfix enabled while running Froyo.
Firmware packages I have tried back and forth so far:
s1_odin_20100803.pit
DBdata.rfs.tar (and I followed this post: http://forum.xda-developers.com/showthread.php?t=953339)
I9000UGJH2
I9000UGJK3
I9000UGJL2 (last thing I did on Odin and flash with re-partition)
And I did check the re-partition box in some cases when flashing with Odin.
Hope I can get more help here so that I don't damage the phone any further.....
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
odin
find your stock rom from ramad, flash with odin 3 files with repartition and pit.
http://forum.xda-developers.com/showthread.php?t=1102881
no problem to flash in odin with ext4 system.
its important to open odin and insert the files before you connect the phone, also take out the battery before you enter download mode can do the trick.
Removing lagfix isn't mandatory if you are using
re-partition option, since it's setting up all partitions and formatting 'em also. I have many times flashed with Odin without removing lagfix and never had any problems regarding it..
Sent from my GT-I9000 using xda premium
Thanks for everyone's suggestions.
I only applied lagfix after I updated from eclair to froyo. There was no further update after that. So my last working firmware should be a froyo. The bootloop was not caused by any software update process. I dropped the phone and the battery came off. I rebooted the phone (most icons missing from home screen after this boot) but the camera application gave me an error msg when I used it so I rebooted it again. It started to bootloop after this reboot.
I couldn't get the phone in the download mode without the phone battery. And if I get to download mode with the battery, plug the usb, then remove the batter, the phone turned off. so not having the phone battery is not an option to me.
So I did too more reflashes, screen shots attached:
(1) UGJG8
(2) UGKG3
The phone still looped with the circular bars.
I'm wondering if I should check the Phone Bootloader Update box at Odin. Or should I tried Darky Resurrection Edition rom?
nwsk said:
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
Click to expand...
Click to collapse
I took your suggestion and flashed a rom that supports ext4. I flashed it with Darky's Resurrection 10.2. Now I got a boot menu after the reboot. But I got "failed to mount /sdcard (file exists)"
Any idea? thanks.
PLEASE HELP....GT-I9000 Not Working..!
What i did?
I was using GB 2.3.6 XW_JW7
I rooted it with CF-Root-XX_OXA_JW4-v4.4-CWM3RFS via ODIN
I wanted to flash pa_galaxysmtd-1.9.2a-27JUL2012-202615 (PARANOID ANROID)
I went into recovery mode,
factory reset
wipe cache
wipe dalvik under advanced
i flashed pa_galaxysmtd-1.9.2a-27JUL2012-202615.zip but it restarted not completed and it stuck
I again went in recovery again tried to flash, that time could not found files,
I went to downoad mode
installed again GB 2.3.6 XW_JW7
It gave me pass
But when phone rebooted automatically it gave erros
E:copy_dbdata_media: Can't mount /dbdata your storage not prepared yet. please use UI menu for format and reboot actions..
Meida files copy failed
-- Deleting files...
E:failed to mount /dbdata (File Exists)
E:copy_dbdata_media: Can't mount /dbdata your storage not prepared yet. please use UI menu for format and reboot actions.
-- Updating filesystem..
E:failed to mount /dbdata (File Exists)
E:discard_filesystem_for_rfs:Can't mount /dbdata
-- Wiping cache...
Formating cache...
Cache wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ITV/system/'.
Successfully applied multi-CSC.
I tried flashing again stock rom, but not helped, it is only one PDA file.
Please Please let me know solution, So that i can atlast start phone with STock GB.
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
http://snappybytes.blogspot.in/2012/04/how-to-fix-cant-mount-dbdata-error-sgs.html
Should i use this trick? and for flashing stock rom again, what i need? repartition tick?
stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
Thanks it worked. But I did not understand problem. Why this happened. Did I miss any step or used wrong files?
Sent from my GT-N7000 using xda app-developers app
jeet.chaudhari said:
Thanks it worked. But I did not understand problem. Why this happened. Did I miss any step or used wrong files?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I don't know the exact settings you used, but I assume the following:
ICS ROMs have different partition layouts than GB ROMs. Therefore the initial flash of the ICS failed, as it probably needs a reboot after changing the partition layout. If you had flashed it again, it should have worked.
But what I'm pretty shure about is, that flashing ICS the first time, changed the partition layout. As a result you probably had to check "repartition" when flashing stock GB with Odin. But when you check "repartition" in Odin, the ROM you are flashing needs all ROM parts (including dbdata.rfs), because all partitions of the internal flash of the phone are cleared after repartition. If a part is missing, it can't mount the related partition, because the partition is still unintialized.
If you flash a GB ROM with missing parts and "repartition" unchecked over an already working GB ROM, Odin will only flash the parts of the ROM that are present and leave the rest untouched. Thats how flashing only a kernel works, it just flashes the kernel to the kernel partition and leaves the rest of the ROM untouched. Also thats how the fix you posted works. The dbdata.rfs.tar only contains dbdata.rfs, flashing it with "repartition" unchecked only overwrites the dbdata partition and leaving the rest (which you flashed earlier with the PDA file) untouched.
stbenz said:
I don't know the exact settings you used, but I assume the following:
ICS ROMs have different partition layouts than GB ROMs. Therefore the initial flash of the ICS failed, as it probably needs a reboot after changing the partition layout. If you had flashed it again, it should have worked.
But what I'm pretty shure about is, that flashing ICS the first time, changed the partition layout. As a result you probably had to check "repartition" when flashing stock GB with Odin. But when you check "repartition" in Odin, the ROM you are flashing needs all ROM parts (including dbdata.rfs), because all partitions of the internal flash of the phone are cleared after repartition. If a part is missing, it can't mount the related partition, because the partition is still unintialized.
If you flash a GB ROM with missing parts and "repartition" unchecked over an already working GB ROM, Odin will only flash the parts of the ROM that are present and leave the rest untouched. Thats how flashing only a kernel works, it just flashes the kernel to the kernel partition and leaves the rest of the ROM untouched. Also thats how the fix you posted works. The dbdata.rfs.tar only contains dbdata.rfs, flashing it with "repartition" unchecked only overwrites the dbdata partition and leaving the rest (which you flashed earlier with the PDA file) untouched.
Click to expand...
Click to collapse
Yes. I assume its all right but I didn't tried ICS. I was jumping from stock GB to JB ROM. So what you will now suggest me to flash JB PA ROM on currently working stock GB ROM?
Sent from my GT-N7000 using xda app-developers app
The things I wrote about ICS also apply to JB.
I don't know, how to install JB PA, but the install instructions should be in the thread where you got the ROM from. If flashing fails, you should ask there, as it may be a known problem and the people there would probably be more of a help than me, as I never flashed JB PA.
2.3.6GB fw.root after installation, the kernel semaphore cwm, then save the sd.kartu,, clearing the ultimate script for kernel instal script, factory data reset wipe, wipe Dalvik cache and rom and installed the ICS sd.karty.
it is better to have clean sd.kartu before the flash rom ICS or JB.
stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
Thanks, this worked for me. I downloaded the latest firmware and that set my phone straight.
Galaxy TAB GT-P1000L - Solved
I was facing the same issue with my Galaxy TAB GT-P1000L, where it was on loop in the Samsung Logo screen. Please note that after flashing the dbdata, you must flash the Stock ROM again
Hello everyone.
I have a problem which I hope you'll be willing and able to help with.
I wanted to try out CyanogenMod 10 on my Galaxy S I9000. I was on 2.3.3 so I used Odin to update to 2.3.6 (rooted). Then I installed superuser and mod manager, after which I installed Clockwork. I then used Clockwork to install CM 10. It worked flawlessly and this was my first time flashing ever.
However, I didn;t like CM 10 and decided to revert back to Gingerbread. I read it was as easy as simply using Odin to flash 2.3.6 again. I tried that but got stuck into a bootloop displaying the S sign over and over and over again. I tried downloading the PIT file which made Odin check Repartition by default and flashing like that but it didn't help, I'm still stuck in bootloop. I can access download mode without a problem but I'm stuck in bootloop forever.
Any help would be greatly appreciated. Thank you in advance.
Update: I found a thread detailing how to get back to Froyo so I tried it. I used a PIT file, PDA file, PHONE file and CSC file all separately and it worked. Now I'll just have to update back to 2.3.6 No idea why I was only able to revert back to Froyo and not Gingerbread, but it worked, thread can be closed.
Hey,
Bit of a late answer, but so you can refer to it if you ever go back to custom roms.
When you come back to stock from CM10, or any custom rom for that matter, you need to flash in a file named dbsdata.rfs.tar. Fixes the bootloops (custom roms and stock have different data partitions so incompatibilities in data partition cause bootloops like yours)
Sent from my GT-I9000 using xda premium