so ive got the same issue as the op in this thread. problem is i think its actually on OH3. been like this for a few months apparently (never rooted, totally stock, second hand to me) and sammobile is DREADFUL for downloading firmwares. also im not sure if Kies is taking. been stuck at "Software update and initialisation for SPH-L900 is in progress..." for about 45 minutes, no progress bar on the phone to indicate its actually running and oddly enough no errors. Kies IS using a hell of alot of resources out of my pc though, so its doing...something...i think...
a similar issue regarding a hard brick on an old tracphone S3 got that phone running again by allowing the device to boot from an sd card through some terminal voodoo. cant remember who helped me out back then, been a few years, but thought id mention it as to show i am quite a capable user here...not a noob by any means.
any chance for some help?
Related
Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:
79TAKid said:
Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:
Click to expand...
Click to collapse
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit
dixit said:
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit
Click to expand...
Click to collapse
That is what I did to get it working again was flash the correct TAR file. the IMEI still shows up. It sounds like the issue is still happening so I may back it up with titanium and reset it.
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
nuclearteacup said:
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
I don't think its going to work without the stock cord. But I think unplugging it would just result in a failed root I don't think it would brick. Not positive though
Sent from my SPH-L710 using xda app-developers app
nuclearteacup said:
...
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
did you unplug the phone yet? how did it go?
Just FYI since it sounds like you are new to this, there are a few different s3 models depending on carrier. Make sure you flash something compatible with your phone.
From your screenshot, looks like everything flashed except the cache partition. Are there any other images in the .tar.md5 file you downloaded?
Ok, first of all, new to rooting and all that follows. However, I'm not new to forums and if this is in the wrong category, or if I overlooked a similar post, I am sorry. Feel free to redirect me to wherever you see fit. I know just too well how similar posts can be annoying, but I feel like I've exhausted Googlesearching and looked everywhere I can think of.
So, I have a Note II. N7100, Android 4.4.2 and I want to root it. Googlesearching has found me a lot of nice looking ROMs, and besides looks the added functions tempt me. Wont be long until I upgrade to a Note 4 or 5 anyway, figure I might as well. For what its worth, I live in Norway, and AT&T does not exist over here, nor does any other major american carrier. USB debugging was on the entire time.
I got the Odin V3.10, and appropriate clockworksmod files, and thought everything was peaches. Into download mode (after backing up ofc), Odin finds it, I upload everything and Odin says "PASS" in nice, green letters. When it reboots, it looks the same as before, but.. "Unfortunately, SuperUser has stopped", Titanium backup does not work since it apparently isnt rooted. Root Checker says the same. However, when checking for updates my phone displays "The operating system on your device has been modified in an unautorized way. Try downloading software updates using Samsung KIES on your PC, or visit a customer service center."
Read alot about devices having to be unlocked from carrier, however all google searches on "how to check for carrier lock on Note 2" yields numbersequences I have to input into the dialler and dial. None of the sequences give anything other than "Connection problem or invalid MMI code". I honestly dont remember if its carrier locked or not.
I came across an article here on XDA saying that with the later versions of android, KNOX has become an issue when trying to root, but someone had found a way around it. I downloaded MJ5BLPatch.tar.md5, uploaded to my phone via Odin, and here it fails, looses connection with the device and cant reconnect. Phone displays something alon the lines of "Invalid magic code" or the similar in red text.
I am the newb here, looking for help, and if I screwed up big somewhere I am cool with a little flaming. I just want to squeeze this for what use I can before upgrading, and probably rooting that too.
Any help as to how I can root it and load custom ROMs? I appreciate any and all help, sincerely.
Forget that MJ5 bootloader related stuff.
Reflash CWM using Odin and untick auto reboot, run through and reboot manually.
After reboot into recovery flash SuperSu.zip, start supersu after reboot system and disable knox by following the advices from app.
Thank you very much. i feel exceedingly stupid, I had been using the guide found on Note2root.com, when I applied step by step from this guide (http://forum.xda-developers.com/showthread.php?t=2143479) everything worked out. hope this may be of help to anyone having the same issues.
Again, thank you very much for your help.
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.
Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.