Hello XDA gurus
I am trying to upgrade my Samsung Galaxy II (Belgium)
from (gingerbread)
stock-rom : GT-I9100_XEN_I9100XWKK2_I9100XENKJ1_I9100XXKI4
cf-root : CF-Root-SGS2_XW_XEN_KK2-v5.0-CWM5
to (ics)
stock-rom : GT-I9100_XEN_I9100XWLP7_I9100XXLPS_I9100XENLP3
cf-root : CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5
I use Mobile ODIN Pro (also tried CWM5) with pre-root option and
flash goes well. Andriod got upgraded, applications adjested and I
correctly end up with rooted ICS (and no CWM5):
Model number
GT-I9100
Android version
4.0.3
Baseband version
I9100XXLPS
Kernel version
3.0.15-I9100XWLP7-CL340913 [email protected] #3
But the system is not running well at all, in fact, -whatever-
application I try, after some time (sometimes seconds, sometimes
minutes) the system abrubtly falls back to the Samsung splash
animation ending up in showing the "Swipe screen to unlock"
again. This goes on forever, that is: no application works without
problems.
With some patience and some luck I managed to install cf-root (I
think using Mobile ODIN Pro) and reverted back to my gingerbread
latest backup (using v5.4 CWM5), which has been running well for
several months now.
Then I retried the upgrade (using v5.0 CWM5). Same behaviour: no
activity runs without suddenly falling back to Samsung splash
animation. In fact, perhaps nothing is wrong with the apps, and the
problem is with the app launcher itself? For example if I choose the
ADW Launcher instead of the TwLauncher, I seem to have a slightly more
stable system (and I managed to install cf-root again).
Questions:
* Does this kind of Samsung Galaxy II gingerbread-ICS upgrade issues
ring a bell?
* Am I missing some obvious step to correctly perform the upgrade?
Thanks for any hint.
The easiest would be to download the desired firmware for use with Odin (not mobile) or Heimdall and flash it like this. After that do a factory reset in the recovery. Mobile Odin cannot flash bootloaders for example.
Thanks a lot TheSniperFan
Is CWM not able to flash bootloader either?
I have no windows computer (only linux) so I have no Odin (I could perhaps
find a friend who does have a windows computer).
I can use 'adb' from linux, would that allow to flash bootloader ?
And, is the problem really the missing (or wrong) bootloader?
also in the ROM I see :
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
Sbl.bin
zImage
is Sbl.bin the bootloader?
Have a nice day
No only Odin and Heimdall can.
You only have l Linux? No problem, I do all my Android stuff with Fedora. ;-)
You want the Heimdall suite. It's multi platform.
http://www.glassechidna.com.au/products/heimdall/
cool!
I did not know about Heimdal ...
just compiled it for my 64bit gentoo, let's see how that goes...
Hi all,
Not sure how but after almost 24h of looping into samsung splash my device is running fine now. Keep fingers crossed that next reboot will take less time to finish...
The first boot takes longer. After that it should be fine.
Btw, you should ask in the device specific forum, if it's a device specific problem though. You have much better chances to get help there. I only found this thread because I was bored. ;-)
being bored is a luxury for you and a blessing for me and others
I appreciate!
24h seems long for a 1st 'slow' boot
In fact, I rebooted and the 'samsung animation fallback' issue is going on for another new 6h or so.
I have patience and do not complain since I experiment to begin with.
I also know it will eventually be OK ... maybe today maby tomorrow
as a conclusion I guess something must be fishy with my specific setup
I could (as I did) wipe cache and data again but for now I just hope system will settle into usable state soon
btw: I do not know if I can post to device specific areas yet ... for now I am gaining points with (hopefully) relevant post attempts ...
You've meant 24 hours of continuous reboots?
That's really much longer than it should EVER take.
I'm wondering what could be the cause of this.
Besides that you can post in the device specific forum right away. You cannot post links in the beginning though.
I recommend you to see if this issue is still present now. If yes, I could guide you through some steps to determine if it's a wrong firmware or a broken device. Let's hope that it isn't the latter.
Nofan Tasi said:
btw: I do not know if I can post to device specific areas yet ... for now I am gaining points with (hopefully) relevant post attempts ...
Click to expand...
Click to collapse
You can post in the device forums, just not development forums, but since you're asking a question it should go in the Q&A anyway. You may get more help in the device specific area of the site.
Thanks all for the kind help
The reboot sequence is looping but not into -reboots-, what happens is that any running app abrubtly halts (usually in a few seconds) and the samsung aminated splash shows and brings me back to 'slide to unlock'. In practice I cannot finish any task.
All this might relate to heat. if I turn off device at night and next day (today) try booting again, still the issue is there but it stops eventually (say after 10 minutes, not 10 hours). Also: if I boot with wifi enabled, probability to have problems seems bigger.
have a good weekend.
One question:
What Galaxy S2 do you have?
I9100...?
Is there some letter after it like I9100G?
You see it when you reboot your device.
Your issues are NOT the usual issues that people around here have.
At the moment there are three problems I can think of, but you need to help me help you. ;-)
1. Firmware issue
2. Firmware for wrong Galaxy S2 (though I doubt that)
3. Faulty hardware
Do you have an USB-Jig?
Hi SniperFan
It's a plain I9100.
I have cleared
- cache
- dalvik cache
and done
- factory reset
All apps got reinstalled (and data from cloud sync-ed back)
System seems rather stable now.
Every now and then, only after reboot, I have the 'problem' again
(problem being that any app dies and samsung splash animation comes).
If wifi is off, this seems te happen less.
I must say: even with Gingerbread this would sometimes happen.
But never so persistent as it was this weekend right after ICS upgrade.
I guess clearing all and factory reset did help.
Once system is stable it stays stable.
Thanks for your kind support.
Related
Hello all,
To keep it concise:
Received my SII from Vodafone yestersday - all is well.
Proceeded to flash the phone with XWK37 firmware and rooted the phone by flashing chainfire's insecure kernel, applying root and then flashing the stock XWK37 kernel - have used Odin before and all is well.
By the time I finish playing with the phone it's 3.00am so I put the SII on charge (battery at around 30%) - all is still suspiciously well.
Get up at 7am to take my kid to school and when I get back I discover that the menu key no longer does anything when pressed (home key and return key still work fine) - it doesn't light up nor does it bring up a menu - all is not well.
So far I've tried:
Reflashing both the firmware and kernal - no effect.
Removing sim card, sd card and battery - no effect.
Hard resetting (both via button method and android privacy menu) / formatting sd card - no effect.
Dialling *#*#2663#*#* and updating the touch firmware - no effect.
Accused my wife of breaking my phone before she went to work - no effect.
Now If it's a hardware problem (which would be disappointing since I've only had the phone for 1 day) then I'm stuck since there is no stock UK Vodafone firmware available yet to flash back to before handing in for repair - plus I don't want to go back to using my N97 in the meantime.
Yes I preordered the N97 before it was released and got myself stuck in an 18 year contract - words can't describe how much I hate that worthless piece of Nokia - I kept it to teach myself a lesson, early adoptions don't pay off.
The only other relevant thing I can think of is that I was trying to install ADW launcher (previously used it a lot) before I went to sleep last night however although the phone claimed that it downloaded and installed - no icon appeared and I was unable to launch it although it's wallpapers showed up when I was switching my live wallpaper.
Can anyone help with any idea's of what it might be aside from a hardware issue?
If it is a hardware issue, anyone know when the Vodafone UK firmware might shown up?
Tell you what, I'll throw in a free N97 for anyone who solves the problem
Thanks guys.
K37 firmware ????
I would flash old firmware like WKDD .
Possible with pit and repartition checked if that failed . Not used either yet on SGS2 but always cleared SGS1 by that method .
jje
Thanks for the reply jje,
The XWKE7 is the latest generic XEU firmware available from this guide:
http://forum.xda-developers.com/showthread.php?t=1075278
I flashed it exactly as the guide stipulated.
However I didn't even think to try flashing it to a earlier version to see if the problem might be with the actual firmware.
Should be finishing work in a couple of hours so will try flashing the older XWKDD
firmware and see if that relocates the menu key.
Will update as soon as I know.
Damn.
No luck - tried flashing KDD (and also KE1/KE2 for good measure) accompanied by full memory wipes - still no luck. All these firmware files come in one .tar package which i place into the PDA section of Odin.
Even tried one where the pda, modem and csc were split into seperate files from:
http://forum.xda-developers.com/showthread.php?t=1075278&page=11
Still no return of the menu key.
When I am flashing - I leave the pit section of Odin completely alone and leave re-partition unticked - I take it this is correct?
It's strange because apart from the menu key - the S2 is working perfectly.
The only other thing I can think of is that the Vodafone branded version of the S2 in won't work with any other generic firmware which is pretty unlikely methinks.
jje - "...possible with pit and repartition checked if that failed.." - I didn't quite understand what you were recommending there mate - should I be using a pit file and checking repartition?
Any other ideas guys?
Off to go glare at my wife's dumbed down yet fully working iphone - it's laughing at me...
I've got the same problem. The menu button works just when it wants. Sometimes it doesn't react at all, sometimes it works perfectly.
I have KE1 firmware, I have rooted it and unrooted (for sim unlocking), then installed original kernel via Odin. Everything was wonderful and I was the happiest guy in the world! One day later the button began behaving like a goast! as chronicpoetic mentioned.
I would like to try installing the new firmware via Odin, but I am afraid that if it's hardware problem, then it won't be taken by service.
Any suggestions?
sounds like hardware faults guys :/
Thank you for reply! I thougt it was too, but... read below
I found out something else.
The menu button works, but with an extreme long delay - 15-30 seconds! More often just right after screen unlock. It just appears and disappers 30 times if I pushed it 30 times before.
And still it can work just perfectly. Sometimes after connecting it to PC or charging it. That dosn't work like a rule.
I am trying to find the reason of such unusual behaviour, but I am lack of expirience.
Any help?
Hello man
I hope that my info will help you
I was in samfirmware.com site and i remembered your problem and i recall that you say Vodafone
so i saw "Provider Samsung I9100 Firmwares" and one of them looks like Vodafone firmware...... please see this site hope to helps you:
http://www.samfirmware.com/WEBPROTECT-i9100.htm
sorry for my bad english
Yeapp, I visited the partner of samsung service center, they said it was a hardware.
Same thing here, any progres?
Just revisited this post - I managed to get a hold of the original Vodafone Firmware from Intratech's thread, flashed it and returned the phone - turns out it was a hardware fault.
Vodafone promptly replaced mine folks.
Sent from my GT-I9100 using xda premium
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I'm a rather experienced pc builder...but this seriously stumps me.
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
can you enter the download mode, if yes then try flashing stock firmware which comes with .PIT file (using odin)......may be that will help
try this thread as well http://forum.xda-developers.com/showthread.php?t=1457458
RazorwireClouds said:
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
Click to expand...
Click to collapse
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
as far as i know if you can enter into download mode, your phone is not dead...........................i don't know much about android development but i am sure that your phone can be revived...........keep searching the forum and try contacting some of the sgs2 developers they might be able to help you
cheers
RazorwireClouds said:
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
Click to expand...
Click to collapse
pretty much what i'm thinking as well, there should be a way to restore it without resorting to cannibalism and taking a broken phone's mobo.
but i have been searching and being new to these forums i've no clue who to contact, but anyways, thanks for the reply sir. my thanks
bumpdonkey.
Come on,are you trying different things like disabling kies/USB cables/ports/different PC.
Have you tired flashing the stock Rom through Odin? You can find it at sammobile.com.
Sent from my SGH-I727 using xda app-developers app
as i've stated in the first post, i've tried almost everything. this includes flashing a series of different roms, kernels, pits etc.
as well as trying it with kies uninstalled, and since it's been attempted by other people, i'm guessing it's superfluous to try it on another PC than my own because others have already done so with it. and the cable is just a cable.
i have the same problem and i still searching
when i try to mount the data partition it fail
i tried all things but still no solution
come on guys help us to revive our sgs2
so far, the most i've accomplished was bringing it from the error message to the boot screen where it remains forever...by flashing the bootroom.
but if i tick "nand erase all" it fails to do anything.
No bumping
Do not bump this thread. The answer will come because someone knows it, not because it's bumped every few hours.
which reatmne
sorry about that, i'll cut the bumping then...i'm just...beyond frustrated at this point...it's been a brick for about a month now...nobody seems to know how to fix the blasted thing
Maybe...
I had once got stuck.
If you could get to the recovery, i think you can try wipe data, wipe data, wipe data....................
Then flash stock rom, or those you think is reliable.
wipe and flash. wipe and flash.
If you can't, use ODIN....... the only way
flash and flash the stock rom or any others.............
if it works, there you are.
Hope it works!!
you may wanna read the whole topic before replying, just saying
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
RazorwireClouds said:
you may wanna read the whole topic before replying, just saying
Click to expand...
Click to collapse
Exactly pal.Surprised he didnt say "if only you could boot up the phone you wouldnt need to get it repaired"......lol
MistahBungle said:
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
Click to expand...
Click to collapse
if i may ask what are thee two things which are going to fix the phone cuz mein is in the same situation thanks
I'm stuck in a similar position I'm stuck at galaxy s2 boot screen can get to download mode but not recovery I havnt tryed Odin yet only because I don't know what I'm.doing with Odin could somebody direct me on where to get the right files n stuff for Odin please I would be really gratfull thanks
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Google Odin 3, use the 1.85 version. Get the stock Rom from sammobile.com for your device. Unzip Odin and then run it. In PDA browes to the stock Rom. Make sure only auto re boot and F. Reset are checked in odin. Then hit start. Check the stickies for more details. See vincom's in the development forum.
Sent from my SGH-I727 using xda app-developers app
Cheers mate am all sorted now bk rooted with the rom I wanted lol
Sent from my GT-I9100 using xda premium
This problem actually caused me to go out and buy another i9100 (which i've successfully rooted multiple times, so I don't think my process is wrong). I'm just trying to get it working so i can have a spare. I've tried searching and couldn't find anything relating to this problem.
Firstly, the problem is like the phones memory is locked. It works completely normally, but if there are any data changes (send/receive messages, install apps, take pictures, change settings... or even deleting things), as soon as the phone is restarted, everything is restored back to the state it was in on 9th November. I don't think the date is relevant to the problem, however
Taking that into account, I'm trying to fix my phone by rooting it and installing a fresh OS on top, but because of this "locked memory" anything i do is ineffective.
I've tried to go into download mode and flash CF-Root onto it, which appears successful, but when it boots back up it's as if nothing happened - no superuser app, no triangle at boot screen. See here: hxxx://i.imgur.com/M0LKW.jpg
I've also tried SuperOneClick. It goes through its process but hangs after "rooting device step#7". See here :hxxx://i.imgur.com/XcPwO.jpg
Entering recovery mode and performing a factory reset doesn't do anything
Deleting everything on the internal SD through windows doesn't do anything.
So because I can't get root, I can't flash CWM or a new OS on top and i'm stuck with a phone which won't change. If i use the phone normally, after a few days it gets stuck in a crash loop (crashes, hit force close, app relaunches and crashes immediately, repeat) and i'm forced to restart. See here: hxxx://i.imgur.com/ACFl5.jpg
I'm out of ideas. Is there anything else I can try?
Phone details:
Model: GT-I9100
Android v: 2.3.6
Baseband: I9100XXKI4
Kernel: [email protected] #2
Build: GINGERBREAD.XWKK2
Thanks in advance
chunkmo said:
This problem actually caused me to go out and buy another i9100 (which i've successfully rooted multiple times, so I don't think my process is wrong). I'm just trying to get it working so i can have a spare. I've tried searching and couldn't find anything relating to this problem.
Firstly, the problem is like the phones memory is locked. It works completely normally, but if there are any data changes (send/receive messages, install apps, take pictures, change settings... or even deleting things), as soon as the phone is restarted, everything is restored back to the state it was in on 9th November. I don't think the date is relevant to the problem, however
Taking that into account, I'm trying to fix my phone by rooting it and installing a fresh OS on top, but because of this "locked memory" anything i do is ineffective.
I've tried to go into download mode and flash CF-Root onto it, which appears successful, but when it boots back up it's as if nothing happened - no superuser app, no triangle at boot screen. See here: hxxx://i.imgur.com/M0LKW.jpg
I've also tried SuperOneClick. It goes through its process but hangs after "rooting device step#7". See here :hxxx://i.imgur.com/XcPwO.jpg
Entering recovery mode and performing a factory reset doesn't do anything
Deleting everything on the internal SD through windows doesn't do anything.
So because I can't get root, I can't flash CWM or a new OS on top and i'm stuck with a phone which won't change. If i use the phone normally, after a few days it gets stuck in a crash loop (crashes, hit force close, app relaunches and crashes immediately, repeat) and i'm forced to restart. See here: hxxx://i.imgur.com/ACFl5.jpg
I'm out of ideas. Is there anything else I can try?
Phone details:
Model: GT-I9100
Android v: 2.3.6
Baseband: I9100XXKI4
Kernel: [email protected] #2
Build: GINGERBREAD.XWKK2
Thanks in advance
Click to expand...
Click to collapse
This is the first time I have heard anything like this (it's like deep freeze(for pc) activated) Anyway I suggest you re flash a stock rom and then root by using something like Siyah latest both via Odin.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
king_below_my_lord said:
This is the first time I have heard anything like this (it's like deep freeze(for pc) activated) Anyway I suggest you re flash a stock rom and then root by using something like Siyah latest both via Odin.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried this but the same thing happened - booted up with nothing changed
chunkmo said:
Thanks for the suggestion. Just tried this but the same thing happened - booted up with nothing changed
Click to expand...
Click to collapse
After flashing a stock firmware via Odin your phone booted up like nothing happened? It's quite impossible I tell you, you must have done something wrong, you must download a stock firmware for your phone (according to region if required) go into download mode flash the tar.md5 file selecting PDA in Odin don't check re partition tick factory reset, and after flashing your phone should be having a new stock rom, try jb or gingerbread stock if the problem persist (logically it shouldn't).
Locked memory huh good name, if you're memory is resetting because of a hardware fault then we can't do anything except send it to the service center, could you post a link to a video of this particular problem it's hm.. You know it's quite unbelievable and maybe a video of your phone resetting itself could maybe stir up some developers who know a bit of hardware.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
king_below_my_lord said:
After flashing a stock firmware via Odin your phone booted up like nothing happened? It's quite impossible I tell you, you must have done something wrong, you must download a stock firmware for your phone (according to region if required) go into download mode flash the tar.md5 file selecting PDA in Odin don't check re partition tick factory reset, and after flashing your phone should be having a new stock rom, try jb or gingerbread stock if the problem persist (logically it shouldn't).
Locked memory huh good name, if you're memory is resetting because of a hardware fault then we can't do anything except send it to the service center, could you post a link to a video of this particular problem it's hm.. You know it's quite unbelievable and maybe a video of your phone resetting itself could maybe stir up some developers who know a bit of hardware.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Click to expand...
Click to collapse
Yep i'll record a video later today.
I'm guessing i'll have to send it in, but it'd be good just to document this kind of problem
Reflashes via odin and nothing Changed
Hit me with a hammer....
Seems like your phone is alive and dont want to die
Sent from my GT-I9100 using Tapatalk 2
A video for your viewing pleasure: (delete the space)
you tube.com/watch?v=31gjELaVDm0
Any ideas?
After recently updating my S II to CM 10.2, some battery issues occurred. When i reflashed my phone to CM 10.1, the phone had boot issues.
My situations can be summarized with the following symptoms:
The phone does not boot normally, and doesn't even turn on at all while it's not charging
When the phone is charging, the charging screen appears in a loop. It doesn't give an actual battery reading, but reboots instead.
Download mode is accessible and I'm still able to flash using Odin.
Recovery mode is not accessible.
According to numerous other threads, these symptoms indicate a NAND r/w corruption. My bootloader could be damaged too.
I have already followed many guides to fix this issue. None of them had these symptom combinations as my phone. These threads didn't solve my problems. I also tried Samsung kies to reset it to factory, but it returned an error message in Korean instead.
What kind of brick is this? And how can I make my phone boot normally again?
I really appreciate your help.
Thread moved to the i9100 section.
If I were you, I'd flash JB leak in Odin. It's a 3 part firmware which will wipe your phone as it flashes and gives a good chance of it booting normally. Worth a shot at least. It's firmware XXLSJ, google search 'JB leak i9100 samfirmware' and it'll be one of the first links. Flash the 3 parts of the firmware as it describes.
Edit: that's assuming you have an i9100, not i9100g/othet variant. If it's another variant font flash that.
Sent from a galaxy far, far away
Unfortunately, that didn't work.
Does someone have another suggestion?
Sent from my Nexus 7 using xda app-developers app
Motherboard replacement. Or you can keep trying; these things have a funny habit of not working for the first 22 flashes you try (as an example), but for whatever reason the 23rd works. Unless the NAND really is borked.
I think it's time for me to get a new phone.
Thanks to everyone who replied to the topic!
Sent from my Nexus 7
Fixed
mineturtle123 said:
I think it's time for me to get a new phone.
Thanks to everyone who replied to the topic!
Sent from my Nexus 7
Click to expand...
Click to collapse
I got my phone working again. My phone had indeed a nand rw corruption, but the boot issues were caused by a defective battery.