Related
After seeing lots of users struggle to root their phone with the existing guides (or worse, brick their phones), often times because of an inability to install/use ADB correctly (so they hobble together steps from multiple guides), I decided to write up a guide for rooting without the need for ADB. This guide uses the Visionary program to achieve temporary root and then gfree to achieve permanent root. Visionary is used only for the temporary root and nothing else (since many on these forums are wary of the app for permanent rooting). All of the gfree steps were scripted together to make things more convenient (and allow less room for user error in typing things in). This has been tested to work with multiple G2s and theoretically should work with the Desire Z as well (if you have the 1.72 OTA though, you will need to downgrade first in order to root as per the instructions in the wiki). All credit goes to the original developers of these programs and those others who aided in achieving root originally (I didn't add anything new content-wise, just bundled it up nicely).
WARNING: A few Desire Z users have reported being stuck on the HTC logo after following this guide. Without having a Desire Z myself, it is difficult to figure out why (since this simple automates known working methods). For the time being, I recommend Desire Z users obtain permanent root using one of the other guides out there.
Instructions
1. Install Terminal Emulator and a file manager (such as Astro File Manager) from the Market.
2. Extract the contents of the zip file to the SD card (this will create a directory called root_files on the card). When done, make sure you unmount your SD card from your computer if you had mounted it as a storage device to transfer the files.
3. Enable Unknown Sources (under Settings->Applications) and USB Debugging (under Settings->Applications->Development).
4. Using your file manager, navigate to the root_files directory on your SD card and select "com.modaco.visionaryplus.r14.apk" to install the Visionary app.
5. Start the Visionary app.
6. Click on "Temproot now." Leave all other settings unchecked.
7. Start the Terminal app.
8. Type the following commands (the $ and # symbols represent the command prompt and should not be typed):
Code:
$ su
# cp /sdcard/root_files/perm_root /data/local/perm_root
# chmod 777 /data/local/*
# /data/local/perm_root
You will see multiple messages scroll by as the programs run. Once you are returned to the prompt in terminal, you will have permanent root (S-OFF), as well as subsidy unlock and SuperCID. At this point, you can also choose to flash the engineering hboot as explained in the wiki. Flashing this hboot allows you to use the flashboot program to flash images from your computer to your phone (which can be very helpful when stuck in a bootloop for example). Note, this is often times the step that bricks people's phones when following other guides. To help mitigate the danger involved, I created a script that first checks the md5 of the hboot file to ensure it didn't get corrupted and then actually performs the flash (many times the bricking occurs because of a typo in this command). If you wish to flash the engineering hboot, type the following command in terminal if you have a G2:
Code:
# /data/local/tmp/flash_hboot
Or this command if you have a Desire Z
Code:
# /data/local/tmp/flash_hboot_z
If you get a verification failed message, you should re-download the files, re-extract them to your SD card, and run the flash_hboot script again.
If you don't want the engineering hboot, just reboot your phone. You can verify you have permanent root by holding volume down while powering on (you'll see S-OFF in the first line of the bootloader). You are now free to install a new recovery and start flashing custom ROMs. If you don't want to flash a new ROM, it's safe to uninstall the Visionary app at this point.
And if you are curious, you can open the perm_root and flash_hboot files in a text editor to see what they are actually doing...
thnak you bro man this was way better !!!
does this apply to someone who just bought the G2.currently on stock 2.2?
GHOST99K said:
does this apply to someone who just bought the G2.currently on stock 2.2?
Click to expand...
Click to collapse
YES!!!! Especially you! This is much easier than the previous ways!
NICE!
I wish I had seen this last night before I spent 4 hour trying to get ADB to see my wife's new phone. Oh well got it working the hard way
Copy flash_hboot
Do you need to copy the flash_hboot like the perm_root file?
Crey23 said:
YES!!!! Especially you! This is much easier than the previous ways!
NICE!
Click to expand...
Click to collapse
cool i guess 2 of my friends will be pleased to hear this cuz i'll be helping them to root their phones.
worked like a charm! sweet man, saved me a lot of time by making this thread and guide, definitely should be added to wiki or sticky thread.
I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.
misterykid89 said:
I just bought a T-mobile G2 as well, and I love the phone as is, but I just want to root it, so I can over-clock the cpu just a little bit (maybe about 1Ghz is fine). Can I use this method and keep the phone as is? Or does this method delete everything and I need to use custom rom? I'm coming from original MyTouch 3G (without 3.5 jack) rooted with CM, but I am still a newb.
Click to expand...
Click to collapse
Once you root the phone, everything will stay as is. Here's a link to overclock to at least 1 GHz on stock ROM: http://theunlockr.com/2010/10/20/t-mobile-g2-overclocked-to-1-42ghz-how-to-overclock-your-t-mobile-g2/
However, it's required you first set up ADB.
I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...
misterykid89 said:
I can't just download setCPU and over-clock? I thought as long as the phone is rooted, I can do that...
Click to expand...
Click to collapse
You can still download SetCPU, but just having the app itself won't let you overclock the phone. You can try flashing a different ROM and you'll be overclocked once you run that ROM.
Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?
KoolKidsKlub said:
Wait, but the recommended and safest way is still with Rage and GFree, right? VISIONary was found to do something with the phones file system that messes up some phones I thought, right? I thought that is why scotty2 made Rage, or am I wrong?
Click to expand...
Click to collapse
Rage/G-Free is still the safest but they both require ADB, which can be quite a hassle to install for many. True that Visionary has been found to mess one's phone up, but this method only implements the temp root procedure from Visionary (which doesn't require ADB) and the perm root procedures from Rage/G-Free for a more simple way to root one's G2.
so its more like the best of both methods then... i gave up cus i couldnt figure out the ADB but this way looks way easier so ima give this a try thanks for this
Worked perfectly first try. Thanks!
What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.
misterykid89 said:
What exactly is kernel? I've seen some people saying they are running over-clock on their G2 with a modded kernel on stock ROM.
Click to expand...
Click to collapse
Search google for "Kernel Operating System"
What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?
misterykid89 said:
What I meant was is it okay to just change the kernel and run stock ROM that came with my T-mobile G2? Would it not change anything except for the clock speed?
Click to expand...
Click to collapse
Different kernels can be compatible only with certain ROM's. Check on on the kernel before you flash to stock ROM
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
pbrady5 said:
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
Click to expand...
Click to collapse
You do have Superuser and it's su binary, so yes, you should be rooted. Try this app if you want to be sure: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en.
Besides the root checker that theonew pointed you too I have always found downloading and installing Titanium Backup from the market as a surefire way of determining if root was successful.
Upon first run it will ask for SU permissions and should present you with a dialog box asking if that is ok with you. I always answer yes and make sure that the "remember this selection" box is checked.
That will be the first sign that you are rooted. Then, The program should provide you with a summary where you will see a bunch of green check marks. Most notably Busy Box should have a green checkmark and it will probably state Installed from program or something to that effect.
Wahla, you have confirmed you are rooted.
BTW, I recommend this program for it's ability to backup your apps which makes flashing new rom's easier as the apps can then be restored after performing a data wipe which is usually a requirement of flashing new Roms. Just be sure you understand that sometimes restoring app's AND their associated DATA can mess with a new ROM. In that case you can simply install the APP only. which still saves you the time and bandwidth of re-downlaoding it from the market.
Good luck and welcome to the playground.
Okay, ive been doing my research, and I lasted aprox. 4-5 days and its sadly to know but this phone (HTC Evo Design 4G / Kingdom / Hero S) doesnt have that much of fame. But I was crazy trying and trying alot of methods trying to root my phone, but just couldnt. I was about to give up, until I found a Guide, and made it possible for me to root the phone, so I decided to share this guide to you guys, to who ever has a HTC Evo Design 4G / Kingdom / Hero S. Credits go to LOLINTERNET who wrote this guide. :good:
Ok, here we go. :laugh:
In order to root your Evo Design you'll need to unlock your bootloader, flash recovery, flash su binary, and install superuser and busybox. In this guide I will try to explain these steps as simply as I can. My goal is for it to be thorough enough that anyone that reads it can root their phone and enjoy the full benefits of this nifty little phone.
First and foremost, you will need to install the Java SE Development Kit. You won't use this directly in any way, but you need it in order to install the Android SDK.
Click Here To Download SDK
After installing the Java JDK, you will have to install the Android SDK which contains two tools that are essential to gaining root. They are adb (Android Debug Bridge) and fastboot. These tools are used to send files to your phone from a Windows command prompt. You will need these tools to unlock your bootloader and flash recovery.
Click Here to Download Android SDK
Instructions on installing the SDK
How to add packages to the SDK
Once you have the Java JDK and the Android SDK installed you will need to install the proper drivers for your phone. This one is pretty straightforward and necessary for your phone to be recognized while plugged into your computer. After you have the HTC drivers installed you can begin the fun parts, but first you will need a few things. :good:
HTC Drivers CREDITS TO: CNexus
You will need a recovery.img. 2fast4u88's unofficial ClockWorkMod Recovery version 5.0.2.7 and 5.0.2.8 are the only two recoveries I have used since I got my Evo Design. Many thanks to him for putting in so much work to get this device where it is today.
Download Recovery
Also, you'll need su binary version 3.0.3.2 efghi. This is the actual file that will root your device. It is a flashable .zip file that you save to your sdcard and flash in recovery. You'll be amazed at how easy this step is.
Download for su binary version 3.0.3.2 efghi
Download for su binary version 3.0.7 efghi
3.0.3.2 binary is for Gingerbread and 3.0.7 is for ICS
The superuser app is like the control center for apps that request root permissions after you're finally rooted. You will need to install this app and then Busybox, both of which can be found in the Google Play Store. After installing the Busybox app you will need to actually install busybox. The app itself is basically an installer for Linux applets that are required by root apps such as Titanium Backup and Root Explorer among many others.
Now that you have a basic overview of what it is you will be doing and the files need to do it, the only thing left is to actually perform these steps and root your device. So, lets do this!
1. Unlock your bootloader at htcdev.com. You will need to sign up and you will be warned that unlocking your bootloader will void your warranty. Once you've followed all instructions at the website an unlock token will be emailed to you. DO NOT DELETE THIS FILE. You can place it in the platform tools folder of the Android SDK and use fastboot in command prompt to relock and unlock your bootloader whenever you like. Also, anytime you unlock your bootloader all data will be wiped so be sure you sync all your contacts and backup other information first before performing this step.
2. After unlocking your bootloader you will need to flash a recovery.img. The manual way to flash recovery is to place the downloaded recovery.img for 2fast4u88's unofficial ClockWorkMod recovery port of version 5.0.2.7 in the platform-tools folder of the Android SDK. Power down your phone but be sure that Fast Boot in Power under the settings menu is unchecked or it will just reboot normally instead of into bootloader (also called hboot) like you want. After it's been powered down for a minute or two, press and hold Volume down then press and hold the power button. When the white HTC splash screen appears you can let go. Scroll down with the volume down button and select fastboot by pressing power. Plug your phone into your computer and open a command prompt, then run these commands without quotations.
"cd C:\android\platform-tools" (This is where adb and fastboot live. It may be different for you depending on where you installed the SDK. I always suggest installing it to the root of your C: drive.)
"fastboot flash recovery recovery.img"
Should only take a few seconds, then you have yourself a recovery partition and you can proceed to the next step after rebooting. Yay!
3. Next, we're going to flash the su binary in recovery. First, you'll need to place it on your sdcard. Doesn't matter where exactly just as long as you can find it. I would suggest the root of your sd just to make things easier on yourself. After you have the su binary zip saved to your sdcard power off your phone and boot into hboot. Now, I can't remember which, but either hboot or fastboot will have an option to boot into Recovery. Once you're booted into recovery, select "install zip from sdcard," then "choose zip from sdcard." Scroll down and find the su binary then select it. Pressing the Up Vol button will take you directly to the end if you don't want to scroll all the way through. After selecting the su binary zip select "yes" to flash. It's a small file, so it won't take long. When it's done select "reboot to system" and we'll move on to the next step because you just rooted your phone.
4. But, you're not done yet. You need to install the superuser app and the busybox app in that order. This is the easy part because both apps are free in the Play Store. Install Superuser, then Busybox. You shouldn't have to interact with the Superuser app, but if you want to set an automatic response to apps that request root you can open it and go to Preferences. Scroll down and you should see a few options. I have mine set to automatically grant su permission to apps that request it because I have no reason not to lol. I also unchecked the option to receive a notification every time an app is granted root permission because that junk just gets annoying. Next, after you install the Busybox app, you'll need to actually install Busybox. The app is merely an installer for the actual Busybox applets that govern root apps. The app should open automatically after you install it. You should see it in your notification bar. Open it up and follow the prompts. When you're done, reboot your phone.
5. Check If you have rooted your phone successfully, download Root Checker on Play Store.
6. Congratulations! You should now have a rooted Evo Design 4G. Enjoy. I hope this guide is both complete and comprehensive enough that everyone can enjoy the benefits of having a rooted device, but if I've missed something or if you have any questions whatsoever, please post them here and I will do my best to answer them in a timely manner. I hope you enjoy rooting your device, but please be careful. You now have administrator privileges, so use them wisely. I would highly suggest installing Quick Boot from the Play Store so that you can boot into recovery easily without having to go through hboot. I would also suggest using your newly installed app that requires root access to boot into recovery and make a backup. If anything should ever happen to your phone's system and data you will have a backup and can restore it to that state. Again, I hope you enjoy. I apologize for this being such a lengthy guide, but hopefully you understand the wonderful world of Android a little better for having read it. :good:
*EXTRA* 7. I recommend doing a backup via recovery of your phone, because this phone doesnt seem to have any roms or any stock roms etc, so i recommend making a backup, but dont worry, ill try to make a backup ROM so there could be one on the internet, because I searched and could find one! :s
Great post Julio. I saw this post somewhere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
maikalwolf said:
Great post Juan. I saw this post somewere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
Click to expand...
Click to collapse
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
re you follow up question
julio626 said:
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
Click to expand...
Click to collapse
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
maikalwolf said:
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
Click to expand...
Click to collapse
Thanks man!
Gracias Julio
It was quite tedious to be honest. But reading your guide and this one how-to-unlock-the-bootloader-of-any-htc-device en cultofandroid I finally was able to root my phone. Thank you so much!
Amazing
This is the best guide I have ever found. It was fluid and easy to understand for me. Just went from my JB IPhone 5 (cellular happened to break). now i have this phone lol (but its so slow and useless I decided to root and it was an unbelievable pain.. nothing worked). Then I found your guide which is fantastic, completely like no other. I am very impressed with it and just wanted to say THANK YOU!!!!!! :good:
So Close PLEASE can you help.
I followed this guide about a year ago & got to the image you see linked h**p://i.imgur.com/zfle9n7.jpg To be blunt I do not recall where I left off in the rooting process except to say I'm dead ended. Where did my efforts go wrong and what do I need to do in order to finally get this rooted? Also please tell me what bearing info in this thread: h**p://forums.androidcentral.com/htc-evo-design-4g/142434-s-off-s.html may have on my results. THANK YOU
[Tut]How To Systemless Root+Root+More!
This was fully tested on SM-G928A;Baseband:UCU2AOJ1 on 5.1.1
Just in case needed //SM-G928A\\ **Full Odin Restore G928AATT2AOJ1**
$<Download Mode & Odin Systemless Root Flash>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.Odin 3.10.7
4.Kernel_Root_Android_5.1.1_AT&T_SamFirm.NET
5.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
____________________
Okay now assuming that everything has been required, we can begin.
Turn off your phone and open Odin with admin rights on the computer & connect your phone to the computer using the usb cable that comes with the phone.
On the phone now hold all of these following buttons down, Volume Down+Home Key+Power Soon after once you see the blue screen release those buttons and press the Volume Up key to enter Downloading Mode.
Now in Odin on the computer, it should have recognized your device now press the "AP" button and open up for example, "G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.MD5" now just press start and sit back and relax and soon you will have Systemless Root!(Note your phone will reboot which is normal after the flash.
--------------------
#<Obtaining Root Access>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
4.Flashed The Systemless Root
5.Kingo Root
6.Root Checker Cost $FREE
7.SuperSU Cost $FREE
8.BusyBox Cost $FREE
9.Developer Options (USB Debug)
____________________
Okay now assuming that everything has been required, we can begin.
Go into Settings>System>About Device & Enable Developer Options.(Keep tapping the "Build Number" category until it says Developer options have been enabled.
Connect your device with your usb that which comes with the phone on the computer. Open "Kingo ROOT" on your computer with admin rights, and once the program asks you to turn USB Debug on, go on your phone into Settings>System>Developer options and make sure it is enabled as well as usb debugging. Wait for kingo root to find your device and once found, it will ask you to either "Reroot,Root, or Remove Root, click "Reroot" then wait for it to start.(After it starts you should see on your phone the kingo root usb app pop-up and show the same thing you see on your computer)
After it is done it should confirm you have been rooted and will ask to donate.
Now you may exit out of the program on the computer and the phone and once out of the app and back on your phone, you will want to look in your app drawer for the kingo root "Superuser" and uninstall this. Then head on over to the playstore if haven't all ready and install "SuperSU" & "Busybox" if want to. Once have the SuperSU app open it and install the su binary updates with the "Normal" option not the recovery one since we don't have that.... & once done just press OK DO NOT REBOOT or you will bootloop and will have to use Odin to reflash your system of your phone to get it back working out of the box "state"
UPDATE Have a pc around and can still boot with root:
Yamaha169 said:
You can restart the device while rooted... but you have to have ADB to do so...
When you reboot ... you will get stuck at the ATT logo... at this point... plug your phone in to your pc...
Open up ADB (COMMAND WINDOW)
type in
ADB devices
until your device # appears in adb... (this can take a minute for your pc to find your phone) so don't panic
This means the phone is found...
From this point... type
ADB ROOT
ADB SHELL
YOU will now be inside the shell of the device with root permissions
Now type
setenforce 0
(MAKE SURE LOWERCASE just like seen. "setenforce 0" if do Setenforce 0 it won't be found.....)
This will set selinux to permissive ... allowing the phone to boot...
Someone with enough experience could probably create a selinux permissive stock kernel ... but I've contacted several developers with no response ...
Click to expand...
Click to collapse
Now open up the root checker app & click verify to see if you truly do have root.(You must grant root access so allow once it pops up.) Enjoy your root but never ever reboot.
UPDATE: How to Root If Possibly not allowing you to root!!!
Step one you will need to of downloaded "Android Studio
Step two you will now need to install all of the updates(Well that's what I did) inside the studio program.
Step three now locate 'program tools" which for me was located here: C:\Users\NameofComputer\AppData\Local\Android\android-sdk\platform-tools
Step four make a cmd.exe file to go in the platform-tools simply just clicking on the "start button" on windows and searching "cmd" then dragging the cmd file to the folder.(Rename it to something like ADB Root or something different than just cmd)
Step FIVE download the su binary which can be located HERE and place it in the "platform-tools" folder.
Step SIX now almost there. Open the cmd file(ADB Root.exe) and once opened, plug the phone into the computer with the cable that came with your phone.
Step Seven:^.^ now with the phone plugged in and the program start, type this command to make sure your device is found:
Code:
adb devices
and if found you will see your attached devices and if more than one or can't see your device, you can do
Code:
adb kill-server
command and it will restart adb.
Step Eight: MAGIC time lol now that your phone is connected and you can see it is indeed listed, type these commands as followed:
Code:
adb root
adb remount
adb push su /system/bin/su
adb shell
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
You don't really have to do the other commands after pushing su it's just for pre-caution.
Step Nine: Now do the following at the top and try to use the Kingo root once more and click root or reroot.
If this doesn't work try to press unroot and restart phone then try this again.
Also like down below I talk about if you did reboot before you unrooted, you can still unroot but sometimes it's tricky and it needs you to do the adb remount before will work so just remember that...
--------------------
$#$<UnRooting & Keeping Systemless Root So You Can Reboot & Reroot>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.Root Checker Cost $FREE
____________________
This is very simple and easy to do, all you must do after every root and before every reboot is to go into "SuperSU" and go into the settings and scroll down until you see "Fully Unroot" and click that and once done verify with the root checker that you are indeed unrooted but still have adb shell and once done that you may freely reboot with no bootloop and then if want root once more just use "Kingo Root" on the computer to reroot once more.(I'm hoping someone will come out with an app that does the same thing and works so we don't need the computer anymore which would make it much easier..)
Edit/Update:
I found that if you maybe forgot to unroot before a reboot that you can still unroot without the need of going into odin and reflashing stock system just by connecting your phone to the computer via the usb that which comes with your phone and opening up Kingo Root and waiting for it to find your phone then click unroot and wait for it after you have unrooted and you will hear a sound which means it's fixed! So just force shutdown the device with pressing both: Volume Down+Home Button+Power then it will boot back up as normal!
-------------------- ____________________ -------------------- ____________________
~My Findings Through Long Research & Errors~:
<How to Fix Wifi Bug That Comes With Flashing Systemless Root>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.BuildProp Editor Cost $FREE
____________________
On your phone open up the "BuildProp Editor".
click on the search button and search for "ro.securestorage.support=true" now once found change the =true to =false and save. Now you must reboot for it to take place but remember to UNROOT before you reboot.
Now doing this your wifi will stay connected and you no longer have to enter your password millions of times so it will be nicer to keep systemless root.
--------------------
<How to Enable AT&T Hotspot System FULLYApp>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Root Explorer Cost $3.99
4.NEW Modded TetheringProvision .apk Cost $FREE(Also can be found in this thread in attachments.
5.ADB Root cmd knowledge or Download SQLite Editor Cost $2.99
6.BuildProp Editor Cost $FREE
____________________
Okay my fellow members that stayed on 5.1.1 with me, this tut did once work but then at&t blocked me and it stopped working but now rejoice becase there is a bypass once more!!!
NEW WAY:
I'm not sure which worked so I'm gonna just tell you everything that I did...
1.I first rooted obviously
2.I found a new TetheringProvision.apk which I have uploaded down in the attachment and at the top.
3.I used adb root for this but this can also be done with sqlite editior so I'll explain both ways, first way will be the easy way the adb root...>>>
Step 1: Ensure you have the correct OEM drivers installed for your handset on the computer
Step 2: Download and install the necessary ADB drivers (v1.4.2)
Step 3: Enable USB debugging on your Android handset:
Go to Settings > About Device, and tap the build number 7 times or until you see 'You're now a developer' message.
Return to Settings > Developer options and use the toggle button to turn on USB debugging. Then tap OK button to accept the warning and continue.
Step 4:Connect your device to PC with original USB cable.
Step 5: Launch a command window on your Windows PC.
Step 6: Access ADB shell and run the following command:
adb shell now just type " settings put global tether_dun_required 0 " and enter.
________----------Now the sqlite way
Step 1:Go into sqlite editor and allow root rights...
Step 2: Locate "Settings Storage" and click on "Settings.db then click on "global"
Step 3:Locate tether_dun_required 0 and if not there add by clicking on the +
then fill out name as " tether_dun_required " >>And value as " 0 " and then save file and unroot then reboot.
Now then after all of that I downloaded the build.prop which I know you don't have to but it makes it easier for me to do so and probably for you too...
Step 1:Get build.prop editor from the playstore and open it to grant root rights.
Step 2:Click on the pencil icon on the top right where the search icon is.
Step 3: Scroll all the way down to an open line.(If not one make one.)
and put this in the line....>>> " net.tethering.noprovisioning=true " and then click the save button at the top right and then save it and unroot then reboot.
Then replacing the Tetherprovision.apk . >>>
Step 1: Download the NEW modded TetherProvision.apk at top or at bottom.
Step 2: get a root explorer and go to System/App/TetheringProvision
Step 3: Rename the actual TetheringProvision.apk to TetheringProvision.apk.bak
Step 4: in the same location, go into "arm64" and rename the TetheringProvision.odex to TetheringProvision.odex.bak
Step 5: Now locate the modded TetheringProvision.apk you've just downloaded and place it in System/App/TetheringProvision/ now should be two TetheringProvision, the TetheringProvision.apk.bak and the modded one, TetheringProvision.apk.
Step 6: change the property promissions of the tetheringprovision.apk to give it root rights by changing the promissions to look just like the actual one which is " rw-r--r-- "
Step 7: save and unroot then reboot!
Now youre wifi tether and usb should work!!! enjoy!
--------------------
<How to disable OTA & Security Notification>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
____________________
Open up titanium back with pro license and freeze these following apps:
1.SecurityLogAgent(This is that annoying notification that which comes with the systemless flash root that keeps annoying you to reboot and undo what you done.)
AT&T Software Update(This will make it so AT&T won't push any updates to your device anymore so no need to worry about installing an update ota and losing your root or something else like bootlooping.
And again, all of this sticks after you unroot and reboot!
___________________________________________
<How to Get Youtube RED (Sort of) FREE!>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.OGYoutube Cost $Free
Basically all you do here is download the modded sort of youtube app(OGYoutube) and install it then done! You now can download videos/music on the app and have access to run audio in the background plus NO ADS!!! (if there are I haven't seen any yet...)
Best part of this too since can't be used fttb, no need for XPOSED apk!
_____________________________
<How To Install Viper4android>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Fast Reboot
4.Soft Reboot
5.Viper4Android V2.3.4.0
6.Audio_Effect.Config
7.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
8.IRS Impulse Response Sample files
9.Root Explorer Cost $3.99
~~~~~~~~~~~~~
To Read the tuts yourself than rather follow my tut, you may do so by following This Link & This Link
~~~~~~~~~~~~~~~~~~
Alright, I decided to do my own detail tut to make it much easier so follow me and you'll have viper4android in no time : )
So let's get begin, download if not already, the busybox,SuperSU,TitaniumBackup,Fast reboot,Soft Reboot, & Root explorer. Now having all that done open up Busybox and allow it root rights and you may wait for it to research for a smart intall, or just press install. Once you installed it in the default location System/xbin, click on the will be installed to location and choose System/bin and install it there too.(Not sure why but that's what the tut called for.)
Now let's download the folders for viper4android, go ahead and download Audio_Effect.Config.zip file,IRS Impulse Response Sample files, & the Viper4Android V2.3.4.0 folder.
Now open up the root explorer and unzip all that which is zipped up.(Which is all of the files;Audio_Effect.Config.zip file,IRS Impulse Response Sample files.zip, & the Viper4Android V2.3.4.0 folder.zip
)
Now once all are extracted, we will begin putting what is needed where.
Let's start off with the ViPER4Android_FX_A4.x (The actual name of the folder) you're gonna want to long press it and copy this folder. Once done, you're gonna want to paste this folder in System>Priv-app and make sure to change the permission of the .apk to 0644 rw-r--r-- & the FOLDER to 0755 rwxr-xr-x(The folder should have the same permissions as the other folders in that location.) which is inside the folder to give it root access which is 0644;rw-r--r-- and if not sure what root permission should look like, refer to this link Or Google what it looks like, then save/press ok.
Now go back to where you extracted your folders, and this time copy the "audio_effects.conf and go to System>etc and find and rename the actual audio_effects.conf to audio_effects.conf.bak and then paste the copied modded audio_effects.conf here & DONT FORGET change the permissions to give it root rights.
Now after all is done, open the app "Titanium Backup Pro" and look for and freeze these following applications: 1.Adapt Sound 4.0 & SoundAlive 3.0 now open the app "Soft Reboot (Root) and click yes you want to do a soft reboot. Then once back up(If want you can click the "Fast reboot app" to quickly refresh the system) and running you should see the viper app inside your app drawer. Open it and install the update/software when ask you to and once done it should ask for you to reboot just click on ok and then go out and back to the "Soft Reboot (Root) then do another soft reboot.
Now almost DONE!!! Once back up and running again, go to your root explorer again where you extracted the folders and grab the folder of "ViPER4Android and move it to your device storage ex; Storage/emulated/0 (It's where the download folder is and dcim folder is.. Then finally, go toSettings>Device>Sounds and notifications>Sound quality and effects and toggle on all of the listings[NOTE YOU MUST PUT EARPHONES IN FOR THESE TOGGLES TO SHOW]; UHQ Upscaler|SoundAlive+|Tube Amp Pro now you're done enjoy viper4android via editing the settings in the app.
Edit
You need to download SELinux Mode Changer and give root rights and just click on permissive mode and all done. Also might need to use compatible mode in the Viper4Android settings.
I found that this mod works with Pandora and Youtube app but not with google music or the default music app and not sure how to fix that....
__________________________________0
This is some more quick finds which you don't need a tut for just information I'd like to share so you all know.
I found out that you can use Titanium Backup Pro Cost $5.99 and freeze anything you want such as bloatware and that annoying notification that appears every time you reboot if have systemless root installed "SecurityLogAgent" and as long as you UNROOT before you reboot, it is safe and everything you froze stays frozen.
Now I haven't tried uninstalling any system apps so I wouldn't advise doing that unless you wanted to but I don't see the point except to free space up since you can just freeze anything and does the same thing except for freeing space....
I haven't been able to unlock the bootloader in my research and errors which probably never gonna happen anytime soon....
I also never found an app that could root the device yet without a computer....
And yeah that's it! I just was so happy to find out all of this and just had to share it with xda members which are on the same boat as me that has been wanting some "freedom" which now can have a piece of it. : )
If found these tuts to be helpful, feel free to hit thanks button and if want donate.
AngelRyu said:
Just gonna get right to it and be fast.
Odin Flash Kernel for systemless root.
obtain root
Download SuperSU
After rooted download some sort of buildprop editor and search for " ro.securestorage.support=true" Now change =true to =false. and save!
Now go into the superSU app and fully unroot then reboot and also keep adb shell root!
So you fix the wifi bug plus keep the adb shell so you can obtain root once more! Now we just need some app that can give root access with 1 click without needing a pc and this would work for me until we can actually reboot with root without it bootlooping anyways.... I still can't find a wifi tether app or a method that works for the at&t hotspot app though...
Click to expand...
Click to collapse
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
fuzmik said:
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
Click to expand...
Click to collapse
Yes you must unroot to remove the su binary so the system acts like nothing has happen. I use kingo root for windows and it works every time with root all you need to do is hit "root" or it may say "reroot" and works every time. I have been playing with this a lot trying to do things to get it to reboot with root but have failed so far.... I wish someone with more experience would approach this so we could have an app to use at least so we not have to use pc every time to reroot until we get the ability to keep root and reboot.
Kingo root can be found here : https://www.kingoapp.com/android-root.htm
and this works after flashing the kernel from odin. This was the only way I actually found to be able to get root was with this because manually pushing su just didn't work for me....
Thanks for being much clearer on the instructions and idoit proof. I was worried about the bootloop and I thought there was no exit strategy on this expensive phone until you mention reflash. With your extensive tinkering on this, did your knox security trip up?
If this is the only possible way, maybe the community could make some sort of app that if we have to shutdown or reboot the phone specifically for g928a, it will safely unroot it for us.
TASKER?!
Anyone know if this still works after taking the latest OTA a few days ago?
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
tonys.94 said:
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
Click to expand...
Click to collapse
I was wondering if maybe we could place SU somewhere else so we might could trick it to reboot with root but haven't done it yet and or maybe keep SU on the sdcard/storage and use the terminal on the phone to push su to xbin every reboot but just hoping maybe can get root working without making the stupid thing bootloop.... Like I said I been doing a lot of dumb stuff with my phone because I have been so disappointed in this phone with not having wifi tether at the most really but now that got that I'm much happier but I'm still on the research of keeping root and being able to reboot.
I won't be updating until something maybe for sure comes along with 6.0 I can wait because my galaxy s4 I had stayed on stock version forever because was able to do everything so was no need to update really.... Anyways yeah lol maybe someone greater or maybe my playing around will work. WE can only hope...
Oh yeah, to the other guy NO it did not trip knox doing any of the things I've done. which I wouldn't care if could unlock the bootloader lol...
Edit:
I've done all I can think of and didn't work to keep root on a reboot except it did keep root without bootloop with a soft reboot...
I found out to maybe later will add tut up top but for now I'd like to tell you or whoever, if you do bootloop due to not being able to access the su unroot in time, you can still connect your device with Kingo Root in that bootloop and can unroot to save you from having to reflash every time... Might have to reboot as soon as you hear the found from the unroot though.
Oh and on a factory reset everything sticks excepts what was frozen becomes unfrozen just fyi...
Yeah, that's all I can find so I'm done with it hope someone can help later on but I'm just happy with wifi tether so much : )
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
O0Gjulian said:
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
Click to expand...
Click to collapse
Hi, I didn't come up with anything but the fix for wifi bug and hotspot app.
I just made a very detail tut to help others, but thanks.
I would wait on the bounty to be paid to someone who can make it possible to keep root on and still be able to reboot.
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
antizombie said:
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Click to expand...
Click to collapse
It's true, that's how my phone is rolling with frozen apps and the modded hotspot without root, but still the systemless root remains in the system but doesn't do anything with out a computer or applying the kingo root to true root it.
I haven't tested the adaway yet so idk if will work or not.... and I been wanting xpose to work to disable youtube ads but haven't tried that either. . I might root tonight and try out adway tho.
But yeah to your question you are 100% safe and will not change anything or trip anything; phone can reboot all it wants with no bootloops with the modded tether is what I'm trying to say lol .. .
Edit:
Yeah adaway works after unroot and reboot. . . But I decided not to use it because a lot of people us adfly and it wouldn't let me access the link so yeah.....
On another note I froze a lot of stuff and done a lot of things not sure which part caused it but it doesn't bother me because I don't use samsung pay but in the end I had to freeze samsung framework for samsung pay because it kept saying force closed but which again Idc about that app so no biggy to me : )
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
antizombie said:
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
Click to expand...
Click to collapse
Honestly, I'm not sure but it had to be either the freezing at&t update or securityagent because it seemed to happen after that... Or could be the hotspot mod but I didn't get any crashes until i froze those 2 apps so idk...
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
navalynt said:
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
Click to expand...
Click to collapse
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
O0Gjulian said:
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
Click to expand...
Click to collapse
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Also @
joe3681 said:
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
Click to expand...
Click to collapse
I can confirm freezing anything won't harm the system on a reboot after unrooting but not sure about removing the apps would be safe. I have however remove the youtube app and reinstalled it in play store and it didn't harm anything.
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
O0Gjulian said:
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
I'm not sure because I've never heard of that program, but I did buy it just now for about $1.89 and the activation keeps failing so I can't test it to see the difference but with titanium you can do everything not just freeze stuff but back up apps and their data and much more.
Titanium backup has been around for ages which is why I recommend it.
Click to expand...
Click to collapse
I use package Disabler. Works like TiBu without root. Only reason to root would be to fully remove apps but would it boot okay after?