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.
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.
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
hankhandsome said:
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
Click to expand...
Click to collapse
unfortunately your touchscreen died and your only option is to bring it for warranty because of the bad flash, if you have warranty i suggest follow my simple guide here.
http://forum.xda-developers.com/showthread.php?t=2074756
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
hankhandsome said:
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
Click to expand...
Click to collapse
still follow the guide so the insurance will not detect that you have been rooted before
chris151722 said:
still follow the guide so the insurance will not detect that you have been rooted before
Click to expand...
Click to collapse
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
each rom i try in ODIN never boots - just goes into a bootloop.
i suppose if the insurers do inspect it, they may well not be able to get to see the flash counter if they can't boot it up - so it'll have a stock, unrooted rom on it anyway, so does anyone think i'll be ok ?
hankhandsome said:
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
Click to expand...
Click to collapse
after you flash stock firmware go to recovery try to factory reset
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
Ausboy 2011 said:
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
its a bad flash from odin and bad flash thru phone the reason why touch is dying.
chris151722 said:
its a bad flash
Click to expand...
Click to collapse
every rom though ?
just tried another one and it's bootlooping ..
hankhandsome said:
every rom though ?
just tried another one and it's bootlooping ..
Click to expand...
Click to collapse
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
chris151722 said:
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
Click to expand...
Click to collapse
at the moment i can't access anything - it just sits at the samsung logo now. CWM is now no longer accessible either - i pop the battery, wait a few minutes then put it back in. I hold down Up/Power/Middle button and the Samsung Logo flashes, but nothing happens.
I can still put it in to download mode and flash roms with odin, but nothing happens .. i think i'm going to have to accept it's dead
My last roll of the dice is to grab one of the earlier roms from this thread
http://forum.xda-developers.com/showthread.php?t=1835931
and see what that does in ODIN
FYI:
1. you don't have to wipe anything before restoring a backup, it doesn't make a difference.
2. insurance fraud is a felony
Glebun said:
FYI: 2. insurance fraud is a felony
Click to expand...
Click to collapse
Good job i don't live in the US then ..
I'm pretty sure it's illegal no matter where you live
Well I don't particularly want to get into an argument here, as i'd much prefer a phone that works so i'll just thank you for your input.
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
chris151722 said:
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
Click to expand...
Click to collapse
thanks. it doesn't actually bootloop now, it just sits on the glowing samsung logo and doesn't move.
i just want to get a stock rom back on it and i'm going to just let it go. i'm a bit concerned that on the download screen it says "Custom Binary Download: Yes (19 Counts)". I know I did reset the flash counter not too long ago before I flashed the Darky Rom, so if this is indeed the flash counter, then i've obviously not done something right, so it'll show multiple flashes ..
ok, we've had developments ..
i actually got it in to CWM (don't know how..) and did a factory reset. it then did boot up into the OS but - no touchscreen still.
however, i've just tried connecting it to KIES and it's detected it so i'm going to try the emergency recovery thing ..
he says, as he selects the option and KIES then goes back to "connecting" .. *GROAN* .. and then comes back to tell me it's not supported to upgrade firmware via KIES .. *BIGGER GROAN*
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
hankhandsome said:
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
Click to expand...
Click to collapse
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
JJEgan said:
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
Click to expand...
Click to collapse
i'm aware of that - that's why I've ordered the OTG dongle so I can use my desktop mouse to go in and install triangle away
I bought a USB jig from eBay, which came in the post this morning. I turned my phone off, removed and inserted the battery, and plugged the jig in.The thing is, it only boots into download mode and doesn't clear the flash counter, and therefore not deleting the yellow triangle.
What is the problem? Is is the firmware? I'm running build 4 SuperNexus 4.2.2 JB ROM. On some website I saw that Samsung removed the ability to clear the counter after some version, and that I have to flash some zip file with odin? Or something to do with the bootloader? What's up with this? I looked around, and only saw threads like these for <4.1, therefore I don't wanna flash it so I don't mess anything up.
Here it is: http://forum.xda-developers.com/showthread.php?t=1354888. It's not for 4.2.2 though.
And here are the bootloader things: http://forum.xda-developers.com/showthread.php?t=1402286 Are they safe to flash? If so, which one?
Another bootloader: http://forum.xda-developers.com/showthread.php?t=1578866
http://www.modmymobile.co.uk/phone-...-remove-yellow-boot-triangle-galaxy-s-ii.html Something to do with samsung removing the ability in the blue box.
Shall I flash the bootloader? And what is the difference apart from the ability to reset the counter between the new one and old one? Or shall I just use TriangleAway?
Can anyone help? Thanks in advance
Try TriangleAway
domdomrys said:
I bought a USB jig from eBay, which came in the post this morning. I turned my phone off, removed and inserted the battery, and plugged the jig in.The thing is, it only boots into download mode and doesn't clear the flash counter, and therefore not deleting the yellow triangle.
What is the problem? Is is the firmware? I'm running build 4 SuperNexus 4.2.2 JB ROM. On some website I saw that Samsung removed the ability to clear the counter after some version, and that I have to flash some zip file with odin? Or something to do with the bootloader? What's up with this? I looked around, and only saw threads like these for <4.1, therefore I don't wanna flash it so I don't mess anything up.
Here it is: http://forum.xda-developers.com/showthread.php?t=1354888. It's not for 4.2.2 though.
And here are the bootloader things: http://forum.xda-developers.com/showthread.php?t=1402286 Are they safe to flash? If so, which one?
Another bootloader: http://forum.xda-developers.com/showthread.php?t=1578866
http://www.modmymobile.co.uk/phone-...-remove-yellow-boot-triangle-galaxy-s-ii.html Something to do with samsung removing the ability in the blue box.
Shall I flash the bootloader? And what is the difference apart from the ability to reset the counter between the new one and old one? Or shall I just use TriangleAway?
Can anyone help? Thanks in advance
Click to expand...
Click to collapse
Never Mess with the 'Bootloader' for now ma8
just use the 'Traingle Away' app to get rid of both the 'Yellow Triangle' and the 'Binary count' for now
Ps- do make a bkp of ur exsisting setup before hand
Sun90 said:
Never Mess with the 'Bootloader' for now ma8
just use the 'Traingle Away' app to get rid of both the 'Yellow Triangle' and the 'Binary count' for now
Ps- do make a bkp of ur exsisting setup before hand
Click to expand...
Click to collapse
Thanks, but I'm kinda freaked out about the line:
"THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE.
( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you really mean it! )"
Have you witnessed something like this happen, as you are pretty experienced ? I'm guessing that still, it's probably safer than bootloaders...
It's safer than flashing a bootloader. Just don't go there. Unless you have a very specific reason to & absolutely no alternative (same as flashing a PIT).
You have an alternative.
MistahBungle said:
It's safer than flashing a bootloader. Just don't go there. Unless you have a very specific reason to & absolutely no alternative (same as flashing a PIT).
You have an alternative.
Click to expand...
Click to collapse
Yeah. I might try TriangleAway if I'm gonna be desperate. I can live with the triangle ;D Thanks to everyone who helped.
Triangle Away could (in the worst case scenario) cause a softbrick. I'm sure chainfire wouldn't have released an app that can cause hardbrick, and with his expertise in Android, i bet that's impossible too (unless, if he really wants too)
domdomrys said:
Yeah. I might try TriangleAway if I'm gonna be desperate. I can live with the triangle ;D Thanks to everyone who helped.
Click to expand...
Click to collapse
I've used triangle away 3 or 4 times without any problems at all. It's fast and I believe it's safe!
Cheers!!
I tried Triangle Away, and unfortunately it didn't work. I think this is mainly because of my system being slightly corrupted, as sometimes I don't have signal which requires me to go into the app SGII_repair and do the second option. Also when I press "run tracker" it says that something is wrong and requires a factory reset. I will probably return to stock and then do a clean install of SuperNexus again. Thanks to everyone who helped!
same problem
domdomrys said:
I tried Triangle Away, and unfortunately it didn't work. I think this is mainly because of my system being slightly corrupted, as sometimes I don't have signal which requires me to go into the app SGII_repair and do the second option. Also when I press "run tracker" it says that something is wrong and requires a factory reset. I will probably return to stock and then do a clean install of SuperNexus again. Thanks to everyone who helped!
Click to expand...
Click to collapse
Also using supernexus and Triangle away doesn't reset counter, I wrote chainfire an email and hope for good
If you have succeeded somehow to reset without removing the ROM , please leave instructions .
thanks
I'm having real issues trying to get a stock ROM on my Virgin Mobile S3 (GT-I9300) and I'm hoping you guys can help me. I've looked absolutely everywhere for a solution but so far nothing has worked.
OK so a little history about the problem:
Using phone as normal, and then randomly turns off. Turn it back on and I get the two Samsung splash screens loop booting constantly. I boot into recovery mode and do a factory reset - same problem. Clear the cache - same problem. Send phone back to Virgin and they tell me I've rooted and installed a custom ROM which I absolutely have not but they have a screenshot with the custom counter showing '1'.
I've no idea how this is possible, but I would have remembered if I'd installed a custom ROM. Anyway, they send it back because I'm not going to fork out £100 for them to flash it.
So...lots of research later, I download the latest Odin (3.09), find the most likely stock ROM that will work with my phone (Carrier is Virgin Mobile UK). I find this ROM on SamMobile: I9300XXUGMK6_I9300OXAGMK6_BTU. Cannot for the life of me find an actual Virgin rom so this apparently should be fine as it's a generic EU build.
Fine, so I apply it using the AP selection in Odin, connect phone, it goes through and applies fine "PASS" etc.. and phone reboots automatically.
Now, it just sits at the Samsung splash screen (the static white text) and doesn't go any further. I've left it upwards of 10 minutes but no dice. So look online and find threads that suggest booting to recovery and doing a factory reset will do the trick. So try that (Power+volume up+home) and same problem - static splash screen. Balls.
So now I don't know what to do. I either need to try an actual Virgin ROM which doesn't seem to exist(?!) or my phone is truely bricked and I'll finally have a good reason to destroy the thing.
Can anyone let me know what the next steps should be? I would be eternally grateful.
Thanks in advance.
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
shivadow said:
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
When you say 'wipe' do you mean factory reset via recovery mode? Because I'm not able to access that. All I can get to is Download Manager to use with Odin...
I thought you said you could access recovery and you had cleared cache. In that case you are buggered. If it goes through the flashing phase and reboots but you still cannot get into recovery then you have 3 options..
1. Flash another rom but no lower than 4.3. Carrier shouldn't matter.
2. Full on flash with pit file (dangerous and can perma brick).
3. Return the phone under warranty and state that the flash counter also clocks official flashes too, samsung should know this as they make the phone.. staff need training if they say otherwise.
Sent from my GT-I9300 using Tapatalk
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
It sounds like nand failure, so it's possible that you won't be able to fix it.
Sent from my GT-I9300 using Tapatalk
I thought you said you could access recovery and you had cleared cache.
Click to expand...
Click to collapse
Apologies for not being clearer, before sending it back to Virgin for the warranty repair I could access the recovery mode fine, when I got it back I couldn't - whether that was caused by the flashing of the firmware or something Virgin did I don't know unfortunately.
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
Click to expand...
Click to collapse
Thanks for the tip - I've flashed the stock recovery and I can now get into recovery mode! Looks slightly different but I can now access the factory reset/wipe cache options so that's some improvement.
I'm just downloading the stock international ROM as per this thread http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847 but it's going to take a few hours. Thanks so much for your advice so far i'll report back once the download completes.
No joy
I can however get into download mode and recovery mode now. Is there anything else I can try? Is it possible I can get a custom recovery image on there and flash it with something other than the stock rom?
I've got a feeling you're correct and it could be a hardware fault. Virgin say I can pay £100 to get it fixed, if they have to replace the entire phone that would prove it wasn't 'tampering' that caused it so I could potentially get my money back I guess, if I complained. I think that might be my only option now.
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
crispin85 said:
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
Click to expand...
Click to collapse
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
ag4751 said:
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
Click to expand...
Click to collapse
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
crispin85 said:
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
Click to expand...
Click to collapse
Make sure you are using the USB cable supplied with the phone and it is connected direct to your PC USB port, ideally the ones on the back but don't connect through any multi USB port connectors.
The USB cables and how you connect can make a difference