[Q] SGS i9000 Operating System Problem - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!

jesper10 said:
Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!
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. maybe this will help.

jesper10 said:
Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!
Click to expand...
Click to collapse
1. Just do a 'wipe data/factory reset' and reboot the device when done.
2. Let the device boot all the way then turn it off.
3. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition...

Hi guys!
Thank you for the replies and taking the time to help...my biggest problem is getting the computer to recognise the phone, I think when I flashed whatever it was before I've somehow "deleted" the O/S on the phone and now no mater what PC I plug it into the phone never gets recognised...and that means I can't use odin
If I can get that bit fixed, then I think I can recover the phone but just don't know how to fix that...odin was working perfectly before so I know it does, just need the PC to find the phone now!
Any thoughts? I've tried re-downloading Kies/drivers etc but to no avail.

But you can enter Download Mode?

That's probably has something to do with the fact that you have a I9000M, which is the Canada Bell version of the I9000. There are some subtle hardware differences between the two. Honestly, **** Samsung and their variants. It's a pain in the *** trying to remember if the difference still matters any more. When the I9000M first came out we encountered a whole load of issues with people frying their memories and having to send it back to Samsung for replacement. I think someone eventually came up with a way to overcome this, but I didn't read much about it.
Anyway, try getting a stock I9000M rom instead and flash that. As for your PC not recognising it, you did reboot between uninstalling and reinstalling the Samsung drivers right? Also, kies must NOT be running in the background when you use odin, otherwise odin will not recognise your phone.

KUN1 said:
But you can enter Download Mode?
Click to expand...
Click to collapse
Yeah, I can get into download mode but nothing happens from there...because the laptops/PC won't recognise the phone I can't transfer anything on to it!
I've tried installing a rom from SD card but it fails :crying:
Any thoughts?

snapper.fishes said:
That's probably has something to do with the fact that you have a I9000M, which is the Canada Bell version of the I9000. There are some subtle hardware differences between the two. Honestly, **** Samsung and their variants. It's a pain in the *** trying to remember if the difference still matters any more. When the I9000M first came out we encountered a whole load of issues with people frying their memories and having to send it back to Samsung for replacement. I think someone eventually came up with a way to overcome this, but I didn't read much about it.
Anyway, try getting a stock I9000M rom instead and flash that. As for your PC not recognising it, you did reboot between uninstalling and reinstalling the Samsung drivers right? Also, kies must NOT be running in the background when you use odin, otherwise odin will not recognise your phone.
Click to expand...
Click to collapse
Yeah, I read about that actually - I should maybe have paid more attention when I was looking into this in the first place!
Thanks for your reply man, I'm going to try getting stock I9000M rom tonight and have a go with that! But yeah, 3 different PCs/laptops I've tried it on, with variations of with/without Kies...still no joy as yet!
Thanks again for the reply though :good:

Related

[Q]Random bricking strikes again!

About 4 weeks ago I installed JPH on my Bell i9000 with a lag fix. It randomly froze while I was looking at it, I wasnt even interacting with it. Pulled the battery, booted passed the Galaxy S screen but stuck on black. Recovery had nothing to say, so I re-flashed a firmware on it, and then recovery would say: E: can't mount /dev/block/mmcblk0p1. I imagine this is due to the Lagfix changing the filesystem format, and then flashing a stock RFS rom ontop, but I had absolutely no choice. After a couple days of trying to fix it, I surrendered and sent it off to Bell for repair. Got it back almost 2 weeks later, they had to replace the board.
Now flash-forward to right now.
THE SAME GOD DAMN THING HAPPENED (except this time I almost flung myself off my balcony).
Substitute JPH with JPM. Rinse & Repeat.
I haven't sent it off to Bell yet...again..But I have a feeling I will have too.
Question 1: Any clue as to why these lag-fixed 2.2 builds randomly froze and were rendered unable to boot?
Question 2: I see these "unable to mount" threads popping up but with no success stories. Is there any way to fix this on my own? I remember searching up an article with a dude explaining how to format partitions by pushing tools to the phone via ADB but I never was able to get 'er done.
Thanks for reading my tragic novel
...urge to kill...RISING...
i have had absolutely no luck with the froyo roms on my bell sgs. first time (jpk) around i got the can't mount error (device busy), but somehow fluked saving it by just reflashing back to eclair. second time (jpm) i got massive data corruption (file names "*^@)#$") and eventually lost all my data and had to reflash back to eclair.
i'm not too sure what's going on, but i suspect the international/european froyo's are incompatible with the bell sgs. from what i've read, the captivate users are running the jh2 firmware (same as us?) so i might try again with tayutama's captivate firmware.
to answer your question though, i believe there is hope if it just says "device busy" and not "device not found". keep trying to reflash if it's "device busy" and use jh2. seemed to work for me and my buddy's phone.
wang1chung said:
i have had absolutely no luck with the froyo roms on my bell sgs. first time (jpk) around i got the can't mount error (device busy), but somehow fluked saving it by just reflashing back to eclair. second time (jpm) i got massive data corruption (file names "*^@)#$") and eventually lost all my data and had to reflash back to eclair.
i'm not too sure what's going on, but i suspect the international/european froyo's are incompatible with the bell sgs. from what i've read, the captivate users are running the jh2 firmware (same as us?) so i might try again with tayutama's captivate firmware.
to answer your question though, i believe there is hope if it just says "device busy" and not "device not found". keep trying to reflash if it's "device busy" and use jh2. seemed to work for me and my buddy's phone.
Click to expand...
Click to collapse
Thanks for the info!
Ya...adb says device not found....Deja vu..
Adb does see it while in Recovery though.
well, while searching, i have found people saying not to flash any captivate roms as the bell sgs is closer to the international version than the US captive version.
might have to wait for a bell specific firmware then since i know the international ones don't work well.
Jordiharrison said:
Question 1: Any clue as to why these lag-fixed 2.2 builds randomly froze and were rendered unable to boot?
Click to expand...
Click to collapse
It Happened to me and I had no lagfix installed. The phone was not even rooted.
Jordiharrison said:
Question 2: I see these "unable to mount" threads popping up but with no success stories. Is there any way to fix this on my own? I remember searching up an article with a dude explaining how to format partitions by pushing tools to the phone via ADB but I never was able to get 'er done.
Thanks for reading my tragic novel
...urge to kill...RISING...
Click to expand...
Click to collapse
It happened to me twice. The first time was about two weeks of getting it (not rooted, no lag fix). Bell just replaced it with a brand new one.
It happened again about two or three weeks later (no lag fix). Knowing my way around linux & embedded systems, I could confirm that the kernel was not able to mount the partitions on the internal flash (mmcblk0) and they even seemed to have disappeared. I was getting the same message "E: can't mount /dev/block/mmcblk0p1". I think it's a more fundamental issue and that the internal SDcard gets permanently corrupted.
They sent the second one for repair and after three weeks of pain & frustration with the Blackberry Bold they lent me, they sent me a replacement (probably refurbished!).
Sorry, but I think you will have to send it back!

[Q] E:Can't mount /dev/block/st110 ... my nightmare begin!

Hi! Here is the story of my nightmare... I have a Bell i9000m with Android 2.1. I have use GST tweaker tools to root it. I also have do a backup with titanium backup (but I think it useless at this step) After this I have try to change the battery icon with the same utility. When I have rebooted the phone, it stop at the "S" logo for a minute and after the screen go black and the button are glowing and the phone buzz. After this nothing happen. When I go in recovery mode (3e) I obtain an error:
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions,
copy default media content failed.
I have try with odin3 1.7 to flash the phone but I'm a little bit confused with all possibility...
One stupid thing I have to say, I don't know my original firmware version... ;-(
I have see many good custom kernel... it is possible to fix this and by the way to upgrade to froyo?
It is possible to fix my problem doc?
Thanks a lot for your help!
P.S. Sorry for my bad english, (i'm from Quebec,Canada)
Easiest fix :
Go in recovery and wipe.
Then restart and see if that fixed your problem.
Alternate (Guaranteed solution) :
Go here
Click "Direct Download". If you don't see it try to refresh the page.
Fire up odin.
Extract the zip u downloaded
For pda in odin select the .tar you extracted
Put your phone in download mode.
Flash w/o repartition or nething.
That should work.
Hi! I have try the 2 solutions you mention. But always same problem... I have to mention I have installed speedmod-kernel-k12p-500hz it is correct or I have to replace it?
Ok then do this :
Get these two
Flash odin with repartition and select the pda,modem,csc
Once done
Go back to odin. Flash just pda with no repartition or nething of the jl2 (previous thing u downloaded in my first post).
Sorry for this question but what do you mean by nething? (sorry english is not my first language!)
So leave everything the way it is.
Dont check mark anything extra.
YEAH! You solved my problem!!! You rock man!
Before I do any other stupid thing any advice?
I have visit some european site about android. They offer some firmware.. it is better to keep the "bell" specific firmware?,etc...
I don't know if I already say this ... Thanks you!
Try them.
Now u know
exactly how to restore if nething ever happens
thenamelessthing said:
YEAH! You solved my problem!!! You rock man!
Before I do any other stupid thing any advice?
I have visit some european site about android. They offer some firmware.. it is better to keep the "bell" specific firmware?,etc...
I don't know if I already say this ... Thanks you!
Click to expand...
Click to collapse
Glad to hear you got your problems sorted. Maybe you could hit the "Thanks" button under Daneshm's post.
Daneshm90 said:
So leave everything the way it is.
Dont check mark anything extra.
Click to expand...
Click to collapse
Thank you! You indirectly helped me immensely!
thenamelessthing said:
Hi! Here is the story of my nightmare... I have a Bell i9000m with Android 2.1. I have use GST tweaker tools to root it. I also have do a backup with titanium backup (but I think it useless at this step) After this I have try to change the battery icon with the same utility. When I have rebooted the phone, it stop at the "S" logo for a minute and after the screen go black and the button are glowing and the phone buzz. After this nothing happen. When I go in recovery mode (3e) I obtain an error:
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions,
copy default media content failed.
I have try with odin3 1.7 to flash the phone but I'm a little bit confused with all possibility...
One stupid thing I have to say, I don't know my original firmware version... ;-(
I have see many good custom kernel... it is possible to fix this and by the way to upgrade to froyo?
It is possible to fix my problem doc?
Thanks a lot for your help!
P.S. Sorry for my bad english, (i'm from Quebec,Canada)
Click to expand...
Click to collapse
this problem accure bcs of
1.you didnt remove bettry b4 flashing rom
2.some stoke filmware give you error message but if you flash with 521+pda+csc+modem file then tht problem is solve
and i found that I9000XWJM5 filmware is really good if somebody need it then pm me i all send zip file
Can anyone tell me how do bring back to life my phone??? I used this on my Vibrant and now my phone is DEAD!!! IT WON'T TURN ON AT ALL
ANY IDEAS??? PLEASE HELP!!! I KNOW I MADE A MISTAKE... ANYONE PLEASE
mobileoneexpress said:
Can anyone tell me how do bring back to life my phone??? I used this on my Vibrant and now my phone is DEAD!!! IT WON'T TURN ON AT ALL
ANY IDEAS??? PLEASE HELP!!! I KNOW I MADE A MISTAKE... ANYONE PLEASE
Click to expand...
Click to collapse
do u have download mode??
if not buy a JIG or send back to samsung
HELPPPP
azzledazzle said:
do u have download mode??
if not buy a JIG or send back to samsung
Click to expand...
Click to collapse
hi guys, i've follow this guide but my phone it's blocked from 15 minutes... any help please?
Daneshm90 said:
Ok then do this :
Get these two
Flash odin with repartition and select the pda,modem,csc
Once done
Go back to odin. Flash just pda with no repartition or nething of the jl2 (previous thing u downloaded in my first post).
Click to expand...
Click to collapse
.. ok. call me a n00b or w/e u want, but i understood everything up until that last part. when u go back to odin.
It would help if you can describe the set-up, because clearly i did something wrong... screenshots would help if possible /:
p.s. i have all the files downloaded from ur previous posts... i just need to know the order. also for the second download file, which file is the PDA file? the one with the word "CODE" in it? or i dont even apply that one .. ;;;
Hello, i've been having the same problem with my GT-i9003, and even after flashing with odin i still have the same problem. Well, it's not exactly the same, cause my phone will keep on a starting bucle if i try to start it without my EXTERNAL sd card (the one i bought), and if i start it with the external card in, it starts, but i can't use anything that uses the sd card (music, camera, 3g), so yes i can call and message and use wifi, but that's not how it's ment to be. Basically it's like i had no external or internal cards.
So everythime i try to flash without the external sd card, i get the mounting error, and if i flash with the external card, it seems ok , but i still can't use any of the things mentioned above.
I'm a bit lost, and i believe it's because i'm missing something (i'm new to this). i don't want to send it to samsung (yet)
i've been using the firmware that came with the phone, didn't try anything new.
to sum up: any attempts to flash with/without the external card are irrelevant, the problem persists.
Any thoughts/ideas/solutions?
thanks in advance.

[Q] Galaxy Tab Memory Problem

I've got a problem with my Galaxy tab. The problems are:
1. Whenever the device is turned off all the files are deleted - like a factory reset.
2. The language always reverts back to Chinese or something like that when turned off and on - I always need to change it back to English.
2. Recorded videos show unsupported file format when attempting to playback.
3. Doesn't charge using the wall charger when it is on but when it is off it's ok.
I've tried some TS like:
1. Factory Reset / Wipe Cache and anything I could see at Recovery.
2. Reflash Gingerbread
3. Tried downgrade to 2.2 - I haven't succeeded yet since I need some files to DL.
If anyone has an idea on how to solve it or encountered the problem pls share some thought.
The main problem I'm really frustrated is regarding the memory problem whereas I can't save any files nor store anything on the 16GB internal memory.
BTW, I'm running on 2.3.3 GB
BB: P1000DXJPD
Thank You.
this is wired ... can u tell us what is your Tab old firmware ?
and did you tried to back into froyo and back again to flash the gingerbread ?
k0sh said:
this is wired ... can u tell us what is your Tab old firmware ?
and did you tried to back into froyo and back again to flash the gingerbread ?
Click to expand...
Click to collapse
I can't really say what's the old firmware since my mom just gave it to me.
I'll be trying to flash it back to froyo later though I'm still trying to figure out what Firmware I should download since the last time I tried it, the tab only goes to a constant boot loop.
I can't really figure out what's the problem with this tab. It seems like it's using deepfreeze (PC App) Since, the prior files saved are still present even after turning it off. I even tried deleting those files but to no avail after reboot it returns.
So, I'll try flashing froyo and let's see.
Thanks.
what is your tab ? GSM , CDMA ?
k0sh said:
what is your tab ? GSM , CDMA ?
Click to expand...
Click to collapse
It's GSM, I've managed to flashed 2.2 now and the charging issue seems to be solved, could charge it now using the wall charger and via usb.
But the memory problem is still the same.
Let me expand on it a little more.
The internal memory which is 12.82 GB (12.80 Avail) and Internal Device Storage (1.85 GB) seems to be detected by the TAB, the problem is whenever I save a file or anything on it after reboot it's gone but some files (Pics) even though I delete it after reboot it comes back. It seems like the memory is froze or something.
Thanks.
craphack said:
It's GSM, I've managed to flashed 2.2 now and the charging issue seems to be solved, could charge it now using the wall charger and via usb.
But the memory problem is still the same.
Let me expand on it a little more.
The internal memory which is 12.82 GB (12.80 Avail) and Internal Device Storage (1.85 GB) seems to be detected by the TAB, the problem is whenever I save a file or anything on it after reboot it's gone but some files (Pics) even though I delete it after reboot it comes back. It seems like the memory is froze or something.
Thanks.
Click to expand...
Click to collapse
Did u use pit when u flashed the rom¿
Can u reflash and use pit and after that go to recovery and wipe data and factory reset and check whether it works or no . If not this is totally a freak and wirdo thing lol
Sent From Hell To Take Your Soul
k0sh said:
Did u use pit when u flashed the rom¿
Can u reflash and use pit and after that go to recovery and wipe data and factory reset and check whether it works or no . If not this is totally a freak and wirdo thing lol
Sent From Hell To Take Your Soul
Click to expand...
Click to collapse
Yes I've used a PIT file. I've successfully flashed it now with the ROM on this thread http://forum.xda-developers.com/showthread.php?t=939360.
Still the same so it seems like this is most probably a hardware problem.
I've noticed that when I connect the Tab to my pc as a media storage, I could see the files on the internal memory. I've tried deleting it manually and quick format it. But after disconnecting it the same files returns.
I'm now trying to format it the long way, not the quick format.
I have the EXACT same problem with my Galaxy Tab 7 inch Sprint. My internal memory boots up as read only and resets itself every time I boot the device.
I've been looking for days to figure out what I can do solve this but it really doens't seem promising.
I was able to make the internal memory read writable through adb shell with:
mount -o remount, rw /
The problem is, when I reboot. All the changes are gone. If anybody has a clue please post here or PM me. Thanks!
jrhsu529 said:
I have the EXACT same problem with my Galaxy Tab 7 inch Sprint. My internal memory boots up as read only and resets itself every time I boot the device.
I've been looking for days to figure out what I can do solve this but it really doens't seem promising.
I was able to make the internal memory read writable through adb shell with:
mount -o remount, rw /
The problem is, when I reboot. All the changes are gone. If anybody has a clue please post here or PM me. Thanks!
Click to expand...
Click to collapse
i didn't even root mine and i am having the same issue with a Verizon Galaxy Tab (CDMA)
u can try by flashing different firmware..i means if now u r using jqx1..try flash another that
Sent from my GT-P1000 using xda premium

[Q] Problem flashing back to stock rom

I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
everett1911 said:
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
Click to expand...
Click to collapse
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
prbassplayer said:
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
Click to expand...
Click to collapse
last time I had bothered to update cyanogen, it was a week ago. I don't remember the exact nightly build. The other roms I tried were miui, apex and something else that wouldn't boot and which I deleted quickly (apex wouldn't boot either but I spent a couple hours trying to make it work). I wiped everything prior to flashing.
as for the stock rom, it's a stock rom for the SGH-I896 (I896UXJI2), my phone model. before, the stock rom worked fine. I just can't figure out why it's suddenly not working now.
anyone? I really want to put the stock rom back into my phone.
Are you using a PIT file when flashing? If not try using this one with that package then report back.
I've already did that with odin.
and just out of curiousity, what are pit files for?
everett1911 said:
I've already did that with odin.
and just out of curiousity, what are pit files for?
Click to expand...
Click to collapse
I dont know what it exacly does BUT I know if you want to repartition your phone and you are on a AOSP like CM7 or MIUI you need a pit.
P.i.t.
Partitioning
Information
Table
Lol makes sense now
Sent from my SAMSUNG-SGH-I897 using xda premium
studacris said:
P.i.t.
Partitioning
Information
Table
Click to expand...
Click to collapse
*windows user* so it's a bit like a batch fdisk?
if so, is the internal sd card itself supposed to be wiped clean? because it didn't happen when I used mine.
Ok so using the PIT file didn't work for you. I've seen several Samsung devices suffer from a problematic internal OneNAND in the past but never one a Captivate. It's always been a TAB, i9000 or Vibrant. Can you try flashing the base files used in the Serendipity ROM? It's the stock Gingerbread installed before flashing the Serendipity ROM itself. You can find them in that thread. It will help distinguish whether you have an actual issue or whether you just need some in depth CSC scripts to help clean it up. In general that ROM has a very nicely built CSC cleanup script that is able to correct what I call "partition bricking" on the Captivate, i9000 and Vibrant. Give it a shot and report back...
Also, if that won't work, I have been able to correct this via JTAG. PM me if it comes to that. If JTAG won't correct it, then it is indeed a case of a partially dead OneNAND. It's rare but does happen.
I'll give that CSC script thing a try. What's JTAG, by the way?
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
anyone, please?
everett1911 said:
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
Click to expand...
Click to collapse
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
For2ndtwin said:
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
Click to expand...
Click to collapse
thanks but I think it's too late. while trying to flash serendipity two days ago, I used the odin flasher that site linked to, and it flashed my phone with at&t's firmware, which somehow completely ruined my phone. now, the phone won't boot, and I can't enter download mode at all. I'm not sure even a usb jig would help, and right now I don't have money for that, so I'll have to wait till I do.
And if this doesn't work, then what? All the phone does is show a spinning little circle, immobile for 3 seconds, and the phone turns off. when I insert the battery (after pulling it out), the phone automatically starts with the same screen, same result. if I plug in the usb cable, it shows the charging battery indicator, freezes, and reboots. This repeats over and over, with no end at all, and since I can't enter download mode in any way so far, I can't do anything about that. It's so bad that not even windows detect my phone, and I've plugged it into two separate computers, so I know it's not just my pc pulling a trick on me.
The worst part is that since I was using wifi tether on my phone (hello, pdanet), now I'm without any internet (right now I'm typing this on my little sister's laptop, from my dad's place.)
So... yeah.
By the way, the heimdall link is for i897 phones, even in the post for i896 phones. Is there any risks my phone will react as badly as it did with the at&t firmware?
^ I've read good things about Heimdall. Btw, if ur phone has any signs of life, then a Jig should get u back into download mode.
The fact that it was at&t firmware has nothing to do with it. Running I897 firmware on an I896 is fine. **** you can run I9000 firmware...
so many days after, I still can't get it into download mode at all. all it shows is a spinning circle, a spinning circle and then the charging battery image for a second when the usb cable is plugged in, and the AT&T world logo when the battery is low.
I could go for a solderless usb jig but even then I don't have cash for that right now (next week.), so until then I'm screwed.
I tried everything minus the usb jig, looked for many threads on the topic, and nothing works. nothing.
no matter how many times I do the battery trick or the three finger salute or the odin stuff, and it still doesn't work.
so... yeah. that usb jig better damn work.
I'll call it magic
First, I'd like to thank 4-2ndtwin for providing a complete stock rogers rom.
Second: how does a usb jig work, really? my thing's computers, software and hardware in general but not to the point of knowing how capacitors, resistors and all that stuff works, so for me the usb jig bringing back my phone from firmware limbo... that's magic. seriously.

[Q] Error Rooting SM-G730A

Hello Everyone,
I have been trying to root my Samsung Galaxy S III SM-G730A AT&T Android JB 4.22 and keeps failing. Can't write files. I have use odin and at least 3 different files and always get the same error that it fails due to write protection error. I have did a hard reset and when I try to delete the cache partition that fails as well. I have looked and find noting to lead me in the direction as to what is wrong. Can someone please shed some lite on this for me. Here is a list of files I have tried so far.
SuperUser.zip
CF-Root-SGS3-v6.3.zip
Odin3-v1.87.zip
gapps-kk-20140105-signed.zip
cm-11.0.0-tass-13042014.zip
As you can see I have bee busy. I am a computer technician and have unzipped and ran all files as I'm supposed too but nothing is working. The protected mode and failed mode is kicking my tail. Any input will be greatly appreciated...
Charles
texasgoldbuyer said:
Hello Everyone,
I have been trying to root my Samsung Galaxy S III SM-G730A AT&T Android JB 4.22 and keeps failing. Can't write files. I have use odin and at least 3 different files and always get the same error that it fails due to write protection error. I have did a hard reset and when I try to delete the cache partition that fails as well. I have looked and find noting to lead me in the direction as to what is wrong. Can someone please shed some lite on this for me. Here is a list of files I have tried so far.
SuperUser.zip
CF-Root-SGS3-v6.3.zip
Odin3-v1.87.zip
gapps-kk-20140105-signed.zip
cm-11.0.0-tass-13042014.zip
As you can see I have bee busy. I am a computer technician and have unzipped and ran all files as I'm supposed too but nothing is working. The protected mode and failed mode is kicking my tail. Any input will be greatly appreciated...
Charles
Click to expand...
Click to collapse
Hi. SM-G730 got a locked bootloader and won't be able to flash anything with odin except from official signed firmware untill someone find a way to unlock it.
You'll find root for it here
"Safe" method in post #125 http://forum.xda-developers.com/showpost.php?p=52699213&postcount=125

Categories

Resources