Related
Bought this phone last week, recovery & download worked with 3 button.
Rooted, flashed Darky, Voodoo Lagfixed in recovery, worked great.
Tried Doc Kitchen, worked great.
Voodoo lagfix in recovery, booted once, crashed, now stuck at Galaxy S screen.
No recovery, do have download mode. Power on, Galaxy screen, reboot, galaxy screen.....
This doesn't seem to be the same symptoms as SD failure, seems the only thing left to do is try to flash via Odin...
Downloading UGJL2 from SamFirmware, concern is;
If Lagfix is enabled, most Odin guides say this is an issue? Or should I just select and flash?
Thanks.
And Samfirmware.com gave me a .rar file?
Contents:
factoryfs.rfs
cache.rfs
modem.bin
param.ifs
sbl.bin
zimage file?
I had similar problem. However, I was trying to flash to JH2 because i wanted to unlock my phone, but ended up with boot loop and no recovery mode.
I fixed this problem by trying to flash JH2 firmware and it came back to live. The first time flashed it, the phone went into recovery. However, there was a msg something about Media cant be found. So i flashed it with JH2 again with re-partition not checked and no .pit file. In addition, I used Odin 1.7 instead of 1.3. and the phone is all good now.
I think the problem might be with Odin v1.3. you can give a try but no guarantee..
OK.
Stupidity = Off
Flashed UGJL2, JH2, JG8 using Odin 1.7, Pass!
Still no recovery, still in a bootloop.
flash jpc from samfirmware with pit 512 and repartitioning checked, that worked for me,
using .tar or pda et all?
End thread.
JK4 flash for replacement status nets 3e recovery and a failed SD.
Cheers.
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).
I wanna know if you can help me, ...
I was on sprint gtab stock rom DJ30 which updated to EA24 and EB28. Data service worked very well. Then I flashed voodoo CWM in order to install Honeycomb rom. Then install the rom via CWM. The installation was indeed finished, but it stucked in samsung logo boot. I turned off device and boot in cwm mode. Sure, it was HC rom's CWM. But it couldnt mount system, Seems the convertion to ext4 didnt work. Worse thing it couldnt mount sdcard either. So I couldnt reinstall the rom. I also couldnt reboot, so i had to long press the power button.
Stop trying installing HC rom on my device, i decided to revert back to stock rom (DJ30>EA24). But it was weird, i cant revert to stock rom with modem.bin inside the package. It always stuck in modem.bin when flashed with odin. But, when i use the package with no modem, it can flashed succesfully. I had flashed that stock rom (with modem.bin) million times without fail, but now always fail.
Yeah, my gtab is running but without modem.bin so no signal and i cant use data services. Like wifi only tab.
Many ways i've tried:
- I've tried flashed DJ30 with no modem first. Okay, it is successful. But when flash with EA24 (with modem) it stuck on modem.bin.
- I've tried flashed DJ30 with modem.bin. And it also stucked on modem.bin. Trying flashed EA24 without modem.bin, it is succesful.
- Try using heimdall. Progress 100% but it wont reboot. But when i retry n uncheck modem. Flashing work flawlesly.
- Try using odin modem only flash. Progress bar is full but it wont reboot.
- Try flashing via CWM, but still no luck.
Weird, huh. Seems my gtab cannot use modem.bin anymore.
Any clue? Thanks before ...
I'd appreciate if you can help me flashing modem.bin to my device. Or it end up with wifi only tab.
EDIT: even OTA update, stuck on "verifying modem ... updating modem ..."
I would like to bump this as I am having the same issues also. I am flashing my Sprint Galaxy Tab to EA24, and it is held up at modem.bin.
I posted a question on this, and am hoping that someone helps us.
Thanks in advance,
Claud
try re-partition and flash pit by using odin,i suffered the same issue with my vzw tab
depending on which file you're using to restore. You need to use the .tar.md5 file from the EA24 flasher and rename it to just .tar, then flash with Odin. I've flashed this several times and it gets past modem.bin just fine. If you are using the 2 files 1 with modem (Epic 4g modem) and 1 without modem you're not using the right files. I ran into the same issue with the with/without modem files. Here's a link to the EA24 flasher and the .tar.md5 file you need to go back to stock.
http://www.multiupload.com/LXQKGX5RHL
Bumping this to avoid making a new thread.
I've done many reverts back to stock from different ROMs, but this past time coming from BTL or HC (Sprint Tab btw) I'm also getting hung up on modem.bin. Never had a problem here before, so not sure what's going on.
I didn't use a pit and only had reboot checked and it worked fine.
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Maniken50 said:
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Click to expand...
Click to collapse
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
pvtjoker42 said:
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
Click to expand...
Click to collapse
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Maniken50 said:
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Click to expand...
Click to collapse
I've never had to repartition a device, but i've read about it working for people to bring them back from boot looping etc. If somehow the partition table gets corrupted etc. If you're already soft bricked, there's no harm in trying.
Having the same issue, trying to go from Rooted GB to BTL then back to GB or EA24
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
ezitec said:
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
Click to expand...
Click to collapse
http://www.mediafire.com/?jb40cs460rf8aq7
Try that one.
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
mbanton said:
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
Click to expand...
Click to collapse
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
pvtjoker42 said:
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
Click to expand...
Click to collapse
I have the correct files for the tab for Verizon. I have the original files Following: Sbl.bin boot.bin cache.rfs dbdata.rfs efs.rfs factoryfs.rfs ldb.db modem.bin param.lfs param.rfs pit.pit zImage
But my problem is how to record using that pit. What other files should I use a recording that will restore the partition table?
I fear that a problem occurs with even higher tab.
I am having this issue as well, and I'm also coming from HC and on Sprint. I have no trouble flashing any kernel/rom of my choosing EXCEPT for the modem.
At this point, I'm just trying to reflash it back to stock. I've got the Sprint EA24 files, including the pit (tried with and without) but it refuses to flash the modem. If I omit the modem, it flashes perfectly fine and I'm left with a bone stock tab with no modem.
Is there anyone here who went to HC and then managed to go back? As stated by others, I've gone back to stock before without issue. The HC build seems to be what caused this problem
I ran spacemoose's HC port for a day or 2 and then went back to stock until the official GB came out. I've had no issues flashing the whole EA24, or any other updates.. with and without the modem..
Hmmmm. Maybe different hardware revisions? You have any suggestions? I'm completely out of ideas and it's of little use to me without 3G.
I just did a flash back to complete stock (including modem) 2 days ago, and it didn't hesitate once while flashing everything with Heimdall. Only thing I can say is keep trying.
At this point, I've attempted to flash it no less than a dozen times and still can't get the modem to flash. I'm completely baffled as to why it won't accept it.
I've been trying to reflash my Bell Galaxy S from not booting up without success. I have tried Odin and Heimdall no less then 10 times with different suggestions in this forum. And I went from getting the "Can't mount /dev/block/mmcblk0p1" when the phone first loop boot to not booting at all after first Odin, then to "Can't mount /dev/block/stl10" - "Can't mount /dev/block/mmcblk0p1" after another Odin.
After many Odin and Heimdall flashes now all I got is just a round inanimated "sun-ray" with the usb cable plugged-in or the Samsung splash screen without the usb cable.
I don't want to proceed further because I think the solutions I got from other posts are not specific enough for my situation.
I have read in many posts that you MUST disable lagfix before flashing with Odin or Heimdall. This I did not do because my phone started to loop-boot with the lagfix enabled.
Someone even mentioned here you can't flash your Galaxy too many times as every flash is registered in the phone, or you will void your warranty.....
My phone: Bell Samsung Galaxy S GT-I9000M. Updated from Eclair to Froyo via Kies. I do not know the exact Froyo version but my mental image of the "About phone" info screen seems to agree with UGJK3. Rooted and lagfix enabled while running Froyo.
Firmware packages I have tried back and forth so far:
s1_odin_20100803.pit
DBdata.rfs.tar (and I followed this post: http://forum.xda-developers.com/showthread.php?t=953339)
I9000UGJH2
I9000UGJK3
I9000UGJL2 (last thing I did on Odin and flash with re-partition)
And I did check the re-partition box in some cases when flashing with Odin.
Hope I can get more help here so that I don't damage the phone any further.....
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
odin
find your stock rom from ramad, flash with odin 3 files with repartition and pit.
http://forum.xda-developers.com/showthread.php?t=1102881
no problem to flash in odin with ext4 system.
its important to open odin and insert the files before you connect the phone, also take out the battery before you enter download mode can do the trick.
Removing lagfix isn't mandatory if you are using
re-partition option, since it's setting up all partitions and formatting 'em also. I have many times flashed with Odin without removing lagfix and never had any problems regarding it..
Sent from my GT-I9000 using xda premium
Thanks for everyone's suggestions.
I only applied lagfix after I updated from eclair to froyo. There was no further update after that. So my last working firmware should be a froyo. The bootloop was not caused by any software update process. I dropped the phone and the battery came off. I rebooted the phone (most icons missing from home screen after this boot) but the camera application gave me an error msg when I used it so I rebooted it again. It started to bootloop after this reboot.
I couldn't get the phone in the download mode without the phone battery. And if I get to download mode with the battery, plug the usb, then remove the batter, the phone turned off. so not having the phone battery is not an option to me.
So I did too more reflashes, screen shots attached:
(1) UGJG8
(2) UGKG3
The phone still looped with the circular bars.
I'm wondering if I should check the Phone Bootloader Update box at Odin. Or should I tried Darky Resurrection Edition rom?
nwsk said:
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
Click to expand...
Click to collapse
I took your suggestion and flashed a rom that supports ext4. I flashed it with Darky's Resurrection 10.2. Now I got a boot menu after the reboot. But I got "failed to mount /sdcard (file exists)"
Any idea? thanks.
Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.
Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?
btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?
N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]