Once after restarting my galaxy s i9000 i could not get phone signal. I reinstalled eclair with odin and it worked properly. then using clockwork recovery and returning back to doc 5.1 the phone signal is still not there. tried dark's 7.0 too. with the same result no phone signal. any help is appreciated
Since you recovered all settings went back.i had this once.maybe try to flash a modem file with odin,no repartition and no pit clicked.
Sent from my GT-I9000 using XDA App
I did not revert back to my old settings. I checked re partition and installed eclair. Then i flashed doc 5.1 without restoring my settings. Plus i tried to manually push modem.bin file using odin. No result
Can you check if you Flight mode is working or gets stuck?If it gets stuck then there is something wrong with modem version.When it happened to me i had to flash a 2.2 modem to get it to work.
Yes my flight mode did get stuck. But i tried installing new XXJPY firmware's modem through clockwork recovery and still same result. Which one did you flash? Plus my baseband version is unknown in the settings app.
I was on stock JPU at that time,i had flashed it through Odin and by mistake i had not clicked Modem and flashed without it while i was at work.Then i got home and didnt have JPU there but had JPA so i though,wtf,it was on factory reset anyway(after i had a major brick) and flashed the JPA modem on its own,no pit,not repartition,did a factory reset again,clear cache and it worked.Hope it fixes yours too.
Tried that too. Still the same. No difference. I am getting the range in eclair but not in custom firmwares. Plus the baseband is unknown
Related
I have flashed all sorts of 2.2 ROMS on my GT-I9000 ranging from stock JPC to Doc JPO and latest CyanogenMod beta.
Now I wanted to return to DDJG4, the official eclair firmware for out region. I flash it via odin with repartition enabled(512 pit). Everything goes fine, the phone boots up. One minute after boot up it shuts down again.
Any idea whats going on?
did u factory reset also?
yes i did.
Hi guys,
I have browsed the forum and have tried several of the remedies here but still no luck. I have been running Darkyy's 9.0.2 rom for a few weeks now, with a 500hz- speedmod kernel (don't remember what flavour, but was flashed via CWM). It has been running great since I flashed.
The problem arose when I went into settings to simply change the lock screen. I selected another lockscreen and my phone rebooted. Then it gave me quite a few FC errors,so I decided to boot into recovery and 'restore' a previous save. Now my phone just shows the samsung logo and reboots.
I am able to get into download mode but not recovery. This will be the fourth time I have to send it away. Is there another option or is this still my only option?
Any thing specific I should try to flash.
If it helps I am on the BEll network (gt-i9000M)
try to flash JPY base stock ROM with Odin......
try without repartition and pit (1 file PDA, no pit file from samfirmware.com)....
Then flash the latest speedmod kernel.....
Now it should work (maybe! XD)!!
Thanks for your reply, I tried your suggestion but still the same problem. I also tried all of the suggestions on this link. I finally was able to get into the recovery console by flashing JPY (no part, no pit), then immediately flash JL2 (with bootloader, no flash, no pit) but I got the dreaded 'no such directory'...again. So I am SOL but have to take it back today.
Did you tried flashing with 3 files + pit + repartition?
With this method it should work...
Remember: no bootloader update!
Sent from my GT-I9000 using XDA App
Did you ever upgrade to the official Bell JL2? If not, I'd probably do that through Odin and have it update the bootloader. I had gone from JH2 to different cooked roms and would always run into corruption/fc problems a week later. And eventually the phone would just not boot into the OS. The last time it happened, even flashing to another cooked ROM would not work. The official bell JL2 has an bootloader update that seemed to have fixed the issues I was having.
Booted official JL2 and remembered how much I hated lag After that, flashed a 2e kernel through Odin then seeARM's cooked JL2 through clockwork. Been running that for 3 weeks now without any issues.
Hi Guys,
I should probably write down what I flash when I flash it. I honestly do not remember what I flashed. I went through all the threads I could find and tried everything. So to answer your question, I cannot say for sure if I did that or not. But I ended up sending the phone away. It was weird, I asked my fiance to take my phone in while I was at work. She called me later that day and told me that her phone did the same thing so she sent hers back the same day....weird.
I have checked other similar threads before posting, but I couldn't find anything helpful.
I had a stock 2.1 Eclair then updated to FroYo through Kies a couple of days ago (firmware JPA). Then I applied the voodoo lagfix through Odin and everything was working fine. Today I tried to install CF-Root using Odin. It went fine and my phone rebooted but then it went into a blank screen after the booting animation/sound.
I CAN boot into both recovery and download modes but I'm a little bit confused on what to do now. Should I flash a new firmware or is there any thing else that I could do to fix this. And if I have to flash a new firmware, which version do you recommend (I prefer stock 2.2.1 Samsung firmware, preferably ones for the Middle East so they would have Arabic support).
Thanks in advance
Just a little update. I flashed a new firmware (XWJPA), it went fine and rebooted then came up with the recovery menu with an error message that the /dev/block/stl10 can't be mounted. I tried to wipe stored data (not internal SD card) and rebooted it. Now it goes into the same blank screen but keeps vibrating randomly!!
Any suggestions?
your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...
azzledazzle said:
your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...
Click to expand...
Click to collapse
Can anyone confirm which one has dbdata, JM5 or JM8? I currently have a very slow internet connection and downloading both would take a lot of time.
Also could anyone explain the reason it got corrupted?
Thanks for your help
I flashed JM5 and now my phone boots fine again. Later I tried to flash JS5 but I got the same problem again! What am I doing wrong? And which is the latest stable firmware that I should flash to?
Don't tick repartition in odin when you upgrade to JS5
Thanks for the quick reply. The update went fine
Hi all,
EDIT: After many false starts and some nervous near-brick experiences, I managed to solve my problem with one of the simplest solutions I hadn't thought of: Heimdall. I just extracted the tar file then dropped each individual file into Heimdall and reflashed the Tab and it is now back from the dead, ready to be reflashed.
After my GT-P1000T started having some unexplained slowness and FC's, I thought I would flash it back to stock before upgrading to the newer Overcome ROM. So I wiped my Overcome 3.0.1 Jupiter Tab from Clockworkmod and then plugged it into my 64-bit Win7 machine to try and flash it back to stock. Dropping the necessary JQ1 files (including the TAR, PIT and Modem files) into Odin with all options checked .
Unfortunately, Odin gets quite a way into flashing factoryfs.rfs and then throws a FAIL! message and the Tab restarts to the weird phone-triangle-pc icon on-screen at which point Odin re-recognises it.
I have tried toggling re-partition, rebooting the Tab, rebooting the PC, changing ports, redownloading the files and running Odin with admin privs, all to no avail.
Anyone have any ideas on what I can do to get back to working condition?
Do a search for Telstra rom galaxy tab, reflash that to see if it works. Then retry flashing gb...
Never had trouble flashing but I generally restock the telstra rom first....
Cheers...
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.