I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.
Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.
Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.
Related
Hi, I have been reading up about how/why i should unlock/root my android smart phone. I found interesting tidbit saying...some phones need to be unlocked before rooting and the rest don't. What about my samsung galaxy s3 (at&t) phone? is unlock required before rooting?
I tried following instructions for mrRobinson's method at http://www.xda-developers.com/android/how-to-root-the-samsung-galaxy-s-iii-xda-developer-tv/ .
But I ended up with an unstable phone. I kept getting pop-up error messages on the phone about a "android.process.acore" being stopped. I did a reset with power+volup+home and got things back to normal (lost by apps etc but i expected that). I re-tried with the same end result. Any idea on what went wrong here?
I will wait on a response before i try the second method (Chainfire) in the link mentioned above.
thanks in advance.
achincho said:
Hi, I have been reading up about how/why i should unlock/root my android smart phone. I found interesting tidbit saying...some phones need to be unlocked before rooting and the rest don't. What about my samsung galaxy s3 (at&t) phone? is unlock required before rooting?
I tried following instructions for mrRobinson's method at http://www.xda-developers.com/android/how-to-root-the-samsung-galaxy-s-iii-xda-developer-tv/ .
But I ended up with an unstable phone. I kept getting pop-up error messages on the phone about a "android.process.acore" being stopped. I did a reset with power+volup+home and got things back to normal (lost by apps etc but i expected that). I re-tried with the same end result. Any idea on what went wrong here?
I will wait on a response before i try the second method (Chainfire) in the link mentioned above.
thanks in advance.
Click to expand...
Click to collapse
Did you go to the following link: http://forum.xda-developers.com/showthread.php?t=1739426 ?
I rooted my at&t SGS 3 with this method and had no issues. I downloaded ODIN and the latest JellyBean ROM and it went flawless on the first attempt. My phone was and is not unlocked (figured I would wait at least 2 or 3 months after purchasing to request). If you think unlocking your phone might help, call AT&T direct first and ask for the unlock code. If you are potentially looking at a trip or vacation overseas then say so. They have worked with me on multiple occasions in the past. My wife is a foreign national so I really did take trips. Worse case scenario is that AT&T will tell you no and you have to unlock via other means.
aybarrap1 said:
Did you go to the following link: http://forum.xda-developers.com/showthread.php?t=1739426 ?
I rooted my at&t SGS 3 with this method and had no issues. I downloaded ODIN and the latest JellyBean ROM and it went flawless on the first attempt. My phone was and is not unlocked (figured I would wait at least 2 or 3 months after purchasing to request). If you think unlocking your phone might help, call AT&T direct first and ask for the unlock code. If you are potentially looking at a trip or vacation overseas then say so. They have worked with me on multiple occasions in the past. My wife is a foreign national so I really did take trips. Worse case scenario is that AT&T will tell you no and you have to unlock via other means.
Click to expand...
Click to collapse
Thanks..rooting went well with the JellyBean version. Not sure what the problem with ICS was... my phone did come with ICS from factory.
Unlocking your phone is a separate process and should not interfere with rooting. It seems like something else funky was going on there. The only reason to unlock your phone is for use with other carriers. Many of us here just root without unlock like myself.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.
S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).
You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.
My brother gifted me an old phone which he was using in America. The LG G2. I think it had some sprint contract initially. When I got the phone I was unable to use my IDEA sim on it. So I visited a local mechanic. He said that it will have to be unlocked. I paid the charges and he gave me phone after a few days. It wasn't working well from that day. I thought maybe its hardware is not so good. And then, one day it stopped saving call logs and giving and error like unfortunately google process has been stopped every time I called someone. Then I visited some other mechanic who previously worked in Samsung Service Centre. He said the device is not unlocked properly. And he has to unlock the device again. For that he started to download some LS980ZVE file from the internet. I peeked into his computer. When I saw build version in my mobile it was previously running LS980ZVE. I didn't interrupted. And paid the charges in advance. Today he called me to visit him. He said that he has installed the new software file he downloaded but when I tried it wasn't accepting my SIM. I tried another SIM but the result was same. He scratching his head said that maybe the device has gone to locked state again. He said me to leave the mobile with him as he will give it to me unlocked tomorrow. But now I am keen that if I can do the unlocking at home. I had a friend who is an engineer. He always talked about unlocking, rooting, jail-breaking etc. He always said that it was a easy job. I couldn't get in contact with him. Then I started searching on google and finally saw XDA DEVELOPERS. I thought of finding a solution here. But couldn't understand a thing. I hope if you people can help me about it.
If you could give me a permanent solution to the problem. Also if I could get latest android version working on it.
Even if there is no permanent solution I am keen to know more about this unlocking thing. How it works and what it requires.
Thanks in advance.
The unlock guide is in the General section. Read and read. If you already have TWRP recovery, sounded likely. The simplest way is to completely wipe your phone and flash a stock ROM of your choice and go from there.
e20140 said:
The unlock guide is in the General section. Read and read. If you already have TWRP recovery, sounded likely. The simplest way is to completely wipe your phone and flash a stock ROM of your choice and go from there.
Click to expand...
Click to collapse
I don't have a TWRP recovery. Yesterday I tried to google about ROMs and everything else. I found that there are custom ROM s like Cyanogenmod that can be installed. I downloaded the CM 12. Copied it into Internal memory because it doesn't supports a sd card. Pressed the volume down and power button. Booted into recovery. But couldn't found the ZIP file there. I searched for TWRP at twrp.me but couldn't find the file for LG LS980. My phone is already rooted by Kingo Root. It would be very helpful if you could tell me step by step method to completely wipe my phone and install CM 12 ROM.
Thanks
Rooted it for a buddy using KingRoot, worked totally fine. Verified that it was working and went about our day. I didn't attempt to install recovery or anything like that because I know the bootloader is locked. For some reason, it is now saying that the software is unofficial, and to take it to a Verizon store for some damn reason. 100% sure this is an AT&T tablet, as it says SM-T707A right on the back panel, and it's on his AT&T plan.
I can't find the flashable software on either AT&T or Samsung's site...does anyone know where I can get it, or what I can do to fix this? I can get into download mode no problem. I've owned many Samsung devices in the past and it's never been as issue if you can get into download mode....but I can't find the damned firmware.
May have figured it out - http://forum.xda-developers.com/galaxy-tab-s/general/stock-kitkat-image-sm-t707a-revert-t3403934
Gonna odin back to Kit Kat and take the OTA if available back to lollipop.
Still dunno why the hell it says Verizon on the error screen though...
Reporting back in case someone finds this via search. This totally worked. It's back up and running.
Wasn't able to do the OTA, but was able to manually update to Lollipop via the zip files posted in the thread I linked above. Worked a treat.
Try this. You'll have to scroll down but it might help.
http://www.androidayos.com/galaxy-tab-s-stock-firmware/
sparkie6point0 said:
Try this. You'll have to scroll down but it might help.
http://www.androidayos.com/galaxy-tab-s-stock-firmware/
Click to expand...
Click to collapse
Thank you for the links, I was able to find the answer, but those links might help someone in the future with this same issue.
Have you looked at updato...
Just found this
No one is reading the thread apparently...
Thanks for the replies though!
I'm actually pretty frustrated right now. This is not my first time messing with an Android phone. I've had several in the past, have dabbled in installing various custom roms, etc., but the guides for this phone seem to universally suck. I have a developer edition Note 4 that I rooted and unlocked the bootloader when I first got it. I bought the developer edition because I knew the bootloader could be unlocked easily, which I thought was supposed to make installing ROMs easier and less hacky. Now, It's been stuck on KitKat 4.4.4 for over a year and a half, and I wanted to update it to 6.0, but it seems like a massive pain in the ass. What gives? I'll link to all the guides I've followed thus far.
First, I found this: http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This is all I wanted to do. This guide told me to upgrade and (re?) unlock the bootloader via this guide:
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
This guide, for whatever the reason, tells me that even if I have a DE, I should install this other ROM for some inexplicable reason, then re-unlock the bootloader. Okay then. That points me to ANOTHER GUIDE:
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
And this guide tells me I have to root to unlock the bootloader (a reasonable assumption) but doesn't tell me how. I don't know how I did it the first time dude, it's been over a year and a half! So, with some searching I found this freaking 40 step guide:
http://forum.xda-developers.com/not...ide-how-to-root-verizon-galaxy-t3454593/page2
Now, not only is this guide stupidly long, its 'helpful' link to all of the software needed is broken. So I searched for the crap myself. I tried KingRoot, which rooted at first, but had other issues. I switched to Kingo Root, which seems to have worked better. I was able to get the n4-fix file to /data/local/tmp, change the permissions to be able to execute it, and run it. It seemed like I was finally making some progress. Except, when the phone restarted, it got stuck in a boot loop at the Verizon logo screen.
I don't know where to go from here, but I am really at my wit's end on this one. I've been working on this for 2 days. And before anyone asks, yes, I backed up my aboot, and I also have backups using TWRP from when I first got the phone and from its most recent state before I changed anything. Though, I don't know how to restore aboot, so if that's a problem, I'm pretty screwed.
Help would be greatly appreciated, before I throw my phone against a wall and buy a new one. I like this phone. But it really started to get bogged down and stop working right, so I thought it was time for an Android upgrade.
---------------------
I got it working, after hours. There were a couple things at play here, chief among them is the fact you have to remove the SD card from the device after attempting to unlock the bootloader, because it causes a boot loop. I also had to do a factory reset after flashing even in some cases where it wasn't specifically stated. Pretty frustrating. Anyhow, hopefully I don't have to ever go through this again any time soon. I made it to 6.0.1.