Hi everybody,
I've got a friend's I9000M (Vibrant) and needed to upgrade its Froyo OS.
As I'm used to CM9, I started the Full Update Guide as described in the wiki. First I followed [1], by mistake, and flashed a I9000 kernel (hardcore's) into the I9000M using Heimdall (having the phone in Download Mode). It didn't boot up, of course. I was stuck there for a while until I realized that I should have been following [2].
That kernel, cmenard's booted up ok. But then I realized that I needed the CM9 zip in the INTERNAL card (I had it on an external card, as I'm used to other devices). So I had to go back to a stock Froyo ROM.
I looked around for a while and the best I could find was XWJSD (I don't know which firmware revision I had installed before). That kernel booted up OK, seemed to work, so I copied the file to the internal card. Just in case, I tested if it worked as a fallback, so if I screw up I can go back again. WiFi was not working. Everything else seemed ok.
After I flashed cmenard's firmware + CWM, I found that Recovery mode can't mount any partition (only system, no data, no sdcard) [3]. So I'm stuck and can't install CM9 from SDCARD.
So it seems that I can only flash Heimdall-packaged firmwares. I looked around for other alternative ICS / JB ROMs, and the only ones I found weren't Heimdall-packaged. They needed to be installed via Recovery.
So,
1. do these mounting errors mean I fried the internal card? can they be solved?
2. is anyone aware of an ICS / JB ROM packaged in a way Heimdall can upload?
3. do I have a way to know what stock Froyo firmware will work best with this phone?
4. regarding the WiFi issues, does that mean that I need a different firmware or can it be fixed?
Thanks in advanced, any help is much appreciated!
P.S. I looked around the forum but couldn't find answers to these question. If these are asked elsewhere, then I apologize/
-- nachokb
[1] (I can't post outside URLs) the "Samsung Galaxy S: Full Update Fuide" article in CyanogenMod's wiki
[2] (I can't post outside URLs) the "Samsung Vibrant: Full Update Fuide" article in CyanogenMod's wiki
[3] video of CWM Recovery errors: (I can't post outside URLs) Youtube Video ID t2VBt7TsohM
I would ask around the I9000 thread. If you flash any of these ROMs, I think you'll be asking how to fix your friends phone...
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959.
sent from the depths of helly bean
Toast6977 said:
I would ask around the I9000 thread. If you flash any of these ROMs, I think you'll be asking how to fix your friends phone...
Click to expand...
Click to collapse
I wondery why, given that this phone is a I9000M. I flashed a different ROM for a while, but after that I flashed a stock ROM and it worked OK.
Thanks!
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959
Click to expand...
Click to collapse
Is the T959 somewhat more resilient to internal card damage?
I doubt it, the phones are nearly identical.
sent from the depths of helly bean
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959.
Click to expand...
Click to collapse
Just to be sure: this is a Bell I9000M, not a T-Mobile SGH-T959.
I just flashed stock XWJSD. It almost worked. System looks fine. Internal SD Card is fine - NOT toasted :good: (I even could access its previous contents).
Sadly, no WiFi (can't obtain IP address, keeps trying) and SIM locked (!) so no calls and no 3G . So, I'm holding a nice brick in my hands.
I've been trying to flash UGK3G, but I don't know how to flash its 3 files (CSC, PDA, PHONE) with Heimdall, and every forum post or tutorial says something different. Almost giving up here .
Thanks for your answers anyway!
-- nachokb
Related
Hey folks, heres a synopsis of what I did:
1) Stock Bell Vibrant, rooted.
2) Installed Clockwork, installed, backed up.
3) Tried to install voodoo for vibrant.
Then during reboot, it sat at the "Vibrant" screen for well over two hours before I gave up on it.
Pulling battery and rebooting always ends up on "Vibrant" screen.
I booted into clockwork recovery, and recovered my backup using nandboot. It runs the process for a while then outputs:
ClockworkMod Recovery v2.5.0.4
Checking MD5 sums...
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk0p2
(File Exists)
Can't mount /data/!
If I reboot, I'm stuck at the same "Vibrant" screen.
I've been searching the forums, and the only solution I can find is to re-flash, but I can't find a stock bell rom for the galaxy s... I was under the impression clockwork backed up my original rom.
Anyway, any help you can provide would be great!
Thanks
Shado
You need to learn how to use Odin if you are going to mod your phone with beta software.
You can use Odin to reflash your device to stock. From there you can start over or skip it. Since you had problems with Voodoo make sure you follow the instructions with the addition of checking the "repartition" box.
Check this thread for instructions on Odin: http://forum.xda-developers.com/showthread.php?t=748074&highlight=ODIN
Youtube tutorial: http://www.youtube.com/watch?v=AnY7P14JSWQ
I agree odin is a lifesaver for most ppl here, and it doesn't hurt to learn something new
I've not installed Voodoo yet, but I read through the thread yesterday and If i remember correctly when Voodoo BETA creates it's EXT4 partition it was actually formating the internal SD card. Deleting most of the data, which would include backups. It seems as though people were using Eugine's 2.2 Froyo Rom then going back to there original nanbackup by moving over a backup that they were smart enough to store on their pc. This is all verbatim, and straight from memory. Start at page three and read on if you havn't yet. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=781456&page=3
I love xda and everyone on it!
When I was waiting for a reply I found samsungfirmwareworld and grabbed I9000UGJH2 which was the latest Bell firmware, and I also found the 512.pit.
Following the instructions on that Odin instructions link got me back to stock, and avoided any major medical problems (like heart attack, stress induced coma, etc.).
Thanks so much!!
Now that I'm back to stock firmware, is it ok to re-root, install clockwork, and restore my backup I made pre-voodoo? I did copy the entire clockwork folder from the phone to my PC.
shadoslayer said:
I love xda and everyone on it!
When I was waiting for a reply I found samsungfirmwareworld and grabbed I9000UGJH2 which was the latest Bell firmware, and I also found the 512.pit.
Following the instructions on that Odin instructions link got me back to stock, and avoided any major medical problems (like heart attack, stress induced coma, etc.).
Thanks so much!!
Now that I'm back to stock firmware, is it ok to re-root, install clockwork, and restore my backup I made pre-voodoo? I did copy the entire clockwork folder from the phone to my PC.
Click to expand...
Click to collapse
You do know that the Bell Vibrant is an sgs i9000 and NOT the same as the t959 vibrant for t-mobile that this forum is solely for/about, right?
And yes, you should be perfectly safe to restore your clockwork folder and do a nandroid restore.
Cheers,
=)
~ Jocelyn
s0niqu3 said:
You do know that the Bell Vibrant is an sgs i9000 and NOT the same as the t959 vibrant for t-mobile that this forum is solely for/about, right?
Click to expand...
Click to collapse
Yeah, I figured that out over the course of this whole process. I guess just because they share the "Vibrant" name, doesn't mean they're the same. Given the large number of Bell users here, I'm surprised we don't have our own forum for the i9000m. Would it be more appropriate to post in the i9000 forums, even though the Bell phones (from what I understand and firmware wise) are far from their European counterparts?
Either way, for having these problems and potentially posting in the wrong forum, you folks have been great
I have the same problem but i cannot get the samsung usb drivers to work. please help
@shadoslayer... i'm not really sure but i think the only diff between the bell vibrant ang the international i9000 is the hspa bands since bell vibrant has north america hspa.
except maybe for the few that do not have the 3 button combo.
btw, i'm using a bell phone too, on JM7 firnware.
Sent from my GT-I9000 using XDA App
Clearly I'm an idiot and get over excited. I now need to find the stock Bell firmware to use with Odin so I can go back to normal. Any Canucks with a link to it?
EDIT: I got it back to Bell's stock firmware.
So we can't use what other odin post is using for the i9000m bell vibrant?
How did you get it back to bell firmware?
beowolf said:
I have the same problem but i cannot get the samsung usb drivers to work. please help
Click to expand...
Click to collapse
Download kies
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Hi Guys, I've have been very confident about rooting and flashing ROMS on different Android Phones because of this Forums but I'm stuck with this Korean S2 that I've flashed a MOD ROM to. It's an SHW M250S and unfortunately I've bricked the internal storage of the phone during hack. I thought that this was the issue why whenever I flash a ROM it will eventually crash. It'll turn-on and boot-up okay (though sometimes it initially gets stuck on the CM logo and I have to reboot the phone to reach the Set-up wizard) but when I start installing apps it'll eventually stop responding and then crash, it will still start up but then it will crash again immediately. And when I say crash I mean i get stuck on a particular screen, it'll eventually goes black (notification bar still visible) and the only way to get it running again is to restart it. I tried Multiple Mods JB and KK and Stock 19100 Roms but i had the same result. The last thing I tried doing was swapping the Internal Storage with the SD card and I though I had it fixed but still same issue remains. Please Help Guys.
There's a "how to" thread on converting Korean s2 into i9100. You can find the thread in the general section. It involves flashing a pit file and stock i9100 ROM. The info works as I have 2 of the same model you have and I've converted both. Good luck
hawaiisteve said:
There's a "how to" thread on converting Korean s2 into i9100. You can find the thread in the general section. It involves flashing a pit file and stock i9100 ROM. The info works as I have 2 of the same model you have and I've converted both. Good luck
Click to expand...
Click to collapse
Thanks, I have already done that though, i've flashed the original pit file from that thread and then an original stock rom, that's where my problem started actually. I also tried the pit file to unbrick the internal storage and was successful in doing so, as far as i can tell, but still the phone crashes. Funny thing though, it only crashes now whenever I start restoring apps from google play. If I don't install anything, it works okay... so far.
pinoymark said:
Thanks, I have already done that though, i've flashed the original pit file from that thread and then an original stock rom, that's where my problem started actually. I also tried the pit file to unbrick the internal storage and was successful in doing so, as far as i can tell, but still the phone crashes. Funny thing though, it only crashes now whenever I start restoring apps from google play. If I don't install anything, it works okay... so far.
Click to expand...
Click to collapse
Ya, you have a strange situation. You might want to try flashing a dorimanx kernel and use the partition check and repair in stweaks. Maybe you have corrupt blocks...just a guess...
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Kari458 said:
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
Click to expand...
Click to collapse
Yup
cyril279 said:
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Click to expand...
Click to collapse
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
I've raged on this device a time or three myself, I promise.
The most abnormal part of each of your posts is the battery involvement. You shouldn't have to touch the battery at all for recovery mode, download mode, or flashing, so I would guess that you're up against dirty or failing charge port, a near-dead or failing OEM battery, or similar issue which made your flashing journey more troublesome than it should have been.
There are several posts [like this one] about troubles using i9100 batteries. They fit and function, but exhibit undesirable charging issues, which consequently tend to get blamed on some other aspect of the device.
The symptoms of a dirty or failing charge port also commonly mis-direct users to blame firmware, batteries, and everything-else.
-Cyril
Kari458 said:
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
Click to expand...
Click to collapse