Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
Boot into recovery, wipe data (factory reset), wipe cache and try to flash the custom ROM again.
Good luck !
The issue is, I can't even wipe factory data. It will start and then just sits there, unable to complete the wipe. I'm so out of ideas.
sooby77 said:
The issue is, I can't even wipe factory data. It will start and then just sits there, unable to complete the wipe. I'm so out of ideas.
Click to expand...
Click to collapse
Have you tried upload stock rom to phone on download mode? I saw your checked link, maybe you should try with different stock roms like 2.3.5 and etc.. If you try that, what the say ODIN as error?
Flash a siyah kernel with odin.afther you have cwm...
Inviato dal mio GT-N7000 con Tapatalk 2
First of all stop doing things that you are not sure about...
If you can get into Recovery then your problem is simple.
1. Wipe Data/Factory Reset,
2. Wipe cache partition,
3. Advanced/Wipe Dalvik Cache,
4. Flash a new rom (from sdcars probably),
5. Wipe cache partition,
6. Advanced/Wipe Dalvik Cache.
Let me know if this helped.
Hey guys, I apreciate all the responses. panagiostis4te - I am unable to wipe data/factor reset. It just hangs trying to do that. I've let it sit and it never completes.
sinasi11 - ODIN never throws an error. Depending on what firmware I flash, it either get stuck at datafs or data. It just sits there. I've even left it overnight and nothing happens.
I was able to flash to completion a few or the 4.0.4 rom (XWLPF) and it would reboot, show the android logo with animated progress bar. Then it reboots and is then stuck at the Galaxy S2 very first boot screen. I'm so out of ideas.
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
Questions:
1 . Have you seen This Warning Thread before?
# I don't think so
2. Were you running a safe Custom kernel before flashing Chameleon?
# I don't think so.
Here are my conclusions
1.
You were affected by the infamous Brick bug.
# You should blame yourself for this, for apparently failing to read that sticky warning thread, or even ask questions before messing with your phone while running the Dreadful ICS 4.0.4 firmware!
2.
The reason why your phone is still partially coming on is because you have a partially insane emmc chip.
# If you were using a fully insane chip, your phone would just black out without any sign of life.
3.
Your Nand /Emmc chip is corrupt!
4.
You can try combinations of pit file and ICS bootloader (where suggested). Who knows, you might be lucky
# Visit here and try the suggested solution
## If it doesn't work, then you can try the combinations suggested here.
5.
Jtag service will probably not work for you.
6.
The only (probably) solution (if the suggestions in 4. doesn't work for you), will be for you to replace the motherboard of your phone.
# Changing motherboard costs between $120 to $200
7.
If your phone is still under a valid warranty, the best solution would be to send it to Samsung Service center. Repair if free.
Sorry about what happened to your phone, but you really must shoulder the blame!
jokesy - thanks for the suggestions. I accept the blame. I was running stock and I read the Chameleon 1.3 thread and didn't see any warnings. I thought everything was safe. I guess lesson learned the hard way!
sooby77 said:
jokesy - thanks for the suggestions. I accept the blame. I was running stock and I read the Chameleon 1.3 thread and didn't see any warnings. I thought everything was safe. I guess lesson learned the hard way!
Click to expand...
Click to collapse
have tried my suggestion 4 yet? any news?
It's a Monday and I've got lots of things I need to take care of I've tried some of the suggestions prior to starting this thread but I'm going to give it another shot. Meanwhile, I'm going to try and survive without a phone for a few days. I'm almost ready to give up. I'm going to work on it more tonight. Will post if I have questions. Thanks again jokesy!
jokesy - I want to report success. I tried several of the pit files and finally at
i9100_u1_02_20110310_emmc_EXT4--patched--brick-between-176-and-2323-MB--FACTORYFS-moved-by-2048-MiB.pit
I was able to get it to complete install and format with bootloaded. The device then booted up! I now have 9.5GB vs 11GB and that's OK. Thank you so much for your help. It's now not the perfect S2, but nevertheless, a usable one! I sincerely appreciated your help. Lesson learned truly the hard way!
sooby77 said:
jokesy - I want to report success. I tried several of the pit files and finally at
i9100_u1_02_20110310_emmc_EXT4--patched--brick-between-176-and-2323-MB--FACTORYFS-moved-by-2048-MiB.pit
I was able to get it to complete install and format with bootloaded. The device then booted up! I now have 9.5GB vs 11GB and that's OK. Thank you so much for your help. It's now not the perfect S2, but nevertheless, a usable one! I sincerely appreciated your help. Lesson learned truly the hard way!
Click to expand...
Click to collapse
Wow! that's a good news at least.
PS: Always try to go through all the sticky threads, they are made for some reasons. Also if you are not sure about something, search, if you can not find clear answers, then ask questions.
Enjoy your phone
Jokesy said:
Wow! that's a good news at least.
PS: Always try to go through all the sticky threads, they are made for some reasons. Also if you are not sure about something, search, if you can not find clear answers, then ask questions.
Enjoy your phone
Click to expand...
Click to collapse
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
sooby77 said:
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
Click to expand...
Click to collapse
I seriously don't know but if you have any important thing you want to extract from your backup, follow these steps:
1. Flash siyah kernel
2. boot to CWM recovery,
- dual boot options
- restore ROM to 2nd ROM (you need about 2.1 Gig free in your internal storage)
- done
3. Boot to your Second ROM
- Extract all info you need
4. Restore these info to your 1st ROM
5. you can delete the Second ROM when done, using the same dual boot menu in CWM recovery.
Thanks Jokesy. I did have 2 backups, Titanium and another backup app (name escape me at the moment). I think I'll restore app data and do it that way instead.
Just go back to original OS
sooby77 said:
Hi all,
I was running XWLPT and decided to try Chameleon 1.3. After flashing, it would not boot up. I've tried all kinds of things for the last 2 days, and read quite a bit. I've even tried the method in this thread http://forum.xda-developers.com/showthread.php?t=1457458
At the moment, I can get into recovery and I can get to download (power+vol down+middle button). But it's stuck at the Galaxs SII GT-I9100 very beginning boot up. Nothing seems to be working. I've tried several pit repartition and I know it's risky. But at this point, I have nothing to lose I guess.
Can anyone help?
Click to expand...
Click to collapse
You can go back to the original OS using Odin and a package found on many sites for the original Gingerbread that came on it... then go to Kies and update to the ICS and there you go. I have done this several times and unbricked mine after a mod. This was the best way for me.
Scott
sooby77 said:
A quick question. Now that the pit is different, I assume that the nandroid backup I made cannot be restored to the device anymore?
Click to expand...
Click to collapse
You said you have Titanium - it can restore elements out of a nandroid backup, almost everything, stright back into place. Much easier than second ROMs.
ScottsDesk said:
You can go back to the original OS using Odin and a package found on many sites for the original Gingerbread that came on it... then go to Kies and update to the ICS and there you go. I have done this several times and unbricked mine after a mod. This was the best way for me.
Scott
Click to expand...
Click to collapse
I've tried that and the flash would get stuck in Odin and never complete.
gyaku_zuki said:
You said you have Titanium - it can restore elements out of a nandroid backup, almost everything, stright back into place. Much easier than second ROMs.
Click to expand...
Click to collapse
Good to know. I am actually waiting for my microsd to sd adaptor to arrive. I accidentally formatted my microsd card with all my data in desperation of trying whatever method to format the device. I accidentally selected format emmc. Took out the card immediately, and am hoping to be able to unformat it in windows since it's using fat32. Fingers crossed!
Related
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.
I recently updated my phone from 2.3.3 to Cyanogenmod 7.1 I believe and went to overclock the phone, Unfortunately, I overclocked it too much and now it is stuck in an endless loop on the boot screen..
Phone is obviously a Galaxy Ace, Network carrier is Vodafone UK.
I have been trying for the last two hours to look for answer's on how to fix this and I haven't found anything, So I thought the best idea was to come to here.. Any help would be appreciated, I have also tried to install other ROM's on to the phone to correct it but it look's like the CPU is still at the overclocked setting and because of that, Won't boot up.
thanks.
Dan.
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
madman_amit said:
go to recovery and wipe data+cache and try to boot..
if still no luck --> ODIN
Click to expand...
Click to collapse
I tried wiping everything before but will give ODIN a try. Thank you. I really like the phone and am trying my best to get it working again. lol
So, I downloaded ODIN and I have absolutely no idea what I am doing.. I don't want to risk breaking the phone anymore.. The only tut on how to use ODIN is for the Galaxy 3..
I have never done anything like this before so it's all new to me.. :/
Ok, I used ODIN and I have the original ROM that came with the phone, But still in an endless loop on the Samsung boot screen.. :/ I am totally stuck now.. I have tried all I know to get it to work
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Th3GrimRipp3r said:
I managed to sort the problem, the "One Package" on ODIN didn't work, Luckily I had the 4 seperate files needed on my laptop, So all is workign now.
Click to expand...
Click to collapse
Excellent work having a backup on your laptop. First thing now do a full backup on your phone before you think about further experiment. If overclocking make sure "set at boot" is not ticked. Finally read up a little on xda before you do anything - a good place to start is "Tutorial" on top of dev section and the "q & a " thread here.
I hope this works for You.
You've a one packege STOCK Rom?
so open ODIN 4.38
Untick Reset Time
Choose your one package file.
choose OPS; attatched here.
press start.
to sum up: you have this ticked only:One package, auto reboot, protect OPS
if doesnot work go to recovery and try factory reset& cache wipe.
if doesnot work, try flshing CWM and install any backed up rom, if you want one. just PM and i will upload backed up stock rom.
I really hope it helps because I got the same issue after flshing a stock from ODIN, but been removed from wipe data& factory reset.
_________________________________________________
If I've helped you in any way, Press THANKS
i have my wifes att gs2. i rooted succesfully with official ics version. made a nandroid backup. attempted to flash an aokp rom (which is what i use on my lg phone). upon reboot it just stuck at samsung gs2 screen. couldnt get into recovery to restore the backup at first. now i am able to get into recovery but now it get and md5 mistmatch when tryin to restore the backup. when i rooted it changed the boot screen to i9100 when the phone is an i777. please help.
thanks
woodardbg said:
i have my wifes att gs2. i rooted succesfully with official ics version. made a nandroid backup. attempted to flash an aokp rom (which is what i use on my lg phone). upon reboot it just stuck at samsung gs2 screen. couldnt get into recovery to restore the backup at first. now i am able to get into recovery but now it get and md5 mistmatch when tryin to restore the backup. when i rooted it changed the boot screen to i9100 when the phone is an i777. please help.
thanks
Click to expand...
Click to collapse
You need to read a little more. The i9100 screen is because you have tripped the flash counter. Recovery is holding power and both volumes forever. Then you Factory reset.
Also maybe next time make the thread title something about the problem you're having. HELP isn't really telling much.
122ninjas said:
You need to read a little more. The i9100 screen is because you have tripped the flash counter. Recovery is holding power and both volumes forever. Then you Factory reset.
Click to expand...
Click to collapse
ive been trying to read up on it. unfortunatley there are different methods scattered everywhere and confusing. however when i do a factory reset its sticks at gs2 gti9100 screen. if you can point me to a thread that has a fix i'd appreciate it. coming from lg forums, these gs2 forums and fixes are a little confusing to me. i guess because of the different variants of the s2's.
thanks
Phalanx7621 said:
Also maybe next time make the thread title something about the problem you're having. HELP isn't really telling much.
Click to expand...
Click to collapse
Not to mention it is also useless for those who respect the forum by doing a search before posting.
woodardbg said:
ive been trying to read up on it. unfortunatley there are different methods scattered everywhere and confusing. however when i do a factory reset its sticks at gs2 gti9100 screen. if you can point me to a thread that has a fix i'd appreciate it. coming from lg forums, these gs2 forums and fixes are a little confusing to me. i guess because of the different variants of the s2's.
thanks
Click to expand...
Click to collapse
Factory reset then flash AOKP FOR OUR PHONE
122ninjas said:
Factory reset then flash AOKP FOR OUR PHONE
Click to expand...
Click to collapse
thanks for your help 122nijas.... ive tried a "supposedly" aokp rom for gs2 i777 but it doesnt come up after reboot. just hangs at the gs2 i9100 screen. i have tried a couple more but nothing seems to work to get a working driver. to me it seems like if i flash a compatible rom, it should work. i am able to get into cmw fine. on top of that, my backup that i did have that had md5 mismatch is no longer there. so when i connect to my pc and usb and navigate to clockwork mod folder it says file is corrupt. so now i have lost that initial bacup it seems.
so what course of action do you think i should try now?
again thanks for ur help
woodardbg said:
thanks for your help 122nijas.... ive tried a "supposedly" aokp rom for gs2 i777 but it doesnt come up after reboot. just hangs at the gs2 i9100 screen. i have tried a couple more but nothing seems to work to get a working driver. to me it seems like if i flash a compatible rom, it should work. i am able to get into cmw fine. on top of that, my backup that i did have that had md5 mismatch is no longer there. so when i connect to my pc and usb and navigate to clockwork mod folder it says file is corrupt. so now i have lost that initial bacup it seems.
so what course of action do you think i should try now?
again thanks for ur help
Click to expand...
Click to collapse
Where are you getting the rom from
Flash another rom ... and for the i9100 screen use this http://forum.xda-developers.com/showthread.php?t=1494114
Sent from my SAMSUNG-SGH-I777
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
My S3 i9300 is gets stuck on the welcome screen and none of the buttons work. I've tried dozens of official firmwares and the latest i9300XUFME7 test firmware as well to fix the problem but all to no avail. I've tried different recoveries, CWM, Philz and TWRP and I've tried wiping cache, data/factory reset and dalvik cache but still the phone gets stuck on the Welcome screen. What is the problem and more importantly what is the solution? I'm thinking of trying the next flash again with Auto Reboot, F.Reset Time and Re-Partition checked and also to check the Nand Erase All if my phone survives the next flash. Any suggestions?
okizen said:
My S3 i9300 is gets stuck on the welcome screen and none of the buttons work. I've tried dozens of official firmwares and the latest i9300XUFME7 test firmware as well to fix the problem but all to no avail. I've tried different recoveries, CWM, Philz and TWRP and I've tried wiping cache, data/factory reset and dalvik cache but still the phone gets stuck on the Welcome screen. What is the problem and more importantly what is the solution? I'm thinking of trying the next flash again with Auto Reboot, F.Reset Time and Re-Partition checked and also to check the Nand Erase All if my phone survives the next flash. Any suggestions?
Click to expand...
Click to collapse
sounds not good to be honest, did you check:
(1) try a stock rom flash with prior use of mega wipe (deletes anything, only leaves ext. sd card)
(2) read the SDS thread (not sure if your phone might concerned though)
(3) read the occasional freeze thread
okizen said:
My S3 i9300 is gets stuck on the welcome screen and none of the buttons work. I've tried dozens of official firmwares and the latest i9300XUFME7 test firmware as well to fix the problem but all to no avail. I've tried different recoveries, CWM, Philz and TWRP and I've tried wiping cache, data/factory reset and dalvik cache but still the phone gets stuck on the Welcome screen. What is the problem and more importantly what is the solution? I'm thinking of trying the next flash again with Auto Reboot, F.Reset Time and Re-Partition checked and also to check the Nand Erase All if my phone survives the next flash. Any suggestions?
Click to expand...
Click to collapse
Try this method. It worked in my phone after strugling five days reading and trying different methods!
Best wishes!
chrismast said:
sounds not good to be honest, did you check:
(1) try a stock rom flash with prior use of mega wipe (deletes anything, only leaves ext. sd card)
(2) read the SDS thread (not sure if your phone might concerned though)
(3) read the occasional freeze thread
Click to expand...
Click to collapse
khaaba said:
Try this method. It worked in my phone after strugling five days reading and trying different methods!
Best wishes!
Click to expand...
Click to collapse
Thanx guyz. I've tried both methods but unfortunately the result was the same.
Anyway any further help would be appreciated.
If the rescue firmware didn't help then it's a hardware fault.
Sent from my GT-I9300 using Tapatalk
okizen said:
Thanx guyz. I've tried both methods but unfortunately the result was the same.
Anyway any further help would be appreciated.
Click to expand...
Click to collapse
After what I told you to do[method which was successful in my case], if you still stuck there, goto recover mode[vol up+home+power] and do factory reset. It should work!
boomboomer said:
If the rescue firmware didn't help then it's a hardware fault.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
khaaba said:
After what I told you to do[method which was successful in my case], if you still stuck there, goto recover mode[vol up+home+power] and do factory reset. It should work!
Click to expand...
Click to collapse
Thanx guyz. But still no joy. Like boomboomer says it must be hardware fault because all my hard buttons work and the phone shows up correctly when connected to my pc but there is no touch response when I get to my Welcome screen on the phone so I'll take it to the Samsung Repair Centre but before I do I want to know is there any repair tar or zip I could try to use?
okizen said:
Thanx guyz. But still no joy. Like boomboomer says it must be hardware fault because all my hard buttons work and the phone shows up correctly when connected to my pc but there is no touch response when I get to my Welcome screen on the phone so I'll take it to the Samsung Repair Centre but before I do I want to know is there any repair tar or zip I could try to use?
Click to expand...
Click to collapse
Well, you may try this. It will do re-partition, format your phone and will make it as if your phone just comes out of FACTORY
Go here and download "I9300XXEMG4_KOR_MULTI_FACTORY", extract and install. Installation guide is found here.
Thereafter, flash your phone again using your country's FW via Odin with PDA option! Hope it works. In my case, it worked like a charm! I re-partitioned my phone three times already while doing experiments! It's ok! It must work!!
I even mixed[JB4.3's Bootlodaer, PDA and Modem + JB 4.1.2's CSC] this way[see attachment]! If you know what you are doing, all goes well!
khaaba said:
Well, you may try this. It will do re-partition, format your phone and will make it as if your phone just comes out of FACTORY
Go here and download "I9300XXEMG4_KOR_MULTI_FACTORY", extract and install. Installation guide is found here.
Thereafter, flash your phone again using your country's FW via Odin with PDA option! Hope it works. In my case, it worked like a charm! I re-partitioned my phone three times already while doing experiments! It's ok! It must work!!
I even mixed[JB4.3's Bootlodaer, PDA and Modem + JB 4.1.2's CSC] this way[see attachment]! If you know what you are doing, all goes well!
Click to expand...
Click to collapse
I have had the phone repaired. The technicians told me that it was a hardware problem. I reckon they charged me too much but hey, at the end of the day I've got my phone, fully working, back again.
okizen said:
I have had the phone repaired. The technicians told me that it was a hardware problem. I reckon they charged me too much but hey, at the end of the day I've got my phone, fully working, back again.
Click to expand...
Click to collapse
Aha! Congrats!!
khaaba said:
Aha! Congrats!!
Click to expand...
Click to collapse
Thanx for assisting me.