Hey all!
Wanting to upgrade my firmware from ICS to Jelly Bean (as a definite noob, though having flashed firmwares before) I opened Odin and added what I considered the correct .tar file from Sammobile in the PDA field. In short, it failed and I thought I had a new brick*. Following Phistacio's guide to fixing an unflashable GSII I've now got my phone back (woohoo!!), but am stupid enough to want to give it another go!
My question really, is what could have gone wrong, and more largely, what are the variable errors that us noobs make when trying to flash? I'm using Odin, but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
I'm rooted, on an unlocked GSII, recently moved from O2 to Everything Everywhere (T-Mob), currently using an O2 issued ICS, stock kernel and tried flashing Jelly Bean from Sammobile.
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Thanks in advance for any light you can shed!
*I think I was softbricked - could enter download mode but not recovery, flashing would hang on either "Nand write start!!" or Sbl.bin or Cache.img.
my two cents
Hi joelinit,
First of all, should congratulate you on taking the first step of flashing the roms..
Second, good you got an issue while flashing. It helps you understand the intricacies better once you try to solve it yourself.
You need not worry about the brick. Try flashing back to stock rom available from sammobile using Odin(3.04). (United Kingdom (O2) 2013 March 4.1.2 PDA-I9100XWLSD CSC-I9100O2ULS7). Yes carrier is important as Modem file differs based on which carrier you use.
This will fix the recovery and will get you on stock JellyBean.
but it seems using a CWM (is this the correct term?!) might now be the chosen route to flashing?
Click to expand...
Click to collapse
CWM is clockworkmod recovery which provides options for flashing custom roms(CM10, SlimRom, NeatRom etc, there are so many).
So what's critical here? Is my carrier relevant? Is it not possible to go from some firmwares to others? Do I need a different kernel for some firmwares? Or is my mistake in thinking it's as straight forward as I'd like, when in fact all the above make a critical difference in which firmware I can flash, and therefore I should stop trying??!
Click to expand...
Click to collapse
Searching in sammobile for firmwares you will find different firmwares for different carriers. You can flash a UK firmware for some other country, but might have issues with call reception, 3G connectivity, etc. as the modem files are different.
It is possible to go from some firmwares to others.
Stock Roms come with Stock Kernels. When you flash a ROM, kernel will remain the same.
You need to change kernels if your phone is consuming too much battery, crashes etc. This normally happens after flashing custom roms as the kernel is not capable enough to handle the updates in the rom.
Dont stop trying, you will love your phone, once you start flashing the awesome roms,kernels found in xda.
Cheers,
Maddy
Galaxy S2 || CM10.1 nightly 4.2.2 || Dorimanx 9.24
Most of the above is good advice. ....apart from the kernel bit.......
All custom roms and firmwares come with their own optimised kernels. These kernels get flashed during the rom/firmware flash. You can choose to install a custom kernel after you have flashed your chosen rom/fw. Custom kernels offer more control over your OS. All custom kernels offer cwm or twrp (depending on the kernel) and will root an unrooted phone. Most need to be Odin flashed, but some (PhilZ) can be flashed via stock recovery........
Sent from my GT-I9100 using xda app-developers app
Hey guys! Thanks so much for the friendly replies - I thought I might have got abuse as a noob, possibly asking very repetitve questions!!
So then with my recovered GSII, I decided to give it another blast and, inevitably, it's bricked again! Seems to be the same bahaviour - though instead of hanging on either "Nand write start!!" or Sbl.bin or Cache.img., it's failing on them. And this time, I can't seem to fix it,following Phistacio's guide to fixing an unflashable GSII .
I also tried flashing that firmware you suggested (although as I mentioned, I'm now on T-Mobile, not O2? So also tried T-Mobile's Jelly Bean), though with no success.
To clarify, I've installed Kies, then closed down all Kies processes, started Odin and put the .tar file into the PDA field, left Re-Partition unchecked, with both Auto Reboot and F.Reset Time checked, connected my phone and waited for Odin to recognise it, then pressed Start!
Can you suggest anything obvious that I've done wrong or suggest what I should do next? Thanks so much in advance!
4 things to try.....
Use the original usb cable. ..
Try different usb ports on your pc....
Disable any firewalls......
If you are running windows 7, open odin as an administrator. .....
Oh and a fifth suggestion.....
Try different odin versions...
Edit.....Don't ever flash/select pit
And don't select repartition......
Sent from my GT-I9100 using xda app-developers app
These steps are originally posted by MistahBungle. Follow all these steps, he knows what he's talking about.
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Turn off antivirus/antispyware/antimalware.
*Check the rom/kernel you download for corruption. Either check the MD5 sum if you have it (use md5summer or similar), if you don't have the md5 sum or can't check it, programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all these steps fail, try a different PC. And if it won't work first go on a 2nd PC, go thru the above steps on that PC. Still doesn't work ? User error (will be almost impossible to say what given we're not there looking over your shoulder, almost always something very obvious being missed) or borked phone - return to service centre or local mobile shop.
I suspect many cases where people (say) they do all the above & still can't get it to work involve problems with the USB ports on the machines they're using. Something along the lines of the port is unable to maintain a constant connection between PC & phone; if that connection drops for even a millisecond (probably not even long enough to be registered as a broken connection by the PC in the normal way), you end up with a constantly failing flash at best and a bad flash which borks your phone at worst.
Obviously the only way I'd be able to test the theory would be to examine/test a bunch of PC's belonging to people who experience this issue, but I've given this issue a lot of thought over the past 18 mths & it's the best explanation I've got for those instances where people are being completely honest about having tried all the steps over & over and on multiple machines (a very very small % of people, most people either simply don't do every step over & over and say they do, or they forget they've forgotten they did A, B & C but not F) & still find they can't flash successfully (and it isn't a case of the phone being borked).
See how you go with that.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Thanks so much for all these useful replies - really was expecting to get fobbed off for my noob questions! What a nice community!
I'll try all the above and report back. I have successfully flashed on this computer before and did manage to restore the phone last time, though perhaps the cable is faulty and slightly intermittent? I'm using the USB port that's connected to the mother board too.
Thanks again...
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
joelinit said:
perhaps the cable is faulty and slightly intermittent?
Click to expand...
Click to collapse
MistahBungle said:
Quite possible. And impossible to diagnose unless you strip the cable (which is pointless given fixing a $10 cable is a waste of time/effort). Go thru the steps Hopper listed (with multiple PC's if necessary) & definitely try a new cable if you need to. Try to get an original Samsung one if you possibly can; for some reason switching to one magically solves this problem for some people when nothing else seems to work.
Click to expand...
Click to collapse
Thanks! Yeah the cable will be the first thing I'll try changing. It's odd that the flash seems to fail at the same point each time though, kind of implying that it's not an intermitted cable? Unless this particular cable is falling short at those particular functions or something?
Anyway, thanks again - I'm actually kinda enjoying learning about my phone, even though there's the fear it's now a brick!! Fingers crossed that's not the case though...
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
joelinit said:
Well how about that - change the USB cable, and flashes successfully first time round! What a fool! I did also remove the battery/sim for the night and left the sim out during the flash - wonder if that made any difference too?
Thanks so much for all your friendly and helpful replies - I think I'll be sticking around this forum and searching for some custom ROMs to try out!
Happy Wednesdays all...
Click to expand...
Click to collapse
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Hopper8 said:
Good job, glad you got it working keep reading up before you do anything else. The more you read, the better you'll get at all this
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Click to expand...
Click to collapse
Will do! Looking forward to exploring new firmwares so will get as clued up as poss! Have now successfully flashed SentinelROM and loving having a "new" phone! Much more exploring to come.
Thanks v.much to all who've helped me in this thread...
Related
A friend of mine came to me today and showed me his SGSII to fix it for him but I`ve never seen this isue, maybe you folks can help. He tried to flash the phone from ODIN and failed, most probably he done it wrong. The only thing the phone does is displaying an icon in the middle of the screen with a phone and a PC and an exclamation point in between them. I can`t get it to enter in download mode (volume down+home+power) and I can`t start it eather. It just stays at that icon. Kies is not recognizing the phone although the drivers are installed. When I pluged the phone for the first time in the PC it automatically instaled 2 drivers and that was it. Is it bricked? I haven`t seen this before.
The phone is an SGS 2 model GT-I9100G, ssn I9100GGSMH.
Has any of you seen this? Can it be repaired? Thanx.
Ok big big certainty this guy has flashed i9100 firmware on a i9100G .
jje
I also find that Odin can see the phone. It`s probably a good thing I guess. But I can`t flash a firmware. It fails. Should I try to flash something else?
It`s still showing the same icon on the screen.
Ok, I`ll find a 9100G firmware and try to flash that, see what happens.
Ok, I`m back it`s not good it still fails at writing the firmware I`ve tried with I9100GXXLB1_I9100GXEFLB1_I9100GXXKL4_HOME.tar.md5 firmware from Samsung site and it`s for I9100G model. Any ideas? Please help. Can I flash a bootloader or something?
Here is the error bellow:
LE. It doesn`t seem to be able to write the nand I guess.
i remember that i faced this proplem before , and i think i flashed a custom kernel , then i was able to go to recovery , and i tried alot of kernels and cant flash any one expect one custom kernel , so try more than one
hope that i helped
sorry for my english
Make sure Kies/any of it's processes aren't running in Windoze task manager, if they are, kill them. Try different USB cables, particularly the one that came with the phone if you're not using it. Try different USB ports (must use a 'powered'/mainboard port). Try different versions of Odin (search for the others). Uninstall Kies, reboot, re-download/reinstall Kies (for the drivers), reboot & try again.
Check/test the download for corruption, Windoze apps like 7Zip, IZarc, WinRar & others will allow you to test the archive you download. If a test shows any files are corrupt/damaged, bad download. Try downloading using a different internet connection if it keeps happening.
Finally, try a different PC.
Could be a case of stuffed up NAND, tho you can still get into DL mode (I presume ?) so you should be able to fix it unless the NAND is scrambled.
I`ve found something, can you confirm? Here: http://ok-interesting.blogspot.com/2012/02/repair-your-bricked-i9100g.html
The icon is just like in that picture. He said it should be flashed a pit file to the phone and repartion check, along with the firmware. But his download link is not working. Can someone give me the corect pit file please?
I did it! Damn I`m happy. You must flash the right pit file toghether with the right firmware of course and not forgething repartition. Pit was: omap4_all_20110627_emmc.pit and firmware was: I9100GXXLB1_I9100GXEFLB1_I9100GXXKL4_HOME.tar.md5
Thas`s it! Phew, that was close.
Flash Siyahs Kernel with Odin and clear data cache dalvik cache and try it again... Very easy xD a friend had the same problem like ur friend
Sent from my GT-I9100 using xda premium
Kaffee4Eck said:
Flash Siyahs Kernel with Odin and clear data cache dalvik cache and try it again... Very easy xD a friend had the same problem like ur friend
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Clearly you did not read the whole thread, nor did you read GokhanMoral's thread on his kernel (Siyah).
The borked phone above is an I9100G. Siyah does NOT work with the I9100G.
Besides, the guy already solved his problem, so thankfully he didn't have to potentially use your faulty information.
Yeah, no worry though, I had some experience in the past with SGS but didn't know that a single letter in phone's model could put your ass in another boat. It seems that my friend didn't knew that either. I've warned him for the future not to flash other roms that are not specific for his model, even moded ones. It seems he wanted to flash ICS for his device but clearly there is none available for his model for now, maybe later.
Sent from my iPad using Tapatalk HD
catanzaro27 said:
Yeah, no worry though, I had some experience in the past with SGS but didn't know that a single letter in phone's model could put your ass in another boat. It seems that my friend didn't knew that either. I've warned him for the future not to flash other roms that are not specific for his model, even moded ones. It seems he wanted to flash ICS for his device but clearly there is none available for his model for now, maybe later.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Yup. To make it even more confusing, sometimes the letter matters, but doesn't matter.
I9100T (Telstra optimized) and I9100P (NFC enabled) have the same SoC/chipset along with other identical hardware, so they can use I9100 firmware and kernels. But if you flash an I9100 firmware, it will require some work to get them fully functional again.
I9100G cannot use any of the above three, because it has a different SoC/chipset.
There are also numerous other I910x models that I don't know full details on (e.g. I9108, which sounds like it is a close cousin to the I9100G).
To make it even worse, in addition to THAT there are also multiple other models of "Galaxy SII" that have completely DIFFERENT model numbers, like SGH-I777, SGH-I727, SGH-T989, SPH-D710... all with their own firmwares and kernels.
Nice and confusing, eh?
I9100T is sold by several carriers other than Telstra. It essentially has a lower SAR value than the I9100 which makes it better/more suited to use on 850mhz networks.
It is for all intensive purposes exactly the same as the I9100 (no difference in firmware whatsoever), except modems specifically for the I9100T usually (not always/not with all networks/not in all locations) tend to work best with this model (tho you can use I9100 modems with it quite successfully in many instances).
Ah, didn't know that about the T model. The majority of people (that I've noticed, anyways) with this model were on Telstra. Or had to flash a Telstra modem to get decent signal maybe, so I assumed they were on Telstra?
My good people lm a big noob first of all, l need assistance. l wiped my internal sd and now my fone wont boot, although l can get into download mode but l cant get into recovery. l have searched on xda on how to fix this issue and followed all the instructions but still no joy. Everytime l try to flash stock firmware l get stuck on setupconnection or boot.bin. l was using siyah kernal and l had dual boot. just want to know if there is a way for me to use the clockmod in my external sd with all my backed up stuff, or there is no chance of me ever making my fone work again...Thanx in advance people...
No recovery, forget about using "clockmod in my external sd with all my backed up stuff" at this stage.
If you're getting stuck part way thru a flash it could be a couple of issues (actually it could be any one/combination of a bunch of things). First thing I'd do is re-download the stock rom you're trying to flash again, and check the MD5 sum if there is one. If there isn't, use a PC app like 7Zip or IZarc to 'test' the package you've downloaded for errors/corruption. If all the files in the package pass, then the download is OK & that isn't your problem.
Once you've ruled that out, go thru the following:-
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are (I have a sneaking suspicion this may be your issue).
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Run Windoze Update.
And if it still won't work after going thru all the above steps, try a different PC, and if it won't work first go on the different PC, go thru the above steps with that PC. If it still doesn't work, borked phone or user error somewhere along the line (very hard to say what given we're not there with you).
Edit to add - Re: your backups on external SD, once you've got your phone up & running on stock again, you can root your phone (if you use CFRoot you'll have CWM installed by default) & try to restore one of your backups with CWM.
What I did was to open up ODIN(phone in download mode & plugged to computer), and reflash CWM.
Can you open up the stock recovery? Boot to download mode and hold your power button 'till it goes to the recovery.
l have tried a couple of the options you have mentioned on your post, like different usbs, computers etc, l will read your instructions carefully and see if l succeed in flashing and will let you know how l get on, sometime during the wkd. Thanx for taking your time to explain this process to me...
No probs. If you have no luck, post to this thread again & we can go thru every single thing you've done with the phone starting with just before you wiped the internal SD & see if someone can glean something from that info.
Hopefully we won't have to do that ;-) Good luck.
MistahBungle said:
No probs. If you have no luck, post to this thread again & we can go thru every single thing you've done with the phone starting with just before you wiped the internal SD & see if someone can glean something from that info.
Hopefully we won't have to do that ;-) Good luck.
Click to expand...
Click to collapse
Hi l have used 3 different computers, different usb ports, disabbled my antivirus and firewalls, removed kies reinstalled it and made sure it was not running in the background. lm also using the original samsung usb cable, also used 3 different versions of Odin and ran them as administrator, l also tested the stock firmwares using 7-zip to make sure they were not corrupt. But now my question is this, l never updated my fone with the official ics firmware when it started rolling out, l was on Checkrom GB and after that l moved on to FOXHOUND PsycoMantis, thats how l ended up on ics. When l put my fone into download mode it displays this, ODIN MODE (In Red) Product Name: GT-I9100..
Custom Binary Download: No.. Current Binary: Samsung Official, The green android man is visible, Downloading... Dont turn off target...
OK. That means one of three things; your phone is borked & can only be fixed by Samsung/authorised repairer or JTAG, you're not doing something right (really difficult to say what as we're not looking over your shoulder. If it is this, there's no way anyone here can possibly identify that), or there's some clue in what you've done with the phone over the last little bit which might help us work out how to fix it.
So...As I mentioned above, you need to tell us everything (every little step, leave nothing out; the more info you give us, the better the chance you might be able to fix your phone) you did to the phone starting with before you wiped the internal SD card.
I'll have a look thru the details you give us and see if there are any clues.
As to why you don't see any sign of having used non-stock firmware in download mode, I have no idea.
MistahBungle said:
OK. That means one of three things; your phone is borked & can only be fixed by Samsung/authorised repairer or JTAG, you're not doing something right (really difficult to say what as we're not looking over your shoulder. If it is this, there's no way anyone here can possibly identify that), or there's some clue in what you've done with the phone over the last little bit which might help us work out how to fix it.
So...As I mentioned above, you need to tell us everything (every little step, leave nothing out; the more info you give us, the better the chance you might be able to fix your phone) you did to the phone starting with before you wiped the internal SD card.
I'll have a look thru the details you give us and see if there are any clues.
As to why you don't see any sign of having used non-stock firmware in download mode, I have no idea.[/
Before l wiped my internal sd l was running two different roms PARANOIDANDROID and turkbey roms, and l also had removed the yellow triangle, and using the latest siyah kernal, everything was fine then, till l decieded to wipe my internal sd. As to the reason why l wiped my internal sd, it was becoz it was full and l wanted to create some space...a grave mistake...
Click to expand...
Click to collapse
OK. Not as much detail as I expected, but that's fine. Being completely honest with you, given everything you've mentioned in this thread and everything you've tried so far, I honestly have no clue as to why you can't flash a stock rom in Odin.
Maybe someone else who has a look at the thread might see some clues.
Edit to add - What version of Siyah were you running when you did the wipe ?
Go through this - if you can't get into recovery, you probably have nand rw corruption.
http://forum.xda-developers.com/showthread.php?t=1457458
Sent from my GT-I9100 using xda premium
MistahBungle said:
OK. Not as much detail as I expected, but that's fine. Being completely honest with you, given everything you've mentioned in this thread and everything you've tried so far, I honestly have no clue as to why you can't flash a stock rom in Odin.
Maybe someone else who has a look at the thread might see some clues.
Edit to add - What version of Siyah were you running when you did the wipe ?
Click to expand...
Click to collapse
I was using the latest and l it was the last release for the sg2 l think...
MistahBungle said:
OK. Not as much detail as I expected, but that's fine. Being completely honest with you, given everything you've mentioned in this thread and everything you've tried so far, I honestly have no clue as to why you can't flash a stock rom in Odin.
Maybe someone else who has a look at the thread might see some clues.
Edit to add - What version of Siyah were you running when you did the wipe ?
Click to expand...
Click to collapse
jim.j said:
Go through this - if you can't get into recovery, you probably have nand rw corruption.
http://forum.xda-developers.com/showthread.php?t=1457458
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That was the first thread l followed when l developed this issue, and followed all the instructions, but no joy...
Wish samsung had a firmeware updater you could use like the one sony ericsson has, which can install you firmware while your fone is off...
Again, not enough detail. It's going to be impossible for anyone here to help you further unless we get details. The exact version of Siyah you flashed. There's a reason I asked you that, that detail might give a hint as to why your phone is currently borked.
Unless you'd rather pay to have it JTAG'd or pay Samsung/an authorised repairer an exorbitant amount to have it repaired ?
Up to you.
Odin is a Samsung firmware updater, I.E Samsung use it. Wishing you could update the SGS2 in the same manner you would another phone is all good & well, but there isn't that option. So you either use the methods available, or you stay on stock. The risks are normally minimal provided you're careful, follow instructions and fully understand what you're doing before you do it.
silverrum said:
I was using the latest and l it was the last release for the sg2 l think...
Click to expand...
Click to collapse
MistahBungle said:
Again, not enough detail. It's going to be impossible for anyone here to help you further unless we get details. The exact version of Siyah you flashed. There's a reason I asked you that, that detail might give a hint as to why your phone is currently borked.
Unless you'd rather pay to have it JTAG'd or pay Samsung/an authorised repairer an exorbitant amount to have it repaired ?
Up to you.
Odin is a Samsung firmware updater, I.E Samsung use it. Wishing you could update the SGS2 in the same manner you would another phone is all good & well, but there isn't that option. So you either use the methods available, or you stay on stock. The risks are normally minimal provided you're careful, follow instructions and fully understand what you're doing before you do it.
Click to expand...
Click to collapse
Oh sorry l forgot to mention that l was using SiyahKernel v3.3.2, did l also mention l also removed the yellow triangle..
OK. There's no issue like that with 3.3.2. I was just checking you didn't flash a version from a month or two back which messed a few phones up when wipes were done.
Given you've tried what Jim suggested & still no joy, Jim's probably right about your NAND being stuffed. I certainly don't have any other ideas that spring to mind (then again it could also be something really simple someone would pick up if they were there with you; but unfortunately we're not).
So I guess the best you can do is sit tight & see if anyone else on here has any other ideas you can try.
silverrum said:
Oh sorry l forgot to mention that l was using SiyahKernel v3.3.2, did l also mention l also removed the yellow triangle..
Click to expand...
Click to collapse
MistahBungle said:
OK. There's no issue like that with 3.3.2. I was just checking you didn't flash a version from a month or two back which messed a few phones up when wipes were done.
Given you've tried what Jim suggested & still no joy, Jim's probably right about your NAND being stuffed. I certainly don't have any other ideas that spring to mind (then again it could also be something really simple someone would pick up if they were there with you; but unfortunately we're not).
So I guess the best you can do is sit tight & see if anyone else on here has any other ideas you can try.
Click to expand...
Click to collapse
Thanx for all the effort in trying to help me identify the problem, hopefully l will get it to work soon, might sell it if l get to work. lm thinking of the sg3, Nexus or galaxy note, which of these would you recommend and why?
I wouldn't recommend any of them. Why ? I don't own any of them. I'm not qualified to comment.
silverrum said:
Thanx for all the effort in trying to help me identify the problem, hopefully l will get it to work soon, might sell it if l get to work. lm thinking of the sg3, Nexus or galaxy note, which of these would you recommend and why?
Click to expand...
Click to collapse
Who here can say they have never plugged in there s2 to a pc or used mobile odin.? Would just like to no
Gt i9100 pacman v20
Really
Gt i9100 pacman v20
ansrewwrightt said:
Really
Click to expand...
Click to collapse
Are you expecting a lot of replies, and even within a couple of hours? Somehow, I don't think so...
Want to take it down to be fair. Don't no how
Gt i9100 pacman v20
Lol.....I guess I must be the only one then.....didn't use PC Odin on my last phone (galaxy W), and so far, not used it with my S2 either........
That's not to say I haven't tried....I have....on many occasions..... There's just something about my laptop that it seems to have a pathological hatred for Odin and simply will not cooperate.......
That hasn't stopped me from rooting and flashing both my phones though, it just meant that I had to do a s**t load more searching than most in order to find methods that didn't rely on Odin.
It's only just within the last day or so that I've got to consider the possibility of using the mobile version.....I need to reflash my stock firmware before taking my handset in for repair...
sent from my CM10.1 powered I9100 with Tapatalk 2
Glad to some one else on here. Don't need odin don't need a pc. Just information
Gt i9100 pacman v20
A lonely place on this thread il bump this after such a long time to see if anyone else hates Odin as much as me
Lol....still reckon I'm the only one...
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
You prob right mate. Is sad to see no one on here but us. I still cant see why people need to use Odin. With the amount of problems you can have using it I don't think its worth the risk using it. Unless its a must. I nearly had to use it when I flashed a kernel with really old cwm but I had my aokp milestoneone nandroid Bk up that saved the day hehe :thumbup:
You're right.....when do you REALLY need to use odin?
Rooting?....no...philz can be flashed in the stock recovery
ROM flashing?.....no....always done through cwm
Modem flashing?.....no......again cwm can handle that
Firmware flashing?....possibly yes.....if you're not rooted....if you are, mobile odin (not even closely related to PC odin) can handle that.
The only time it WOULD be needed is to recover a phone if things had gone badly during a flash....and if you're careful and follow instructions......the risks of that are minimal......
Given all of the above, I fail to understand why PC odin is *the* 'go to' method.......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Even with firmware you can download zip files for that. @Sofos thread with 4.1.2 jb does the job and if your here he's the way to go because its rooted too. Who on xda really wants firmware that's not already rooted?? Be crazy to have to flash stock with Odin then have to root it too. We agree on a lot of things and every thing you put in your last post I agree with. Many wont and think there so wrong. Cwm kicks ass. Btw who made Cwm?? Man/woman needs a drink from me. A big one. As for twrp...its ok but I'm a Cwm fan forever. :thumbup:
Unbootable/Bootloop c/w no recovery.Had that before,and so have many others.Then its pc odin to the rescue.......
-------------------------------------------
maybe your an iphone expert
------------------------------------------
Just like a "bad flash" yes? Other than that Odin is not needed. That is our point here. Odin is to me very risky to use. Yes you can read lots and get it right but lets say your power go's down...phone is gone for good. the point to this thread is who hasn't used Odin.
RR 4.2.2
You're kidding, right ?
Do you know how many people on here I've seen like that on here over the past 20 months (and including those who were 'unlucky' in other ways/other causes) ?
Maybe 10. Out of many many thousands.
You're both being hysterical & simply validating each others pre-existing biases.
andrewwright said:
but lets say your power go's down...phone is gone for goodRR 4.2.2
Click to expand...
Click to collapse
Main causes are not reading and knowing what your doing before you do anything. That's not cwm fault, phone fault that's User fault. My point now is if your using Odin and don't have a choice maybe you shouldn't be be playing with your phone like that. Iv used cwm for along time now and never needed Odin. Why....cuz I read a lot and know what I'm doing. And after 50+ Rom changes not even counting kernel flashes iv never needed it. Odin is for fools who should stick with stock or buy an I phone. Odin=useless User
Cwm=competent user
RR 4.2.2
Same. I've used CWM dozens more times than I've used Odin. There is still nothing to fear using Odin tho. We simply don't hear about the Odin flashes that go right (which is the overwhelming majority of them). We almost exclusively hear about the situations where they've gone wrong & almost all of those are people's own fault (doing dumb things like pulling cables, using wrong files, using PIT's when not necessary).
Re: your last sentence, you've just shown up how clueless you really are. Perhaps you might like to buy a Nokia 5110 ? (I'll leave you two in peace to continue your circle jerk).
andrewwright said:
Main causes are not reading and knowing what your doing before you do anything. That's not cwm fault, phone fault that's User fault. My point now is if your using Odin and don't have a choice maybe you shouldn't be be playing with your phone like that. Iv used cwm for along time now and never needed Odin. Why....cuz I read a lot and know what I'm doing. And after 50+ Rom changes not even counting kernel flashes iv never needed it. Odin is for fools who should stick with stock or buy an I phone. Odin=useless User
Cwm=competent user
RR 4.2.2
Click to expand...
Click to collapse
I don't doubt that a great many users have used PC Odin without issue.....that point is not in dispute.
And yes....PC Odin does have it's uses.......
BUT.....it seems that it is being used regardless.....there are other equally valid and SAFER methods available for rooting and flashing software to your phone. Don't forget that the connection between PC and phone relies on the flawless operation of the USB socket....a number of XDAers will testify that their USB socket functions less than flawlessly and according to my research this problem IS becoming more commonplace. Let's face it....if the USB socket fails during a flash, it's usually bad news for the phone....so YES it IS safer to use CWM or Mobile Odin for day to day flashing.....I don't know about you, but I've NEVER come across a thread where cwm or mobile Odin were cited as the reason for a bricked phone.....Odin on the other hand........
And @MistahBungle....I for one don't appreciate being called hysterical just because my opinion differs from yours.....nor do I appreciate you saying that I have an IQ of less than 25 (different thread). So please refrain from throwing personal insults as nobody is throwing them at you........
Edit.....circle jerk?.....is that REALLY what you think is going on here?
Damn.....
Yet another insult from someone who obviously rates increasing his post count more important than contributing anything constructive......
sent from my Arco powered W via XDA developers app
Maybe pc odin should come with an 18 rating,or use with parental guidance.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
dude..can i join u all for a moment..
my first phone was a galaxy w 'once'..in 2011 back then...i dont have a pc.,nor a laptop..just with a humble phone with mobile data connected..and my first move to rooting my phone..lucky samsung have a stock recovery, and then,googling session begin...first attempt was fail..i hve a bootloop..and many more..thats nightmare teach me a lot..1 month later,i have a CWM 3.x(latest back then)...a custom kernel,custom rom,...i dont even plug my phone to usb~>pc..and detected by ODIN..!using my phone for a year..40+ custom kernel/rom flashed..man..thats was a hard yet a glorious era for me....my phone is all i need.mobile+pc(mini)+movie+music+learning platform+etc etc...etc...
but now I'm on SONY.
(my g W was stolen)
and u all guys now that sony have to rely on flashtool(PC) to flashing kernel and ftf....yet its more reliable than odin..
sent from another space
Lol... @theunderling I think that's taking things a bit far.....but in essence, you're right.... most noobs rush into things without reading the available information across all the relevant threads....we all know this.....
We need to find a way to highlight the inherent risks of Odin flashing so that these noobs have as much knowledge as possible before they rush in and bork their phones.........
sent from my Arco powered W via XDA developers app
Hi all,
Was on Slim Bean 4.2.2 Build 7, but encountered a boot loop for some reason. So I proceeded to flash the stock roms (4.1.2) as listed. Tried several times flashing different roms on that page (just flashing the PDA file), but to no avail. Odin always says that the flash is successful, but the boot loop still continues. Does anyone have any advice on how to get past this boot loop? Thank you so much!
Short of persevering (I.E try different stock roms - different Android versions, released by different carriers), try Hopper8's 'Odin won't flash' thread. Though it appears your flash has been successful, something is obviously not right (almost impossible to say what that might be given we're not there with you watching over your shoulder). Stuff like trying different cables, different USB ports, uninstalling/reinstalling Kies & even different PC's is worth trying (and other stuff in his thread). Also, try flashing a 3 part stock rom (as per Hopper's thread), this should wipe any 'remnants' which might be causing the issue you're seeing & might work (maybe try this first).
Also, I'm going to ask the obvious - if recovery is working, have you booted into recovery after flashing & done a wipe ? Obviously if you have no recovery you won't be able to do this.
Thanks for the reply. I have tried going into recovery mode, but to no avail.
Would I be able to flash a 3 part rom if I just flashed a stock rom? Just wanted to make sure I don't brick it.
A three part rom is a stock rom, but unlike a one part rom which you flash in the PDA section of Odin, the CSC file will wipe your phone in the process, which is what we want if we're working with the theory you flashing one part stock roms up until now seems to be 'leaving something behind' which might be causing persistent bootloops.
If you're worried about bricking your phone, take it to a service centre & pay to have it fixed (All they'll do is try & flash a stock rom/wipe the phone which you're capable of doing for free yourself). You're looking for a simple fix, there isn't one. If you persevere, you'll fix it eventually. This has been the experience on here over the past 2 yrs or so.
MistahBungle said:
A three part rom is a stock rom, but unlike a one part rom which you flash in the PDA section of Odin, the CSC file will wipe your phone in the process, which is what we want if we're working with the theory you flashing one part stock roms up until now seems to be 'leaving something behind' which might be causing persistent bootloops.
If you're worried about bricking your phone, take it to a service centre & pay to have it fixed (All they'll do is try & flash a stock rom/wipe the phone which you're capable of doing for free yourself). You're looking for a simple fix, there isn't one. If you persevere, you'll fix it eventually. This has been the experience on here over the past 2 yrs or so.
Click to expand...
Click to collapse
Thank you MistahBungle! For some reason, a three part rom did the trick. Not sure why though. But I'm so grateful for your help!
There you go. Our theory re: previous flashes leaving something behind must have been right. You're welcome Glad you got it sorted.
darknezx said:
Thank you MistahBungle! For some reason, a three part rom did the trick. Not sure why though.
Click to expand...
Click to collapse
Good for you! Please add [SOLVED] to the title of your post then.
"To err is human, to forgive is divine."
Sent from my SGS II
First of all, I am not new to flashing, rooting and etc. I have helped many of my friends with custom roms and etc so flashing and Odin is not something I know nothing about.
However, I was asked by my friend that his S2 was running slow and wanted me to put a custom rom on there. So I did the usual thing of using the ZergRush method to give him root access and I tested Superuser with Root Checker and everything was fine. So I went to install a custom recovery (Phil's CWM) via Odin and using the latest tar file from Phil's website but this is where things didn't go according to plan.
When I hit the Start button in Odin, it did the normal thing of writing to the NAND but instead of taking the usual 8-10 seconds, it took a lot longer. I actually waited 20 minutes and nothing was happening. There was no indication on the S2 that anything was happening and Odin was still stuck on the NAND Writing with all the buttone grayed out. So I waited a bit longer and after 30 min I decided to close Odin and try again, but when I try to get into Download Mode, I got the message 'Software Update Fail'. I tried to flash the custom recovery again but when it gets to the NAND Write, it instantly goes to 'Fail'.
Out of the 8 Samsung phones I have rooted and put a custom rom on, this is the first time this has happened. I searched the forum but most of it point to a bricked phone. I know at this point is is pretty critical that I do not try any random thing and asking you guys for any advice. I have tried flashing with a different version of Odin and also on different computers but gave me the same result. So any help would be much appriciated.
Hopper8's 'Odin troubleshooting' guide; search for it. You need to try everything in that thread over & over & over, only way you're fixing it is if you get a successful Odin flash away. In particular flashing the 3 part firmware might fix it.
Given the alternative - motherboard replacement or new phone - keep trying stuff, these cases are sometimes fixed by persevering (for whatever reason the first 8 stock rom flashes you try don't work but the 9th does, etc)
Thanks for the information MistahBungle, I have tried most of what has been said but I have not tried the leaked rom for the i9100. I will definately give this a shot.
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
MistahBungle said:
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
Click to expand...
Click to collapse
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Z-Blade said:
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Click to expand...
Click to collapse
Good to see you got it working, always like hearing of people getting their (or not their own in your case) phone back to life
MistahBungle said:
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Click to expand...
Click to collapse
Thanks for keeping on referring my thread, the more people it can help the better I'm working 6 days a week for now so haven't much time to go on Q&A and help out. Also thanks for before, I think you know what I'm referring to. Much appreciated. :good: