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!
Related
I used to work with WM 5 & 6 phones, had plenty of them and enjoyed them all until I discovered the HTC Magic. What a giant leap forward!! Especially when using Google Apps as we do. I am however a bit reluctant to root the magic as it doesn’t seem like a walk in the park. I really miss being able to backup SMS messages and all the other apps that only run on rooted devices.
So my question is if the HERO is a rooted device or not.
Does anybody have an answer to this question? I’m so tempted to preorder one
the answer to the question should be probably yes seing how people have the system dump files. so its just a matter of time
In the meantime, you can back up SMS and MMS with GBackup from Market - backs up to Gmail automatically - can also back up call log and pics...
Dayzz
Apologies for my ignorance but what does rooting the phone mean? I've just come from using a Windows mobile phone - which I have been using since the original SPV!
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Ofcourse it's not 'rooted' when you unpack it from the box.
Eventually I'll guess the Hero will be rooted, but when and how... we'll just have to wait.
dipje said:
Ofcourse it's not 'rooted' when you unpack it from the box.
Click to expand...
Click to collapse
Easy son... He asked, I provided.
barryallott said:
Easy son... He asked, I provided.
Click to expand...
Click to collapse
wasn't ment to be offensive in any way ...
barryallott said:
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Click to expand...
Click to collapse
But as in Unix /Linux you use an ordinary login for normal day to operations and su to to use root. You have to consciously change your privelidges which is safer!!
Simon
Lots of useful info on allsorts, including rooting and other hacks here
http://forum.xda-developers.com/showthread.php?t=542452
Daisy xx
In addition to enabling ADB, SuperNooter will also mount the NC /system partition and copy over Superuser.apk and the su binary. This means you do not need z4root! You should see Superuser in your Extras/App Drawer after booting from the SD card.
Tested with WinImage under Windows and dd under Ubuntu.
http://muffinworld.net/android/nookcolor/supernooter0.1.zip
Thanks for making things even easier!
-CC
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Novarider said:
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Click to expand...
Click to collapse
Yup...do exactly what you did with nooker only use this image. Same steps.
Ok but do we need to wipe anything if we already used nooter? I don't want to brick my NC. Who is going to be the first to try it out? I would but I don't know anything about programing so if I messed it up I would be screwed
You can use supernooter on top of an existing nooter to gain Superuser. I would not try it if you already have Superuser (why would anyone?).
Mistar Muffin...you are the man!!!!
Just picked up a NC today and have been prepping for the past couple days...and pleasantly surprised that the steps have diminished with this.
Thank you!!!
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
johnopsec said:
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
Click to expand...
Click to collapse
What tone? I didn't say a single bad thing about the guy. I just dont want to brick my NC since im not a programmer and probably dont have the skill to fix it if something went wrong
Mistar Muffin said:
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with. The other thread you started has people in it that are getting "bricked" devices. I didn't know you didn't write the particular program that was causing this. I was not implying you were doing anything wrong I just don't want a "bricked" device.
Novarider said:
What tone? I didn't say a single bad thing about the guy.
Click to expand...
Click to collapse
Novarider said:
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with.
Click to expand...
Click to collapse
Novarider, I think that it's just the frustration of people coming on the forum and making posts with big bold red letters that say "YOU BRICKED MY NC!!!" and the like... As many others (including myself) have already stated, it's very difficult to brick a NC. I've yet to do it and I've done some VERY off-the-wall stuff with mine. My personal frustration comes from those two things.
So, sorry if you felt wrongly persecuted by my post. It wasn't directed only at you but at others who have screamed, yelled and lamented about one thing or another "bricking" their NC.
Friends?
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
What are talking about "bricking" devices? Have yet to see anyone claim to have "bricked" a Nookcolor...
That being said, don't think it's possible to brick one with current set of tools..
-CC
Novarider said:
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Click to expand...
Click to collapse
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
norkoastal said:
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
Click to expand...
Click to collapse
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Novarider said:
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Click to expand...
Click to collapse
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
johnopsec said:
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
Click to expand...
Click to collapse
If you figure out an easy way to install the keyboard without having to rename files in system or anything like that please let me know. I hate the stock keyboard on the NC
Step-by-Step Needed
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
docfreed said:
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
Click to expand...
Click to collapse
It would be great if this activated it because I can't install apks from the sd card now
[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.
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
First off, before I get into it; nay sayers and trolls please keep the thread clear. Hopefully we can figure something and more minds together normally equal victory.
Last night an idea hit me, I use a hack with Windows that allows admin permissions and I don't have enough info about android apks to say that it wont work.
In Windows (yes I know they are way different) if you can figure a way to temp change one sys program to be command prompt, you can add users, change admin passwords, delete logs and the such. Basically you own the box at that point. Im not going to go into the details cause as far as I know M $ hasnt fixed it and I dont want them to.
So if we can find an apk with root writing permissions and can change it to be a term emulator we should be able to chmod root.
I have made some attempts, using the hidden menu apk. I figure it can change the prop file it should have root privileges; with no luck. Maybe I am not repackaging the apk correctly or something?
If someone that knows more about apks thinks it may be a possibility lets get to cooking!
The Command Prompt trick you're talking about is very well known. It's been around since Vista and has yet to be patched and unlikely to be due to the nature of how it works.
Thanks Pirate, I know what versions it works with. But I guess no one knows how we can possibly accomplish the same in android.
Zer0C0oL said:
Thanks Pirate, I know what versions it works with. But I guess no one knows how we can possibly accomplish the same in android.
Click to expand...
Click to collapse
If you did, wouldn't you end up in a bootloop due to dm-verity, or is this not modifying /system?
Lifehags said:
If you did, wouldn't you end up in a bootloop due to dm-verity, or is this not modifying /system?
Click to expand...
Click to collapse
The way I understand the DMVerity mechanism is it rebuilds its trust chain every time a legitimate system change is made. When you perform a PRL update, the app makes a change to the system. This does not equal bootloops and I believe we can accomplish the same via this hack, if apk permissions can be loaned.
In the M$ hack you can't leave the change in place as it messes up other processes. Basically you use it to add a user with admin permissions/ open a backdoor and then cover your tracks: which one step is reverting the swap so there are no system issues for the users to find.
Alas, I fear the people this post should be reaching are the ones working towards claiming the bounty and for that reason collaboration will be non-existent.
@Zer0C0oL, please note that unless you are a developer working on a recovery, ROM or a Kernel, you should not be posting the development section. Please refer to this announcement if you have any questions.
I've moved this thread to the How-To section where it belongs.
Cheers :good:
Zer0C0oL said:
First off, before I get into it; nay sayers and trolls please keep the thread clear. Hopefully we can figure something and more minds together normally equal victory.
Last night an idea hit me, I use a hack with Windows that allows admin permissions and I don't have enough info about android apks to say that it wont work.
In Windows (yes I know they are way different) if you can figure a way to temp change one sys program to be command prompt, you can add users, change admin passwords, delete logs and the such. Basically you own the box at that point. Im not going to go into the details cause as far as I know M $ hasnt fixed it and I dont want them to.
So if we can find an apk with root writing permissions and can change it to be a term emulator we should be able to chmod root.
I have made some attempts, using the hidden menu apk. I figure it can change the prop file it should have root privileges; with no luck. Maybe I am not repackaging the apk correctly or something?
If someone that knows more about apks thinks it may be a possibility lets get to cooking!
Click to expand...
Click to collapse
I'm pretty sure it may be possible however impossible to avoid tripping knox.