Related
When i boot into recovery mode an error shows up on the screen. The following is what happens.
Applying Multi-CSC
Installing Multi-CSC
mps_dat value: OPS
Copy_multi_carrier from: OPS
Multi csc: can not access to /system/csc/OPS/system
Copy_common_data
The bit in red is the error. This only shows up when booting into recovery mode. The phone works normally excpet i'm having huge battery performance issue at the moment.
I flash to JM5 over the weekend and had a fair bit of trouble getting it to work. I had to try a few times before it actually worked.
Also (as i mentioned in another thread) When doing *#1234# i get this
PDA:
PHONE I9000DTJD3
CSC:
So PDA and CSC show no value next to them.
Is the error in recovery mode a problem? Could it be linked to my poor battery performance at the moment?
Thanks
Have you flashed the phone with multi-pack firmware (separate files for PDA, MODEM, CSC) and not selected any CSC?
Richthofen said:
Have you flashed the phone with multi-pack firmware (separate files for PDA, MODEM, CSC) and not selected any CSC?
Click to expand...
Click to collapse
Yeah. When i flashe to JM5 i only used the first option in Odin (PDA)
I did try a few times with all three files but it wouldn't work.
So should I try to reflash again with all the MODEM and CSC files?
bump.......!
Im getting this error, too.
But I get:
PDA: I9000XWJM5
PHONE: I9000XXJM3
CSC: I9000SERJM1
Does anyone think that the fact that i only did the PDA file when flashing to JM5, that this could be the cause of the horrible battery life i have been getting since flashing? I loose 10% an hour when push email is enabled, even if i don't touch the phone for the entire hour.
And yes i have seen the thread about resetting the battery statistics.... no difference... something is just weird with my 3G i think.
Hi guys,
A few days ago I made the silly mistake of trying a new rom without first disabling the lagfix. I didn't realise what the problem was straight away so I tried factory reset and wiping cache and dalvik with no luck. I booted to 2e recovery to do the wipes.
I have since been trying to flash a new rom with Odin but am constantly getting stuck on cache.rfs. I have been reading through posts for days and tried every fix I could find with no luck. All ports, different computers, different OS but no luck!
I don't know a lot about flashing or Android so I'm wondering if I'm doing it wrong, or maybe I have the wrong files or something.
PIT: s1_odin_20100512.pit
PDA: CODE_I9000XWJM9.tar.md5
PHONE: MODEM_I9000XXJM4.tar.md5
CSC: CSC_I9000XSAJP4.tar = Australian unbranded CSC
http://forum.xda-developers.com/showthread.php?t=856072
I have been doing some reading on the CSC and I'm wondering if it is incompatible or something which might not be letting it load. I don't know the original CSC major version because I didn't check before I broke my phone.
Is it possible that I am using the wrong major version or something?
I've been 4 days now without my galaxy and I'm starting to get desperate.
Can anyone confirm that I'm doing the flashing right/wrong? Maybe offer a suggestion on something else to try?
thanks guys
Edit: I'm running XP on my laptop, but I have a win 7 pc too
Booting into recovery reads:
E:Can't mount /dev/block/stl11
(invalid argument)
]update media, please wait...
update media, finished
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Milti-CSC
mps_dat value:XEE
copy_multi_carrier from: XEE
multicsc : can not acces to /system/csc/XEE/system
copy_common_data E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
klimovski said:
Hi guys,
A few days ago I made the silly mistake of trying a new rom without first disabling the lagfix. I didn't realise what the problem was straight away so I tried factory reset and wiping cache and dalvik with no luck.
I have since been trying to flash a new rom with Odin but am constantly getting stuck on cache.rfs. I have been reading through posts for days and tried every fix I could find with no luck. All ports, different computers, different OS but no luck!
I don't know a lot about flashing or Android so I'm wondering if I'm doing it wrong, or maybe I have the wrong files or something.
The firmware I am trying to flash is JM9 from Samfirmware.com and the CSC file is the Australian unbranded CSC available here http://forum.xda-developers.com/showthread.php?t=856072
I have been doing some reading on the CSC and I'm wondering if it is incompatible or something which might not be letting it load. I don't know the original CSC major version because I didn't check before I broke my phone.
Is it possible that I am using the wrong major version or something?
I've been 4 days now without my galaxy and I'm starting to get desperate.
Can anyone confirm that I'm doing the flashing right/wrong? Maybe offer a suggestion on something else to try?
thanks guys
Click to expand...
Click to collapse
I know this might be a no brainer, but back when I wasn't as clued up about flashing as I am now. I too kept getting stuck at this while using Odin when I forgot to disable lag fix. After googling I managed to find a solution to my problem and it was very simple yet effective. All I had to do was set odin to run as Windows XP in compatibility mode and run as admin. I never thought it would work but it did, maybe it will work for you...
Hope you get this sorted mate.
PaulForde: Can you confirm that I am flashing the right way? Do you think it's possible I have the wrong CSC file?
WTF!?!?!?! I tried get into the error message screen again and the phone booted up this time... and it works!!!!!!!
Model Number: GT-I9000
Firmware version: 2.1 update 1
Baseband: I9000XXJM4
Kernel version: [email protected] #2
Build number: ECLAIR.XWJM8
What does this mean? Did the Odin flash actually work???????????????
Just checked the internal sd card and all the files are still there. Can anyone shed some light on what has happened?
Are you cheking the "Re-Partition" option when flashing with Odin? I think this option should solve the problem when you forget to disable lagfixes...
Yes I have checked this box but because Odin never gets passed cache.rfs it has never actually finished the process. I have had to pull the battery every time.
What does this mean for my file system? would it still be formatted as ext4 or rfs?
Originally when I installed the custom rom without disabling the lag fix I had tried to apply the lag fix on top of what was already there and this is when all the problems started.
I just tried to flash a different firmware and can confirm that it is changing, yet it is still hanging up at cache.rfs.
Can anyone confirm what will happen if I check the repartition box without having a CSC file? I don't want to make this any worse...
Hey, I'm having the exact problem as you and yes I forgot to disable lagfix But oding is not helping me at all. When I try flashing my phone it actually goes all the way to the green "pass" but after when it reboots I get the error about the sd card not mounting. Any help?
My phone is finally working again but it's probably not 100%
The reason Odin would hang at cache.rfs for me was the CSC file I was using. I googled the errors I was getting on startup of my SGS (shown above) and they turned out to be minor. Simply hitting 'reboot' got my phone to start up! But there were a few problems once it was up like not being able to download apps from the market.
When my phone started up I did the *#1234# and found my CSC to be XEE so I downloaded that and tried to flash with it using Odin and it worked However it wouldn't do the repartition which was annoying.
I'm not game to try and reapply a lagfix and see if my system is back to normal since it all seems to be working now
i'm having the same problem odin is flashin fine getting all the way to complete but when it reboots the phone it gets stuck saying cant mount dev.....blah same as the rest. if i pull the battery and try rebooting i get past the s screen but just stops at a black screen and vibrates every now and then. help me
This one sounds a bit different to my problem. Odin wouldn't flash in my case, which was the problem
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3
I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?
A friend of mine has the same issue on his SGS. Both recovery and download mode working.
Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.
gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks
thanks for the help i love you no homo !
Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks
This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?
Like many I installed the leaked version of Gingerbread on my Galaxy S when it first came out, but now Samsung have finally released Gingerbread in the UK, I would like to install the official release. But need to reinstall the official version of Froyo in order to do this via Kies.
I have had to spend quite a large amount of time looking for the process of doing this, as there seems to be conflicting information/methods out there. Also I understand Gingerbread has a new boot loader (the installed the version including the secondary boot loader) which also needs taking back to original, and I have also found that most of the guides out there always seem to leave a few questions unanswered
So after finding what appears to be the best and I believe the safest method, I thought I would post it on here for others.
Before I go into the steps on how i did this, I need to make a few points:
1) Any firmware installation carries risks. This is not approved by Samsung, and you do it entirely at your own risk....i’m no expert, I simply found a method that works for me. So if it all goes wrong, don’t come crying to me (however, after trying a different method previously, my phone would not boot, but I was able to re-flash with the leaked Gingerbread successfully).
2) Do not try this procedure if you are unable to get your Galaxy S into Recovery mode (Vol Up + Home + Power) and Download mode (Vol Down + Home + Power). A number of these phones have this issue, mine was one of them, there are guides online to fix this issue.
3) There seems to be a number of people who have issues with upgrades on Kies even when they haven’t messed with the firmware, so even if you cannot upgrade thru Kies, it doesn’t mean there has been a problem with Flashing the phone.
4) Backup your phone before flashing, as the phone will be wiped.
5) As far as I understand, this is only for the I9000 model and not for any of the other variants of this phone out there.
6) NEVER try to flash the phone without putting it into Download mode first, you will brick your phone.
------------------------------------------
First of all you will need a Windows PC, USB Cable, 2 Downloads (below)....oh and ideally a Samsung Galaxy S
Download 1 (JPU)
http://hotfile.com/dl/99955459/dea6962/I9000XXJPU.rar.html
Password: samfirmware.com
Contents when extracted:
GT-I9000-CSC-MULTI-OXAJPU.tar.md5
I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
MODEM_I9000XXJPU.tar.md5
s1_odin_20100512.pit
Odin3v1.3
Download 2 (JPY)
http://www.megaupload.com/?d=EWTHLRU6
No Password
Contents when extracted:
JPY_JPY_JPY.tar
The idea is to flash with XXJPU first to get the base version of Froyo which includes the SBL, then to Flash with JPY, this will allow you to use Kies for firmware updates (ensure Kies is completely closed before starting this).
1. Download and extract the above files.
2. Power off phone, remove sim and memory card, then start up in Download Mode and plug USB cable into phone (not PC).
3. Open Odin and select the following Files:
PIT: s1_odin_20100512.pit
PDA: I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
PHONE: MODEM_I9000XXJPU.tar.md5
CSC: GT-I9000-CSC-MULTI-OXAJPU.tar.md5
Ensure the following options are ticked: Re-Partition, Auto Reboot & F.Reset Time
4. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
***Under no circumstances unplug the usb cable, press any buttons on the phone or generally do anything that could interrupt the process, until it has complete and the phone is full restarted***
Once this is complete, you are ready to flash the phone with the JPY version, very similar process, but please read as not all of Odin settings are the same.
5. With USB unplugged from PC, power off the phone and restart in Download mode.
6. Re-open Odin and select the following files:
PIT: s1_odin_20100512.pit
PDA: JPY_JPY_JPY.tar
Ensure the following options are Ticked: Auto Reboot & F.Reset Time (NEVER tick ‘Re-Partition’ when using a single firmware file for flashing as this could Brick your phone)
7. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The Firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
And thats it, you should now be able to upgrade the firmware via Kies....that’s assuming Kies is working correctly, and your carrier has released it, i’m with T-Mobile UK, but bought my phone through the Carphone warehouse, and was able to update immediately.
--------------------------------------------------------------------------
I hope this has been helpful, if you have any queries, I will try to answer, but as I said I am no expert, i've simply spent alot of time looking for the best method
Just thought I should point out that xxjpy is a european version and is not carrier specific. So it shouldn't matter if your carrier has released gingerbread yet.
This method will allow kies to update your phone to the lastest european firmware.
Why the pain?
No need to go through all this downgrading palava any more. Just use *spooffw and upgrade via kies as normal...easy peasy and no flashing required.
Search for "kies spoof"
*it fools kies into thinking you're on older firmware and offers you the upgrade to current fw
Don't need to tick "update bootloader"?
No, only tick the options stated in the guide.
Also be aware that you do not tick "Re-partition" on the second flash (JPY)
Sent from my GT-I9000 using Tapatalk
Thanks for the guide! I flashed it from a branded FW (was a backup) to stock and until now it's all pink and fuzzy!
Thank you, that's what i was looking for.
I never realized there was a written guide for this.
I just posted a video yesterday on how to debrand, unroot, and then update via kies.
Thus going from any custom kernel/rom theme etc.. to:
JPU, JPY then updating your version via KIES to JVO - good for warranty purposes.
thanks for this guide
Thanks for this guide. I was on JVO (samfirmware) and wanted to downgrade to get the official latest version installed later.
It didn't fully work for me but eventually got it working.
After having flashed from JPU to JPY Kies detected the phone (did not on JPU). However, it said there is no newer firmware version available.
So I flashed I9000XXJQ3_XXJPY_DBTJS2\PDA_JQ3.tar.md5 as PDA and I9000XXJQ3_XXJPY_DBTJS2\CSC_DBT_JS2.tar.md5 as CSC which I got from samfirmware (these were the versions I used to have on my SGS originally from Kies when I was still on 2.2.1).
*edit April 2012:*
had to downgrade again and went same procedure. However, couldn't remember whether I also flashed "phone". So this time I also added I9000XXJQ3_XXJPY_DBTJS2\PHONE_JPY.tar.md5 as PHONE in addition to the files I listed above as well as I ticked re-partition and added the same pit file I used on the first two flashes.
Afterwards, Kies detected the phone and offered the upgrade. Did that and now it has PDA: JVI, PHONE: JVO, CSC: JV2 (DBT)
*edit end*
cookm75 said:
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
Click to expand...
Click to collapse
How long is a "few minutes"? Odin has been at the following stage for just over half an hour now...
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
My phone doesn't appear to be doing anything and just has the yellow/luminous green android figure digging with "Downloading..." beneath it and "Do not turn off Target!!!" showing on the screen.
Should it be taking this long?
I have a Samsung Galaxy S I9000 that was on GB 2.3.4, but due to excessive battery draining, and the phone locking up on a black screen with the only way to recover being to remove battery, it was suggested to me at Carphone Warehouse to try flashing it back to Froyo.
No I had the same issue. From what I understand if there are no file names under the do not turn off target line and no blue progress bar on the phone then you waited too long from connection to flashing. Get everything ready and then connect the phone and start.
Nothing has been done yet at the stage you mention.
G
Sent from my GT-I9000 using XDA Premium App
Just pull out the battery, boot into download mode again and try flashing once more, it will pass successfully this time.
Sent from hell to take your soul
Thank you both gfacer & Lunchbox115.
I have now successfully flashed my phone with Froyo and then re-upgraded to Gingerbread through Kies.
I'm keeping my fingers crossed that the problems my phone was having have now been solved.
thanks, very useful information.
This may be a dumb question, but anyway... Does this whole thing works for samsung galaxy mini? If yes, do you need to unroot it if you already have it rooted.
My friend just gave me his Unbranded Samsung Galaxy S GT-i9000 to fix it.
I used the 3 button combo to access download mode then Odin it but when it boots to download mode it checks the internal mmc and returns an error exiting to stock recovery and I can't adb there no install from sdcard stuff. Need help with accessing download mode!
Error description:
E:failed to mount /dbdata (invalid Argument)
-- Verifying internal MMC block...
E:internal mmc : read fail
# MANUAL MODE #
Anyone can figure this out for me please?
Thank you.
akhrot91 said:
Unbranded Samsung Galaxy S GT-i9000
Click to expand...
Click to collapse
unbranded? check this
download mode is home + power for M110S
recovery ia vol down + home + power for M110S
xsenman said:
unbranded? check this
download mode is home + power for M110S
recovery ia vol down + home + power for M110S
Click to expand...
Click to collapse
Thank you brother, thanks so very much.
I just have another question, now how do I get back to stock ROM? Can you direct me to a guide that tells how to do it via heimdall?
I'm using Ubuntu 13.10 and don't want to run Odin from wine.
Thanks again.
akhrot91 said:
Thank you brother, thanks so very much.
I just have another question, now how do I get back to stock ROM? Can you direct me to a guide that tells how to do it via heimdall?
I'm using Ubuntu 13.10 and don't want to run Odin from wine.
Thanks again.
Click to expand...
Click to collapse
you need to flash Repair kit for M110S, download from PIT STOP link below and use this method
xsenman said:
you need to flash Repair kit for M110S, download from PIT STOP link below and use this method
Click to expand...
Click to collapse
I flashed Repair kit for M110S through heimdall suite. The Download mode has changed to korean language and now whatever combination I press it goes to download mode even by simply pressing the power button it goes to download mode.
Can you help me with that?
Should I try again on Windows OS with Odin?
akhrot91 said:
I flashed Repair kit for M110S through heimdall suite. The Download mode has changed to korean language and now whatever combination I press it goes to download mode even by simply pressing the power button it goes to download mode.
Can you help me with that?
Should I try again on Windows OS with Odin?
Click to expand...
Click to collapse
First I hope you had ensured that it was actually an M110S and not another variation of i9000
yes, Korean phones always have everything in Korean, but once having a boot-able ROM, you can use settings menu to change to English. which repair kit did you use? , as long as its in download mode you should be able to flash again, either with Odin3 or heimdall. also what stage of flashing did you complete .
just flash again but make sure you have ample battery charge, as power failure or pulling out usb connection can break the bootloader and you will have a big headache , hard bricking it and only a technician with JTAG can recover it.
xsenman said:
First I hope you had ensured that it was actually an M110S and not another variation of i9000
yes, Korean phones always have everything in Korean, but once having a boot-able ROM, you can use settings menu to change to English. which repair kit did you use? , as long as its in download mode you should be able to flash again, either with Odin3 or heimdall. also what stage of flashing did you complete .
just flash again but make sure you have ample battery charge, as power failure or pulling out usb connection can break the bootloader and you will have a big headache , hard bricking it and only a technician with JTAG can recover it.
Click to expand...
Click to collapse
I used the link from this under the 'first stage heading'. This is the repair kit.
Yes, I can only access download mode now it doesn't go anywhere else. I completed all four stages but as you have shown in the picture it didn't go to that update screen.
akhrot91 said:
I used the link from this under the 'first stage heading'. This is the repair kit.
Yes, I can only access download mode now it doesn't go anywhere else. I completed all four stages but as you have shown in the picture it didn't go to that update screen.
Click to expand...
Click to collapse
Ok, when you complete first stage does your phone boot up using the Eclair ROM? I normal circumstances it should? you say you completed all four stages, , was the flashing completed as successful in ODin3 and your phone rebooted into download mode?
If so try and check your USB port on your phone if you have any lint or anything that may be shorting them and did this phone got in contact with water?
cause what you say is rather strange for any unit as a successful flash can endup in some sort of boot process and never into download mode.
xsenman said:
Ok, when you complete first stage does your phone boot up using the Eclair ROM? I normal circumstances it should? you say you completed all four stages, , was the flashing completed as successful in ODin3 and your phone rebooted into download mode?
If so try and check your USB port on your phone if you have any lint or anything that may be shorting them and did this phone got in contact with water?
cause what you say is rather strange for any unit as a successful flash can endup in some sort of boot process and never into download mode.
Click to expand...
Click to collapse
Firstly I flashed all the files through heimdall in ubuntu not Odin3.
And at no stage it returned any error. At the first stage the download mode was in english on the phone, it had a yellow triangle and below it was saying "downloading" after I flashed the korean .pit file the phone rebooted back into download mode but the text below the yellow triangle was now in korean. After every flash the phone returned into download mode.
I checked as you said, the problem is before I knew the "Home + Power" button combo to access the download mode the phone booted to Samsung screen and hung there and now it goes no where except the korean download mode.
Deleted!
Okay I've figured out the problem with my phone.
When I was on the first stage when I entered the m110.pit file along with the PDA file. The PDA file had a movinand.mst file, while flashing with odin3 it got stuck on the movinand.mst part and remained stuck forever so I plugged out and restarted in download mode.
I did some googling and found out that this problem is related to internal memory damage or corruption or something like that.
Anyway I finally found out a GB file on some forum I don't remember and flashed it over my galaxy S and it kind of worked. When the phone is powered on it goes to the 'samsung anycall' screen and stays there for a while and at the bottom of the screen comes a progress bar, when it goes full the bootanimation comes up and the phone boots into the ROM. Now the problem is there is no internal memory so no apps are downloaded plus whenever I restart the phone it comes to that samsung anycall screen with the progress bar and then the bootanimation but the phone starts as if it were new, like the initial setup accounts and all and also reverted back to korean language. Is there anyway to fix the internal memory problem or any alternative?
Thanks once again for helping me out this much.
Can you tell me what actually is written under your battery ? as what you are indicating about this units behavior is rather strange and have not come across this on an M110S, and mind you I have help a lot of people to solve their problems on M110S units and tens of thousands had downloaded the repair kit from my upload site. Why I am asking is because I am in doubt as to what is your model? is it an M110S, or i9000 variation or a chinese clone?
this must be cleared , in order to get your phone functioning as remedies for it will vary
Hey. Now I tried flashing with odin3 and here's what happened:
1. After the first stage it should boot into eclair but instead samsung anycall screen comes up and then it goes into recovery with the following output:
E: can't mount /dev/block/st111 (invalid Argument)
# MANUAL MODE #
E: can't mount /dev/block/st111 (invalid Argument)
E: can't mount /dev/block/st111 (invalid Argument)
ok this means you have a cache partition problem , meaning stl11 is the cache partition that is not mounting as such you cannot boot, so lets try this ( remove external SD card, sim card etc and Flash the cache.rfs as below..flash it twice and let me know the result.
Problem:- Getting this when you boot
E:format_volume: rfs format failed on /dev/block/stl11
Solution:- Flash a cache.rfs file meant for your model as PDA with Odin. For i9000 i9000 cache.rfs file, For M110S M110s Cache.rfs
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2. I proceeded to the next two stages and flashed the files but still the same.
well, when you get a problem like above, there is no way it can boot until it is resolved, but its has booted into recovery, that is what it should do, not go into download mode.
3. When I press the power button only it goes to the samsung anycall screen and then same happens what i described in 1.
Suggest you flash the cache.rfs for M110S, see if it solves it, If not repeat stage 1 again using the repair kit with the PIT and repartition TICKED using Odin3 see what happens.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
akhrot91 said:
Is there anyway to fix the internal memory problem or any alternative? Thanks once again for helping me out this much.
Click to expand...
Click to collapse
You need to read the posts on PIT STOP about ways to solve internal memory problem. Look under "Solutions for Android problems " also My Android Solutions, link below.
Click to expand...
Click to collapse
xsenman said:
Can you tell me what actually is written under your battery ? as what you are indicating about this units behavior is rather strange and have not come across this on an M110S, and mind you I have help a lot of people to solve their problems on M110S units and tens of thousands had downloaded the repair kit from my upload site. Why I am asking is because I am in doubt as to what is your model? is it an M110S, or i9000 variation or a chinese clone?
this must be cleared , in order to get your phone functioning as remedies for it will vary
Hey. Now I tried flashing with odin3 and here's what happened:
1. After the first stage it should boot into eclair but instead samsung anycall screen comes up and then it goes into recovery with the following output:
E: can't mount /dev/block/st111 (invalid Argument)
# MANUAL MODE #
E: can't mount /dev/block/st111 (invalid Argument)
E: can't mount /dev/block/st111 (invalid Argument)
ok this means you have a cache partition problem , meaning stl11 is the cache partition that is not mounting as such you cannot boot, so lets try this ( remove external SD card, sim card etc and Flash the cache.rfs as below..flash it twice and let me know the result.
Problem:- Getting this when you boot
E:format_volume: rfs format failed on /dev/block/stl11
Click to expand...
Click to collapse
2. I proceeded to the next two stages and flashed the files but still the same.
well, when you get a problem like above, there is no way it can boot until it is resolved, but its has booted into recovery, that is what it should do, not go into download mode.
3. When I press the power button only it goes to the samsung anycall screen and then same happens what i described in 1.
Suggest you flash the cache.rfs for M110S, see if it solves it, If not repeat stage 1 again using the repair kit with the PIT and repartition TICKED using Odin3 see what happens.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
You need to read the posts on PIT STOP about ways to solve internal memory problem. Look under "Solutions for Android problems " also My Android Solutions, link below.
Click to expand...
Click to collapse
The back of my phone behind the battery reads:
MODELO: GT-i9000
FCC ID: A3LGTI9000
SSN: I9000T GSMH
I think its a M110S.
The cache problem is over. I told that in my previous post.
Okay I've figured out the problem with my phone.
When I was on the first stage when I entered the m110.pit file along with the PDA file. The PDA file had a movinand.mst file, while flashing with odin3 it got stuck on the movinand.mst part and remained stuck forever so I plugged out and restarted in download mode.
I did some googling and found out that this problem is related to internal memory damage or corruption or something like that.
Anyway I finally found out a GB file on some forum I don't remember and flashed it over my galaxy S and it kind of worked. When the phone is powered on it goes to the 'samsung anycall' screen and stays there for a while and at the bottom of the screen comes a progress bar, when it goes full the bootanimation comes up and the phone boots into the ROM. Now the problem is there is no internal memory so no apps are downloaded plus whenever I restart the phone it comes to that samsung anycall screen with the progress bar and then the bootanimation but the phone starts as if it were new, like the initial setup accounts and all and also reverted back to korean language. Is there anyway to fix the internal memory problem or any alternative?
Thanks once again for helping me out this much.
Click to expand...
Click to collapse
akhrot91 said:
The back of my phone behind the battery reads:
MODELO: GT-i9000
FCC ID: A3LGTI9000
SSN: I9000T GSMH
I think its a M110S.
Click to expand...
Click to collapse
The scam artists who have converted M110S to i9000 use I9000GSMH and will not indicate the FCC or SSN
yours says its an i9000T and there is such a model, look http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9000T
so best to check your IMEI number , follow this link to identify your model
anyway so long as your phone works its not a serious problem, but wrong ROMs can give you differing problems so ensure your unit is M110S before using solutions in PIT STOP
xsenman said:
The scam artists who have converted M110S to i9000 use I9000GSMH and will not indicate the FCC or SSN
yours says its an i9000T and there is such a model, look http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9000T
so best to check your IMEI number , follow this link to identify your model
anyway so long as your phone works its not a serious problem, but wrong ROMs can give you differing problems so ensure your unit is M110S before using solutions in PIT STOP
Click to expand...
Click to collapse
The IMEI site says my IP is blocked. I tried proxying but still doesn't give me the result.
What about the internal memory problem? And sd-card not reading!!
How do I solve that?
akhrot91 said:
The IMEI site says my IP is blocked. I tried proxying but still doesn't give me the result.
What about the internal memory problem? And sd-card not reading!!
How do I solve that?
Click to expand...
Click to collapse
Already mentioned in earlier post, look in PIT STOP for guide to solve internal SD card problems
Try this links to check iMEI
xsenman said:
Already mentioned in earlier post, look in PIT STOP for guide to solve internal SD card problems
Try this links to check iMEI
Click to expand...
Click to collapse
Okay. And I went through your post in the PIT STOP for internal sd problem.
I just need help with installing CWM and getting root as I cannot install the kernel WF07 speedMode application on the phone as no internal or external card.
Thank you loads for your help!!
akhrot91 said:
I just need help with installing CWM and getting root as I cannot install the kernel WF07 speedMode application on the phone as no internal or external card. /QUOTE]
you need to post screen shots or the contents of
1) settings > about phone ??? all details
2) settings >storage ??? all details
for me to give you solutions
Click to expand...
Click to collapse
I hope the pictures are clear as I can't take screenshots because of Storage problems.
akhrot91 said:
I hope the pictures are clear as I can't take screenshots because of Storage problems.
Click to expand...
Click to collapse
ok, the ROM you had flashed is obsolete, you nee to flash WF07 ( download link in PIT STOP) but before you do that, go into settings>storage and erase SD card, and Format where possible also you must follow the instruction given in flashing guide ( First post concerning repair kit) to the dot, meaning you need to factory reset (settings >privacy) as well as wipe everything and format everything prior to flashing WF07 and also wipe again after flashing.
Only after this you should look at other problems ( Internal SD card)
Its also best to USE the repair kit again and after flashing Ist stage , flash the WF07 ROM ( its the best ROM for the M110S)