Hi everyone I am somewhat new here, I am looking for the stock firmware for the SGS2 I777 from At&t. It should have 3 tar files that is flashable by using Odin, or perhaps a similar method with same result.
Basically I flashed international firmware I9100XWKDF using 3 tar.md5 files in the zip and it was the only thing that fixed my boot loop problem. However the display brightness is too intense even at lowest setting, the sharpness is too high causing pixelation, also the color is faded and mixed with brown almost 16-bit color like. Now I want to return to the original stock firmware for the I777, I think this will fix the color issues. But I do not know what the stock firmware is named, I've seen a few files here and there such as UCKJ but I don't want to brick my phone so any help would be much appreciated. I've written more details in the next paragraph to clarify if needed.
I'll try my best to keep this short. The reason I need this is because I had a boot loop problem a few days back. This came out of nowhere I've been using this rooted phone with cognition 777 ROM for 4-5 months with no problem. So I went to CWM to restore from my backup but the boot loop was still there. I tried a clean flash after wiping data/factory reset, cache/ delvik, etc... and reflashing different kernels, nothing worked. Out of desperation I used Odin 1.85 to flash PIT using the default PIT file that comes with Odin, somehow that worked and I was able to boot up into MIUI but no signal. So I reflashed again and boot loop returned, this time not even flashing Odin's PIT or using the stock i777 PIT worked. I looked around and saw a post on how boot loop was fixed by flashing 3 tar.md5 files using odin from this I9100XWKDF firmware. I tried it, at first it still bootloops and I was unable to get into download mode using the power+both volume button method. Out of sheer luck I decided to just hold the power+down volume button and it worked. Then I flashed a new kernel again to see what will happen, upon reboot everything worked again. Even restore worked and everything was back to normal. But I noticed that the display is very bright and the colors are faded and has brown mix into it. If it was not for the display side effect I would have never known that I used the wrong firmware for the International version. However 3d gaming runs smoothly it is just the color that is messed up.
A cookie for whoever made it this far lol.
When all else fails, look in the sticky.
sent from my Shostock Sgh-I777 running siyah!
http://www.youtube.com/watch?v=JmvCpR45LKA has your solution
any1 nice enough to link me to the correct files or thread containing them, I fear a hard brick and would just like some conformation.
nubface said:
any1 nice enough to link me to the correct files or thread containing them, I fear a hard brick and would just like some conformation.
Click to expand...
Click to collapse
Learn how to read the sticky. It has all the links you need. A new thread was unnecessary.
Sent from my SGH-I777
nubface said:
any1 nice enough to link me to the correct files or thread containing them, I fear a hard brick and would just like some conformation.
Click to expand...
Click to collapse
Sure if that was necessary, it isn't because you didn't read the sticky
Sent from my SGH-I777 using XDA App
I would only say cut him a little slack because the new sticky system is cleaner but isn't right in your face like the old stickies.
ricktat said:
I would only say cut him a little slack because the new sticky system is cleaner but isn't right in your face like the old stickies.
Click to expand...
Click to collapse
I think it's cleaner. And the answer to his question still has its own independent sticky.
ricktat said:
I would only say cut him a little slack because the new sticky system is cleaner but isn't right in your face like the old stickies.
Click to expand...
Click to collapse
The new sticky thread is much better than the old stickys... which were just a bunch of individual threads. Besides, nobody asked you.
As previously stated, sticky thread has your answer. If you cant read, then you cant flash.
Related
I can't post the link but it is on youtube.
If you youtube "bigshotz" and click on my user name, its the last video I uploaded
Long story short, I used the Odin program for the captivate on accdident, but I found the Odin program for the Vibrant and got it back to stock. But I still have the AT&T Start Screen, anyone know how to get rid of it? Thanks!
Look in the Captivate forums for how to remove the AT&T boot screen. It should just be a file you can delete.
Sent from my SGH-T959 using XDA App
Wipe then reflash?
tried everything
anyone?
same thing happened on my phone when i installed a captivate firmware.. did you find any solutions?
same here. found this in the captivate forum, but no solution so far.
forum.xda-developers.com/showthread.php?p=7678939
Hi, I too have been looking for a solution for this. If you search at&t in the forums you will find multiple posts involving this that have all gone unanswered. I have tried installing multiple different roms, internal phone resets, various odin configurations, and probably a few other things I am overlooking to no avail.
Can't seem to find a solution...
Sent from my SGH-T959 using XDA App
You guys probably need to odin 'eugenes froyo that doesnt brick' then odin back to stock. It will completely wipe everything.
Sent from my SGH-T959 using XDA App
sensasian03 said:
same here. found this in the captivate forum, but no solution so far.
forum.xda-developers.com/showthread.php?p=7678939
Click to expand...
Click to collapse
Nice find! For those curious the file may be located in your /mnt/.Ifs directory. Its called logo_ATNT.jpg Also, the standard vibrant boot image is there named logo_T959.jpg
As that thread mentions, it seems any changes made to the file don't stick though. I have tried a few changes including permissions, rename, move, delete with no luck. ** EDIT ** From a little research, it seems that the /mnt folder represents android's current mouted systems. Kind of a 'virtual folder'. I am not a linux guru by any means so if I am mistaken here please let me know.
Fyi, the froyo that doesn't brick method has not worked for me in the past. Thanks for the suggestion though.
Sent from my SGH-T959 using XDA App
my phones network is showing at&t even i'm not using an at&t sim card. i screwed my efs folder. any idea how to fix?
Try flashing a stock Vibrant kernel? Worked for me when I built a kernel using the CONFIG_KEPLER* options by accident.
Kidshyy said:
I can't post the link but it is on youtube.
If you youtube "bigshotz" and click on my user name, its the last video I uploaded
Long story short, I used the Odin program for the captivate on accdident, but I found the Odin program for the Vibrant and got it back to stock. But I still have the AT&T Start Screen, anyone know how to get rid of it? Thanks!
Click to expand...
Click to collapse
I had exactly the same issue.
The problem is that you flashed the att captivate's sbl.bin which shows the first boot screen like "ATT world phone". So please find a vibrant sbl.bin and flash that through Odin.
I don't have that since I'm fine with the dual screens...
Thanks for the explanation on what file it comes from. I look into that. Never really been an issue for me either, more of an annoyance I guess.
Quick question/comment: why does the stock odin build for the vibrant not flash over this file? I guess it is not included in most builds?
Sent from my SGH-T959 using XDA App
SOLVED!!!!
Thanks for the guidance neasoon. Here is what I did to fix this issue.
1) Nandroid / Titanium backup (just in case)
2) Downloaded the 'update.zip' from this thread: http://forum.xda-developers.com/showthread.php?t=804305
3) Apply update.zip using Clockwork Recovery
4) Reboot, and fixed!!!
A few comments on this method:
Apparently the sbl.bin / boot.bin are relatively rare files to come across and are not located in most firmware leaks/updates. Hence the reason restoring using ODIN back to stock is not solving this issue. These files were grabbed from the JI4 leak and have been put into a flashable update.zip provided by untermensch. These files also fix phones with hardware locks and I believe have been included in some of the recent OTA updates. (Cannot verify as I have not received one) So some that have installed the OTA may have magically seen their 'AT&T' screens disappear afterwards.
I applied the update successfully, and all is well. (NO MORE BRIGHT WHITE AT&T SPLASH SCREEN!). Please make sure you read the OP in the link above before you proceed with the update. Keep in mind it is written towards those with hardware locked phones, so it mentions instructions to get into recovery via adb. Assuming you don't have a hardware locked phone you can reboot to recovery using normal methods to apply this update.
Cheers!
yes finally figured it out too.. what i did was i loaded firmware with boot.bin for a vibrant. and now i dont have the att white world phone bootscreen anymore. yay!
i tried the odin method and it works! no more stupid att boot screen. thanks a ton!
Will the froyo 2.2 fix this? After flashing the captivate onto my galaxy s then loading the ji6 pit, I'm not ready for the emotional roller coaster that may ensue if I do this.
As long as the boot.bin is included it should fix it. Not sure which rom this is included in though.
Sent from my SGH-T959 using XDA App
chupacabra613 said:
Will the froyo 2.2 fix this? After flashing the captivate onto my galaxy s then loading the ji6 pit, I'm not ready for the emotional roller coaster that may ensue if I do this.
Click to expand...
Click to collapse
Ok, I decided to grow a pair and used clockwork to install the zip file. worked like a charm!! Many thanks--Al
I'm an admitted noob, but my hope is that somebody here will take pity and be able to shed some light on what I've done and how to fix it.
Here is a general high-level list of what I've done:
1. I attempted to root my phone with SuperOneClick (I think 2.3.3)
2. It hung one Step #7 (as I recall) for about 10 minutes.
3. I disconnected USB cable and reset the phone - it wouldn't boot
4. Started researching, discovered Recovery Mode, selected reset to factory.
5. Reset appeared successful, but then phone went into reboot loop.
6. Tried to access Recovery Mode again, but this time it came to different screen, saying "Deleting cryption meta data".
7. Tried flashing several times with odin and stock PDA's suggested in this forum.
8. Same behavior, so flashed CWM 4.0.0.2 (unfortunately it was for I9100)
9. Flashed new CWM 5.0.2.3
10. When I enter Recovery mode now and I select the wipe data/factory reset option, it just goes to a hat icon with a circular arrow and stays there.
Like I said, I'm new here and have already given up hope on recovering any useful data on my phone. I just want to get it working again so I don't have to buy a new one.
Thanks in advance!
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Click to expand...
Click to collapse
This guy is right. The power button is the menu/logo button in that version. The newer version changes that mapping though.
You'll likely need to flash the return to stock image. One of them is already prerooted, too!
Sent from my SAMSUNG-SGH-I777 using xda premium
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
Click to expand...
Click to collapse
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
digitalsdc said:
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
Click to expand...
Click to collapse
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
creepyncrawly said:
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
Click to expand...
Click to collapse
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
digitalsdc said:
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
Click to expand...
Click to collapse
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
creepyncrawly said:
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
Click to expand...
Click to collapse
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
digitalsdc said:
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
Click to expand...
Click to collapse
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
digitalsdc said:
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
Click to expand...
Click to collapse
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Nerz said:
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Jank4AU said:
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Thanks for your thoughts. I had a similar thought last night and so let it sit through the night rebooting. Sure enough, when I checked it (roughly 8 hours) this morning, it was nice and warm, but still rebooting away.
creepyncrawly said:
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Click to expand...
Click to collapse
Thanks very much for all your help! I'll try to reach out to these other gentlemen as well.
I've seen other people on these forums with the same problem, but unfortunately, every thread seems to end unresolved. I still hold out hope as I really don't want to eat the cost of the phone and start over.
digitalsdc said:
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Click to expand...
Click to collapse
I figured it was the charger because it was connected when it happened. Was driving home from a Christmas vacation, with maps navigation going, stopped at a rest stop surfing the web. Also on another thread that I read that had a similiar problem, they too thought it was the charger.
And no it was not stock, running unnamed at the time, (though I doubt that is the cause). Like yours I think, I could flash from cwm without success. Wasn't until I flashed stock with stock recovery that I got the deleting meta cache or whatever it is.
Sent from my SAMSUNG-SGH-I777 using XDA App
Any luck so far? I think I'm having the same issues. Although I can flash the stock rom, then a CWM .tar file and get into recovery. But no matter what I do, after boot, the phone starts boot looping.
You can see my thread in the Q&A section.
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
THX THX THX THX THX! It worked!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
Hi, did anybody tried this solution??? I'm having the same issue, even tried to contact JTAG unbrick service but these guys told me I'm having a emmc chip failure.
However I didnt like it, so I flashed back to sgh-i777 firmware. However, when I turn the phone on it still says that its a gt-i900, but when I go into the phone settings it says that the model number is an sgh-i77...Any Ideas how to fix this?
Could it be that I accidently installed the i900 bootloader?
Yes I did read the stickys and I admit I had no Idea on what i was doing, but I believe learning comes from these trial errors like I just presented to you guys.
I boot the screen says i900, I gen no triangle. After everything is booted and i get to the phone- I go to phone info in settings and the phone model is an sgh-i777? is this normal??? cause in the boot menu it says its an international version.
you may have to use a usb jig to get it off. that is what works for me
How do you accidentally flash something on these phones?? The CWM that came with Entropys kernel makes accidents nearly impossible. Nearly.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
How the heck do you "accidentally" flash the wrong firmware?
Someone clearly didn't read the FAQ.
Entropy512 said:
How the heck do you "accidentally" flash the wrong firmware?
.
Click to expand...
Click to collapse
I'd guess it has something to do with a trenchcoat, a hot girl walking by, and a cop...
Sent from my VTAB1008 using XDA
Entropy512 said:
How the heck do you "accidentally" flash the wrong firmware?
Someone clearly didn't read the FAQ.
Click to expand...
Click to collapse
Didnt you read his username?
special_noob said:
However I didnt like it, so I flashed back to sgh-i777 firmware. However, when I turn the phone on it still says that its a gt-i900, but when I go into the phone settings it says that the model number is an sgh-i77...Any Ideas how to fix this?
Could it be that I accidently installed the i900 bootloader?
Yes I did read the stickys and I admit I had no Idea on what i was doing, but I believe learning comes from these trial errors like I just presented to you guys.
Click to expand...
Click to collapse
Alright, I'm going to assume your phone boots atleast. You probably see a different boot screen with a yellow triangle and i9100 correct? If so, do not worry all is not lost. You have a microSD card right? Go over to the development forum here and find a ROM you like. I use the MIUI build (purely personal preference), UnNamed is another popular build that many members here use. Download the zip file from the thread and copy it to the microSD card (do NOT extract it, leave as a .zip file).
Put the SD card back into your phone and hold down the vol up, vol down and power keys untill CWM (a text based, bios like thing) comes up. From here use the arrow keys to navigate to wipe data, press the power button to select and confirm. Then go back to the main menu and navigate to "install zip from external SD". Find your .zip file and install.
That will get you a working phone. Search the forum for how to remove the yellow triangle if you want, it is a non-issue, just a leftover from Odin.
EDIT: After re-reading your post it sounds like you got it working again, the yellow triangle thing bootscreen is not an issue at all, removing it is a little advanced but can be done. If you're just getting your feet wet I wouldn't advise changing it untill you have flashed a few roms and found one you are going to stick with.
I think he is just confused by the triangle warning screen, and that the rom works fine. sounds to me like thats all it is, anyway.
edit: if you don't have the warning triangle and it says gt-i9100 on the boot screen, fire up odin and flash this.
http://hotfile.com/dl/145854922/8415983/I777UCKH7_I777ATTKH7_ATT.zip.html
unzip and put the .tar file in the PDA slot. I'm assuming you know how to use Odin (Maybe assuming too much )
the best part is that everyone was thanked!
brent8577 said:
the best part is that everyone was thanked!
Click to expand...
Click to collapse
And you as well...
Sent from my SGH-I777 using Tapatalk
best of luck in restoring your phone to a proper working condition.
if this note helps, please click my thanks button, too!
It's like the free thanks thread!
SHOStock + ICS theme + ICS themed gb keyboard = the flashaholic cure!
I want to say thanks to nbell13 for uploading that file. It was a life saver. I was running into the same problem. Some of the i777 files are named wrong :\
I accidentally flashed an i9100 ics rom and when I restored my old stock gingerbread rom I got no call audio or mic. Ive tried unrooting to stock and resetting about a billion times to no avail. Everything seems normal except my baseband says I9100XXLPX. Any help would be great.
Try flashing a i777 modem? That might help, I'm not really sure.
does it say GT-I9100 at startup? if it does, you need to read more about flashing binaries. Creepyncrawly has a good guide on what to do. find a post he has made and look at his signature for links.
There's plenty of people on here who have done the same thing. they posted threads too. search.
Just flash a modem and you'll be fine
Sent from my SGH-I777 using Tapatalk 2
Couldn't figure how to just flash a modem, but i was able to flash a ics rom and it changed the modem. Thanks for your guys help.
mrtramplefoot said:
Couldn't figure how to just flash a modem, but i was able to flash a ics rom and it changed the modem. Thanks for your guys help.
Click to expand...
Click to collapse
You just download a modem and flash it in CWM.
mrtramplefoot said:
Couldn't figure how to just flash a modem, but i was able to flash a ics rom and it changed the modem. Thanks for your guys help.
Click to expand...
Click to collapse
Wow thats a great post!
:facepalm:
god i hope nobody see's that
mrtramplefoot said:
Couldn't figure how to just flash a modem, but i was able to flash a ics rom and it changed the modem. Thanks for your guys help.
Click to expand...
Click to collapse
Awesome! Who needs to understand the development process when we can flash **** without caring!
Sent from my SGH-I777 using Tapatalk 2
I wanted to post a thanks to Mattdm for the link he provided. I'm a new user here and I've spent the past 4 days scouring this site trying to find an answer to the issues I was having and it seems that every time I would do a search for a thread and find someone with the same issue I was looking for the majority of the replies were simply "Maybe you should try searching the forums before posting."
Perhaps that's an accurate statement, but it's not useful.
Just to document what I went through, in case anyone else finds themselves in the same position:
I have an AT&T Samsung Galaxy S2 (SGH-I777) (The splash screen says GT-I9100 on the only firmware I can get to load)
I was only able to run the CyanogenMod 9 Resurrection Edition (cm-9-20120420-ODIN-galaxys2.tar) but I had no audio on any phone calls. I could place outbound calls and they connected, but neither side heard anything.
I tried fixing this by going back to stock firmware using Odin, but I accidentally put the *.tar file in the Bootloader location and hit start (I was in a bit of a hurry and hadn't had my morning coffee yet). Odin finished and looked like it worked, the phone rebooted and it displayed the AT&T splash screen, but then just stayed on that screen and never booted.
I was able to go back to the CyanogenMod 9 Resurrection Edition, and I even tried MIUI and both boot up, but the phone didn't work in either of them.
I then found this thread with the links to the modems. I tried several different modems but none worked.
My next step was to try the modems with the MUIU firmware since it was the only other firmware I could get to work. While installing the MUIU firmware I did something a bit different from the other times I'd installed the firmware, I deleted the user data and cleared the cache partition and dalvik cache before installing the MUIU firmware.
I booted up MUIU and tested the phone and it worked!
Unfortunately I didn't want MUIU, I want Cyanogenmod 9... so, I tried installing Cyanogenmod 9 again, wiping the data and caches before doing the install and everything now seems to be working!
I now feel confident that I know where I went wrong (I installed the wrong firmware to start with, and then made a series of mistakes that made things even worse). But I also now feel confident that going forward I won't be making these same mistakes again.
I would like to officially 'thank' Mattdm to make his Thanks Meter go up, but I can't see to find a way to do that. (Edit: Looks like I have to post to the thread before I can officially 'thank' someone)
jestranho said:
. . .
Just to document what I went through, in case anyone else finds themselves in the same position: . . .
Click to expand...
Click to collapse
Very thoughtful of you.
jestranho said:
. . . While installing the MUIU firmware I did something a bit different from the other times I'd installed the firmware, I deleted the user data and cleared the cache partition and dalvik cache before installing the MUIU firmware. . . .
Click to expand...
Click to collapse
Wiping is ALWAYS a "best practice" when flashing. . .cache and dalvik when doing lightweight flashes; include data wipe when going from one ROM to another or when a ROM is showing undesirable behavior. It can be a pain, but that pain can be greatly minimized by planning ahead and backing up your user apps and data, etc. beforehand.
Phone: Samsung Galaxy S4
Carrier: Verizon
Model: SCH-I545
Problem: After root, worked for a day, then bootloop. Factory Reset does not work.
I am new to rooting and have apparently soft bricked my phone, but none of my attempts to fix it are working (and worse, i'm afraid I'm making it worse).
I rooted using these instructions.
Then I installed Titanium Backup and started ripping out all things that looked like bloatware. I may have cut too deep.
Everything seemed to work fine until I noticed that my Gallery would not open. I forced quit the app, cleared cache and reboot.
Now i have a bootloop (will not boot past the Verizon Wireless logo).
My first instinct was to factory reset (being a new phone and all). This did not help.
Then I tried to wipe the cache to no avail (though it always immediately rebooted, no status messages like on factory reset)
I tried to repeat the steps in the above link. I've tried to mix and match. I've scoured these forums (and many other sites) looking for any clues, but I'm just too new to this stuff to extrapolate lessons from other phones. I apologize if this seems an obvious repost, but I'm completely at a loss.
Any and all help would be amazing!
[EDIT]: could I have a similar problem to this S3 problem? http://forum.xda-developers.com/showthread.php?t=1840030
All of the symptoms seem to be the same.
I don't know how this went unanswered, but...
Download Odin v3.07
http://forum.xda-developers.com/showthread.php?t=2189539
Download Stock ROM (yes, big file, I cried a little too)
100% Stock: http://forum.xda-developers.com/showthread.php?t=2289325
See parent forum of above for pre-rooted/deodexed ROMs
THANK YOU!
I will try this and post my results!
OverkillSD said:
I don't know how this went unanswered, but...
Download Odin v3.07
http://forum.xda-developers.com/showthread.php?t=2189539
Download Stock ROM (yes, big file, I cried a little too)
100% Stock: http://forum.xda-developers.com/showthread.php?t=2289325
See parent forum of above for pre-rooted/deodexed ROMs
Click to expand...
Click to collapse
This COMPLETELY worked first try. I had even made it to that page at one point, but didn't download the file because I thought it was what I already had. Turns out the files I had were just tiny little ones (the kernel, I guess), and this one was the full meal deal.
Thank you, thank you, and a couple more for good measure.
mpitaji said:
This COMPLETELY worked first try. I had even made it to that page at one point, but didn't download the file because I thought it was what I already had. Turns out the files I had were just tiny little ones (the kernel, I guess), and this one was the full meal deal.
Thank you, thank you, and a couple more for good measure.
Click to expand...
Click to collapse
Glad I could help.
I've been through a lot of this before, and I know how it can suck.
overkillsd said:
i don't know how this went unanswered, but...
Download odin v3.07
http://forum.xda-developers.com/showthread.php?t=2189539
download stock rom (yes, big file, i cried a little too)
100% stock: http://forum.xda-developers.com/showthread.php?t=2289325
see parent forum of above for pre-rooted/deodexed roms
Click to expand...
Click to collapse
this didnt work for me....it keeps on failing in odin. Is there a solution to this??
devanryan14 said:
this didnt work for me....it keeps on failing in odin. Is there a solution to this??
Click to expand...
Click to collapse
Did you download the ROM that matches your build number?
Sent from my NCC 1701 using Tapatalk 4