I need some help... Please!
I have a I9000T galaxy S phone and I soft bricked it. This is the story:
I flashed my phone using Odin with ROM JPY_JPY_JPY (downloaded form samfirmware, only file: PDA), and then flashed supermod-kernel-k13d-500hz...then I uploaded Modem UGJL2 for Froyo as an update.zip file (to get band 850 mhz for my country) and applied successfully!
My phone worked as a charm. No bricking.
Then I realized that there was a newer ROM: I9000XWJS5 with the XEN thing.
Since the ROM has the 3 files (MODEM, CSC, and PDA) and I read that it needed a different PIT, I flashed with the re-partition checkbox checked and with the 803 pit file.
It didn't get through. It got stuck at flashing sbl.bin
I had to unplug it after several minutes and I realized that it was soft bricked. It didn't work but download.
I tried to go back to JPY. After many tries and errors (changing PIT to 512 and repartitioning), finally I could flash back to JPY ROM. At the end of the process it reboots and the system get into Android system recovery <3e>. I can read at the bottom the following signs:
E: Can't mount /dev/block/stl10 (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.
If I reboot the system, it boots and I see the splash "S" moving theme, and it seems that it is booting but then it stops and it starts vibrating from time to time... then the screen goes black and nothing happens (but vibrating from time to time). It never appeared the "login screen"
Reading here and there, some advised to flash first the speedmod-kernel with the PIT 512 file and re-partitioning. I did so, and then, after boot I was able to get into Clockworkmod recovery screen. The menu is green and the version is 2.5.1.0
Someone suggested to flash to JPU ROM (that way it fixed a similar problem) but when I did so, it takes me to the beginning (the process hung at sbl.bin)...
I've been flashing and reflashing with different options these 3 ROMs (JPU, JPY, JS5) the only one that completes the flashing successfully is JPY, and eventhough it tries to boot, it fails to present the logon screen (dots for password)... JPU and JS5 hang at sbl.bin and after that, no boot... freeze. I have to flash back to JPY.
I have read tons of forums, I have learned a lot, but I believe I need deeper advices.
Thanks in advance!
Some further information. JPU, JPY, JS5 are ROMs that were downloaded from samfirmware.com... I guess that is what you mean when you advice to flash any stock ROM. Am I right?
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
droilfade said:
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
Click to expand...
Click to collapse
No... I don't have a I9000m, I do have a I9000T
When I flashed the JPY it turned a I9000, but I applied the Modem UGJL2 which adds the 850mhz band (which is the only difference between the I9000T and I9000.
Someone suggested going to JM8 (Eclair 2.1), but I have read that in some cases it produces hardbrick... what do you think?
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
froysm said:
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
Click to expand...
Click to collapse
Thank you froysm... What I see in your post is that we are going to try to flash a Darky's ROM in order to have CWM so we can flash a custom rom?
If that is so... I already have CWM... It is version 2.5.1.0 with its menu in green.
What is custom rom? are they the roms from samfirmware? I tried JPU and JS5 and they hang at slb.bin... the only one that flashes successfully is JPY, and eventhough it "runs", somehow it is not working.
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Well, if you have CWM try one of the roms of the world famous romkitchen Cook a rom, download it, enter recovery mode, go to mounts & storage (and connect your phone to the computer) and select mount USB storage, put the donwloaded zip file in your phone. Then unmount, go bak to the main CWM menu, select install zip from sdcard, the choose zip from sdcard, find your rom and flash it! However... as far as i can remember i could never mount my phone with CWM 2.x so may need to flash Darky's Rom just to be able to mount your phone, put the zip file there and then reflash with the new ROM viw CWM...
jdelagarza said:
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Click to expand...
Click to collapse
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
froysm said:
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
Click to expand...
Click to collapse
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
jdelagarza said:
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
Click to expand...
Click to collapse
Don't worry, that is exactly why we are here to learn from other people experience and share what we have learned.
About your issues,
I only have access to my Linux machine and heimdall says this when i ask for help (with the command
Code:
heimdall help
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]
action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
So, what you have to do is navigate to the location of your files and write something like this
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --dbdata dbdata.rfs --cache cache.rfs --param param.lfs --kernel zImage --primary-boot boot.bin --secondary-boot Sbl.bin --modem modem.bin
See how i reordered the files to flash leaving at the very end Sbl.bin and modem.bin?
As i told you before this will fail because of the last files, but it will allow to flash everything else. Remove your battery, put it again and try to boot your phone.
I forgot to tell you something really important!! Since the flash in going to fail it will give you the <<scary>> "Connect phone to PC" screen, but don't worry, heimdall can take care of that. Again, asking heimdall for help in the command line says something like this:
action: close-pc-screen
description: Attempts to get rid off the "connect phone to PC" screen.
And that is exactly the next step to take, write down in your command line (with the pone connected to the pc and in download mode)
Code:
heimdall close-pc-screen
And that's it, wait for the phone to boot.
This method is the one i advise when you just can enter Download Mode or when you really need to repartition.
Better? Worse? Nah, they are just really different approaches, Odin is the Samsung standard, Heimdall came to the game because it's OS X and Linux compatibility and CWM allows you to control your phone, custom kernel settings, flash updates packages with modems, boot animations , even whole roms without the need of a cable to connect your phone to a PC and other really cool stuff. Generally, since i've been in custom roms (like darky's, romkitchen, ultimate, etc) since i got this phone, i only use CWM, and when i have a big problem or i need a stock rom i use Heimdall (because i'm on Linux).
The CWM version is just fine, not all the roms are compatible with CWM 3 at the moment, so just make sure you can mount your phone in your pc with CWM. Try first the CWM option, if you can't mount it or it just don't works try the heimdall option.
The last question, I'm not saying it's 100% safe because it is not, but not only custom roms, this also can happen flashing a rom with Odin or Heimdall. Honestly i haven't heard of someone who bricked a phone in the whole thread of the romkitchen or darky's rom. I mean, it could happen, even with a perfectly stable stock rom. but it's not so common, at most, the worst thing you will encounter in your custom rom experience is a lot of Force Closes in applications (if you mix data and apps from incompatible versions) maybe a couple of boot loops, but nothing to be really scared about, just make sure you can enter Download Mode and everything will be fine.
Phew! The longest post if ever written in any forum. I hope i made everything clear, if you happen to have any other question i'll be happy to answer it (But it will have to wait for tomorrow... you know, it's midnight).
Thanks...
I'm downloading darky_heimdall.zip. As soon as it is downloaded, I will try it.
Just for your information, with CMW I tried to mount the USB and it worked!
So, now I am at a dilemma... Should I flash darky with CMW or heimdall?
Oh, if you wanted to know how I managed to install a WORKING STOCK ROM with froyo... here is the tutorial that I followed:
http://neosystm.com/2010/12/actuali...000t-a-froyo-2-2-1-xxjpy-de-forma-no-oficial/
It worked as a charm... I had Froyo 2.2.1 with JPY ROM.
The problem began when I tried to update it to JS5 ROM.
Cheers!
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Hey, sorry i didn't answer sooner, let's see...
jdelagarza said:
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
Click to expand...
Click to collapse
Yes, you can.
jdelagarza said:
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Click to expand...
Click to collapse
That specific version of Darky's rom is intended only for heimdall, so it will obviously fail. You'll see, some files can just be flashed via CWM and some can just be flashed with Odin and Heimdall, be careful and read with which tool can be flashed.
jdelagarza said:
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Click to expand...
Click to collapse
As I told you on my last post, heimdall can take care of that. Just put your phone in Download Mode and write heimdall close-pc-screen. That should solve your problem.
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
Nope, i've never found it (actually i've never needed it).
jdelagarza said:
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Click to expand...
Click to collapse
Try my methods first, I've tested them a lot and never had a real problem. If you want to try this, go ahead. As i told you before it's very rare to hear a phone really bricked, most of the times it's recoverable.
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
jdelagarza said:
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
Click to expand...
Click to collapse
Always, after any task completed successfully or unsuccessfully either with Heimdall or Odin, unplug your phone, reboot it, put it again in download mode and connect it. So do that again, flash, wait for the fail, unplug, reboot, download mode again, connect again and try to remove the error screen with heimdall.
I will read that post and see what i can find (I can't read it right now, sorry).
Hello!
I have SGS I900 which has GB 2.3.4.
I was following instructions as per http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Which for some stupid reason neglected to mention I should enable USB Debugging before the process!
Anyway, after flashing this kernel using heimdall 1.3.1 on Ubuntu, I found out I cant do adb push to place the zip file on the phone.
I tried to mount the SDCARD throguh usb using CW recovery - it worked, but I tried twice, each time transfer speed drops at the last 20mb (out of 158 mb), but eventually after like 10 minutes it finished copying.
However in both attempts, it failes to open the zip file when I try to install.
I am also unable to boot the phone as its in endless loop on the logo.
What do you suggest I do now to get it running properly?
Thanks!
Can you get into download mode?
If you can, flash in a stock rom. Root it using CF-Root.
Sent from my GT-I9000 using xda premium
Soryuu said:
Can you get into download mode?
If you can, flash in a stock rom. Root it using CF-Root.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yes I can, but how to flash a stock rom, if I cant properly transfer the update.zip file?
I would also appreciate a link to stock kernel, because I havent been able to find one.. since I dont now what to flash now.
Carmageddon1984 said:
Yes I can, but how to flash a stock rom, if I cant properly transfer the update.zip file?
I would also appreciate a link to stock kernel, because I havent been able to find one.. since I dont now what to flash now.
Click to expand...
Click to collapse
Go onto sammobile.com and under the Firmware section download a stock 2.3.6 rom.
Then download Odin (its not that hard to get online), any version should do.
Unzip the rom you downloaded. Leave the files as they are (you should get two files, a .tar file and a dl or something like that. We only want the .tar file).
Note that for this you don't need to put anything on the SD. You just need to have things on your computer.
Open Odin. Put the phone into Download mode by using the 3 button method (Vol. Down + home + power button). Once you get the "Downloading!" logo, onnect the phone to the computer (with Odin open) via USB. One of the boxes in Odin should light yp saying ID:COM: with a number next to it. That means Odin's read the device.
Select PDA, click on the .tar file you unzipped from the download. DON'T touch anything else.
Select Start and it should flash in.
That should fix your problem hopefully
Sent from my GT-P7510 using Tapatalk HD
Soryuu said:
Go onto sammobile.com and under the Firmware section download a stock 2.3.6 rom.
Then download Odin (its not that hard to get online), any version should do.
Unzip the rom you downloaded. Leave the files as they are (you should get two files, a .tar file and a dl or something like that. We only want the .tar file).
Note that for this you don't need to put anything on the SD. You just need to have things on your computer.
Open Odin. Put the phone into Download mode by using the 3 button method (Vol. Down + home + power button). Once you get the "Downloading!" logo, onnect the phone to the computer (with Odin open) via USB. One of the boxes in Odin should light yp saying ID:COM: with a number next to it. That means Odin's read the device.
Select PDA, click on the .tar file you unzipped from the download. DON'T touch anything else.
Select Start and it should flash in.
That should fix your problem hopefully
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
Thank you!
After much trouble since heimdall complains about something like "firmware.xml is missing from the package." , tried those steps:
First, on my Ubuntu desktop:
Code:
heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --modem modem.bin --param param.lfs --kernel zImage --no-reboot
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
26%
ERROR: Failed to send file part packet!
FACTORYFS upload failed!
Ending session...
ERROR: Failed to send end session packet!
Re-attaching kernel driver...
Then after further troubles on setting up the Samsung driver on my Windows 8 laptops ( it worked only on one of them!), I get Cpomplete(Write) operation failed line, after param.lfs line.
Any help would be hot :good:
Another updatE:
after a second try on the working laptop, Odin flashed it!! waiting for the device to boot now, hopefully after this, I can get back to flashing the target rom
Thanks!