Related
so how many of you guys are thinking about unrooting to get the new 2.2 froyo update thats coming soon? i know i am thinking about it.
I am unless stated otherwise by someone who knows what they are taking about.
The OTA Rom will be rooted with a day or less and available to be flashed. Not worth losing your root imo.
smjfosho said:
so how many of you guys are thinking about unrooting to get the new 2.2 froyo update thats coming soon? i know i am thinking about it.
Click to expand...
Click to collapse
I hope that people read this before doing anything stupid like losing root. When an ota arrives it is downloaded first into /cache and then the option is givin to install. The best thing to do if you can't receive an ota is to unroot if you have to. Download the ota then adb pull it root and then apply parts of it or put it in an update zip with root whole process only takes mmaybe thirty minutes or so.
Of course I could be wrong ( i did spell maybe wrong). But that's how it goes down.
thatguythatdid said:
I hope that people read this before doing anything stupid like losing root. When an ota arrives it is downloaded first into /cache and then the option is givin to install.
Click to expand...
Click to collapse
Strike the following sentence. If you can't receive OTA, don't unroot, the best thing to do is work on it MANUALLY. And note that root, in and of itself, does NOT prevent OTAs. Community system images disable OTA updates in other ways, such as changing the release keys, or more directly disabling that functionality.
The best thing to do if you can't receive an ota is to unroot if you have to.
Click to expand...
Click to collapse
Download the ota then adb pull it root and then apply parts of it or put it in an update zip with root whole process only takes mmaybe thirty minutes or so.
Click to expand...
Click to collapse
The URL that the update comes from will either be visible in your log, or it will immediately be posted here. No doubt. Once the update hits, it'll be all over. So just download it with your regular computer and work on it. If it comes with an SPL packed in it, remove it and modify your update-script to not write it. If it has a recovery image, remove that too (probably located in /system/recovery.img). Whether the image does or does not provide root access doesn't matter much, just as long as you still have an ENGINEERING SPL installed. Engineering SPL is like a super-root, and from here you can install or boot custom recovery images, which you can use to add root into your installed system image. The most trivial way to do this (though not entirely safe) is to copy your "sh" binary to "su", chown it as root, and chmod 4755 it. I would suggest though, that if you are going to root in this manner, that you call it something besides "su" -- security through obscurity -- it isn't likely that some malevolent application would guess that a binary called "freeporn" will actually be the "su" command...
Of course I could be wrong ( i did spell maybe wrong). But that's how it goes down.
Click to expand...
Click to collapse
I wouldn't say wrong. You were pretty much there.
lbcoder said:
Strike the following sentence. If you can't receive OTA, don't unroot, the best thing to do is work on it MANUALLY. And note that root, in and of itself, does NOT prevent OTAs. Community system images disable OTA updates in other ways, such as changing the release keys, or more directly disabling that functionality.
The URL that the update comes from will either be visible in your log, or it will immediately be posted here. No doubt. Once the update hits, it'll be all over. So just download it with your regular computer and work on it. If it comes with an SPL packed in it, remove it and modify your update-script to not write it. If it has a recovery image, remove that too (probably located in /system/recovery.img). Whether the image does or does not provide root access doesn't matter much, just as long as you still have an ENGINEERING SPL installed. Engineering SPL is like a super-root, and from here you can install or boot custom recovery images, which you can use to add root into your installed system image. The most trivial way to do this (though not entirely safe) is to copy your "sh" binary to "su", chown it as root, and chmod 4755 it. I would suggest though, that if you are going to root in this manner, that you call it something besides "su" -- security through obscurity -- it isn't likely that some malevolent application would guess that a binary called "freeporn" will actually be the "su" command...
I wouldn't say wrong. You were pretty much there.
Click to expand...
Click to collapse
Thankyou. I'm actually a sprint hero user and I just hope some people read this before applying the update realize that they don't like it as much as they thought they would and then make a million different threads asking if an exploit has been found for root. It will happen regardless. We had up to 15. It was just ridiculous. Also want to note that not five minutes after the exploit was found that sprint sent out an ota to patch it.
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section
I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.
As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!
No prob!
Happy Modding!
Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate
I purchased a Bionic from Ebay and was never rooted. Was at .886 and did a manual update to .901 because of 4g issues. Phone has never been rooted although was attempted unsuccessfully.
Would like to get root the easiest way if it is available or should i just wait a while.
It probably wouldn't be a bad idea to at least attempt the manual root method found here: http://forum.xda-developers.com/showthread.php?t=1395911
If .901 has introduced new complications in rooting, they haven't quite been sorted out. It's your best shot at the moment.
Will give it a shot, hope the brick doesnt come thru the window.
Please keep us posted.
negative on the manual root, typing the commands seem to work until the proggie attempted to gain root. I did attempt to finish the commands but no rw permissions leads me to believe root was not gained. I guess just have to remain patient.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
http://www.droidforums.net/forum/dr...ade-path-retaining-root-901-installation.html
these two sites have all the information you need to get back to 896, root, for ever root, and then back to 901 with root
root root root for the home team.
http://forum.xda-developers.com/showthread.php?t=1420266
right there. root the 901
I thought i would post my piece to see if it helps anyone who made the same stupid mistakes i did.
I got my Ouya last night and was not paying attention and ended up messing up the su binary. I was using wireless adb which has some issues and since i lost root i could not change my build prop.
I found the motochopper exploit was able to root my ouya and give me a useable su. From there i was able to change my build prop back to usb debugging. form there i used these drivers http://forum.xda-developers.com/showthread.php?t=1161769 and was able to reboot into recovery and sideload the OTA.
This is a very roundabout way to restore the Ouya but it can be done, even when it seems all hope is lost.
Thanks and good luck.
My employer uses an enterprise email application (Good) that scans the device for root etc.
I restored my device to an old old backup that I made when I first got the device, but for some reason superuser.apk is still lingering around in my system folder.
I can confirm that the device is no longer rooted as superSU fails to find a binary, and my carrier OTA updates have been coming through fine.
However, that pesky superuser apk is sticking around, and I'm convinced that it is the reason my device is failing the compliance test with the software.
Any suggestions on how I can remove the superuser apk from the system directory? Preferably without blowing up my current android install?
I've dug high and low with no luck, and i'm hboot 1.57, so going S-Off and using an RUU to isn't an option.
SD360 said:
My employer uses an enterprise email application (Good) that scans the device for root etc.
I restored my device to an old old backup that I made when I first got the device, but for some reason superuser.apk is still lingering around in my system folder.
I can confirm that the device is no longer rooted as superSU fails to find a binary, and my carrier OTA updates have been coming through fine.
However, that pesky superuser apk is sticking around, and I'm convinced that it is the reason my device is failing the compliance test with the software.
Any suggestions on how I can remove the superuser apk from the system directory? Preferably without blowing up my current android install?
I've dug high and low with no luck, and i'm hboot 1.57, so going S-Off and using an RUU to isn't an option.
Click to expand...
Click to collapse
install superSU from the market .. then in superSU settings theirs cleanup / Full Unroot
clsA said:
install superSU from the market .. then in superSU settings theirs cleanup / Full Unroot
Click to expand...
Click to collapse
I actually still have SuperSU installed. The problem is that I no longer have a superuser binary, so supersu won't run. Just gives me the usual "There is no SU binary installed, and SuperSU cannot install it. This is a problem." error.
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
SD360 said:
I actually still have SuperSU installed. The problem is that I no longer have a superuser binary, so supersu won't run. Just gives me the usual "There is no SU binary installed, and SuperSU cannot install it. This is a problem." error.
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
Click to expand...
Click to collapse
yeah i know what you mean their
SD360 said:
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
Click to expand...
Click to collapse
(unless you are s-off), re-unlock -> yes, then just use a custom recovery.... custom recovery has root access to all your filesystem, there's no real need to "re-root" a full ROM.
you can accomplish pretty much anything in custom recovery
nkk71 said:
(unless you are s-off), re-unlock -> yes, then just use a custom recovery.... custom recovery has root access to all your filesystem, there's no real need to "re-root" a full ROM.
you can accomplish pretty much anything in custom recovery
Click to expand...
Click to collapse
Appreciated. I'll give it a shot. I just really want to avoid anything that's going to break my ability to get OTA updates again. It was a massive pain to get back to that point before.
I'll just be sure to dump my stock recovery before I do it.
SD360 said:
Appreciated. I'll give it a shot. I just really want to avoid anything that's going to break my ability to get OTA updates again. It was a massive pain to get back to that point before.
I'll just be sure to dump my stock recovery before I do it.
Click to expand...
Click to collapse
it's not as hard as you make it seem... their is a Guru Reset for nearly every version / brand phone and their really easy to use to get back to stock for OTA updates.
Returning to total stock, lock not relocked can be a bit more of a PITA but still doable as long as you s-off
clsA said:
it's not as hard as you make it seem... their is a Guru Reset for nearly every version / brand phone and their really easy to use to get back to stock for OTA updates.
Returning to total stock, lock not relocked can be a bit more of a PITA but still doable as long as you s-off
Click to expand...
Click to collapse
Not really worried about the locked/relocked flag. I don't think that's a check that good does. Pretty sure it just looks for certain files and conditions.
Unfrotunately there is no recent guru reset for my carrier (Rogers), and my device is trapped in S-On as my hboot is super new.
I was able to get twrp up and running, and manually removed all traces of root. Now just hoping I can get my stock recovery back. Hopefully will get me back into the game.