So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .
what about adb ? Did tried it ?
a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair
bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen
workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.
I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.
Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks
I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.
Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.
Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Isn't there a way to try and access internal sd card?
Have you try doing a factory reset?
Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/
terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App
Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
This has happened to me, I just flashed with an older version, for me JM5 worked fine.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App
I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?
Hi Guys,
Here's some history on the phone:
- Purchased in Aug 2010, came withJK3 (not sure but it was ECLAIR)
- Since then the phone has been performing unbelievable, I had put several ROMs on the phone custom and stock as well as multiple kernels to fix battery drain, etc.
- A few days back after flashing Hamster's 6.3 ROM (which I had been using for a month prior, thus is completely irrelevant to my issue - find it here), I tried to access an app I had recently used when the phone completely froze on me, even power button would not respond; so I did a hard reboot only to be greeted by the cwm recovery window notifying me that the FS partition had changed and what I would like to do.
Knowing I had not changed anything, I simply picked "remove new configuration and boot phone"
Thats where I crapped my pants, the phone would reboot itself every 2 seconds and would not go past the first samsung boot screen.
I tried everything without luck, when finally 2 days later with special thanks to the following people listed below I found out exactly what's wrong with the phone and how to actually get to recovery and get a working boot on the phone.
I tried many many combinations of ROMs and kernels through ODIN and nothing seemed to work, initially I could get past the first boot screen if I re-partitioned with 512 and flashed JM8, but even that stopped working eventually. Finally late last night, I got the phone to boot. Here's what I did:
re-partition the phone with 803
Flash the phone with stock JLU (you will need the complete ROM with PDA, PHONE and CSC files)
Flash JPY
FLASH CF ROOT
FLASH SPEEDMOD kernel k12j
After the final step above you should have working recovery with adb for the first time! so now try the following umount commands and if they work then you are okay and do not have a dead sdcard/controller
Code:
umount /dev/block/mmcblk0p1
umount /dev/block/mmcblk0p2
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
Thanks to codeworkx for the above commands. If you try the above and they dont work or recovery shows the errors such as:
E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
or cannot mount SD card
then most likely you have either a bad internal SD or bad controller.
Regardless, your phone should now boot. if you can mount your SD card, you should do a complete format in windows after running the commands above; otherwise you still will not be able to access your internal SD and even though you can boot, your data will be lost after each boot and you cannot download anything from market or update current apps.
-------------------------------------------------------------
So now, I have a phone that boots up and works but cannot mount internal nor external SDs, here's the error dmesg gives in this regard, which again codeworkx helped me disect out of the logs:
Code:
"mmc0: error -110 whilst initialising MMC card"
I recently opened the phone up to try and see if I could find the location of the internal SD and to my surprise it only took 5 minutes and a little help from diagrams at phonewreck.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I know where the internal SD is, but no clue where the controller would be and whether its even possible to replace or any otherway to get the data back from the current internal SD which MAY still be okay in my case...
Any help with this would be appreciated - at this point im willing to try anything.
Thanks and if you have any questions feel free to ask.
People to note and thank for spending hours with me, walking me through what they know: virnik0, Jim_Panse, codeworkx, Josaatt, uppon2 & eitama - thanks guys!
that's what they do when you send it back in for repair
they just replaces the damaged PCB with the internal SD
usually error code 303 or 330 something like that
Just an update here.
My "Brand New" replacement from Bell - mk 10.11 just had the exact same failure as above, running stock 2.2 with absolutely no mods.
edit: phone came this way from bell/samsung | last thing I remember doing on it was loading google maps, then it started rebooting... and would boot up to JL2, and after 10 seconds of usability would reboot again... I could still see the internal and external SD... through recovery and adb, all the files were there...
after that happened, I decided its time to flash a custom rom, and at the first step (repartitioning + JM8/JM4) phone went to the infamous boot loop and thats that.
Did you upgrade to UGJL2 via kies prior to installing 2.2.1? If you didn't, or if you did it in odin without ticking "phone bootloader update", that's your problem. There's a problem with the I9000m 2.1 bootloaders wear control on the sd card. If that's not updated before going to any 2.2 or 2.2.1 firmware, you're phone is going to die.
Sent from my GT-I9000M using XDA App
I did not touch the phone, it came with GJL2 on it 2.2 - that's what I had on it.
@tekkneak,
Firstly... Your first phone that you bought in August did NOT have JL2 firmware on it as JL2 is a FroYo firmware and did not come out until late December 2010. The firmware you had on your first phone was probably JH2 which is Eclair.
I bought my i9000M in August 2010 (on the 30th of the month as a matter of fact) but mine came with JG9 Eclair and I had to upgrade to JH2.
This being said and since you mistyped the firmware version in your first post, are you sure that your NEW phone diddnt come with JH2 and NOT JL2? If this is the case then Electroz theory would hold true.
It has been said by both Bell and Samsung that the JL2 Froyo firmware has a new .SBL file that fixes the crashing internal SD cards.
This being said... IF your new phone did have JL2 FroYo on it and it crashed and gave you the internal sd card failure then I would say that for your phone it was a LEGIT hardware issue.
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
I feel where you are coming from for sure. Yes... You would think that these issues should have / would have been fixed by now but... The general concensus regarding failing internal sd cards is that the MAJORITY of the failures were due to a software issue and NOT a hardware issue. That being said, as I mentioned before... Bell and Samsung have stated that the JL2 Firmware with the new .SBL Bootloader File has fixed the "software" issue that was causing our devices to suffer internal SD failure so that is why I am assuming that your new phone may actually have fallen prey to a TRUE "hardware" failure in which case there is no remedy other than to have it replaced or repaired.
For example... Last night I had flashed my phone with a few different files and it "soft bricked" to the point where I was scared that it was my internal sd card too. It would hit the Samsung animation screen, vibrate once, go black screen with the buttons lit up then vibrate with three small bursts. I could go into recovery and download mode no problem and I did NOT see any error message in recovery so what I did is a Factory Reset from recovery and it rebooted just fine.
I lost my contacts and apps but not my phone. Perhaps try a Factory Reset from recovery and see what it does if you have not tried already.
In any case... I wish you luck...
tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
It's probable that whoever update the phone to UGJL2 just forgot to hit the Phone Bootloader update option in Odin as well. After all, Odin is Samsung software released to their tech's. So, something that simple could have done it.
As one last chance, download UGJH2 and UGJL2 from Samfirmware.com and use Odin 1.7, no pit, no repartition.
Flash UGJH2 first, without bootloader update is fine..
Then, after that is flashed, go ahead and flash UGJL2. Make sure to click Phone Bootloader update.
Give that a try and see if it comes back to life.
Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?
packers17-0 said:
Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?
Click to expand...
Click to collapse
What error are you getting in recovery?
Samdroid_G_S said:
What error are you getting in recovery?
Click to expand...
Click to collapse
When i run the report error option in the "advanced ClockWorkMod features" i get this:
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0"
I've been reading that some people have been able to mount and or format their internal sd cards by using the adb console but I'm not really too familiar on how to do this. Anyone had any luck fixing this?
packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky
tekkneak said:
packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky
Click to expand...
Click to collapse
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks
Yes, they will accept it, I did not have it for my phone, they checked when it was sold on their system and said I still had 7 months of warranty left.
Tekky
packers17-0 said:
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks
Click to expand...
Click to collapse
This Bell I9000m that this wonderful place helped me figure out how to toss CM7 Nightly into Just had a melt down this past week I need to figure out if I'm boned or not.
I was pulling my media off the internal SD card with Teracopy the night before it all happened in usb mass storage mode and ever since the data was pulled. Icons on my desktop would only start displaying AndroidMarket like logo's and not launching anything. So i would reboot the phone to see if it was just acting silly and it would only get worse.
So I tried factory resetting and clearing all the cache's via CWM bootloader than load the OS to no avail the system simply stopped booting so I tried installing via zip the original nightly that I had left on the internal SD that was a signed release... The install didnt pass the signature check.
At this point I've just put trying on hold to come and ask around here. Am i screwed or am I just around the corner from having my damn phone back.... again .... I need ideas or solutions to this problem.
***UPDATE***
Bell has sent the phone back with the note on the file, "Replaced Major Component" I cant even begin to imagine what that means. Besides everything is apparently less broken? Although i was recording a meeting in full 720P and it decided to randomly stop recording at 47 minutes without any apparent reason.
If anyone reads this and comes up with any ideas as to what may be able to be done let me know please.
I'm trying EZOdin and easybase but the format does not like to work regardless of the PIT file i use it never seems to play well. But im guessing its probably a good idea to start fresh.
Try regular Odin and see what it says but if you internal SD is hooped it will still flash but it won't boot. You are trying the EZbase Froyo 3 part file with pit?
You could try a stock rom also but note you may need to add a DBdata file to the stock rom if you repartition as you need a db data file and it is not included in jl2 or kc1. I guess kies used the existing one from eclair and that is why it is not there.
It sounds like it could be a dying SD card (especially the heavy file use just before issues started). Have you ever had to replace your handset yet?
G
Bell has had my phone for service twice the first time they charged me 60$ for some reason and the second time they did not.
But both times they just reloaded the phone and returned it to me even though both times were similar problems its like they're just trying to avoid having to deal with giving me a replacement.
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...