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?
Related
Hello - It seems as though everyone is somewhat nice and knowledgeable on this board. I'm hoping that no one flogs me in the process of this thread.
I have a T-based Galaxy Tab and am trying to load a new ROM onto it. I've tried multiple times with multiple different ROMs but am not making really any progress. When I plug in the device to a wall outlet, the attached screen is displayed. This is the first time that I've seen this screen and I'm now hoping that this thing isn't bricked. Please help me bring this Tab back from the dark side.
I need to know which ROM to use and the appropriate PIT file. I also need to just understand how I get the device to be recognized by Odin again as it's not being recognized in it's current state. Thanks to all that will help me.
Jim
hi,
can you tell me which firmware files are you using to flash and the PIT files?
Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim
jimcansler said:
Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim
Click to expand...
Click to collapse
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT
Not wanting to be pessimistic here but after browsing the Galaxy S section I came across a thread with that image on your tab. You may have to contact Samsung and have the device replaced. http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode
Storm, Chow,
I think you may be right. I followed the instructions that Chow gave me and it failed. See attached. I still have the Tab attached to my pc and it still has the same image as original. I've attached my Odin screen so you guys can look at it and tell me if I'm doing anything wrong.
Jim
Hi,
I had that image many times, whenever my tab fails to install any new firmware.
did you reboot the tab after seeing that image
one more try:
after seeing the flash fail > hold the three button combination (power + volume down + home) for long time (may be more than 1 minute) until the tab is switched off and then use three button combination (power + volume down + home) to enter the download mode (you will still see the above image only). now connect the tab to odin and try flashing it.
if i remember correctly, my tab was connected to COM 8 when flashing but i think its USB port selection
this is how i recover my tab to working mode whenever a flash fails
Have you tried with Odin 1.31 with PIT 816 and JHA.tar selecting repartition?In the pic you are using the 1.71, right? I had something similar going back to JID from JJ4 and when I tried with the 1.31 it passed, cant be sure it wasnt just 'the one more try' or the old Odin but it worked.
Good luck
Sent from my GT-P1000 using Tapatalk
I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim
jimcansler said:
I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim
Click to expand...
Click to collapse
just install the JID without use any pit and do not select re- partition, keep using the 1. 31
Sent from my HTC Desire using Tapatalk
chowdarygm said:
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT
Click to expand...
Click to collapse
I quote.
I had that bad image on the screen for some time... If you connect to the PC you should find the TAB as connected in ODIN. If you flash JHA repartioning with the correct PIT, that for me was 9 and something if I remember, you should restore normal functionality. Try and let me know!
Can confirm.
Had this image several times while testing var firmwares.
Simply connect tab to odin and flash jha image with repartition.
This should fix it.
Sent from my GT-P1000 using XDA App
Guys, I think that he solved the problem using Odin 1.31.He already install the JHA and the unit is working.Pls stop posting without read.The issue can be related with the new Odin.Now he is concerning to install JID over a working unit...
MODEM file
Greetings,
Where did you guys get your MODEM file from? I only can see the PDA and CSC files on the samfirmwares.com site... :S
So I got my Galaxy S..used from a friend. it's a used unit and it's running eclair DXJG4 firmware. I've decided to upgrade it to froyo via odin (MTP Driver issue made me not use kies anymore)..At first I tried ticking repartition and flashed it and odin fails and the phone wont go past the galaxy S GT-I9000 screen. (I downloaded my DXJPA firmware from samfirmwares and I ticked both three PDA, PHONE and CSC and all of them are linked to the single tar). I tried the second time...repartition ticked AGAIN (I think this is the main problem cause now) and only ticking PDA. Odin passed. But phone still stuck at boot screen (the Galaxy S GT-I9000 screen). please help?
Ive read some topics..seems that I need to reflash it back to eclair JG4 firmware with repartition ticked and flash froyo without repartition? The most confusing part for me is whether to tick phone and CSC or not.
hi heres a guide on dxjpa http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install-froyo.html
btw dxjpa isnt the latest, dxjpe is latest
guide to dxjpe:http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install-froyo.html
You can try this.
When the phone is froze on the screen, connect it to the PC. If you can access your SD card from within Windows, format the sd card. Power down the phone, and power it back up. It should then boot past the screen.
i think the main problem is about im using a single tar for csc, phone and pda. might need to reflash though.
electro: I can't, its stuck in the galaxy S GT-I9000 screen. windows wont recognize it.
kongmyy said:
i think the main problem is about im using a single tar for csc, phone and pda. might need to reflash though.
electro: I can't, its stuck in the galaxy S GT-I9000 screen. windows wont recognize it.
Click to expand...
Click to collapse
redownload it from the link that i have gave u.have try using it and it definitely works
so I can just reflash it with the correct csc, pda files that is in the link you given and it will work? Or i need to downgrade to eclair first and then upgrade again. because I'm worried my last 're-partition' with the wrong files might need me to downgrade.
im downloading the files right now. wish it could be downloaded soon though, my connection is slow right now.
which one u downloading dxjpa or dxjpe?
u have to enable repartition
dxjpa. okay i will enable. wish me good luck
shouldnt have any problems if u follow the steps on the blog
tried it and now my phone works nicely. Thanks!
probably think u should upgrade to dxjpb since it is actually based on dxjpa with some cleanups of the rom
Purchased two Bell Canada Samsung Galaxy S as-is from local kijiji.
They all performing the same thing, rebooting at Galaxy S logo, GT-I9000M page, it won't go any further. and there is no recovery mode at start-up.
Here are the steps which I have played with for past two days.
1. Trying to get to recovery mode
- tried ADB, but it doesn't work, since "USB debug" is not on, and it won't accept as a device, and I am not able to turn that on, since I can't even get on the main screen.
- tried three key combo, vol up + home + power on, at least a hundred times for past two days, it doesn't work. fortunately download mode is working (at least I have more option to try). and I know how to get to recovery mode, I played with my friend's before.
2. Trying to use ODIN to flash the firmware
- unchecked "re-partition", unchecked "bootloader", pick 512 as PIT and then choose following as PDA
JH2, JK3, JK4, JL2
always successful on refresh, but phone still does the same, stuck at LOGO page
- also tried, checked "re-partition", and checked "bootloader", pick 512 as PIT and repacking following into PDA, Phone/Modem, CSC, still won't work...
JP series, JH, JK series, JL
At the beginning I though it was problem on CSC, I didn't use correct one to match my phone model #, but what's mine??? I can't go into my phone to check. I checked my friend's I9000, he used I9000BMCJK4, and I assume all JK series should work with me, since our IMEI are similar. And I tried many times on different cache.rft as CSC.tar, still no luck for me
I go crazy now, $400 USD gone. Seriously needing help. Any help is highly appreciated.
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
lgkahn said:
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
Click to expand...
Click to collapse
I have tried one of JL2 file from somewhere (don't remember where), but I will get one JL2 file from samsungfirmwares.com again, see if that works.
Do you mean, only choose the file for PDA, left PIT empty, and get everything uncheck?
permantely trashed internal memory? are these the common problem with this model? I got two of these, and both of them have the same issue, I think, there should be a way to slove it, right? Should I give up these thoughts???
anyways, thanks anyways, I will report back after I flesh JL2 from samsungfirmwares.com
Ok, you need to flash jl2 with pda, repartition, pit file and the secondary boot loader... The SBL(secondary boot loader) is what will actually fix your phone
Hopefully it will work.
Sent from my GT-I9000m using XDA App
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Still no luck on this firmware, I9000UGJL2, by the way, should be samfirmware.com instead of samsungfirmwares.com
above message I got from ODIN3 v1.30, it looks fine for refresh, but it doesn't work. the phone keep rebooting, it won't pass LOGO page, again, only download mode I can use.
HELP! HELP! HELP!
any leads???
is "<ID:0/005> Sbl.bin" secondary boot loader???
I got the file for PDA, I9000UGJL2, is this the one? if not, where should I get it? how do I update it?
I did it again, with "re-partition" checked, PIT choosed as s1_odin_20100512.pit, I9000UGJL2_homebinary_add_param.tar (which I just downloaded from samfirmware.com), it still doesn't work.
anything else I can try? maybe something simple I didn't do???
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
jt_kyle said:
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
great!!! Another option I can try. Thank you.
I will try it out right after my work. so the idea behind this, is bricking it into recovery mode and S10 error code. and then fresh right back with correct ULG2 (is this correct? frist time heard about this rom)
anyways, I will post back with result.
Where can i find this ULG2 rom?
did it work?
Thananjeyen said:
Where can i find this ULG2 rom?
Click to expand...
Click to collapse
I think jt_kyle meant I9000UGJL2
and you can get them from samfirmware.com
Paallikko said:
did it work?
Click to expand...
Click to collapse
yes, lucky I got one of my Bell Samsung phone work. Since I done a million times of refreshing and rebooting and etc... I am not sure what I did, now I still trying to remember last 10 steps I did to make this work.
But definitely, I could not have done this repair without jt_kyle. Thank you so much, jt_kyle.
jt_kyle, Thank you!!!
but none of JP1 or JP2 is givining me the error "tl10", I tried
I9000DXJP1
I9000TGYZSJP2
I9000XXJP1
I9000XXJP2
it come out error started with "m..."
I just keep refreshing each on PDA 3 to 4 times, and choose with re-partition or without. At the end I try a few another ROMs as well, I still get no "tl10", but somehow, just that magicical moment, the screen come out a set of commands that look like format sd card, so I got excited, fresh it with JL2. It is back to work.
still no clue the steps of fixing the problem.
one done, the another one to go.
any more ideas please, and I think I am really close to solve this one now.
Thank you All
FIX
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
EVERED78 said:
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
Click to expand...
Click to collapse
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Could it be dead?
Since you have one of the infamous i9000m's it might also just be a dead SD card? You might try calling samsung and trying to get it repaired under warrenty as they are all under a year old (try and flash jl2 first even it will not boot up). It sounds like no receipt may not be an issue.
Lots of info from allgamer's list of i9000m issues in the general section.
At least you have one in the meantime!
same problem
Hey ive got pretty much the same problem that you had. Only differences are that I'm from Australia and am on Virgin network.
My phone became semi bricked one day when it restarted and since the 3 button combinations did not work i ordered in a USB jig which i received today. I used odin 1.8 to try and flash to I9000BVJJPD which i got from samfirmware.com but it ended up stuck on the logo screen vibrating once in a while. I decided to repeat it with no avail and began to use other roms and use .PIT.
This is where my phone became even worse and is now in it's current position; rebooting at the GT-I9000 page. I tried the method that jt_kyle suggested, substituting australian roms instead but it is still in the same position.
Does anyone have any other suggestions or should i just try getting a warranty?
Look for the ugjl2 complette and repeat what I said
Sent from my GT-I9000 using XDA Premium App
EVERED78 said:
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Click to expand...
Click to collapse
I think I have this I9000M_JL2_JL2_JL2_JL2_UG_BMC file, is the same file that you are talking about? JL2 Complete?
I tried this file many times, it won't work neither.
for past one hour I played around this phone, trying to repeat the steps I did for the first phone. Unfortunately, nothing is working for me AGAIN!
but I got these error page all the time, like following...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
I think that's bigest problem in my case, and for a lot of people in this forum. Do any people has a good solution for this???
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.
before writing, I'm so sorry for my pooooor English.
I live in Toronto, Canada. I bought my Galaxy Note(SHV-E160L) from Korea, so change sim card from LG U+ to Rogers.
but when I sleep, Note encounter Unlimited Reboot.
so I try to repair in 3-way.
first, Factory reset. but I could make Download mode only, couldn't make Recovery mode.
so I try Samsung Kies Recovery mode, but Kies show me binery Error.
last, I want to use ODIN, but ODIN show me Error Message, too.
"Complete(write) operation failed"
What this means?
If it can't be repaired, I must send my cell phone to Korea.
I'm very embrassed...
please help me!!
and Merry Christmas for you
Is it sticking on factoryfs.img in ODIN ? this usually means its bricked which kernel where you on when you did the factory reset ?
I had a similar issue last week, stuck in odin, everything failing, I was convinced it was bricked, I manage to repair it by (no joking here) flashing a million wrong things in ODIN.... But DO NOT TRY THIS lol
try to flash a safe kernel through ODIN, and then see if it bring back recovery, then you can wipe and flash a new rom (hopefully)
otherwise there is the pit file method to revive from a brick, which works well, but loses around 3gb of internal sd space
hello
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.
Thanks for your reply
hanzo777 said:
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.
Click to expand...
Click to collapse
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..
Sigea said:
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..
Click to expand...
Click to collapse
Perhaps should follow closely the guide for using odin from Dr ketan should help:
http://forum.xda-developers.com/showthread.php?t=1424997
1. Installation
- Download stock ROM (should start with a GB rom), and extract it to .tar file
- Download Odin, open it
- select PDA tab and point to ROM file. Leave Re-partition, pit, CSC, Phone tab unticked.
- Switch off device, Put in download mode (Vol down + Home + Power)
- completely close kies, Anti virus if running
- Connect device to PC
- ID com port shud turn yellow (not shown in image)
Now hit Start
----
see how it goes.
Same problem as OP
Hello guys,
unfortunately, I have the same problem with my 32GB SHV-E160L as OP. Little backstory:
I bought the GNote in Korea and brought it back to my country. I successfully rooted it with one of the guides here on XDA (Tegrak kernel, no OC whatsoever). No problems so far, the phone worked for weeks and I was able to do what you can do with rooted phones. One day while surfing the net it just crashed and was stuck in a boot loop. This is where I am now.
I tried:
Go into tegrak recovery. result: It gets stuck on samsung logo, funnily the phone would establish a usb connection if plugged in (as if in download mode)
Reset from Kies. result: After beeing told by Kies to go into download mode, instead of flashing the new software it gives an error message in Korean about missing binaries (see attachment)
Flash from odin. result: the dreaded red box with "fail" appears after the NAND write command
Now, after doing my research here on XDA I found out that my emmc might have damaged partitions and I need a PIT file. Here's where I'm stuck.... I can't find a PIT file for my 32GB note, only for the N7000 or the I717. And I don't want to mess things further up... so if anyone here could provide me with a PIT file, or tell me how to fix the phone through other means I would be really grateful
Thanks in advance....
You should ask hg42 if he can make one - in his thread I read that he did this before even for other devices.
So try a pm or post in his thread. Good luck