Related
[GUIDE] Fre3vo / Fre3dom Official Thread (Discontinued)
#teamwin is proud to announce the Fre3vo tool for the HTC EVO 3D and Sensation!
What is Fre3vo: Fre3vo is a temp-root acquiring tool, allowing users access to a root shell on their HTC EVO 3D and Sensation devices.
What is Fre3dom: Fre3dom was the name of the tool being developed to enable S-OFF on the EVO 3D and Sensation. This has been abandon since AlphaRevX has announced on twitter that they've had the devices open for weeks now.
Fre3vo can be downloaded here: http://tinyw.in/1lJ
Prereqs:
1. You must be able to push files via adb to your device.
2. You must know what a shell is.
Instructions:
1. Download the fre3vo zip
2. Unzip the fre3vo binary
3. Push the binary via 'adb push fre3vo /data/local/tmp'
4. Change the permissions via 'adb shell chmod 777 /data/local/tmp/fre3vo'
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt. (Some may get more messages, but it seems the Sensation buffers the stderr more than the EVO 3D)
run 'adb shell' and you should have a '#' prompt instead of '%'.
This is temporary root. A reboot will clobber it. There are many threads with scripts for doing what the community has dubbed "perma-temp root", which lets you run all your root-based apps.
[Reserved for future details]
[More reserved for future use]
Want to thank you and your team for all the effort and contributions you've given to this community.
I have updated the FAQ with the contents of last nights "meeting".
I will update this post with results once testing beings.
Thanks Again!
adb?
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
http://pastebin.com/wiQc8Mid
steal25 said:
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
Click to expand...
Click to collapse
Here's a good thread regarding ADB. Sorry if you already know all that. I've gotten it to work, but every command results in the "adb server is out of date. killing......" message. In the end, the command goes through, but it has to restart the sever every single time.
FWIW, I didn't take any updates.
This thread is closed. When this rom is ready to go, then it can be re-opened, until then I don't see any actual development ongoing in here.
agrabren - PM me when your ready to post the rom.
Thread has been re-opened, sorry for the delay I am out of town
its all about getting su to stick
Rooting information added to the first thread. Please keep this thread on topic and without trolling, flaming. Any flaming or trolling may warrant a ban as we do not tolerate such things here at XDA.
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
yeah it does
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
Double confirm from me.
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
rooted here.. all updates applied.. confirmed..
Will we learn how the exploit was achieved, possibly post-perm-root?
installed it successfully but for some reason when i run su in terminal it does not give me root, and none of my root apps do not work am i doing something wrong or am i not understanding something?
Doward said:
Will we learn how the exploit was achieved, possibly post-perm-root?
Click to expand...
Click to collapse
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Thank you this worked for me on latest OTA.
DWhite456 said:
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Click to expand...
Click to collapse
#teamwin only tells HTC about intentional exploits. non intentional they dont:
20:28 <@joshua_> agrabren, By the way, traditionally, unrevoked's policy is to report to vendors holes that appear to be 'intentional' (see skyagent), but to package and protect vulnerabilities like that the best we can.
20:29 <@agrabren> This was a non-intentional hole.
20:29 <@joshua_> Yeah. Traditionally, unrevoked just packs and protects that sort of thing until someone finally reverses them.
20:30 <@joshua_> We'd love to be able to do the responsible disclosure thing, but this is an arms race...
20:30 <@zule> htc created the arms race, we just fight fair
How do I update my path environment variable?
NEver mind found it here. Have to copy contents of 'Platform tools" to 'tools' folder.
Hello Everybody!
Here is just a simple little script that roots your Flyer. You need an exploit address, so they are listed down below. You should also make sure you have the HTC Sync Drivers for the Flyer/View Download Also, there is now a Perma-Root method, which root access doesn't expire, so it is definitely better than mine. Since there is one now, I won't develop any more releases of the script, unless it is utilizing the new method, but they already have a script.
Exploit Addresses:
HTC EVO View 4G: Use the EVO View root.bat, it is automatic. Sorry Flyer users, there are too many exploits that work and don't work. If you want, you could try using the EVO View Root.bat with a Flyer. If it works, tell me!
HTC Flyer WiFi 16GB: exploit at adress 38126600:a00 or 38125600:1a00 (this works with mine.)
HTC Flyer 3G 32GB: exploit at address 38125e00:1200
Your root may expire, so please run Superuser.bat every time. Sorry for the trouble, I might make one that will run directly on your device that runs every ten minutes or whatever. Also remember this is only a temp root, so you will have to run the rooting script every time you reboot.
Also, a script that you don't have to enter an exploit address is in development.
Thanks,
pndo1
PS - A Mac version is in development.
Credits:
agrabren and teamwin for fre3vo
Elim for the exploit addresses
dalada for his root script (which I modified) and his superuser, su and busy box binaries.
And finally, all of XDA for being the best mobile device forum I have ever seen.
thank you very much but i think you forgot the attachment
Updates
Updates:
0.2 Added support for the Sprint EVO View
0.1 Released.
i can confirm that is it working on my htc flyer 3g thanks alot
Thanks for getting the scripts. Let us know when you get the one for the View.
pndo1,
thanks, really easy.
New we can hope for a root that sticks.
There is one that roots the EVO View!
pndo1 said:
Hello Everybody!
Hi pndo1,
Sorry, I not very familar with rooting, can you help explain further on this script? Can you help confirm my below understanding.
1) Connet Flyer to PC with sync connect
2) run the Flyer root bat file and enter the code
Question: Do i have to install the adb and adb shell sw in PC prior running this script?
Click to expand...
Click to collapse
Will you please help me understand what I do wrong. I run the script from the Windows folder. Successfully get to the point where I should enter the address. Do that. Then once I was successfull in getting to the "exploiting device" step and further. But that resulted in no actual root. Then I tried again after a reboot. But now it only gets to the address stage and no further. I connect in the charge only mode. USB debugging on. What did I do wrong?
@yongck7
No, connect the Flyer/View in Charge Only mode, with debugging enabled, and then run the root script for your device (Flyer or View).
@romanas2007
You can try and try again, as it appears you are not rooted. If it says exploiting, and there is no superuser, than run Superuser.bat
I ran the root script again from a freshly unzipped folder and it went ok. But when the script is trying to install the SU, I get the error messages all the time, like this:
Unable to chmod /data/local/tmp/busybox: no such file or directory
Unable to chmod /system/bin/su: no such file or directory
What can be wrong? Sorry, for noob questions.
Your Flyer/View is most likely one that has trouble mounting /system. Some guys were reporting it in the general section. You could try going into a command prompt, and type in cd, and a space, and drag the folder with the root files in it into the window, and press enter. Then type adb shell. If there is a # sign, you are ok. Try typing in "mount -o re,remount /dev/block/mmcblk0p5" without the quotes, and see what it says. But, if there is a $ sign, rerun the rooting script after a reboot, it can only be run once or twice, if you run it too many times, /system can't mount as write properly. Oh, and if the output from the mount command says "mount -o re,remount /dev/block/mmcblk0p5" then it mounted properly and you can run superuser.bat. If it says "mount: filesystem read only" or "mount: filesystem r/o" then reboot and run root.bat again.
Sorry for the long instructions, the script is kind of fussy as of now.
thank you. working very well.
pndo1 said:
@yongck7
No, connect the Flyer/View in Charge Only mode, with debugging enabled, and then run the root script for your device (Flyer or View).
@romanas2007
You can try and try again, as it appears you are not rooted. If it says exploiting, and there is no superuser, than run Superuser.bat
Click to expand...
Click to collapse
Dear
pndo1
I tried to execute the flyer root.bat I got a message "Device not found"
My device is flyer 32G 3G
connected in charge only and debugging enabled
any help
You may have to install the drivers for the flyer, aka HTC Sync, which is on the HTC website. Google is your friend. Also you do not have to sync or even open HTC Sync once installed. I will update the OP.
Doesn't work properly with my 32 gb flyer ...
Installs SU but when opening SU i get a FC
.. Also any apps that require SU fail
Kris
i00 said:
Doesn't work properly with my 32 gb flyer ...
Installs SU but when opening SU i get a FC
.. Also any apps that require SU fail
Kris
Click to expand...
Click to collapse
Works well here on 32GB Flyer.
When running the code, I let the Flyer connect in sync, rather than charge only. No problem whatsoever.
You should try running superuser.bat again. Thats what I had to do, sometimes it doesn't copy and have the right permissions. Also in development is a version with no user input, if it is a good day it should be released tomorrow.
Works with my 32 3G Flyer
update: Noob question - I tried to perform run superuser.bat but no idea how :-(
You should just be able to double click.
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Androidious said:
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Click to expand...
Click to collapse
I have. No reply. Prob busy.
Sorry bout the post location.
Sent from my HTC PH39100 using xda premium
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
gtkansan said:
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Click to expand...
Click to collapse
xHausx said:
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
Click to expand...
Click to collapse
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
joeykrim said:
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
Click to expand...
Click to collapse
All apreciated. They did use a similar method, http://forum.xda-developers.com/showthread.php?t=1345620
[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows] to get stick temp root. Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board. I would think with the huge board level similarities between the raider/vivid and all the sensations that someone would have some experience to lend an idea or three ... Any help would be REALLY Apreciated! Thanks everyone.
Sent from my HTC PH39100 using xda premium
gtkansan said:
Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board.
Click to expand...
Click to collapse
android exploits take a lot of work to find/test/develop/release. bootloader exploits are generally more time/labor intensive to find/test/develop/release as bootloader code is closed source compared with android code that is open sourced. in addition, bootloaders can be very specific to only a few devices, where as android is running on many devices.
bootloaders have to be reversed engineered which is a skill set not many people have.
after all that negative news, perhaps somebody with the skill set will take the time to examine this device. perhaps a previous method will work or hasn't been patched!
after reading the thread linked above, seems everybody is on the right track. hope the extra information helps. good luck!
https://sites.google.com/site/mophocorner/
Site to help with everything Motorola Photon 4G.
Hoping to help with newbies that want to flash, root, unlock, etc. before they get stuck and have to wait for replies to fix there phone, Hopefully this guide will just work and they wont HAVE to post for help. That is the point of this at least! Let me know if there is anything I can add or change and I will gladly give it some thought!
Thanks!
I have updated the page, just so everyone knows!! Check it out!!! Let me know if I am missing anything.
Sent from my Xoom using XDA
The photon torpedo method is needed to root the 2.3.5 version just released.
Sent from my MB855 using Tapatalk 2
THANKS!
Thank you for that. Added the Torpedo root method! =]
Thanks for putting all that info into one spot! Definitely helps out that much more as it is somewhat easier to refer to rather than bouncing from one post to another here in the forums! I would imagine it'll help out many people (including me!).
I'm still fairly new to some things and some times the added explanation of certain topics and/or issues is what's needed to get the job done!
Also, as far as the *photon-torpedo* root method goes... I used that method without an issue on Android 2.3.4. After updating to Android 2.3.5 the other day, I used that same method again without issue and it worked perfectly! Unfortunately (at least from what I've read), being that I updated to 2.3.5, I won't be able to unlock the bootloader as if right now. Not really something I'm too concerned about, being that I hadn't prior to the update anyway.
Sent from my MB855 using Tapatalk 2
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Grep,
To answer your question, yes. The new update unroots your device so you will have to re-root using the photon-torpedo method again.
I was rooted prior to the update with that method and after the update I was un-rooted! Trying to re-root using Terminal Emulator on device wouldn't work. Got "permissions denied" when running the tar command. But, using adb on the computer worked without a problem!
So basically, just redo the torpedo root method from step 1 and you'll successfully get root back guaranteed!!
Hope that helps!
Also, I had the SU binary in place as you did along with other root specific apps. Those apps are pretty much worthless until you gain root again.
It has been confirmed in the "soak" that 2.3.5 update will completely un-root your device...
Sent from my MB855 using Tapatalk 2
nice. should come in handy for others. even me cuz im kind of a noob.... waiting for way around locked bootloader after 2.3.5 ota
Sent from my Motorola Electrify using XDA
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Sent from my MB855 using Tapatalk 2
Root
You could always use root-keeper from the market if your lazy like me.
the link to the download torpedo is not working
spursrob said:
the link to the download torpedo is not working
Click to expand...
Click to collapse
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Lokifish Marz said:
The Imperium has your back. I will be upping a new guide and Root-Unlock-Relock pack soon but hosting is changing servers so for now torpedo is attached to this post.
Click to expand...
Click to collapse
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
cool old lady said:
Clearly, I am retarded....I have studied this post 15 times but I can't find any way to see an attachment. Where is it?
Click to expand...
Click to collapse
try it now, post 6. Are you on 2.3.4 or 2.3.5? If you're on 2.3.4 then just use the root/unlock/relock pack (the link is at the top of post 6.
OK - I see it now and I've downloaded it - thank you very much. I am on 2.3.5 from the soak test.
Are these still the correct/only instructions? If so I may still be in trouble...my "favorite method....into /data/tmp"? I don't know any method, much less have a favorite.
Instructions:
Use your favorite method to get photon-torpedo.tar into /data/tmp
Install Superuser from the Market
Install Android Terminal Emulator from the Market
Run Android Terminal Emulator
Run cd /data/tmp
Run /bin/tar xf /data/tmp/photon-torpedo.tar
Run /data/tmp/photon-torpedo.sh
Run /data/tmp/install-su.sh
I'm actually on my way to bed. I will write a more detailed walkthrough tomorrow and post it in the Photon Compendium. Eventually I plan to script the entire process but am working on unified webtop stuff right now.
Grep_The_Truth said:
I hate to be that guy but this is certainly relevant to the discussion at hand. I used the Photon Torpedo method originally when it first came out. Since then I have kept it stock and performed the OTA updates as they come. After each update I just run the last two commands:
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Always worked in the past. I just got updated to the new "2.3.5" and I can't seem to get root back. The photon-torpedo script has multiple errors "libpcprofile.so cannot be loaded as audit interface" and "permission denied". Consequently the install-su script doesn't succeed. Can't mount /system as RW and everything is permission denied.
Worst part is that the SU binary still exists in /system/bin/su but I can't use it. I get permission denied on everything I try.
Am I borked? Is there something I have forgotten?
Jleeblanch, are you using the new update from Motorola from the soak test?
Click to expand...
Click to collapse
Me to, had to used one click Root (20 times)
Navigate to the Android Market and install the “Superuser” application from ChainsDD
Download and extract 22MB Root-Unlock-Relock.zip from the Imperium website
Go to the "rsd drivers" folder located in the Root-Unlock-Relock folder and install the drivers for your system (32bit or 64bit windows)
Download photon-torpedo.tar
Place photon-torpedo.tar in the "AIO Root" folder located in the Root-Unlock-Relock folder
On your phone, in menu/settings/applications/development make sure usb debugging is checked
Connect your phone to your computer and select "charging" mode from the connections options in notifcations
From the "AIO Root" folder, double click the "Command Prompt" shortcut
Type the following commands:
adb push photon-torpedo.tar /data/tmp
adb shell
cd /data/tmp
/bin/tar xf /data/tmp/photon-torpedo.tar
/data/tmp/photon-torpedo.sh
/data/tmp/install-su.sh
Ignore the errors when running torpedo and let the process complete.
Once I get some free time I'll write a single script covering everything from rooting to SBFing back to stock. My goal is to get any given process down to ten keystrokes or less.
Hmph. Well....I think it worked. Root Checker says "congrats" - but wasn't it supposed to wipe all my stuff from the phone or something?
no root doesn't wipe data. (neither does unlock if done right)
Sent from my mopho
I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
premo15 said:
I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
Click to expand...
Click to collapse
the top right there is a search box.. type your question in there and im sure u will find your answer
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
I have searched...extensively But I haven't been able to find any detailed information regarding my questions. Lots of general information about flashing su packages, etc. but I'm interested in how it works from a developer's perspective. I've read conversations between developers regarding su binaries but because they already have a mutual understanding of what they're discussing, it tends to be a little over my head.
Did the basic info site I provided help you understand
/
Rxpert said:
Did the basic info site I provided help you understand
/
Click to expand...
Click to collapse
Yes, it's a good start, thank you. One thing that's still throwing me though is that I've read some posts from people using one of the automated methods that say it completed partially (i.e. the bootloader was unlocked) but didn't actually root. When they attempted to install SuperSU manually, it complains about not having root access. Is that because they only have the apk and not the binaries? Do the binaries not get installed at the same time? Is that what flashing the Evo4GLTERoot.zip does?
Sent from my EVO LTE
Rxpert said:
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
Click to expand...
Click to collapse
Ok, went back and re-read a bunch of stuff with the understanding I gained from that article and it's starting to make sense now. Just one last question: when you install a custom "rooted" ROM, I assume that means that it has the su binaries and apk baked in. If that's the case, then really all you would need to do to gain root access is unlock the bootloader, flash a custom recovery and flash the rooted ROM. Is that correct?
Thanks again...
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
michael.stollaire said:
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Alright, I get it now! Thanks guys!
Mike, I'm already at my thanks limit today so I'll hit you up tomorrow. Out of curiosity, my limit seems kinda low (8)...does that increase as you gain seniority?
Yes, I believe u get infinite thanks capability, as ur XDA stature increases, although not entirely sure, to be honest.
A written thx is more than enough for me, BTW, and happy to help. Feel free to PM me with other inquiries, if u feel this will hasten ur getting answers and/or mitigation of outstanding issues.
Rock on!
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Rxpert said:
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Click to expand...
Click to collapse
Ah, good to know, "thanks" for the info...
Sent from my EVO LTE