I flashed a few roms like PACman and SHOstock and it booted up but it seems that it was lagging quite badly and camera showed a black screen. I thought it was the phone's camera that was broken. I flashed the UCLE5 rooted found here: http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 and it booted up just fine. However, camera crashes when I tried to take a picture (atleast it's not a black screen now) and it randomly crashes and reboot.
When I tried to flash UCKH7, I get stuck on the "Rethink Possible" screen and did not get anywhere else.
Can anyone help me? I bought this phone for my brother and the previous owner flashed some stuffs already so I just want it back to its original state with stock before going forward with custom roms..
Boot into recovery. With the phone off, hold all three buttons, vol+ vol- pwr, until the initial screen shows, goes black and shows again, then release buttons. Once in stock recovery, perform a wipe data/factory reset. After this, the phone should boot. Then test the camera to see if it is working correctly, and test other functions of the phone.
Does the previous owner say the phone was working fully functional before you got it?
If you get the phone to boot and working correctly, then you should flash the latest stock firmware which is UCMD8, or a good stable custom firmware. Be happy to help with that as well.
I performed the wipe in the stock recovery and it is stuck at the "Rethink Possible" screen. Only time that I got it to boot was to load the UCLE5. UCKK6 and UCKH7 didn't boot for me. I will try the UCMD8 but I don't understand why 1 stock would boot while the other one didn't.
Previous owner said it was working okay for him but he didn't know about the phone being rooted and made some kind of update or changes to the phone (software wise). I'm guessing he flashed it weirdly or something like that. I saw the count as 25 when I got into the "download recovery" portion to flash UCLE5 through ODIN. Maybe he flashed it wrongly and it has messed something up.
Since a wipe data/factory reset will not clear the problem, it is safe to assume that there is some issue with memory. Since your were able to get the phone to boot at least once, but it was not functioning normally, it is fairly safe to assume that the memory is not permanently damaged. Based on these assumptions, I would guess that there may be nand read/write corruption. My reasoning may be incorrect, but it is sensible to try to clear the nand r/w corruption next to see if that will clear up the issues.
Instructions to clear nand read/write corruption. It is critical to follow these steps in order.
Odin3 v1.85 is recommended.
Perform a wipe data/factory reset both before, and after if needed.
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.
I followed all of your steps and it seems that I am still at the "Rethink Possible" screen. Even after flashing and wiping everything according to your directions.
I downloaded the "I777UCKH7-REV02-home-low-CL503881.tar.md5.7z" which I assumed was the full UCKH7 that you mentioned in your post. After flashing and wiping, it still hangs. I flashed the "I777 UCKH7 sbl.tar" and repeated step 1 and 2, wiped and it still hangs.
When I am doing a "wipe data/factory reset" I see an error under "Appling Multi-CSC".
This is what I see,
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
Does this have anything to do with the hanging at the boot screen?
nomoney4me said:
Does this have anything to do with the hanging at the boot screen?
Click to expand...
Click to collapse
I'm not sure. Most of what I know about this phone is gained from observation of the information that people have posted in these forums over the past two and a half years. I haven't seen an issue exactly like yours, as far as I can remember. There was one case where the phone would boot into the system, but not function properly. When it was sent to Mobile Tech Videos for jtag repair, it was found to have damaged emmc memory. I just don't know whether your issue is similar to that one or not. Any further advice is beyond the scope of my understanding.
What I have seen happen a few times is that if a person keeps trying to get the phone working, eventually some operation (flash or whatever) works differently and the phone then works. This would indicate trying different equipment, as in different pc, different cable, etc. I know that the flash is completing successfully so I don't know if this is irrelevant advice or not.
Another thing to try could be re-partitioning the memory when you flash. There is an I777 pit in the download repository. I have no experience with using it, but I remember at least two cases where a phone was recovered by flashing the pit. In one case, flashing the pit with the firmware the first time didn't clear the problem, but then flashing the firmware again worked. Flashing the pit is generally considered risky, especially if you don't know exactly what the correct steps are, but at this point, what is there to lose?
Related
I have a Galaxy S 2, I777 from AT&T. I had been running UnNamed 2.0 for a while. I started messing around with different modem files trying to get my data rate a little higher. When those failed to work, I decided to go back to stock and start from scratch. This is where my trouble begins:
I flashed with ATTGalaxyS2Unroot_SGH-i777.tar using Odin 1.85. I've used that before and all was well. After this flash, I'm stuck in a boot loop. The galaxy s 2 logo just keeps recycling.
I have tried a lot of other items I've found on here in various threads about getting out of a boot loop, but have not been successful. I was able to get to the stock recovery mode, chose to wipe user data and did the "yes I'm sure" option. The phone rebooted and I have not been able to get back to it. When it tries, I get in yellow "deleting cryption meta data" and then the phone reboots.
My last attempt was flashing with i777uckh7-cl503881 full. Odin writes everything, says pass and the phone reboots. After it restarts, it quickly goes through some items:
-- Intalling package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfuly installed package...
-- Copying media files...
successfully copied meida files (yes, media is misspelled on the screen)
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
--Updating application...
Successfully updated application.
--Appling Multi-CSC...(again yes, applying is mispelled on the screen)
installing Multi-CSC
Can't access to '/system/csc/02U/system/'.
Successfully applied multi-CSC
Rebooting.
then I get the boot loop all over again. I am still able to get to download mode using the volume button, and my jig still boots to download mode too, so I think there's still hope, but I don't know what to do next.
Any help would be greatly appreciated.
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Creepyncrawly:
Thank you for your post. I didn't find anything searching for that, but, I downloaded and flashed siyah kernel and was able to get to a recovery mode.
I am now restoring the nandroid backup that I made (luckily I was smart enough to do that) before I started messing with modems and stuff.
We'll see how this goes
you sir are a life saver. I was able to restore the nand backup and boot into the os again.
creepyncrawly said:
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Click to expand...
Click to collapse
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Entropy512 said:
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Click to expand...
Click to collapse
I did not think of that, but it makes sense now. At the time, I figured I would stop and get help before I made it worse. Why I didn't restore to my backup to begin with is beyond me.
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
For those who are experiencing the "Deleting Cryption Meta Data" problem, creepyncrawly is correct, it is difficult to solve, but the following steps seem to solve it reliably:
Download and install the I777UCKH7-CL503881 Stock Binaries from creepyncrawly's download repository. Use heimdall or odin to load the stock binaries. You may need to load the param.lfs and/or the bootloaders. However, it may work without loading these files (and loading the bootloaders can be in the "danger zone")*.
With the stock binaries installed, the device will be in a boot loop, and entering recovery mode will either indicate that the device is installing CSC (unsuccessfully), or indicate that it is "Deleting Cryption Meta Data". In either case, you will be unable to actually access anything in the recovery.
In order to get to a working recovery, load the SGH-I777_ClockworkMod-Recovery_5.0.2.3. You'll need to untar this file to get to the zImage kernel file*.
With the CWM kernel installed, you should be able to actually enter recovery mode by holding down Volume Up + Volume Down + Power until the Samsung logo appears for a second time. Note: In this version of CWM recovery, the home button is the 'select' button and the power button acts as the back button. This is different than most versions of CWM.
Using the recovery run both clear data/factory rest and format sd card (in mounts and storage).
Finally, install the Siyah Kernel, using either heimdall* or CWM.
At this point, the phone should be restored, and you can re-flash the I777UCKH7-CL503881 stock kernel (on any other compatible kernel).
onecoolpilot said:
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
Click to expand...
Click to collapse
You can re-flash any kernel you like.
Thanks everyone who directed me to the steps for solving this problem!
* To load these kernel files, put the phone in ODIN mode by holding down the "Volume Down" button while the phone is connected to USB. Use either the ODIN or Heimdall tool to actually flash the device. See this post for complete instructions on flashing the files.
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Red_81 said:
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Click to expand...
Click to collapse
Is this the "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII that you bought on ebay for cheap, or a different phone?
Do you know the history of this phone? Knowing it can help with troubleshooting.
Did you ever see the "Deleting cryption meta data" error message?
As far as having vulnerability to the eMMC firmware bug, you are safe as long as you don't use the buggy kernel, which is pretty much out of the picture by now.
LOL, you read my other post. It is one and the same. The standard story from the seller. "I gave it to my Brother in Law and now it is like this." He stated it did boot properly before. Liquid indicator checks out (haven't pulled the back off to check the full indicator).
I don't get the "Deleting cryption meta data" but I do get the "multi-csc error". Wiping data doesn't seem to take care of that one.
It's really odd because I can flash ICS roms with no problems, but the GB ones stick at the bootscreen every time. Even CM7 stuck there.
I may have to try to rule out hardware damage at this point
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
creepyncrawly said:
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
Click to expand...
Click to collapse
The one from the repository with bootloaders. I tried the one without bootloaders first, but it did not fix it.
Currently I flashed over to ShoStock2. However, I'm getting alot of problems on that too (Com.android.phone not responding).
I can try to flash back to stock at any moment because I have no data on the phone.
I did try using the latest version of Heimdall, but it kept crashing at 42% (from what I read that is a known bug)
So the one thing you have not tried is flashing PIT? I wouldn't try that next if it was my phone, however, since it is the area I know the least about. There is not a whole lot of information available about using PIT with the I777 (as in nothing I could find).
The behavior of flashing to ICS and running OK but bootlooping on Gingerbread is new to me.
If you have a jig, does the jig boot the phone to download mode?
The phone should be recoverable. If it was mine, I would start by flashing the full stock package with bootloaders and param.lfs again. Then wipe data/factory reset from 3e recovery. Then flash the Gingerbread Siyah kernel. And then wipe data/factory reset from CWM Recovery.
Actually, I thought I typed that before.
I did flash the PIT file at one point out of desperation.
I have a jig that works beautifully (wipes the counter too) and has been a big help through this whole thing. That tells me I should at least have the correct bootloaders.
Do I need to let it attempt to boot between each flash or just go directly one to the other?
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
creepyncrawly said:
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
Click to expand...
Click to collapse
I actually found and tried that a few days ago. Never got that error message before. But I flashed the repair anyway. No change.
I did manage to just let the phone run for a while and all the process error messages went away, but the dialer refuses to start. I also noticed I don't think I'm getting any sound out of the earpiece.
I think I'm going to have to take the back off to check for water damage and to make sure they didn't bleach the dot.
I'll attempt to do some more flashing later tonight if the wife lets me.
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
creepyncrawly said:
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
Click to expand...
Click to collapse
Lol. Under normal circumstances indeed. I appreciate all the help so far. I wonder if there is something borked with the chip.
Sent from my SAMSUNG-SGH-I897 using XDA
Not sure if it helps much since you said you think the correct bootloaders are there but I had the exact same problem as you a couple months back. Like an idiot I flashed the original "one click" ATT ICS leak from Rootzwiki that updated my bootloaders. After this attempting to go back to CM7 resulted in me soft bricking the phone. The ONLY rom that would flash and work was that same ICS one click. Everything else Odin just failed on. Eventually I managed to get the complete stock GB back on it by flashing the full package in creepys guide several times. I gave up on Odin on my pc and had to remove Kies from my Mac so Heimdall would work but it flashed finally and I was saved. If you search through my posts here and find that thread maybe there's something in there that will help cause it sounds like you're having a bootloader issue like I did..
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks. I'll take a look.
On a side note.... I can't get any sound from the device. I'm thinking now that it might be hardware related.
Sent from my SGH-I777 using xda premium
Hiya. Phone was fine, running UnNamed v2.3.6, until the phone completely randomly started boot looping (showing the Galaxy SII name over and over).
Tried deleting user cache, etc. from CWM, this didn't help.
Read the threads here, flashed Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders from creepyncrawly's repository page. No joy, and now I've additionally picked up the "Deleting Cryption Meta Data" problem, where that's all CWM says before it boots me out.
I've been trying to follow the guide here on how to resolve the Deleting Cryption Meta Data problem, but the link in item #3 for "SGH-I777_ClockworkMod-Recovery_5.0.2.3" goes to kind of a strange post with dead download links. My understanding is most/all i777 kernals have CWM, but I definitely don't understand enough about this to feel comfortable substituting files.
Any hope for me? I borrowed a Blackberry from work for the weekend and it's considerably less tolerable since Google pulled all of its app services. If my i777 is bricked I'd rather find out sooner than later. Thanks!
1)Assuming your phone operating system is Gingerbread, go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the download repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful your 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.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution from the download repository, I777UCKH7 including the bootloaders and everything, in the PDA slot, as in step 2.
If you are unable to get any of these to flash successfully, first you should assume a bad port, or bad cable, and try other ports, other cables, even another pc. If you can get no flash to succeed, then you may have damaged eMMC memory.
In case it is damaged memory, This post from Mobile Tech Videos.
Annnd, I'm in! Thank you thank you thank you, creepyncrawly, this is amazing! I will never take a successful phone boot up for granted! (Okay, not for a little while at least.)
So would it be imprudent to restore a Nandroid backup from about a month ago? I feel like the answer is "yes," but if the bootloop was caused by firmware issues, then maybe it shouldn't matter?
Thanks so much again!
Ok, I'll start from the beginning. I wouldn't consider myself a noob, instead a novice power user. I've done my share of flashing and resurrecting my device from a soft brick before. I'd been running 10/21 build of Carbon for a solid week without issues until my phone completely froze while browsing on Dolphin browser. I hadn't restored any system data using TiBu after flashing Carbon running 4.3.1.
So with the device hung, I proceed to restart as always and got stuck on "SAMSUNG" boot logo. I did a battery pull and tried again to no avail. At this point I tried going into recovery and once I got there I had no selections on screen. Simply 6.0.4.4 CWM written at the bottom. Now I really started getting worried. I thought to go back to stock at this point through Odin and this is where things really got mucked up. I tried flashing UCMD8 using Odin 1.85 and it would hang on Sbl.bin and the last message would be "NAND Write Start". I've done a few Odin flashes before and knew this wasn't normal. Few minutes later, no progress so now I'm stuck with the "Device needs to be recovered using Kies" bull**** at power on.
After some research, I came to the conclusion that I have the NAND r/w corruption problem. So I tried flashing creepyncrawly's files from his "download repository" and all the files (stock kernel, UCKH7 system package, bootloader) would get stuck somewhere and last message would read "NAND write start". I just don't know why this happened. Things were smooth sailing and working perfectly and next second I have a semi hard brick on my hand?
Can somebody please guide me through this and try to revive my aging I777 please? Maybe one the senior members, contributors, etc? I'd greatly appreciate any effort. Like I said, I'm not a noob and can work with adb and odin, I just need to be pushed in the right direction with any ideas. :crying:
Did you follow all of these steps in order? If not, go through this sequence again, from 1 through 6.
creepyncrawly said:
Did you follow all of these steps in order? If not, go through this sequence again, from 1 through 6.
Click to expand...
Click to collapse
I knew you'd be the first to come to rescue. So I couldn't complete step 1 because it got stuck at NAND write start. So I first flashed the secondary bootloader and that got me to the Samsung Galaxy SII i9100 boot logo. Proceeded to flash siyah kernel and it's stuck at NAND write start. Maybe I have to put the pit file in for it to remap the emmc?
mpkothari said:
I knew you'd be the first to come to rescue. So I couldn't complete step 1 because it got stuck at NAND write start. So I first flashed the secondary bootloader and that got me to the Samsung Galaxy SII i9100 boot logo. Proceeded to flash siyah kernel and it's stuck at NAND write start. Maybe I have to put the pit file in for it to remap the emmc?
Click to expand...
Click to collapse
I haven't had any personal experience flashing with partitioning checked and using the PIT from the Download Repository. It it were my phone, I would try it though.
Damaged emmc memory is only one possibility. The bad flash could also be due to the connection between the computer and the phone. I would suspect and test everything else first, so use a different good cable, use a different port on the computer, even try a different computer, etc. Also, some have reported that multiple attempts to flash eventually resulted in a pass, so try multiple times.
I do have first hand experience in flashing bad eMMC with repartitioning.
It killed the phone, turning it from a "soft brick" into a "hard brick", and I had to get a new main board.
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.