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
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .
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 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?
Hey all,
First, I just wanted to say that I have searched high and low for a solution to this already without much success, so I'm coming to you guys in sheer desperation; normally these forums and/or Google turn up the answer pretty quickly, but for once I am thoroughly stumped, so I'm coming to you sages for help.
tl;dr: After failing to unlock the bootloader through Odin (failure at sboot.bin), I re-installed a previously-working stock VRALJB ROM through Odin only to be met with a frozen Samsung boot logo and an inability to enter into recovery mode. I can get the phone into download mode, but that's it. Leaving the phone on for hours has given me no results, just the Samsung logo.
Background
Before I did anything last night that caused this current situation, the phone was running an unlocked/rooted (but otherwise stock) VRALJB ROM since I purchased it second-hand back in 2013. Actually, the bootloader may not have been unlocked as I had assumed, because what started all of this was me deciding it was time for a newer, better-optimized ROM. It was certainly rooted, as I had no issues running and granting root privileges to CWM and flashing the recovery loader. This was something I have done a dozen times for other people's phones (ah, hubris), so when everything appeared to be in order for me to boot into CWM's recovery mode, I did so, but was immediately greeted with Verizon's wonderfully-annoying Yellow Triangle-o-Death. I guess that's what I get for assuming the bootloader was unlocked.
I wasn't too worried; I had already backed up everything prior to attempting this, and I had Odin and my stock ROM ready to go should anything happen. So, I did exactly that: booted into download mode, connected the phone to Odin, and installed the stock VRALJB ROM. After about 6 minutes, the phone restarted and booted into a fresh, new stock version of Jelly Bean. There were no issues with the install, and the phone was working just as it should.
Where the problem started
So, now that I knew that the bootloader had never in fact been unlocked, I began searching down the process needed to unlock it so that I could then install a custom ROM. I began following the steps found on galaxynote2root.com's page for the SCH-I605, including downloading the "GalaxyNote2UnlockVerizon" archive will all the necessary tools (CASUAL, SuckItVerizon, etc).
**NOTE**: I know, now, that there were other, better options that existed and that I should have taken that path instead, but as it had been about a year since I had attempted any kind of flashing on my phone, I was rusty on the most current best-practices for unlocking the bootloader, and just went with the first tutorial I found that matched my phone model/firmware.
I loaded up Odin, included the option to re-partition with the included .pit file, placed the BootloaderBaseline2.tar.md5 file in the Bootloader section, and hit start. Everything was going great until Odin reached the infamous sboot.bin part of the bootloader; it failed at that moment, giving me the usual error message:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
"Okay, no biggie," I thought to myself. I must have done something wrong, or maybe the bootloader baseline file was corrupt.
Assuming I had just soft-bricked my phone, I went ahead and reset Odin, loaded up the sch-i605-16gb.pit file, the stock VRALBJ ROM I had just successfully installed 20 minutes earlier, told Odin to erase everything, and hit start.
Odin had no problem re-installing the ROM. It went through the entire process again in about 7 minutes, and I was happy to see the Samsung logo pop up at the end. Only problem was, though, that the Samsung logo stayed there.
"Damn it," I thought. So, I let it sit for a while, thinking that maybe something was happening in the background, but after 10 minutes, the logo was still there. Obviously, something had gone wrong in the install, so I decided I would boot into recovery mode, clear the cache, and to a factory restore now that the ROM was "successfully" installed.
Except I can't get into recovery mode. When I do the usual Volume Up-Home Button-Power Button combo, the Samsung logo appears as it should, but stops right there; it will not enter recovery mode.
Okay, so I can't fix it that way. I'll just go ahead and re-install the ROM through Odin again. After all, I had just used this exact same .md5 ROM file only an hour earlier and the phone booted fully and I had zero issues; so, I knew that the ROM file itself wasn't corrupted.
So I tried re-installing the ROM again through Odin, but got the same result: Samsung logo, with no ability to enter recovery. I tried again and again, and even went and downloaded another copy of the stock VRALBJ ROM in the hopes that maybe something was wrong with the one I was using.
Nope. Same results.
So now my phone is bricked, and I'm at a loss as to how to get it back. I have yet to try newer ROMs, only because I don't want to update to a newer stock version and lose the ability to unlock the bootloader; after all, the entire point behind last night's excursion into madness was so that I could load a custom ROM.
That said, if installing a newer stock ROM from Samsung/Verizon is the only way of fixing this, I will do it, but I was hoping there was another way that may allow me to stay on the VRALBJ ROM as a stepping-stone to another custom ROM.
I appreciate any help I can get, and I apologize for the wall of text, but I know how important background information is when trying to diagnose and fix these kind of problems, so I assumed you guys wouldn't mind