I apologize up front if this is has been previously asked. I found lots of helpful info on here searching through old threads but being a bit of a luddite I was a bit confused exactly which situation applied to me. I live in China and recently bought a s3 I9300I and attempted to root it using the chainfire method from the video on this site. Odin declared success but when the phone rebooted it just went back to download mode with a message at top saying, "Could not do normal boot, ODIN MODE." Turning it off and on, removing battery and retrying Odin flash produce no results. The most important thing of course is just to get the phone back to functioning but I'd also like it rooted if at all possible. I read that using Odin to install a custom kernel would root it and I would not be at all opposed to a good custom kernel. I read something about a binary counter that may need to be reset but that seemed to require doing something with the actual phone functions which don't seem to work. Odin still recognizes it when I plug it in and attempts to let me redo the rooting but it just shows a progress bar then reboots right back into download mode. Sorry if this is basic stuff but I'm kind of terrified of bricking this thing and am just not sure what the best course of action is here. Thanks for any help you can offer.
Chinese stock firmware is different to the international, there is a special thread in general forum on rooting etc.
Do you have a link to that thread? I have looked and cannot find anything that seems specific to this problem.
Please. Searching for "China" or "Chinese" gets me absolutely no relevant results. If this has already been covered can someone please direct me to the thread. I really need to get this phone working and am at a loss. Thanks.
Related
Hello all,
If any of you pros can help me out with this I'll be eternally grateful.
So, I rooted my galaxy S2 with the guide on here and after superoneclick it just switched off. I booted it up and it just loops forever, yellow triangle then my provider (LGU+ Korea).
I can reboot into download mode and re-flash with XWKDD_insecure.tar. This starts the phone and I can access main features but it says rooted and I can't make any calls or 3g access.
As soon as countdown is up and screen locks (or I press lock) then the phone is bricked again and I have to re-flash just to get to that screen. So, I re-flashed and then ran the superoneclick program. Clicking unroot this time. It seemed to work and now I can get WIFI but no calls.
However, as soon as the screen is locked it is due a flash. Also, it's impossible to charge.
I'm new to this as you can tell but the guide is simple and I followed it step-by-step. I've read elsewhere on here that I can unroot this with a custom ROM? Where can I find these on the site?
Also, will they be applicable for me in Korea?
Basically I need to undo what I've done and get the phone reactivated. Please can somebody give me some advice and the download location of these ROMS that so I can get the phone reactivated.
Thanks in advance. Really stressing out here. It's on a rather expensive 2-year contract!
http://forum.xda-developers.com/showthread.php?t=1075278
Follow guide .
Flash with XWKDD to see if you can recover to a working phone ..
These are European firmwares .
jje
Thanks for your tip. Unfortunately I've tried that one and the other two all to no avail.
It just flashes until about 95% and then says 'FAIL!'.
Any other suggestions? or am I just going to have to go back to the shop and deal with the consequences.
hmmm havent heard of a fail flash, maybe try posting in the Dev thread
hmmm havent heard of a fail flash, maybe try posting in the Dev thread
Against the rules .
I would take to shop and say Kies offered an update and failed half way through .
A thought go to dev section find a kernel and just flash the kernel .
Post 2
http://forum.xda-developers.com/showthread.php?t=1056334
jje
Okay, So I am as NOOB as NOOB can be,
I got a used SGS2 (Bell/Virgin), I am on Telus so I figured, how hard can it be to unlock it instead of paying some dude to do it for me? (First mistake, and have been humbled every step of the way since!...)
Anyway I will try to keep this relatively short (it will be difficult)... ...I read a few things online and saw that I needed ODIN and a Rooting software, I originally used SuperOneClick, and to download the right insecure kernel to match my original one etc... ...problem is I obviously didn't read nearly enough when I started because I was almost done and then there was a hiccup when SuperOneClick said that I needed to enable SU in Kies. So I decided to go into Kies to try and do so but the instructions before I started Rooting said to put the phone in USB debugging mode. Apparently Kies doesn't see the phone if it is in that mode. Well by this time I can't get past the logo screen and this is where my downward spiral begins.
I then tried to unroot the phone to go back to stock but didn't really know what I was doing and then I read something about the cache needing to be wiped and then after that I read that maybe my OS was wiped. So at this point I did lots of reading (what I should have done in the first place) and most of anything useful I found was on XDA so that is why I am here. It seemed like yes, in fact my OS was wiped because of one of my not so S-M-R-T actions. So I fumbled through and found the right OS for my S2 and I had ODIN going strong and I had the OS loading, the green bar getting bigger in ODIN and the blue bar working it's way across the screen of my S2...I thought "finally!!, I rock!!"... ...then for some reason everything stopped! I had seen in a post that I had to uninstall Kies before doing anything, which I did...but I didn't see until after the fact that my anti-virus likely interfered (I didn't disable it for the process before I started).
At that point of course I was left with a phone that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So then I was afraid to try anything else because many say to steer clear of Kies and also I had read that I may need a USB jig to be able to get it back into download mode because all I was getting was the "firmware upgrade issue" screen. I did make a USB jig with a resistance of 300K Ohms and I *can* get the phone into download mode. (Though another concern is that when I plug the USB jig in and it brings the phone into download mode, the counter is not reset and I read that that was supposed to be reset by the jig.)
So last night I got brave and decided to try and run ODIN and to have another attempt at installation of OS. Now I can get ODIN to detect the phone, but I put the I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 file into the PDA section of ODIN and it starts and gets to the part where it says loading firmware or something and then bootload.bin and it stayed like that for like, an hour and then I gave up, fearing that I am just going to screw it up even more.
So now I decided that I am not even close to knowing what to do next but every time I found anything to move forward it was on this site so I figured I may as well join the site since I have been here so often. Now I am hoping for some kind of miracle...so, in advance, please please please and thank you thank you thank you all for your input. (Sorry for the length of this I just wanted to get all the info I could into this)
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry for the length of the story, I thought there may be alot of useful info mixed in with the useless info... ...when you say use stock firmware do you mean the kernel or the actual OS? I tried loading ICS onto it (which I thought was stock but I may be wrong). Is it supposed to be gingerbread or something else? Also where would I find a good file for it.
Thank you again for any input, very much appreciated!
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
schtiven said:
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
Click to expand...
Click to collapse
Thank you all so much for your help, I could not get it to work after several tries, I even tried three or 4 different USB cables and ports on my PC and still no. I read on another thread that one person tried another PC and it worked so I tried my friend's laptop and it worked!...my SGS2 boots up and all that now! Very very happy thank you all.
Hello.
A year or two ago I purchased this Samsung Galaxy S2 GT i9100 from Ebay, which came to me in Chinese. I changed it to english, eventually, but I could never get it to update firmware, which was a minor contrivance. I continued using it for a long time, with some reservations.
Though two days ago, I finally got around to giving a workaround a shot, which didn't work. I tried another, and another; and nothing worked until I gave up and then all of a sudden, kies decided it would update the firmware out of the blue - without me actually doing anything.
Go figure.
Anyway, the phone started working great until I did some updates on my apps, I lost my "Navigation" app which I am told, most likely got put back into google maps (as it was a part of it) and the phone has crashed twice, frozen for several seconds several times and been quite slow in general since. I googled a bit and found that the culprit was likely the /data/logs - but I cannot get to them as the phone isn't rooted. I deleted some apps to make room on the phone, as it was 1.8/2gig (wouldn't let me update half of my apps at one point!), bringing it down to 1.4 but that had very little affect on the phones performance, and I still have half a dozen Gigs left on the USB. So the logs seem to be the culprit at this point.
Further googling indicated to me that I should err on side of caution and factory reset the phone, but I was unsure whether I should do it before or after rooting the phone, which caused me to find out about this "brickbug".
And I also found out, by an "eMMC brickbug checker" app, that I have a:
Type: VYLOOM
FwRev: 0x19
Brickbug? YES. Insane Chip.
Which leads me to asking you guys what the best process for me to go about this is, considering that I need to not brick my phone as I return to university in two days, but cannot continue with phone locking up and crashing?
Should I skip on the factory reset and just root phone, and if so which process is best, there are so many?
If further info, which update etc, is needed to select proper method I require, please let me know how/where to find it, and I'll post it asap.
Thank you in advance,
Don.
Whether you have a susceptible chip or not is largely irrelevant; the brick bug is triggered by running rooted stock 4.0.4 & doing a factory reset, anything else & you're fine.
I'm not sure why you think rooting the phone is going to fix the problems you're describing ? I'd only be rooting the phone if you have a specific reason to do it. Also, if you absolutely cannot be without your phone, don't root or flash anything to it ever. Sometimes stuff goes wrong, and you simply can't completely remove that risk regardless of what some people on here might tell you (even tho that risk is very very small for a given flash).
So...If I were in your situation, first up a factory reset. If that doesn't help, find Hopper8's 'Odin troubleshooting' guide stickied in the General section, download the 3 part firmware linked in the thread, flash it with Odin. This will wipe your phone. I'd then download a stock rom for your country/carrier from Samfirmware (anything but 4.0.4) & flash that with Odin. This will give you a clean installation & should resolve your issues. If it doesn't, you're probably looking at either something on the app side not playing nice, or a hardware issue.
If you want to root the phone or flash a custom rom from there, that's up to you, but be mindful of the potential for stuff to go wrong. So far as methods to do these things go, this stuff has been/asked answered thousands of times here over the past 2.5 yrs. We have stickied threads near the top of Q&A & also a thread with a multitude of guides/tutorials stickied near the top of the General section. If you do go down this path, taking as much time as you need to read/learn/understand methods on your own (as opposed to someone regurgitating a bunch of steps you don't understand the consequences of) before you do anything should limit the chance of 'accidents' happening.
Phone specs first
Samsung Galaxy S2 GT-i9100
Rooted
CWM
Hardcore speedmod
android 4.1.2 jb
PC is windows 8
I remember i had turned the usb debugging on in dev options
so last night i tried to install cyanogenmod on my device with the cyanogenmod installer for PC and Android.
I was having a bit of usb problems with noticing that my pc did detect the phone, but i couldn't see the phone in
"my computer" file. I thought it would soon fix by itself(i dont know why) and also noticing that detecting device in cm installer
took a lot of time. So when it finally detected the phone it started installing the CM. Although after coming to the
"installing operating system" point, it stopped and said "we couldn't talk to your phone" and having this blue CM guy standing in the screen
of my phone. I tried again several times with rebooting my pc and phone. To the phone appeared again this blue cm figure just standing there.
When i would go and try again on pc it said the "we couldn't talk to your phone" text again. So i gave up with the installer and thought that would be better to flash that CM with Odin. At this point i couldn't access my phone(except for download mode and recovery) of course because it had screwed up the system. I tried to search internet for some usb problem fixes and there were some solutions on changing something in your
device settings and dev options, i cant go there, so for now thats not an option. I started following a tutorial in youtube on how to install cm with odin and root your device. My first question here is that should i install everything and start from scratch (Gapps,CM and kernel) or just the CM ROM? And the problem here is that when i started following the tutorial and came up to the part of having to move the Rom,kernel and gapps to the phone's sd card, i realised that wouldn't work because i cant see the phone on my pc, for now that's the problem number 1. My pc says "unknown device" ( i think thats what it means, see im translating) when i try to plug my phone in. Got any solution for this so we could move on to step 2?
And btw this is in a bit of a hurry, as i really have to get this phone working today.I need it! :crying:
And yeah i did read the other threads about PC not recognizing the phone but those solutions there require the phone to be turned on and changing something there. So basically my phone is bricked and cant connect to pc with usb, i have tried another pc too with 2 usb cables but the phone wont show up under "my computer"
Get stock firmware from Samfirmware, try & flash with Odin. Problems with flash ? Find Hopper8's 'Odin troubleshooting' thread stickied in General; try as much of the stuff in that thread as you need to in order to get a successful flash of stock firmware & a clean slate (I.E a working phone, getting the phone back to this state should be your only thought at this point), then you can try reflashing a custom rom/whatever from there if you want to.
If you do have problems with the stock flash, make sure you actually do everything in the thread, or your phone will stay busted. These things are fixed with perseverance & doing everything possible, there is no easy fix.
Also, please don't post about the same issue twice, there was no need for you to make this thread & post to the other thread as well.
MistahBungle said:
Get stock firmware from Samfirmware, try & flash with Odin. Problems with flash ? Find Hopper8's 'Odin troubleshooting' thread stickied in General; try as much of the stuff in that thread as you need to in order to get a successful flash of stock firmware & a clean slate (I.E a working phone, getting the phone back to this state should be your only thought at this point), then you can try reflashing a custom rom/whatever from there if you want to.
If you do have problems with the stock flash, make sure you actually do everything in the thread, or your phone will stay busted. These things are fixed with perseverance & doing everything possible, there is no easy fix.
Also, please don't post about the same issue twice, there was no need for you to make this thread & post to the other thread as well.
Click to expand...
Click to collapse
So just flashing the stock rom? Does the firmware need to be specifically from that region you live in?
Got the Odin detecting my phone now so that's one step further. Huge thanks for helping me!
itsFreezy said:
So just flashing the stock rom? Does the firmware need to be specifically from that region you live in?
Got the Odin detecting my phone now so that's one step further. Huge thanks for helping me!
Click to expand...
Click to collapse
Yes, for me. I never tried to flash stock rom using other country. So, I don't know what will happen if I do so. Maybe you will get some problems with calls, messages, etc..?
So now i have tried to flash 3 different ROM's and everytime i get stuck for a while in the SetupConnection step and after about 2 minutes it just says all threads completed succeed 0/1 failed and cant open the serial (COM) port. I am on download mode on the phone.
Then you need to go back to Hopper's thread and try everything suggested in the thread, including multiple PC's if necessary.
I did say your phone will stay busted in my PP if you didn't do everything in that thread as many times as you need to (looks like the prophecy is being fulfilled). There is nothing else that isn't in that thread that can be suggested in these situations, that thread is the Bible.
Only you can fix your phone in this situation, we can't do it for you. I've given you the tools to get it done, it's up to you whether you do & how long your phone stays in its current state.
Huuuge thanks to you !
MistahBungle said:
Then you need to go back to Hopper's thread and try everything suggested in the thread, including multiple PC's if necessary.
I did say your phone will stay busted in my PP if you didn't do everything in that thread as many times as you need to (looks like the prophecy is being fulfilled). There is nothing else that isn't in that thread that can be suggested in these situations, that thread is the Bible.
Only you can fix your phone in this situation, we can't do it for you. I've given you the tools to get it done, it's up to you whether you do & how long your phone stays in its current state.
Click to expand...
Click to collapse
I already said this, but thank you for helping, i got it working! I flashed in a cwm kernel and stock rom.You really dont know how
grateful i am! It was kinda stupid to go and try install cyanogenmod without backing up, but that's not going to happen in the future.
Also i think i needed this to happen, i mean it still was a very good lesson to understand the basics of odin flashing and kernels,roms and rooting.
I really thought for a while that i had lost my phone. Hopper8's thread really helped!
Good man. And yes, you're right, having this sort of thing happen early on can be a really good learning experience & give you the knowledge/confidence to recover from just about anything (had a not dissimilar experience to yourself about a week after I got my S2 2+ yrs ago, I learned a helluva a lot in the two days my phone was borked) that happens in future.
Don't forget to thank Hopper's OP in his thread if you haven't already.
Hi all. I've been reading (and not understanding) a lot of threads on here about flashing firmware to this old Galaxy player.
All I wanted to do originally was get a newer android version for the store and games for my 14 month old wee lad to play with.
Anyway after a fair bit of research I got Odin and the US version of a Rom and dove right in to upgrading and of course I made an unholy mess of it and bricked the device.
I chose the US version knowing it probably wasn't going to support the physical home button after but took the risk.
I plugged it into my windows 10 PC and went from there. So the process failed initially after a very quick scroll of information. Then I started ticking the check boxes in Odin to a point where the process took longer and seemed to be actually doing something instead of flying through and failing. Well then it seemed to be doing something so I left it for an hour or two and when I came beck it was stuck where it was, not doing anything. It was late so I unplugged and went to bed.
Now the device only displays the very commonly reported 'phone... ! ...PC' icons.
I have Odin v1.82 running right now and its detecting the player ( yellow box 0:[com8] ), then after a while the player shuts off and comes back on for Odin to detect it again.
Nothing else happens, windows won't read the device even to access as a storage device.
So I've been to step 2, which is trying to unbrick it. I don't really want to go the Ubuntu route as I know even less about Linux then Android.
Also theres the problem of trying to get the original international roms and pit and bootloader(?) files. All the links on here seem to be broken.
So does anyone have the actual files I need and maybe an idiots guide to doing the work?
All help would be greatly appreciated.
didihno said:
Hi all. I've been reading (and not understanding) a lot of threads on here about flashing firmware to this old Galaxy player.
All I wanted to do originally was get a newer android version for the store and games for my 14 month old wee lad to play with.
Anyway after a fair bit of research I got Odin and the US version of a Rom and dove right in to upgrading and of course I made an unholy mess of it and bricked the device.
I chose the US version knowing it probably wasn't going to support the physical home button after but took the risk.
I plugged it into my windows 10 PC and went from there. So the process failed initially after a very quick scroll of information. Then I started ticking the check boxes in Odin to a point where the process took longer and seemed to be actually doing something instead of flying through and failing. Well then it seemed to be doing something so I left it for an hour or two and when I came beck it was stuck where it was, not doing anything. It was late so I unplugged and went to bed.
Now the device only displays the very commonly reported 'phone... ! ...PC' icons.
I have Odin v1.82 running right now and its detecting the player ( yellow box 0:[com8] ), then after a while the player shuts off and comes back on for Odin to detect it again.
Nothing else happens, windows won't read the device even to access as a storage device.
So I've been to step 2, which is trying to unbrick it. I don't really want to go the Ubuntu route as I know even less about Linux then Android.
Also theres the problem of trying to get the original international roms and pit and bootloader(?) files. All the links on here seem to be broken.
So does anyone have the actual files I need and maybe an idiots guide to doing the work?
All help would be greatly appreciated.
Click to expand...
Click to collapse
'phone... ! ...PC' is merely forced download mode. Find a full international stock and flash with odin...
Meticulus said:
'phone... ! ...PC' is merely forced download mode. Find a full international stock and flash with odin...
Click to expand...
Click to collapse
Yes I have read that on here mate, that its still in download mode, however no button combo gets it to do anything else (like trying to enter recovery mode).
Also and I guess this is the main problem, I can't find the stock files anywhere, and trust me I've been reading threads here and googling elsewhere.
The links on here all seem to be broken, which given the age of the threads is no surprise.
So I'm still kind of hopeful someone reads this and can supply the files I need.
Oh and I'm open to a non stock version as long as its for the international version (home button) and proven to be good.
I'd love to be rid of the bloatware and free to install play store etc.
didihno said:
Yes I have read that on here mate, that its still in download mode, however no button combo gets it to do anything else (like trying to enter recovery mode).
Also and I guess this is the main problem, I can't find the stock files anywhere, and trust me I've been reading threads here and googling elsewhere.
The links on here all seem to be broken, which given the age of the threads is no surprise.
So I'm still kind of hopeful someone reads this and can supply the files I need.
Oh and I'm open to a non stock version as long as its for the international version (home button) and proven to be good.
I'd love to be rid of the bloatware and free to install play store etc.
Click to expand...
Click to collapse
Here is full stock RU froyo..: https://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
Here is full stock USA : http://www.meticulus.co.vu/p/downloads_2.html?m=1
Here are more : https://www.sammobile.com/firmwares/galaxy-player-50/YP-G70/