I have searched the forum for a few hours now trying to find something that related to my problem. I have found nothing...
I am resorting to making a new thread.
This is my first Android phone ever. I was with Apple for awhile and got fed up with they way there were operating things, and Android is better.
Now,
Last night I tried using Hasoon2000's All-in-One toolkit.
During the perm root process my phone fell off my desk and came uplugged from the OEM cable.
it rebooted back to factory settings, so it still works(which is good).
I'm stuck in what to do next.
I'm not sure if I have TWRP recovery flashed or not.
I also have a kernel that I want to flash over as well.
My bootloader is unlocked.
My general question is, how do I get my phone rooted with the kernel flashed over?
I would have posted this in Hasoon2000's toolkit thread but, I can't because I just registered.
Any help at all would be much appreciated.:laugh:
Nevermind, no answer is needed. I have successfully rooted my phone.
This thread can now be deleted.
Related
Sorry about the double post. i first posted this in the Q&A.....
So i am a iphone user moved to android. im trying to root my phone and just cannot seem to get it running.
I have download simple root .1
I click setp1, it does its thing, goes to the skating guys and i do what it says.
Next i do step 2, same thing. skating guys, i do what it says.
now when i click step 3 the phone reboots and on my phone i get a phone with a read ! and triangle over it. nothing happens after that......
reboot the phone nothing seems changed.... what am i doing wrong?
anyone have a more complete "walk through"?
Also, i am a little confused. some people are saying to put "roms" onto the phone. are the roms like the OS? how do i wipe the phone and put a new rom on?
i am looking to get 2.3 onto my phone and get free wifi hotspot tethering.
i am running windows 7 ult. 64.
also, any links where i can get apps that only rooted phones can get?
any help would be great. sorry for the noob questions
Root using Unrevoked. It is the easiest method by far. Once you have root and s-off, you can worry about flashing custom roms. I'm not sure what you mean by "simple root .1" so you may want to post a link to what you tried so we know where you stand.
Also, it'd be easier to help if you provide your phone info as far as which hardware version, what software is on it now, which hboot, etc. If this is all new to you, then read some more and get a better understanding of this before you mess up your phone.
Can you boot your phone normally or is it stuck somewhere?
Simple root it outdated, you can check out the following thread for info on how to root.
http://forum.xda-developers.com/showthread.php?t=865204
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.
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 friend had a rooted M8 which was completely stock up until yesterday afternoon. He received the OTA update and I told him not to install it until we looked around on here. Well long story short, we ended up flashing SkyDragon 2.0.1 over a completely stock and I'm assuming S-On device. It acted funny for a little bit but ultimately booted up into SkyDragon. Now he has absolutely no data, but that isn't our biggest concern. We have tried 3 PC's and a Macbook, none of our devices or ADB seem to detect the phone. I just want to help this guy restore this thing to 100% stock and be done with but I seem to be completed stumped. I have tried so many different Unrooting/Stock methods in the last 24 hours that my head is starting to hurt. Can anyone please help us out with this situation, I feel foolish that it reached this point because I've rooted numerous devices over the years and I've never had this problem. Thanks in advance.
T-Mobile HTC M8
Unlocked Bootloader
S-On
TamaleJohnson said:
My friend had a rooted M8 which was completely stock up until yesterday afternoon. He received the OTA update and I told him not to install it until we looked around on here. Well long story short, we ended up flashing SkyDragon 2.0.1 over a completely stock and I'm assuming S-On device. It acted funny for a little bit but ultimately booted up into SkyDragon. Now he has absolutely no data, but that isn't our biggest concern. We have tried 3 PC's and a Macbook, none of our devices or ADB seem to detect the phone. I just want to help this guy restore this thing to 100% stock and be done with but I seem to be completed stumped. I have tried so many different Unrooting/Stock methods in the last 24 hours that my head is starting to hurt. Can anyone please help us out with this situation, I feel foolish that it reached this point because I've rooted numerous devices over the years and I've never had this problem. Thanks in advance.
T-Mobile HTC M8
Unlocked Bootloader
S-On
Click to expand...
Click to collapse
If you have no data the APN settings are missing
to get adb to recognize the phone turn on developer options and usb debugging. and/or install htc sync and then uninstall it and leave just the drivers
If you want to return the phone to stock use the correct nandroid posted here >> COLLECTION of Stock backup's
http://forum.xda-developers.com/showthread.php?t=2701376
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.