hi, my friend has a galaxy s2 i9100 on stock unrooted gingerbread, it crashes each time when turning on wi-fi,
i wanted to try to upgrade the the rom to see if the problem persist but unfortunately the kies encounters some error when upgrading the s2..
so i told my friend to try using odin, but odin also encountered an error (not sure what kind, im not with my friend when he tried)
do i need to match kernel to successfully flash the stock rom?
kies updated? closed all kies applications before flashing with odin? tried older odin versions? newer versions? tried all usb ports? another pc? a laptop? tried flashing siyah kernel?
Sent from the little guy
Without knowing the exact details of what's going wrong I.E exactly what your friend is flashing, what Odin says when it fails, what version Odin, etc, etc it's going to be nigh on impossible to provide any meaningful help.
At a guess, I'd say your friend is probably using Odin 3 (again, I'm guessing here because you've provided sod all info). Try flashing with an earlier version of Odin (Google search) & also check Windoze Task Manager & make sure Kies/it's processes aren't running when you're trying to use Odin. If they are, kill those processes.
MistahBungle said:
Without knowing the exact details of what's going wrong I.E exactly what your friend is flashing, what Odin says when it fails, what version Odin, etc, etc it's going to be nigh on impossible to provide any meaningful help.
At a guess, I'd say your friend is probably using Odin 3 (again, I'm guessing here because you've provided sod all info). Try flashing with an earlier version of Odin (Google search) & also check Windoze Task Manager & make sure Kies/it's processes aren't running when you're trying to use Odin. If they are, kill those processes.
Click to expand...
Click to collapse
why yes.. he is using odin v3+, i actualy recommended it becuase thats the version i used to flash my S3 over and over again, tnx for the help,
will definitely try a lower version of odin , will post what happens,
tnx alot
Related
Can someone confirm they have managed to successfully flash in Mobile Odin? Coming from GB are there issues to upgrade this way?
I have the firmware downloaded and unzipped on the INTERNAL memory, does it need to be in an external? Also... I have 3 files...
GT-I9100-MULTI-CSC-OXALPJ.tar
I9100_CODE_I9100XXLPJ_CL140368_REV02_user_low_ship.tar
MODEM_I9100XXLPJ_REV_02_CL1105553.tar
Im unsure of the process and where they should go. Ive heard of people flashing in multiple fields. Could someone please explain for my particular query? Thanks
Sent from my GT-I9100 using xda premium
I flashed LPQ using mobile Odin, but needed to do a wipe after the fact to stop a bootloop.
If you just load the files into Mobile Odin it'll put them where they're supposed to go, IIRC (I used the single file ROM, and it just filled everything in).
make sure you want to upgrade/flash xxlpq. i did and it works fine, but:
when charging, no flashing of lightning bolt in batt icon, drive and walk gone, voice search gone, touch screen not as responsive as with 2.3.4/5, it seems as if the phone slower and sluggish.
Flashing Upgrade
Hi. I'm a beginner. But I've flashed a few times some custom ROMs on my Galaxy S2 and every time they were successful. I always follow the instructions properly.
My question is : Can I flash the ICS XXLPQ (on top of Gingerbread 2.3.6 XWKL1 baseband DDKL1, kernel 2.6.35.7-i9100XWKL1-CL809037 [email protected] #2) , and keep all my old apps that I already have installed, just like it hapens if you update the firmware through Kies?
I don't want to backup anything using any tools to backup apps. Just want to mimic the Kies update, where you don't have to backup your apps manually and you still wouldn't lose them during the upgrade (if nothing odd happens!).
Thank you for your help.
monitorix said:
Hi. I'm a beginner. But I've flashed a few times some custom ROMs on my Galaxy S2 and every time they were successful. I always follow the instructions properly.
My question is : Can I flash the ICS XXLPQ (on top of Gingerbread 2.3.6 XWKL1 baseband DDKL1, kernel 2.6.35.7-i9100XWKL1-CL809037 [email protected] #2) , and keep all my old apps that I already have installed, just like it hapens if you update the firmware through Kies?
I don't want to backup anything using any tools to backup apps. Just want to mimic the Kies update, where you don't have to backup your apps manually and you still wouldn't lose them during the upgrade (if nothing odd happens!).
Thank you for your help.
Click to expand...
Click to collapse
flashed my sister's phone using odin and DXLP7 from DXKL3, and worked great, didn't even wipe data.
i did however wipe data on mine, since im using a MIUI. (flash using mobile ODIN)
GB 2.3.6 to ICS with Mobile Odin not successful
Hi, my SGS2 is currently on I9100DXKL3 (flashed via mobile odin) and rooted.
I downloaded I9100DXLP9 and used the usual way I did before in mobile odin (v 2.35) to flash i.e. Picked the file from internal memory, ticked on Everyroot, Inject etc...all the check box and clicked flashed. Mobile Odin ran the verification check file and than it just stops, it didnt hang, it just stops after running everything but it's didnt boot into recovery.
Is there anything I did wrong ?
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?
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...
OK, so i have no idea where i went wrong but here we go.
I was flashing my phone (i9100 for reference) with the latest Neatrom ROM. seen here http://forum.xda-developers.com/showthread.php?t=1569686
from a stock samsung firmware on my international galaxy s2. so its not branded or anything. ( with virgin moblie canada if that matters... ) anyway booted into recovery. ( after putting the .zip file onto the phone ) and updated in the stock recovery to the Neatrom. THen i wiped dalivk and the normal cache. and rebooted.
i got the samsung logo and yellow triange..
tried factory reset
same thing.
(at which point i forgot to back up the phone like an idoit)
tried to use triangle away. ( got confused and gave up, never really even tried because it was a .apk and i didnt know how to launch it from a phone stuck on boot)
tried ODIN, by flashing the base samsung stock rom for virginmoblie canada phones.
and this is where i really got confused. the phone says that it needs to be connected to kies. so i installed kies ( because i never used before ) and kies wouldnt recognize the phone. ( also at this point the phone wouldnt go into recovery mode at all so i was really freaking out )
i then flashed siyah 6.0b5.tar on ODIN to the phone and thank God it flashed and the phone now went into recovery mode and i tried flashing neatrom agian and i was back to the start ( samsung boot logo with yellow triangle )
( i then flashed the stock rom and went back to the whole " please connect phone to kies, and the computer wont recognize it )
now i dont know what to do. my first idea that comes to mind is to reflash siyah kernel, after that im at a loss.
Any Help would be amazing
You need to successfully go back to stock & get a 'clean slate'. Then you can flash whatever custom rom//kernel you want again from there.
You've also gotten yourself seriously confused re: Kies & flashing with Odin. It's the opposite; you don't want Kies or any of its processes running (check & kill them in Windoze Task Manager if they are) because it messes with Odin. The reason Kies gets mentioned re: Odin flashes is because in order to use Odin you need to have drivers installed on the PC, and for many people the easiest way to do this is to simply install Kies.
I very much recommend to do an advanced search of Hopper8's threads & find his 'Odin won't flash' thread. I'd be very surprised if you can't end up successfully flashing the phone using the info in that thread.
MistahBungle said:
You need to successfully go back to stock & get a 'clean slate'. Then you can flash whatever custom rom//kernel you want again from there.
You've also gotten yourself seriously confused re: Kies & flashing with Odin. It's the opposite; you don't want Kies or any of its processes running (check & kill them in Windoze Task Manager if they are) because it messes with Odin. The reason Kies gets mentioned re: Odin flashes is because in order to use Odin you need to have drivers installed on the PC, and for many people the easiest way to do this is to simply install Kies.
I very much recommend to do an advanced search of Hopper8's threads & find his 'Odin won't flash' thread. I'd be very surprised if you can't end up successfully flashing the phone using the info in that thread.
Click to expand...
Click to collapse
Will try in a couple days ( i dont have my phone right now forgot it at home and im currently moving )
will post results
so go back to stock and get a clean slate should i reflash the siyah kernel through odin and flash a stock samsung rom?
just making sure here
Why would you 'reflash the siyah kernel through odin and flash a stock samsung rom?' if you've already just flashed a stock rom through Odin ? Take some deep breaths, lose the panic & re-read my last post slowly.
I got myself an AT&T branded S2 (i777). I used Samsung Kies to update to the latest firmware and something happened while doing so. I turn on the phone now and it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Recovery in Kies doesn't work.
I can get into download mode. Although I can't seem to get Odin to be successfully done, always fails.
Is there any solutions to fix my problem?
I have searched and found fixes for the international version, but that does me no good as mine is the SGH-I777. I just want to be able to have a working phone again.
I'm pretty sure we can get your phone back to working.
A more detailed description of your inability to flash with Odin would be helpful.
What were you trying to flash?
Were you able to get Odin to recognize the phone?
What were the error messages in Odin?
After you answer, I'll give you some things to try.
That would be awesome.
- Tried using I777UCKH7-CL503881-Full it gets to sbl.bin and then fails.
- Tried using Odin v1.85 with a stock i777 tar file. Sticks at factoryfs.img and then fails.
- Odin does recognize the phone.
The majority of issues with failed flashes have to do with the connection between the computer and the phone. The standard advice is, use another cable, use another USB port on the computer, or even use another computer. However, lets skip that step for now, and assume that the connection is good.
It's possible that there is an issue with nand read/write memory corruption. Let's see what happens if we clear nand r/w memory. I assume that you know how to use Odin correctly, but if you want additional instructions, I can post some.
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Link to the download repository is in my sig.
---------- Post added at 09:04 PM ---------- Previous post was at 08:57 PM ----------
The latest stock for this phone is I777UCMD8, which you can also get in the Download Repository. I would suggest you flash that after you get the phone back to working. Or, if you want to customize, there are good versions of custom firmware available in the forums.
I try to check in to the forums every couple of days, at least. It was just serendipity that I came into the forum 10 minutes after you posted. I'll try to remember to keep an eye on this thread more often, but sometimes I get a littly busy, so if I'm mia, just be patient.
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
fluttershys said:
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
Click to expand...
Click to collapse
Okay. Maybe your issue was only a connection issue. But I would suggest that you complete the sequence above exactly as written. As it says, instructions are specific; do them in order, and don't skip.
If the issue is nand r/w corruption, this should fix it. If that was not the issue, this will not do any harm. The firmware used is the oldest original firmware for the I777, and is seriously out of date. But it is known to fix the specific issue of nand r/w corruption.
Once you have the phone working normally, ie. booting into system without issue, then you should probably flash the latest stock firmware as I suggested earlier, or the custom firmware of your choice.
Thank you for all the help. I was actually able to use Kies and re-do the firmware that way. I have done the framaroot root.
Is there a ROM and Kernel that you would suggest using for the I777?
You need to decide whether you want firmware that is Samsung touchwiz based, or AOSP based.
If you want touchwiz, you should look at cooked or SHOstock3. No one is doing active development right now, but these two are stable and each is good in its own way.
If you want AOSP, I can't recommend anything since I haven't flashed them, but would suggest you read the development forum and look at the threads for firmware that have been actively posted in the past few months.
The latest touchwiz is Jelly Bean, but with AOSP you can get Kit Kat, or even Lollipop.