hey guys im not new to flashing or anything but im new to the SGS2.
so im in canada. i bought an unbranded unlocked SGS2 off of a dude.
So i went to flash CWM, it did, with success. it rebooted and it just stays at at the boot screen with the yellow sign. wth? i tried loading the ATT one and that gets me a lil further. it gives me the animated samsung logo and then gets stuck there. \
i tried to mount my usb drive via CWM and that failed as well. Then I decided to try and fix things and i downloaded a BELL stick firmware (im in canada) + kernel and it goes straight to the stock recovery with logs in the bottom in yellow telling me all sorts of failed things.
what the hell guys? did i miss something critically important? i never had this much trouble with my captivate or with my desire.
hostilebynature said:
hey guys im not new to flashing or anything but im new to the SGS2.
so im in canada. i bought an unbranded unlocked SGS2 off of a dude.
So i went to flash CWM, it did, with success. it rebooted and it just stays at at the boot screen with the yellow sign. wth? i tried loading the ATT one and that gets me a lil further. it gives me the animated samsung logo and then gets stuck there. \
i tried to mount my usb drive via CWM and that failed as well. Then I decided to try and fix things and i downloaded a BELL stick firmware (im in canada) + kernel and it goes straight to the stock recovery with logs in the bottom in yellow telling me all sorts of failed things.
what the hell guys? did i miss something critically important? i never had this much trouble with my captivate or with my desire.
Click to expand...
Click to collapse
The yellow sign just means you're not on a stock kernel; it doesn't mean anything's wrong with the phone. You can buy a USB jig for a few bucks off Amazon to get rid of it or just put a stock kernel.
yes i realize that brother, but it doesnt go anywhere. it doesnt do anything. and i did flash stock firmware and kernel and nothing happens. it just stays there. and i cant even mount my usb storage via cwm.
hostilebynature said:
hey guys im not new to flashing or anything but im new to the SGS2.
so im in canada. i bought an unbranded unlocked SGS2 off of a dude.
So i went to flash CWM, it did, with success. it rebooted and it just stays at at the boot screen with the yellow sign. wth? i tried loading the ATT one and that gets me a lil further. it gives me the animated samsung logo and then gets stuck there. \
i tried to mount my usb drive via CWM and that failed as well. Then I decided to try and fix things and i downloaded a BELL stick firmware (im in canada) + kernel and it goes straight to the stock recovery with logs in the bottom in yellow telling me all sorts of failed things.
what the hell guys? did i miss something critically important? i never had this much trouble with my captivate or with my desire.
Click to expand...
Click to collapse
Lack of proper research would lead to these types of things
1.Did you make note of exactly what model of SGS2 you have?
2.Do you know what ROM the phone was running before you decided to flash?
Give us information about the device before you flashed, right now the only option I see for you is to go to Intratech's official firmware thread Here, download a firmware and flash through Odin and hopefully it should boot if it's the international version, IF it isn't then it's a guessing game
hey, yeah you're right man, i got too excited to get things running.
i believe it was running just stock firmware but im unaware of what version.
the box says
samsung galaxy II GTI9100M
GTI9100HSB *BKNRB
and ive already went to that thread and downloaded the bell stock firmware and the kernel and it still didnt go. i flashed the firmware, rebooted, then the kernel, rebooted. nothing
You always need to flash CM7 twice. The CWM/CM7 install process is broken and the first attempt doesn't actually do anything other than stuff things up.
Boot into CWM again, do a full wipe, flash CM7 twice and you should be ok.
hey, yeah i just tried doing that, it did nothing. i also have a hard time getting into recovery for some reason. is there something special i sohuld be doing? i turn the phone off and press power+ home+ vol up and most of the time it doesntgo into it.
hostilebynature said:
hey, yeah i just tried doing that, it did nothing. i also have a hard time getting into recovery for some reason. is there something special i sohuld be doing? i turn the phone off and press power+ home+ vol up and most of the time it doesntgo into it.
Click to expand...
Click to collapse
That's normal. It's picky about timing.
It might pay to try flashing a complete firmware via Odin, either stock or custom, probably doesn't matter. Litening is a good starting point assuming it's compatible with your particular phone.
FWIW - Your phone looks like it's definately a Bell Canada model, you could also try to flash an original firmware back from this thread:
http://forum.xda-developers.com/showthread.php?t=1075278
Then investigate from there and see if you need to do anything else to get it to behave.
man, im really sorry to ask you to spoon feed me here, but i have no idea which firmware to choose from that list, can you help me out?
i also just tried flashing the lightning rom thur odin and it still gets stuck in what i guess is called the bootloop. just a black screen saying samsung galaxy s2 gt-i9100.
edit: one more thing, i originally flashed cwm without being rooted, is that something to think about?
ok, so i seem to have it working now?
i flashed the ATT clockwork mod...my home button doesnt work, but i still somehow managed to clear the cache, and delete user data after. the phone booted up and is running lightning rom.
i get into the rom and none of my bottom buttons work. (menu, home, back)
so i flashed the regular CWM and it doesnt boot up again. any ideas?
when i finally get into cwm 4, when it loads up it tells me right away at the bottom
cant mount /cache/recovery/command
cant mount /cache/recover/log
cant open /cach/recovery/log
cant mount /cache/recovery/last_log
cant open /cache/recovery/last_log
if i try and wipe cash i get
Formatting /cache
E: format_volume: make_extf4fs failed on /dev/block/mmclbk0p7
Cache wipe complete
in fact if i try and do anything i get that same error .
whats the deal guys?
You can probably get yourself back to a normal state by flashing the stock firmware/modem/CSC/kernel from SGS2 Bell/Virgin Canadian Thread Q&A (Root/Unlock/Firmware) Modems KG6/KH3/KI1/3/4, if that is indeed your model.
Also from that thread (I presume he means lose):
KayvinM said:
We do not have a CF-Root version of our kernel so just flash any kernel using the instructions provided in the link and flash the stock kernel back (found below). Root will remain as well as the CWM app but you will loose clockwork mod recovery.
Click to expand...
Click to collapse
i tried that. i loaded the firmware, then it rebooted and it went right into recovery and gave me a bunch of errors. mostly unable to mount this and that.\
i then went and downloaded the matching kernel and flashed that and that made no diference.
Guys honestly ill paypal $20 to whoever can help me get this sorted out. Im in a tougg situation here.
hostilebynature said:
man, im really sorry to ask you to spoon feed me here, but i have no idea which firmware to choose from that list, can you help me out?
Click to expand...
Click to collapse
Just grab the Bell one.
i did, and the matching kernel. it didnt work. it fixed the bootloop but it goes right into recovery and shows a bunch of mount errors
You said you tried going into the bootloader (not recovery) and flashing the stock Bell ROM via ODIN?
yeah i flashed the stock bell firmware and kernel via odin and it still didnt work, it just went right into the stock recovery followed by a lot of mounting issues. it's weird. i definately dont have a 4 button att galaxy s2. i have the one big middle button and 2 soft keys. the phone will ONLY boot if i flash att cwm. but the buttons arent the same.
all of this started when i flashed CWM 4.
edit: no, i didnt flash anything to the bootloader via odin. all the things i flashed i checked off as .pda in odin.
everything else i tried to flash it just gives me mount errors.
example; i flashed lightning rom (while having cwm flashed) and it just stayed in bootloop. then i flashed the ATT cwm and it booted no problem. it let me go into recovery and clear the cache and delete user data. only problem is all the buttons are messed up. as soon as i flash back to cwm, it blootloops again and it wont mount anything. i cant clear cache, cant delete user data and cant load usb storage.
im so very confused.
edit: also, while im in cwm 4 and i try and mount stuff, it just says error, example
Error mounting /cache!
Error mounting /data!
Related
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.
I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?
Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Nick281051 said:
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I checked it out..seems like putting the Stock back on might help me. Just so that I understand this better before I do it, am I installing the UCLE5_Stock_Rooted.tar using ODIN and that is enough to get me through.
Thanks
creepyncrawly said:
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Click to expand...
Click to collapse
Thanks for stopping by. I did not see your post when I posted my reply to the previous poster..I am so worried that I might screw it up more that I wanted to be doubly sure about this. from what I read, I am doing Step 2c as indicated below. Am I correct?
Thanks
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
UPDATE: I did download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package and extracted the file. Double clicked on it with the phone connected and all I see are the words I777- UCKH7 with Root with a lot of empty boxes below. Went to Odin and I see the phone connected (Com has yellow box) but nothing else is ticked off. Clicking Start does not do anything at all.
At my wits end- will not get any sleep tonite if I don't fix it.
Thanks in advance
I had a similar thing happen after trying to make a backup of the stock rom with Rom Manager (Yes, I know now, thanks much.)
If you keep trying new kernels/roms and it never clears up, you're pretty much stuck with wiping data. It won't wipe your sdcard, but more and more apps are sticking their data in the phone's memory rather than on the sdcard, so if you can get a backup at all, you really should.
Source: Was up until 2:30 the other night trying to make my phone work again. The above is a GUESS - it's probable I missed something that creepyncrawly wouldn't.
Ok more progress..turned off the phone and started 'I777UCKH7 OCD With Root.exe". Got the same window with lot of empty boxes. Had turned off the phone by this time and disconnected it. Now, I connected the phone and pressed the volume buttons. Phone goes into Download mode. Now, the Odin3 window has a Com port for the phone. Now I press start and it goes through a bunch of things before it declares "FAIL" in red. What do I do?
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
This stuff makes me so sad seeing these threads............ Thanx for helping him Creepy, ALWAYZ with 100% accurate info!!! Looks like this is the page he got the tar from in the zip on step 3 http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/ Much respect Creepy.....
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
g.kupster said:
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
Click to expand...
Click to collapse
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
creepyncrawly said:
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
Click to expand...
Click to collapse
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
g.kupster said:
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
Click to expand...
Click to collapse
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
creepyncrawly said:
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
Click to expand...
Click to collapse
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
g.kupster said:
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
Click to expand...
Click to collapse
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
creepyncrawly said:
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
Click to expand...
Click to collapse
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
g.kupster said:
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
Click to expand...
Click to collapse
Post the answer when you have your phone in hand and I'll suggest something to try.
creepyncrawly said:
Post the answer when you have your phone in hand and I'll suggest something to try.
Click to expand...
Click to collapse
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
g.kupster said:
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
Click to expand...
Click to collapse
I'm not working from first hand experience, but I'm fairly good at correlating information and making deductions. Something in the sequence of events doesn't add up to me. You're sure you have the I777? You pulled the battery and looked at the label?
At this point any suggestions that I can offer are based on educated speculation. The first thing to try would be to flash an ICS kernel using Odin, but you have already done that. I would suggest that you try that again, but discard the tar you already have and download the tar again, from here. That may be the same place you downloaded it before, not sure. Be sure to use the original USB cable that came with the phone.
- i can get into recovery mode (normal recovery mode, not clockwork)
- i can get into download mode
- i am with Bell in Canada
Here's what lead to this error:
I updated the phone, through samsung kies to 4.0.3.
I followed this guide to root my phone: http://forum.xda-developers.com/showthread.php?t=1501719
I installed the jelly bean supernexus (i19100) rom but i forgot to wipe before doing it
after it installed, i wiped and it just stuck and rebooted and the phone wouldnt turn on
so, i used odin to flash the stock bell samsung rom and now the it gets stuck at the logo
Further research led me to this: http://forum.xda-developers.com/showthread.php?t=1760107. Would it help? I have no idea what LQ5/LPM is.
I just want it to work I dont care what rom
Any help would be appreciated, thanks!
interioralligator said:
- i can get into recovery mode (normal recovery mode, not clockwork)
- i can get into download mode
- i am with Bell in Canada
Here's what lead to this error:
I updated the phone, through samsung kies to 4.0.3.
I followed this guide to root my phone: http://forum.xda-developers.com/showthread.php?t=1501719
I installed the jelly bean supernexus (i19100) rom but i forgot to wipe before doing it
after it installed, i wiped and it just stuck and rebooted and the phone wouldnt turn on
so, i used odin to flash the stock bell samsung rom and now the it gets stuck at the logo
I just want it to work I dont care what rom
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Can't you wipe data in normal recovery mode?
Sent from my Nexus 7 using xda premium
kilometers4 said:
Can't you wipe data in normal recovery mode?
Click to expand...
Click to collapse
Nope, same thing, it gets stuck at Formatting data.... and then after a while (~7-10min) reboots and gets stuck at the logo.
I researched some more and found this: http://forum.xda-developers.com/showthread.php?t=1760107. But I don't know what LQ5, LPM is. Would it help?
LQ5 and LPM are the frimware versions ... From what I can tell, Jelly Bean SuperNexus ROM is LPX. Although the problem you describe and the problem the thread you linked sound pretty much the same, at this point I don't think that you have much to lose here.
Before you do, was Odin successfully able to flash the stock ROM on there, or did it fail? If you're not sure, try again and take note. If it was successful, it sounds like your problem might be slightly different from what is described in the linked thread you posted. If it wasn't, then I'd say you don't really have much to lose by trying it out. Your phone is currently useless, if you try the fix in that thread and it doesn't work, it's still useless and you're in the same place you are now... Although there is a small possibility that that place my be a little more permanent...
Porkchops said:
LQ5 and LPM are the frimware versions ... From what I can tell, Jelly Bean SuperNexus ROM is LPX. Although the problem you describe and the problem the thread you linked sound pretty much the same, at this point I don't think that you have much to lose here.
Before you do, was Odin successfully able to flash the stock ROM on there, or did it fail? If you're not sure, try again and take note. If it was successful, it sounds like your problem might be slightly different from what is described in the linked thread you posted. If it wasn't, then I'd say you don't really have much to lose by trying it out. Your phone is currently useless, if you try the fix in that thread and it doesn't work, it's still useless and you're in the same place you are now... Although there is a small possibility that that place my be a little more permanent...
Click to expand...
Click to collapse
Yes, I flashed the stock ROM twice and Odin (v1.85) said it was succesful both times. I only set the PDA (with the rom) and left everything else (PIT, CSC, etc) blank and I made sure re-partition was unchecked.
Thanks for responding!
ok, now i cant get into recovery, it says in red text "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." There is a pic of a red android with a exclamation sign. I can boot into download mode but wheneever i try to flahs something from keys it gets stuck at setupconnection....
interioralligator said:
ok, now i cant get into recovery, it says in red text "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." There is a pic of a red android with a exclamation sign. I can boot into download mode but wheneever i try to flahs something from keys it gets stuck at setupconnection....
Click to expand...
Click to collapse
Just relax first of all you need a stock rom bro which have 4 files code , modem, csc & pit files
Just flash that rom there you govnow ur phone is unbricked
Yea but when I try to flash from odin, it gets stuck at SetupConnection...
Thanks for the helping, btw!
Ok, lol, now I can flash again. I have a question: to flash a PIT file (the one I found in OP) do you have to tick re-partition or leave it unchecked?
Also, I still cant wipe data (it gets stuck at:
formating /data....
for a looooooooooong time and then reboots.
I have a trouble the same with interioralligator. are you sovle it? Please for me a solution for this case. Thanks
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
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
the donkey said:
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
Click to expand...
Click to collapse
Do you mean you can't even get into recovery? If it can, I would think a data wipe might get the ROM to be able to boot.
the donkey said:
hi hoping someone can help. i have a samsung galaxy s2 i was trying my hand at rooting but now the phone wont do anything but reboot. i even bout one of those jigs. i can get it into download mode i install odin then a kernal i have also an official s2 firmware but no matter what i do it will only reboot constant anyone any ideas or suggestions cheers in advance and if iv cocked up on the tread i appologise in advance
Click to expand...
Click to collapse
You might want to double check if you are using the right version of recovery that kernel is fully supported with your ROM. For example, if you are trying to install a KK ROM using an old version of CWM you will end up in error 7 or end up in a boot loop screen. My words are pretty mess up but I hope you get what I mean. So make sure you have the right version that match each other (recovery, kernel, ROM).
Hope that helps.
im new to all of this. when i hold the home button the power button and the vol down button i get a screen telling me installing a custom os could be bad press up to continue i do this and install even the official software but when it reboots it keeps looping on the samsung logo
cglegion said:
You might want to double check if you are using the right version of recovery that kernel is fully supported with your ROM. For example, if you are trying to install a KK ROM using an old version of CWM you will end up in error 7 or end up in a boot loop screen. My words are pretty mess up but I hope you get what I mean. So make sure you have the right version that match each other (recovery, kernel, ROM).
Hope that helps.
Click to expand...
Click to collapse
i cant access the phone to see what kernal was on it so i am just trying to get it back to normal
the donkey said:
i cant access the phone to see what kernal was on it so i am just trying to get it back to normal
Click to expand...
Click to collapse
I suggest you flash a working recovery via odin first. Look for TWRP, it's the best newbie-friendly recovery or try CWM if you are looking for more advanced options. After that, flash a stock or custom ROM to get your phone back working. Make sure they are compatible with each other. Why didn't it work when you try flashing the stock firmware via odin? Make sure the zip file is downloaded properly.
Hope that helps.
cglegion said:
I suggest you flash a working recovery via odin first. Look for TWRP, it's the best newbie-friendly recovery or try CWM if you are looking for more advanced options. After that, flash a stock or custom ROM to get your phone back working. Make sure they are compatible with each other. Why didn't it work when you try flashing the stock firmware via odin? Make sure the zip file is downloaded properly.
Hope that helps.
Click to expand...
Click to collapse
that sounds excellent but being new and a bit thick what is a twrp and where would i get one?
still no joy
ok so now i have tried 3 official samsung roms h3g o2 and t mobile the h3g installs but just keeps looping the boot screen the o2 failed and the t mobile installes but all i get is a blck screen but it showes the batter the clock and the usb conection i can also go into it through my computer but it wont boot up properly. is it possible to get a samsung rom thats not network based?
the donkey said:
ok so now i have tried 3 official samsung roms h3g o2 and t mobile the h3g installs but just keeps looping the boot screen the o2 failed and the t mobile installes but all i get is a blck screen but it showes the batter the clock and the usb conection i can also go into it through my computer but it wont boot up properly. is it possible to get a samsung rom thats not network based?
Click to expand...
Click to collapse
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
il give it a go
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
il try that just now cheers
ahhh my heed
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
ok so i downloaded the romnuke and the neatrom the instructions say... Boot into Recovery
- Install RomNuke (Does all clean & backup your android folder as well) - Thanks to Hawkerpaul
- Install ROM
- Reboot & Enjoy
but when i unzip the files i cant see any way of gettong romnuke to work i tried odin but it doesnt pick it up is there some other download i need??
still no joy
cglegion said:
It seems like you have broken files. Make sure those firmwares are for the right model of your phone. Are you using I9100 or I9100G? Is your phone still under warranty? What do you mean by not network based? I think it's time you head on to NeatROM JB 4.1.2 Aroma and flash that to your phone. It's way better than the stock one from Samsung. If you don't know how, read the instructions from the OP.
Hope that helps.
Click to expand...
Click to collapse
ok so i put the zip files on an sd card and put it in the phone. but when i try and install them it says ignature verification failed also if i try and wipe the date and retore it says faild to mount/efs invalid argument. when i manage to get the t mobile rom to load the screen is black but i can get the swipe down screen to turn on blue tooth or wifi
the donkey said:
ok so i put the zip files on an sd card and put it in the phone. but when i try and install them it says ignature verification failed also if i try and wipe the date and retore it says faild to mount/efs invalid argument. when i manage to get the t mobile rom to load the screen is black but i can get the swipe down screen to turn on blue tooth or wifi
Click to expand...
Click to collapse
This error is most probably because you don't have the right Rom for the right model or not compatible hence the verification error. Are you doing this in recovery mode? Make sure you follow the installation instructions properly and download the right one for your phone model. Just try cyanogenmod for starter. Installation is easy to understand.
still no joy
cglegion said:
This error is most probably because you don't have the right Rom for the right model or not compatible hence the verification error. Are you doing this in recovery mode? Make sure you follow the installation instructions properly and download the right one for your phone model. Just try cyanogenmod for starter. Installation is easy to understand.
Click to expand...
Click to collapse
ok so i went to cyanogenmod downloaded the newest file for the s2 when i did unzip i get 2 folder meta-inf and system plus a boot.img file. i burned the boot file to a disc but when i check it the disk is empty even though i can see its burned. also when i go to sammobile to get firmare it says no files available...therte must be some way of getting this to work H E L PPPPPPPPPPP
Dude, you're not supposed to be burning anything to discs. The zip file is what the recovery uses to install from. It should include the custom kernal too.
Copy the zipped ROM file to your SD card, put it in your phone and boot into recovery. Assuming you've already flashed the latest custom recovery CWM or TWRP (I prefer TWRP)
From here, to be safe, do a full wipe (That's everything except sd-card: system, data, cache, dalvik-cache)
Now you install/flash the zip file via recovery. Hopefully that completes without error. After that clear cache and dalvik-cache again just to be sure (I do this out of habit)
Reboot.
Hope this helps. I saw you mention something about "efs" and that gives me a bad feeling, read something about needing to back that up before bad things happen. But anyway, good luck :good: