Hi,
Has anyone been using froyo (JPK, JPM) on the i9000m (Bell version only) for more than 20 days without issues.
If so what is the batch number on the sticker under your IMEI. 08/10, 09/10 etc...
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks
Same here, sd problem with JPK but cant tell S/N since phone got swapped.
Also looking foward for a froyo that do not mess with internal sd
Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.
rdenis said:
Your problem is not Froyo. Internal SD issues are unrelated to firmware.
Any Froyo + Bell modem works just fine. There are other modems with 850 support that work just fine too.
Click to expand...
Click to collapse
My SD dissapears once in a while - i just reboot it and it comes back
is this happening to everyone ?
I had an issue where I restarted my phone and everything was erased. The SD card was still recognized. I had to reflash my phone with Odin to get it to work again though. Even the factory reset in the boot menu wasn't doing anything. I think it had something to do with the OCLF.
I've been using it for about 15 days or so now without OCLF and everything works fine.
Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks
juinny said:
Just wondering if there's a video on how to install Froyo on the i9000m. All these posts about corrupted internal SD is making wonder if it's worth upgrading to Froyo since it looks like it's pretty risky. Worse is I'm a noob and I've got a bad feeling about doing it myself without any help from a video.
Thanks
Click to expand...
Click to collapse
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.
mattomatic said:
If it makes you feel any better, my i9000m corrupted itself, despite not having been rooted, not running any lag-fix and running the same ROM out of the box...I managed to save it by combining a bunch of tips I found for people recovering from a bad flash.
Click to expand...
Click to collapse
Okay. So you're saying the phone itself is just badly manufactured? I was really hoping that froyo will fix all this awful things. I'm also having trouble connecting to Kies. Is Froyo for the i9000m out on Kies yet?
Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.
This I9000M SD thing is a hardware issue. If you have a phone from a bad batch, you'll eventually succumb to the SD card issue regardless of what firmware you decide to use. People have even experienced this without ever flashing/modding anything. If you have a good phone, froyo or any other firmware for that matter will be fine.
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M
MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Click to expand...
Click to collapse
i too bought mine on launch day, and i just sent it in for repair last week, so don't count it "safe" just yet.
MaestroSeven said:
The question is how long till you know you are out of the woods?
I bought my bell galaxy s on launch day and have had no issues with the sd card. Does this mean I am worry free? So that was back in August.
Also shouldn't there be a recall if this is happening to so many people?
Sent from my GT-I9000M
Click to expand...
Click to collapse
I bought mine in early August on launch weekend, and my SD card died this past weekend, even though I had never flashed any new roms.
I had to send it in for repairs.
kmkarim said:
Hey,
Ive been running froyo stable on an i9000m for a month now using the kies reg. hack that was available a couple of weeks ago. Have had 0 problems.
Click to expand...
Click to collapse
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?
15 days with doc's rom with lagfix ext4 no rfs
Funkadelick said:
What registry hack ?
do you NEED to do a registry hack to get the official 2.2 froyo on your bell i9000m ?
if so, why ?
shouldn't we be able to upgrade officially without having to resort to hacks ?
or are you using this hack in the case that the official upgrade isn't out yet ?
Click to expand...
Click to collapse
Currently there's pre release (dev roms) available via test mode on kies. It is in no way final but still pretty stable
rumy said:
The reason I ask is coz bell swapped my phone due to SD issue and I donot want to rebrick it.
Thanks
Click to expand...
Click to collapse
Just play and re-brick it. If it's going to fail it will fail and there is nothing IMO that you can do about it. If it needs to go in 5 times then so be it. I bought mine on a visa doubling the warranty. My guess is it will be going in at least 5 times unless they "actually" fix the issue which I doubt.
Related
Anyone else having this problem? Any time I try to move an app to SD it just sits there for a little bit and then reboots. I can't update google skymap because I think it's trying to install on the SD too.
I tried searching but my search-fu is weak in this case. I did find someone in some other forum saying he had this problem but it seems to have gone unnoticed.
Anyone? Bueller? Not even a "apps2sd works for me wtf are you talking about?"?
Apps2sd works for me wtf are you talking about?
How about some details?
AT&T or T-Mobile Nexus One?
Bootloader locked or unlocked.
Rooted or unrooted
Stock FROYO? FRF50? FRF72?
What radio?
Using custom cooked rom?
This is me: AT&T Nexus One, unlocked, rooted, official FRF72, apps2sd works just fine, wtf are you talking about?
I'm having this problem too. I suspect it's related to having used cyanogenmod's a2sd for the apps in question - your thoughts on that?
I'm currently running frf50 on an unlocked t-mobile n1. I used someone's pre-rooted Rom. I was running cyanogen 5.0.7, used apps2sd once but decided to undo it and did a nandroid restore. I didn't do a wipe so I'm going to try that and see if it makes any difference.
This is exactly my situation, I suspect even the same pre-rooted froyo (Paul's). Let me know if the wipe helps, and if it does... how do you recover all your stuff?
paulvallee said:
This is exactly my situation, I suspect even the same pre-rooted froyo (Paul's). Let me know if the wipe helps, and if it does... how do you recover all your stuff?
Click to expand...
Click to collapse
So I wiped my phone last night, and everything seems to be working now. Started up my phone, logged in, and all my apps started reinstalling. I used SMS backup & restore to restore my SMSs, and everything is mostly back to normal.
How are you moving apps to sd?
I have the exact same problem as the op describes.
Running frf50 on a T-Mobile N1 that I updated the day that build leaked. Not the pre-rooted version I don't believe.
I'd like to figure out exactly how to fix it since from time to time my phone will tell me it's low on space and I end up having to delete several things.
I'm gonna be blunt and say anyone who doesn't want too root their phone really should not be running leak builds of an OS either.
You're just asking for trouble, and without recourse to fix it.
wrong topic
1st A big Hiiii from India.
I am a noob in this android scene. The most closest experience I have had to this is moding PSP's(done so many can't count) bricked and unbricked as well.
I got my SGS this week and the first day itself i started to see how i can make it better.(had seen a lot of vid in youtube). Some problems i faced initially was:
1. the 3 key hold to go into recovery mode just wont work for me so i used the easy reboot recovery script.
2. Intially i tried a couple of roots which would give me errors like it failed to run. The phone came with DDJG4 and i was able to get Superuser 2.3.1 was able to update SU database to V5 from android market.
3. Installed Ryan ZA lagfix 1.6.0 from market and now I am able to get a quadrant score of 2172. Earlier it was around 900.
What I want to do now is to have 2.2 froyo on it. I want feedback as well as help. Feedback as in is it worth it? How do I goto 2.2 custom and which one? where do i get rom and which custom one to go for. I have been seeing so much of stuff on the internet that i am a little too much confused. All help appreciated and thanks for your post.
DO NOT INSTALL FROYO! you will brick or have problems. Read all the people who installed Jpc and prev betas. Seriously. Im sick of people asking for help after installing froyo who have not done their research as to how much problems it has. Also your phone had download disabled. If you screw up there's nothing anyone can do other then tell you to get hair dryer and heat the thing up. Also don't ask me about that as im not stupid enough to install unofficial froyo
Sent from my GT-I9000 using Tapatalk
DDJG4 is gr8 .. dont try to install any Froyo build as of now.. i have tried all and have experienced a lot of issue and reverted back final to DDJG4 ... wait for the official release or mess things up as u like.....
dewimagica said:
DDJG4 is gr8 .. dont try to install any Froyo build as of now.. i have tried all and have experienced a lot of issue and reverted back final to DDJG4 ... wait for the official release or mess things up as u like.....
Click to expand...
Click to collapse
how to revert back to DDJG4... cant find ne thing...
Alright folks i am so sorry had been away! I am really sorry i did not check the posts however was really restless to see flash 10 so I ended up using odin to get into I9000ZSJP2 I used paul's rom with clockwork mod from modaco.
It was real laggy and the ryan fix also dint help much. So I downloaded the OG DDJG4 as well as I9000XXJPC. Wanted to give one last try as had seen a lot of youtube vids of it being the most stable one out there.
Frankly it worked like a charm. I used it for couple of days it had all the features working. I even rooted it the way told in xda here. by using odin and couple of files. I restarted it many times and had no issues.
Suddenly this is the problem when i switched it off to switch my sim. The phone starts goes to Galaxy S logo and stays there for like 2 mins and then it goes black.
None of the recovery mode combo and download mode combo work for me hence I had to use script.
The script also dont work now over USB. I tried removing sim and sd card. How do i get back to JG4. all help appreciated. I am sure i am not going to froyo until final build if i get this fixed.
ickyboo said:
DO NOT INSTALL FROYO! you will brick or have problems. Read all the people who installed Jpc and prev betas. Seriously. Im sick of people asking for help after installing froyo who have not done their research as to how much problems it has. Also your phone had download disabled. If you screw up there's nothing anyone can do other then tell you to get hair dryer and heat the thing up. Also don't ask me about that as im not stupid enough to install unofficial froyo
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
ok i had froyo jpc and then easily went back to eclailr build because of bugs and then went to the hk jp2 which i love. yes he can have issues but bricking the phone is hard with odin if you follow the instructions
I dont think mine is brick eh! i can still turn it on. Its more like a no boot. Brick is a no post
I tried both JP2 and JP3 and they were OK at best since they were in early beta and inspite of speed, they were unstable and very unstable. I would say they are good to play around a bit but definitely not for daily use.
If you still want to get your hands wet, you can try Doc's RomMod Froyo V2 + Superlite (I9000XXJPC) 9/9/10
But as every one is saying already, stick to the current ROM and wait for an official release from Samsung.
Just don't forget to install a lag fix.
And don't worry about bricking, it's very hard to brick your phone, so go ahead and give a try and play around to know your device better.
Enjoy the SGS!
Thx mate.. needed some emotional support on this one.. well i have to report officially I could not get my phone working and recognized by Odin. The guys at samsung service center also gave up after looking at it for 30 mins. I have to say.. they knew less than I did about the phone. I have said its less then 7 days so either they fix software of I replace the phone. Thats how it works in india and guess what I went on the 7th day I read a lot of peps here sayin if the phone does not go into recovery or download by key combo it is getting replaced. I am going to post soon what happens. Until then keeping my fingers crossed and prayers.
PS: another guy in my office has SGS and he is able to go to recovery and download so its not like an all india thing.
I got my phone back last week they replaced it with another one with JG4
Which City do you live in? I have a Bricked phone and I am thinking of getting it replaced.
dhiru1602 said:
Which City do you live in? I have a Bricked phone and I am thinking of getting it replaced.
Click to expand...
Click to collapse
I am from HYD.. Btw I found a way to fix the non three button fix from the forum itself.. i just fixed one of my friend who had the recovery mode hold not working.. ova the weekend..
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
JP2
JP3
BOJI
HVJHI
GJH2
JM2
JM4
XWJM5
JM7
JM8
UGJH2
1.20Ghz Kernel
Bad:
JPC
JPH
(possibly caused by One click lagfix)
To keep 850mhz radio
Modem: http://www.mediafire.com/?qic38waf8px13mz
CSC: http://www.mediafire.com/?7ow6p25nhzle5jo
JPC worked fine on my Bell Vibrant. Any of the international firmwares will work without any issues short of the issues inherent in the firmware already.
That was my understanding as well, but many people and all of the seem to have Bell Vibrants are getting corrupt sd cards from JPC, which basically bricks the phone.
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Fuzz21 said:
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Click to expand...
Click to collapse
No exactly what this thread is about sorry.
I also have a brick sent back to Bell/Samsung for repairs due to JPC.
I'm pretty sure any other firmware is fine. I had the HK JP2 installed without issue. Other than that I just stuck with the UGJH2 as it's nearly as new as any of the international firmwares and runs smooth, even without a lagfix.
mafiaboy01 said:
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
HK JP2
JP3
UGJH2
Bad:
JPC
JPH
Click to expand...
Click to collapse
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
For me and some others JPC did it :S
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
JPC ran like garbage on mine but no major issues aside from the lag, JPH though has been a champ for me thus far.
Sent from my GT-I9000 using XDA App
we need to pin down as to what caused these SDCARD errors so we can all avoid that.
I'm thinking maybe repartitioning with the wrong pit file might cause something like this ?
I'm using JPC on my I9000m now, working nicely (some lag here and there, but nothing AutoKiller can't take care of), and since I saw the post about the SDCARD error on one of the i9000m, am a bit hesitant to flash JPH.
Problem is, if it does get bricked, its basically paper weight because am in the US and doubt Bell or Samsung US/Canada would be willing to help.
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
mafiaboy01 said:
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
Click to expand...
Click to collapse
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
JPC messed mine with no lagfix installed. This has been ruled out in several threads on xda.
Sent from my I7500 using XDA App
it is also highly likely that us bell users are flashing with bell modem so that we can keep 850 out of the box and is root of the sdcard corruption.
for some reason i remember having nexus one that every firmware and mod always strongly warned that froyo modem is required as well as flushing dalwik cache right after upgrading from éclair.
and here most of us are doing just that using jh2 with froyo.
well as for me i know i wont be upgrading to froyo as long as this thing with sdcard keeps happening as my 30 days was up on sept 9 so no more DOA and even if under warranty still not willing to be without the phone for more than a month.
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
mafiaboy01 said:
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
Click to expand...
Click to collapse
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
madmack said:
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
Click to expand...
Click to collapse
Yes I did use OCLF, I only allocated the default so something like 800mb.
Sent from my GT-I9000M using XDA App
All the ones bricked, were you also having issues with the 3 button recovery? Trying to see if there is any connection there.
I'm reading around regarding this error, and it seems some guys with other phones and the same error got things running back by using Parted. You basically boot into recovery, push Parted to the bin folder, and then repartition/format that failed block: mmcblk0p1
I'm not sure what the file system currently is on that block, but the guys I got this info from were formatting it to ext2. I think if we modify it to match the filesystem that our ROMs require, then we're good. It's a long shot though, and if anybody has a bricked phone with them now, they could give it a go before sending it back for repair.
I used kies yesterday and upgraded to UGJH2, don't remember what it was before, whatever was factory loaded but now I am having all sorts of problems that I did not before.
GPS is way out of wack. Phone freezes. Signal disappears. Right now it's running smoothly but all day it was going retarded.
I give it a bit, if it doesn't sort itself out by the time froyo rolls I'll be flashing this sucka.
Thanks for the heads on good roms.
Hello Experts,
I'm looking for some sort of check list when I receive my phone to ensure that my phone does not brick again or that I have a solid phone at that.
What sort of things should I be looking for in terms of firmware date, what type of firmware is installed etc?
Should I be seeing JL2 on it? Should the date be 10.12 or higher? Should I ensure download recovery works? etc, ,,, Does anything else come to mind?
Previous phone was an unlocked Bell GT-I9000M with stock JK4 installed, Froyo 2.2, rooted with lagfix. No other custom roms installed.
Thanks in advance.
You might want to tell us 'how' you bricked it?
sturmeh said:
You might want to tell us 'how' you bricked it?
Click to expand...
Click to collapse
Updated the phone to Froyo 2.2 via keis.
Rooted it with SuperOneClick
Installed OCLF.
That's it. Worked great for 3 weeks, then noticed some force closures occurring. Reformatted the phone, pulled down all my apps from myroot backup. Updated all the apps that I had installed. Apps kept crashing and FC's still occurred. Pulled the battery, restarted the phone and that was it.
I curently have a bell i9000M I was running Doc's JPY for a few months but decided to his JS8 version the other day. As soon as I flashed it I noticed my phone was unable to install apps and in manage applications it gets stuck on computing.
So things I have tryed to get this working again........
Flashed EZbase using re-partition , still same issue on base.
Flashed Stock JH2 , still same issue.
Flashed Stock JL2 still same issue.
Flashed JH2 then JL2 through Kies same issue.
It seems I can not write to my internel SD although the rest of my phone seems to be working fine any Ideas?
Another thing I noticed is mass storage is not working on any rom only can connect using Kies method if I want to transfer files. Format internal SD is not working , it asks if you want to format you click yes it seems like something happens but then check the internal sd and all the files are still there.
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
azzledazzle said:
I am not familiar with the I9000M but i know its very common to have SD card failures.
And it seems to me thats whats happened, im sorry for you
best thing you can do is, flash back to stock and send off for repair, hopefully you may get some luck with the next device.
One thing before you get all emotional have a look at this, its a long shot but......http://forum.xda-developers.com/showthread.php?t=905975
Click to expand...
Click to collapse
Yea I was not getting any mounting errors in CWM or 2e/3e recovery...Anyway after a frustrating 3 days I now and I think it's finally working , so far.
I manually deleted all files off the internal SD, then did a format from within 3e recovery while on JL2 (this was acting like it was formatting before but all the files I downloaded were still there after the format). Then flashed Hardcore's K13 and installed a custom rom all seems fine so far but it did work periodically over these past few days so I'm hoping it stays working now.
What was weird is I could download files using the web browser but the market would not work all the time but when it did it was downloading the items but would just get stuck installing them.
Anyway thanks for the quick response. Hopefully I have this sorted out now.