Related
http://forum.xda-developers.com/showthread.php?t=850898
Anyone try this and have it working? Suggestions?
Yes. It works as advertised.
droidroidz said:
http://forum.xda-developers.com/showthread.php?t=850898
Anyone try this and have it working? Suggestions?
Click to expand...
Click to collapse
If you have problems with moving files, you can use Root Explorer to move them. Watch out for typos on the last step. Other than that, it definitely works. I have done it many times.
idk..
I did this, and everything worked up to the last step.
It read no errors, but nothing worked.
I figured out that it didn't actually create the directory, so I created it with rootexplorer, copied the file in, and then when i restarted my phone was bricked D:
I've since exchanged it, but I'm gonna hold off for official support before I try again.
vluhd said:
I did this, and everything worked up to the last step.
It read no errors, but nothing worked.
I figured out that it didn't actually create the directory, so I created it with rootexplorer, copied the file in, and then when i restarted my phone was bricked D:
I've since exchanged it, but I'm gonna hold off for official support before I try again.
Click to expand...
Click to collapse
You probably jumped the gun there. These phones are actually pretty hard to truly brick unless you flash something to the "phone" in Odin. What directory were you creating? All of the directories that you are trying to work with are already there. All you have to do is put two files on your sdcard, move one of them to /system/xbin and then flash flash the other. I've done this probably 50 times in the last month and with the exception of a typo the very first time, I haven't had a single problem.
Don't use SuperOneClick... I had problem after problem when I used it to root. "de-rooted" (not sure that's a word) it with SuperOneClick then used Z4root. Everything worked perfectly after that. Also I was making a mistake when trying this step I think - "adb push path/to/recovery.bin /sdcard/recovery.bin" I was stupidly starting adb shell first then trying to run adb push. Hope that helps some.
I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.
droidroidz said:
I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.
Click to expand...
Click to collapse
Everyone has their own favorite. Personally I use both SOC and Z4, depending on where I'm at. I've never had a problem with either. Good choice, though, reading everything that you can find.
droidroidz said:
I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.
Click to expand...
Click to collapse
i dont know what you are reading but with regards to the US Cellular Samsung Captivate there is O N E method and really only 1 method.
SuperOneClick 1.55 which can be downloaded right here at XDA.
its pretty friggin dummy proof really.
And just incase you were thinking rooting gets you everything (like 3 of my coworkers) rooting just unlocks the door, its up to you whether you want to walk thru and start installed and flashing mods but jsut to ROOT the phone allows you to do things not being rooted will not.
v_lestat said:
i dont know what you are reading but with regards to the US Cellular Samsung Captivate there is O N E method and really only 1 method.
SuperOneClick 1.55 which can be downloaded right here at XDA.
its pretty friggin dummy proof really.
And just incase you were thinking rooting gets you everything (like 3 of my coworkers) rooting just unlocks the door, its up to you whether you want to walk thru and start installed and flashing mods but jsut to ROOT the phone allows you to do things not being rooted will not.
Click to expand...
Click to collapse
Actually I SOC didn't work well for me. z4 worked perfectly on my Mesmerize. I had problems with SOC.
icantplay said:
Don't use SuperOneClick... I had problem after problem when I used it to root. "de-rooted" (not sure that's a word) it with SuperOneClick then used Z4root. Everything worked perfectly after that. Also I was making a mistake when trying this step I think - "adb push path/to/recovery.bin /sdcard/recovery.bin" I was stupidly starting adb shell first then trying to run adb push. Hope that helps some.
Click to expand...
Click to collapse
my friend no offense, but if you had problems with superoneclick then you got problems.....
the biggest problem is the creators instructions, he tells you to disable usb debugging then to enable it when it says waiting for device... to bad you cant because the usb cable is plugged in and you cant do anything like that when the cable is plugged in.
i leave debugging enabled because it needs to be on to run the root.
30 seconds later i am rooted,, easy as that.
It's totally cool that it worked for you.
I'm just saying that I followed the instructions of SOC (not that there are any instructions, you just click on the big ROOT button) and then tried to install Clockworkmod.
I could not get anything to work properly. I then used z4 and it worked.
I'm happy to hear that it worked for you though but "I have no problems" not sure why you have to go there.
You realize that there are lots of reasons why something may work on your phone and not mine right? Also if you want to get picky you called it the US Cellular "Captivate". If it's from U.S. Cellular then it's the "Mesmerize". Maybe that's why SOC worked for you and not me...
I also had problems with the SOC method of rooting my Mesmerize... It looked like it worked but the method for flashing CWM wouldn't work. Kept getting access denied errors. Z4root worked like a charm though. Don't know why, don't especially care either way.
Sent from my Samsung Mesmerize using XDA App.
Does z4root install superuser.apk and buysbox? Also with z4root which version of superuser.apk does it install, I noticed the creator has updated the apk recently here:
http://forum.xda-developers.com/showthread.php?t=682828
Will (auto) root & unroot. Work for the new ota 605.7 update for the HTC thunderbolt
My friend wants to root the easy way ....NEED HELP will auto root work or not ...
sent from my rooted tbolt using XDA app
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
miketoasty said:
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
TheStick13 said:
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
Click to expand...
Click to collapse
Completely agree. You don't even need to learn adb to use it it's all just copy and paste.
Sent from my ADR6400L using XDA App
i was trying to root my friends phone with captains script which holds your hand...
I came across a problem... when trying to flash the downgrade pcimgfile... kept saying "Main version older, update failed"
As per him, he has not flashed anything on his phone, everything is stock andhe got his phone about a month after i did (for it launch day). The script was able to push the files and all seems good, but i have not been able to pin point whats causing the error. (i didnt get to take a screen shot with the firmware and stuff) Ive rooted 2 phones without issues with the script and on this particular phone, it seems to be working fine until i try to flash the update.
will using adb manually help in this case? I am thinking no.... but if anyone encountered this, mind sharing what you did?
I have not had any issue with the script. Its similar to the JCase's method it just issues the commands for you. Capt includes a copy of the commands the scrips runs in his thread so I found it helpful to look at it while I ran the scrip so I knew what it was doing and when. Like any set of instructions its always good to read through it all once before you preform it so you know what to expect. If you just download everything, click start, and expect it all to run smoothly then you are likely to run into problems.
JCase's method is good to learn off of tho and might be easier for people to pin point where errors occur.
The error i am seeing is with the phone itself. I think something may have gotten updated?
the script its doing its job. I also reboot my pc and did a factory restore.
Well Capt's script says it only works with software version 605.6 or 605.9 which I assume from when it was written means 1.12.605.6 or 1.12.605.9. If the phone your using is using software version 1.13.605.7 then you should use JCase's method here
The software is 1.12.605.6
Could it be Jcase maybe also updated the downgrade img file?
That first step is causijg the problem when i try to downgrade (the first time you flash the img file)
*looked at the thread and also went to the original thread, file md info is the same for the ruu on both posts **
I also have all the original exploit files on my pc from when i rooted MY phone... since he had a software version that was on the original root threads, i didnt have to change anything
This may be an issue you would want to ask in the chat room that there is a link to in the Development section. If you look at the scripts contents as well as the manual instructions from JCase they are exactly the same up the the point you are getting stuck at. The MD5's even match. So I wouldnt expect doing one method over the other would solve your problem. Maybe someone on the chat could help you out tho.
yeah... im gonna have to go in there....
Its the same software as mines. I didnt modify any files on my pc.... it should have just worked. thanks for the feed back. Guess i will try when i get home later and have more time to mess with it.
So I had an issue in hboot, i am not sure if something was unconnected or what but i think i am in a bootloop.
It happened during the first round where you unplug you phone, I did and it started to check the sd image and had the expected no image error message.
after it checked them all the phone displayed a error message the the "main version is older" that "update failed" and to press power to reboot.
when i do that it takes me to another screen. I think its the fastboot screen and my only options are bootloader, reboot, reboot bootloader, power down. All of which lead me to the same problem and no way that i can figure out.
I found this while searching for a fix, would i be able to pull the sd card, flash the update, and start over again? (albe it with a different root program)
Thank you before hand for your help.
I searched the forums for this issue, but wasn't able to find it. Hopefully i'm posting this to the correct area.
I have an HTC Hero, and when I first got it, I downloaded and installed Beezy's "One Click Rooter" HeroRoot010. Followed his instructions and it worked just as described - no issues.
I started having problems with the phone recently that I was unable to correct on my own and after having done a factory reset which didn't solve the problem, I took the phone to the Sprint store as a last resort.
They decided that the phone needed to be re-imaged. I left it with them for an hour and when I got the phone back it seemed fine. I re-loaded the apps that I had backed up and then decided to again use "One Click Rooter" solution to re-root the phone.
I booted into Recovery and selected "flashzip from sdcard" and then "rootme".
It ran though several steps and gave me a message saying that it was complete.
However, when I re-booted the phone, I don't have superuser authority, the Superuser icon isn't listed among my apps, and I verified that I do not have root access.
So, from my perspective, I'm doing the exact thing I did the first time I rooted the phone, only now it doesn't work.
Not sure what the problem is, but more importantly, I'd like to know what the solution is. What do I need to to in order to get this phone rooted?
Any thoughts or suggestions on how I can correct this would be appreciated.
Thanks!!
RadioActive1
RadioActive1 said:
I searched the forums for this issue, but wasn't able to find it. Hopefully i'm posting this to the correct area.
I have an HTC Hero, and when I first got it, I downloaded and installed Beezy's "One Click Rooter" HeroRoot010. Followed his instructions and it worked just as described - no issues.
Any thoughts or suggestions on how I can correct this would be appreciated.
Thanks!!
Click to expand...
Click to collapse
consider to read this useful post I'm sure about
I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA
Ok my friends, my name is ska, im 70 yrs old and if i dont type in caps, i cant see what i am typing. I would like to correctly root my phone and unroot it later if need be, before i die and so i have come here for assistance. Although i have worked in multiple engineering fields, i no longer have the mental capability to comprehend or follow any rooting instructions unless they were written for a 6 yr old. Getting old is no fun so dont do it.
Can anyone slow it down a few gears and help me with this bucket list item?
Here is what i have:
Htc one m8(metal)
originally verizon now has straight talk sim
model number: Htc6525lvw
imei: 990 004 998 964 591
android version 5.0.1
htc sense version 6.0
software number 4.17.605.9
htc sdk api level 6.55
it took me 21 minutes to type out this information. Which i will never get back. I just want to have a outta sight phone to show off at bingo and use it as an ice breaker on dance nights.
I love this thread and really hope you can figure it out!
You'll need a few things to accomplish this. First you'll need to get s-off (which I explain below), then you get root access, and finally you install a custom recovery. Once that's done, you're good to go, and can install whatever custom ROM or flashy modifications you want without worry that you'll permanently ruin your phone. Here's a list of things you'll need to do it: KingRoot app, Sunshine app ($25! No way around this...), working Android Device Bridge (ADB) connection to a PC.
Note, rooting your phone (up to the custom recovery) will not erase any of your user data, however further changes (such as flashing a new ROM) likely will, so you'll want to back up everything.
s-on/off: This refers to the security setting of the phone. By default, the phone comes s-on, which protects access to reserved memory and prevents you from rooting your phone. You'll need to change this to s-off first. Once done though, it'll be s-off for good. There are ways to "return to stock" and set it back to s-on, or at least appear as such to a level 1 tech.
First thing you're going to want to do is get ADB working on your computer and ensure you can communicate with and control your phone from the ADB command line. This is arguably the hardest step for a lay person. Detailed instructions on how to get that working can be found here.
Once you can see your phone in ADB and have ensured that's working, you'll want to download the KingRoot app and Sunshine app to your phone using the sites I've linked. KingRoot will be used to get temporary root access to your phone. Once you get tempRoot, if you reboot your phone, you'll have to do it again. Temporary root access is required for Sunshine to do it's thing and set your phone to s-off. Once you have s-off you're essentially done, and the last bit of work is to install the custom recovery and then any custom ROMs or modifications you'll want.
So you have ADB working and downloaded the two apps above. Lets get started.
First, launch KingRoot on your phone, and let it do it's magic trying to get you temporary root access. It'll likely fail a few times, but just keep doing it again until it works.
Once KingRoot says you have root, run Sunshine. It'll evaluate your phone and check if it has root access. If all is well, it'll prompt you to go pay $25 for the app, and will reboot your phone.
Once the phone has rebooted, launch KingRoot again and check to see if you still have tempRoot. You'll likely need to re-run KingRoot a few times until it gets root again.
Now that you have tempRoot again, and have paid the $25, go ahead and run Sunshine again. This time, it'll know you're ready to go, so let it run and it'll set your phone to s-off and reboot when it's done.
At this point, you've broken the man's lock over your phone! Go you!
The last step is to install a custom recovery, I suggest TWRP, which will allow you to backup and restore your phone, and also install things like a custom ROM. Details of how to install TWRP can be found here. You'll be using the ADB to push the code to your phone which is why we set it up and tested it first.
Once TWRP is installed, I recommend making a backup of your phone so you don't lose any information. You can do this in TWRP.
As a final step, and a way to show off your technological prowess, you can install a custom ROM. a whole forum of options and detailed explanations on how to install them can be found here. Some retain the same look and feel you're used to, while others use different user interfaces to offer a modified experience. Review the options and feel free to ask questions!
Good luck!
Hope you get this done, I will help in anyway I can.
You shouldn't need kingroot anymore, just download the sunshine app (http://theroot.ninja) to your device, install it and follow the steps.
I was 68 when I did mine. Just read here and follow the instructions.
Alllllrightttttty then !!!! When can you come over and do it>????
drumz0rz said:
I love this thread and really hope you can figure it out!
You'll need a few things to accomplish this. First you'll need to get s-off (which I explain below), then you get root access, and finally you install a custom recovery. Once that's done, you're good to go, and can install whatever custom ROM or flashy modifications you want without worry that you'll permanently ruin your phone. Here's a list of things you'll need to do it: KingRoot app, Sunshine app ($25! No way around this...), working Android Device Bridge (ADB) connection to a PC.
Note, rooting your phone (up to the custom recovery) will not erase any of your user data, however further changes (such as flashing a new ROM) likely will, so you'll want to back up everything.
s-on/off: This refers to the security setting of the phone. By default, the phone comes s-on, which protects access to reserved memory and prevents you from rooting your phone. You'll need to change this to s-off first. Once done though, it'll be s-off for good. There are ways to "return to stock" and set it back to s-on, or at least appear as such to a level 1 tech.
First thing you're going to want to do is get ADB working on your computer and ensure you can communicate with and control your phone from the ADB command line. This is arguably the hardest step for a lay person. Detailed instructions on how to get that working can be found here.
Once you can see your phone in ADB and have ensured that's working, you'll want to download the KingRoot app and Sunshine app to your phone using the sites I've linked. KingRoot will be used to get temporary root access to your phone. Once you get tempRoot, if you reboot your phone, you'll have to do it again. Temporary root access is required for Sunshine to do it's thing and set your phone to s-off. Once you have s-off you're essentially done, and the last bit of work is to install the custom recovery and then any custom ROMs or modifications you'll want.
So you have ADB working and downloaded the two apps above. Lets get started.
First, launch KingRoot on your phone, and let it do it's magic trying to get you temporary root access. It'll likely fail a few times, but just keep doing it again until it works.
Once KingRoot says you have root, run Sunshine. It'll evaluate your phone and check if it has root access. If all is well, it'll prompt you to go pay $25 for the app, and will reboot your phone.
Once the phone has rebooted, launch KingRoot again and check to see if you still have tempRoot. You'll likely need to re-run KingRoot a few times until it gets root again.
Now that you have tempRoot again, and have paid the $25, go ahead and run Sunshine again. This time, it'll know you're ready to go, so let it run and it'll set your phone to s-off and reboot when it's done.
At this point, you've broken the man's lock over your phone! Go you!
The last step is to install a custom recovery, I suggest TWRP, which will allow you to backup and restore your phone, and also install things like a custom ROM. Details of how to install TWRP can be found here. You'll be using the ADB to push the code to your phone which is why we set it up and tested it first.
Once TWRP is installed, I recommend making a backup of your phone so you don't lose any information. You can do this in TWRP.
As a final step, and a way to show off your technological prowess, you can install a custom ROM. a whole forum of options and detailed explanations on how to install them can be found here. Some retain the same look and feel you're used to, while others use different user interfaces to offer a modified experience. Review the options and feel free to ask questions!
Good luck!
Click to expand...
Click to collapse
WOW THE LAST TIME I HAVE HAD MY MIND BLOWN LIKE THIS WAS BY A YOUNG LADY IN KOREA. I GUESS MY NEXT QUESTION IS WHAT IN SAM HILL ARE YOU TALKING ABOUT ? I'M GOING TO ATTEMPT TO FOLLOW YOUR INSTRUCTIONS BUT I THINK THERE IS A GOOD CHANCE I'M GONNA BREAK A HIP IF I TRY TWRPING.!!! AS SOON AS MY NIECE GETS HERE TO TAKE ME TO WALMART TO GET SOME PAPER FOR MY PRINTING UNIT. I WILL PRINT ALL THIS OUT AND START READING. I'M ONLY GOOD FOR ABOUT 5 PAGES OF EASY READING BEFORE I NOD OUT ONLY TO BE WOKEN UP BY THE IMPACT OF MY HEAD ON THE KEYBOARD. HAD TO WALK AROUND WITH GHBNM IMPRINTED ON MY HEAD FOR A WEEK LAST TIME. I'LL KEEP YOU ABREAST ON MY PROGRESS. THANK YOU FOR ALL THIS INFO AND YOUR QUICK RESPONSE ALTHOUGH I'M NOT TO SURE OF MY ABILITY TO COMPREHEND ANY OF IT.
THOUGHT IT WAS GOING TO BE LIKE MY TOASTER. PUT BREAD IN CLICK ONE BUTTON WAIT AND DING ALL DONE AND NOW HAVE YUMMY TOAST. to be continued........
To make this super simple here are the steps:
1) http://theroot.ninja/download.html (Do the first link and after you finish that do the second.)
2) At this point you could potentially go to the app store, download TWRP which is a recovery program that is almost like a computer bios would be on a computer. Once you have that you could install it after selecting your phone and the TWRP version you want, I would select 2.8.0.0 as I had issues when I tried to flash higher the first time.
3) if that doesn't work you will need to install TWRP via Fastboot the directions for which are here:
https://twrp.me/devices/htconem8gsm.html
You can just put your phone in Fastboot mode and in a terminal on your computer that your phone is attached to type:
"fastboot devices" to make sure your phone is being seen.
"fastboot flash recovery twrp.img" to flash TWRP.
"fastboot reboot" to reboot the phone.
4) Here's the hardest step if you can't install TWRP from the app, installing ADB and Fastboot but just go to Youtube and look up some videos on that. There are some more details involved but you can ask when you get this done as this is all you'll need to install the custom ROMs.
Throttled to a halt in two ways is taking its tole on my project
********could not post with quote due to some error about posting 10 times.......something....yada...yada !!*******
Well gents, my carrier has throttled my speed so slow that it feels like I'm on dial-up in Bedrock. Looking at all those Utube videos and printing out instructions ate up 5 Gb in 3 days. So to make downloading the programs I need "time out" before they can be fully downloaded. But I'm still at. So bear with me. Did I mention that I got throttled? Not only by my carrier, but my doctor had to one up my carrier by informing me that I had a heart attack while shopping for print paper with my niece. I think I had a few more when she was driving me to the ER. So I'm a bit slower this week, but I still at it. Thanks for everyones help thus far. I better get to this before it gets to me.