Hello
To be honest im beginning to wonder why I even bothered rooting my S3 seems to cause more hassle than its worth.
The only reason I rooted it was so that I can use the Vodooo Sim Unlocker App on my handset. I bought it on ebay and rooted the phone and used Vodoo to unlock the network lock all worked fine for a while until last week when I was on holiday I got an OTA update ...so I installed it since then when I start my mobile its asking for the Sim network pin code.
I am trying to get Three to provide this but they say the previous owner (off ebay)has to approve this or they cant do it.
I think that the root access on my mobile is fooked so I downloade dan app called Root Checker Pro results are below:
===========================================================
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.91 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root shell 91980 2008-08-01 13:00 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
===========================================
I have tried to re-root my device by using the same method that worked the first time i.e http://reviews.cnet.co.uk/mobile-phones/how-to-root-your-samsung-galaxy-s3-50008588/ but this does not work now any tips what I can do?
Get your info/rooting methods from xda only, everyone else in the world is stupid.
Flash cf-root and stop blaming root for user error, tbh your post was a case of tl;dr but from what I've experienced its user error 99.9% of the time.
Sent from my GT-I9300 using xda premium
Like I said It was working fine before the OTA update so that was my fault for downloading the upgrade...right ok thanks for your help...
slinkydonkey said:
Like I said It was working fine before the OTA update so that was my fault for downloading the upgrade...right ok thanks for your help...
Click to expand...
Click to collapse
Obviously the OTA broke root access, that's what happens.
Use Odin to flash cf-root 6.4 and Bob's your uncle.
Sent from my GT-I9300 using xda premium
nodstuff said:
Obviously the OTA broke root access, that's what happens.
Use Odin to flash cf-root 6.4 and Bob's your uncle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ok ill try it again tonight I was going to ask you to send me a link the the official XDA developers way of doing it but might be a bit tricky on a mobile so ill take a look around but im sure ive already tried this but ill try again tonight thanks
im assuming i cant just use? http://forum.xda-developers.com/showthread.php?t=1703488
If you couldn't be arsed learning what you are doing and why, and also learning so that you never get stuck in a situation like this again then work away with the toolkit.
Personally I think its the wrong way to do it.
Find the cf-root thread and do it that way if you want to learn how to do something.
Sent from my GT-I9300 using xda premium
nodstuff said:
If you couldn't be arsed learning what you are doing and why, and also learning so that you never get stuck in a situation like this again then work away with the toolkit.
Personally I think its the wrong way to do it.
Find the cf-root thread and do it that way if you want to learn how to do something.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
ok ill search it out but to be honest I have enough learning IT at work
slinkydonkey said:
ok ill search it out but to be honest I have enough learning IT at work
Click to expand...
Click to collapse
Well, if you want something easy to use and doesnt require learning then get an iphone Or dont mod your gs3.
If you only rooted to unlock wouldnt it have just made more sense (and less hassle if you don't know what you're doing) just to buy an unlock code for 10 bucks and be done than trying to dive in the deep end without knowing how to doggy paddle to accomplish the same thing?
plus with odin it couldnt be anymore simple especially for an IT guy.
get odin
get the cf root tar
boot the phone in download mode
point odin to the tar file and flash
it's pretty darn simple actually
graffixnyc said:
Well, if you want something easy to use and doesnt require learning then get an iphone Or dont mod your gs3.
If you only rooted to unlock wouldnt it have just made more sense (and less hassle if you don't know what you're doing) just to buy an unlock code for 10 bucks and be done than trying to dive in the deep end without knowing how to doggy paddle to accomplish the same thing?
plus with odin it couldnt be anymore simple especially for an IT guy.
get odin
get the cf root tar
boot the phone in download mode
point odin to the tar file and flash
it's pretty darn simple actually
Click to expand...
Click to collapse
Your right to a point I should of just bought an unlocked S3 off ebay thats my fault ..I had tried the odin method yesterday it didnt work then but today it has so im happy now ive run Vodooo and my mobile is working again. I use the S3 for my small business and partiuclar apps like Barclays app does not work on Rooted phones so maybe I should of get an iphone haha but im not that stupid .. :laugh:
Related
Okay I posted this also in the Themes forum for Nexus but I wanted to see if anyone could assist. Someone in the theme forum asked about the bootanimation.zip that shows us the cool animation during boot, while reading this it reminded me of the behold 2. See below
What are the permissions for bootanimation.zip if they were left open to non root then this may-b a way to get root with unlocking the bootloader. This would be the same approach that was used to root the behold 2 where the "try3" file was renamed to play_logo . play_logo then was used to root and after root was opened it would make play_logo_real play which was the boot animation. I may be wrong but couldnt this be a possibility. Thanks, any help is appreciated. Im wondering if Zinx could chime in...
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
seraph1024 said:
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
Click to expand...
Click to collapse
You can always write if I am not mistaken using the low-level write dd if/of command. We would use the bootanimation.zip to run the root command. An example is in the Samsung Behold 2 it was done as follows:
Example
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
This is how it was done. I am wondering if the same can be done on the nexus using bootanimation.zip as it executed at startup. We would basically modify the bootanimation.zip to the above and add a line for it to execute the boot image. By gaining root this way we would still be able to put on a custom recovery and roms without unlocking the bootloader in theroy. The try3 file was created by Zinx and used by Maxisma to bring root to the behold 2. I am pretty sure this may work on the Nexus 1. I hope this helps.
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Okay XDA is back up. Yes I can test. Oh man if this works there will be absolutely no need to unlock the boot loader... Thanks
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Hey Seraph1024 take a look at this. Its too big for XDA so I put it up on pastebin. http://pastebin.com/f62780d32 Its what is contained in the try3 file. Zinx used it in flashrec
No joy.
Code:
$ getprop | grep product.model
[ro.product.model]: [Nexus One]
$ pwd
/data/local
$ ls -al try3
-rwxrwxrwx 1 0 0 74512 Jan 25 13:26 try3
$ id
uid=2000(shell) gid=2000(shell)
$ ./try3 /system/bin/sh
[1] Killed ./try3 /system/bin/sh
$ id
uid=2000(shell) gid=2000(shell)
Exploit does not work.
I was that close to rooting today until i saw this now its made me double think again lol I've been waitin for a custom rom by cyanogen until i rooted, and since its pretty much almost here i was going to root. bah guess i'll wait until CM gets released!
flak0 said:
You can always write if I am not mistaken using the low-level write dd if/of command.
Click to expand...
Click to collapse
You can't on this phone. There are two ARM cores - one running the low-level stuff (bootloader, radio) and the other running Linux.
Without the engineering bootloader (or some exploit) we don't have access to the baseband ARM core, and therefore don't have access to its MMU, which is programmed to deny read/write access to protected areas of the flash - such as the bootloader and splash screens. Even with root, Linux can't access that stuff.
It's going to be really hard to find a kernel exploit for the N1 to get root. Most exploits involve mapping memory to the zero page and then triggering a null pointer de-reference bug in the kernel. But the N1's kernel won't allow such mappings.... I believe the minimum address for mmap on the N1 is around 64k. (It's in the kernel config.)
This is a tough nut to crack.
The behold root was done that way because there's no way to flash the partitons on it.
You still need root in the first place to write to that file. The droid guys have been looking a while for a new root exploit but didnt find one. The problem is that all known exploits have been closed in 2.1.
We need to wait for someone to find a new one that works. Then this would be a real posibility, and there' no need to hijack playlogo.
for what its worth, if you need a lab rat i do not have my phone rooted yet and i am willing to test some things if anyone needs...
i dont plan on rooting it until the ball really gets rolling with everything and until I am 100% satisified with the phones performance
kam187 said:
You still need root in the first place to write to that file.
Click to expand...
Click to collapse
That's what I though. And like it was posted earlier, I don't think there is a exploit since this phone is done differently. I am busy for the next couple of days but if anyone want to "try", I'll make up something but I really doubt any of the old stuff will work on this phone.
Thinking about rooting the tfp for the first time. What's the best way from .28?
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
I have had great success with that tool. I was on .21 rooted, but OTArootkeeper didnt keep root (derp) so I rooted with Debugfs, just do what it says on the tool and make sure you have the drivers and you're away.
It also adds the Superuser app
Worked for me But....
SteveG12543 said:
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Manar Aleryani said:
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Click to expand...
Click to collapse
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
yeah i can barely read it lol
lil-devil said:
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
Click to expand...
Click to collapse
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Manar Aleryani said:
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Click to expand...
Click to collapse
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
lil-devil said:
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
Click to expand...
Click to collapse
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Personally, I was able to get the debugfs batch file to work properly, but it took some doing.
My .28 TF Prime wouldn't reboot fast enough for the batch file to work right, so I ended up messing around with the batch file a bit to get it to work.
Even still, the second reboot was too slow and it failed to install superuser. However, I just downloaded SU from the Play Store and it worked fine.
I would recommend running the debugfs batch file again and see if that might fix the issue since your SU binary is already up to date.
Manar Aleryani said:
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Click to expand...
Click to collapse
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Hello, when i try to use this tool on my TFP .28, it just sticks at
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Just use straight commands, dont use a script/toolkit, if you dont know how to tweak or dont understand it
Sent from my i9250
Gipjoe said:
Hello, when i try to use this tool on my TFP .28, it just sticks at
Click to expand...
Click to collapse
Make sure you have ADB and the drivers installed.
---------- Post added at 09:12 AM ---------- Previous post was at 09:08 AM ----------
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
Titanum backup is actually one of the apps that work.
I'm having problems with other root apps.
And yes; they do ask for root access and I grant them.
I will try to use Super SU. But will I have to disable the original SuperUser app? And how?
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
I tried downloading Super SU. It changed nothing but ruining my original super user app. Now the app allows all root apps without prompt and I can't use the Super SU because it's Super slow
Today i tried to root my sgs2 applying liquidperfections method (odin & s2-root). I followed all the steps, but after flashing the secured kernel (step 11), it looks i don't have root access. SU is installed but does not react. Rootxplorer fails and Titanium backup also...
What happened? What do i do now?
Download this and flash via cwm problem will be solved
No custom count as well as no triangle
http://www.4shared.com/zip/IA_mpMSo/SU-Busybox-Installer-1.html
Cheers
Sent from my GT-I9100 using Tapatalk 2
rjsmer said:
flash via cwm problem will be solved
Click to expand...
Click to collapse
OP specifically mentioned he flashed an original kernel, therefore no CWM recovery.
@OP, I don't know why you're having that specific problem, but why not just do what most do and flash a CF-root kernel? One step instead of 11.
Re: No proper root?
Thanks for replying, but I'm pretty confused now...
I'm new to all this, and the only thing I want at the moment is rootaccess; then I'll check and learn, step by step about roms etc. - well, that was the idea.
Becaus SU and Root Exlorer were acting strange and Titanium Backup said I nedded root, I installed free app 'root checker' which says that "the device is not properly rooted" (not properly, that kind of says it is rooted, but not how it should... right??)
Another Senior member pm'd me today about it and says he will help me;
rjsmer tells me to install an apk
and oinkylicious, u, that's what I suppose, are telling me not to install that apk, becaus I have a original kernel again...
So, is there any1 that can tell me what to do exactly;
I don't have any preference for 1 specific method, but I'd like a method that is easy and not too risky...
Oinky was correct, assuming you have an I9100/T (check the sticker under the battery), CFRoot is simple & will install CWM by default which will enable you to to flash roms/kernels, backup & restore easily (among other things).
However, what you really should not do is rush it or take shortcuts. Rushing & taking shortcuts leads to borked phones & you having to pay to have said borked phone repaired/replaced.
Read the first page of the CFRoot thread thoroughly, and follow the instructions to the letter. Pay particular attention to the section a 3rd of the way down the page in bold red that says "Help ! Which file do I use". Read this bit thoroughly & understand it. If you do & then come back to this thread & ask "Hlap ! What kernel do I use ?", that means you haven't read/understood it properly & you're probably at risk of bricking your phone.
Edit - You want a method of rooting your phone that isn't risky ? There isn't one. Flashing stuff to your phone always entails (a normally very small) risk you'll brick your phone. That risk increases exponentially with how poorly you understand what it is you're doing to your phone (gets back to the no rushing/no shortcuts, following instructions & understanding what you're doing I mentioned above).
Narcotrix said:
Thanks for replying, but I'm pretty confused now...
I'm new to all this, and the only thing I want at the moment is rootaccess; then I'll check and learn, step by step about roms etc. - well, that was the idea.
Becaus SU and Root Exlorer were acting strange and Titanium Backup said I nedded root, I installed free app 'root checker' which says that "the device is not properly rooted" (not properly, that kind of says it is rooted, but not how it should... right??)
Another Senior member pm'd me today about it and says he will help me;
rjsmer tells me to install an apk
and oinkylicious, u, that's what I suppose, are telling me not to install that apk, becaus I have a original kernel again...
So, is there any1 that can tell me what to do exactly;
I don't have any preference for 1 specific method, but I'd like a method that is easy and not too risky...
Click to expand...
Click to collapse
What I would do is
1. Flash stock firmware
2. Flash insecure kernel (CF-Root)
3. Check for root
Root will be there and just a case of progressing to custom roms etc
No proper Root
OK, thanks for the info
I don't want to rush anything, and I did inform me well. But for what I understand, is that I did everything alright yesterday, except re-flashing the stock/secured kernel (an optional step...)
Basically, if I apply the CF-Root method, I'll have a unsecured kernel?
So, what do I do now ?
Completely reset my phone, and apply CF-root ?
I think reset, because I have SU on my ophone now...
- Do I reset the gs2 or leave it & apply CF-Root?
- What is strange is that no one can tell me why this happened or what the problem is exactly ?
CF-Root
MistahBungle said:
Oinky was correct, assuming you have an I9100/T (check the sticker under the battery), CFRoot is simple & will install CWM by default which will enable you to to flash roms/kernels, backup & restore easily (among other things).
However, what you really should not do is rush it or take shortcuts. Rushing & taking shortcuts leads to borked phones & you having to pay to have said borked phone repaired/replaced.
Read the first page of the CFRoot thread thoroughly, and follow the instructions to the letter. Pay particular attention to the section a 3rd of the way down the page in bold red that says "Help ! Which file do I use". Read this bit thoroughly & understand it. If you do & then come back to this thread & ask "Hlap ! What kernel do I use ?", that means you haven't read/understood it properly & you're probably at risk of bricking your phone.
Edit - You want a method of rooting your phone that isn't risky ? There isn't one. Flashing stuff to your phone always entails (a normally very small) risk you'll brick your phone. That risk increases exponentially with how poorly you understand what it is you're doing to your phone (gets back to the no rushing/no shortcuts, following instructions & understanding what you're doing I mentioned above).
Click to expand...
Click to collapse
Actually, my phone is a GT-I9100, no letter at the end...
And, I do know that flashing is risky, and I agree that it the less I know, the more it becomes risky, but, hey, I'm willing to understand and learn...
Anyway, my other contact send me this to flash ? What do you think ?
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5
That does not match my current firmware (XWLP4), does it ?
So, I did read page 1 of Chainfire's thread, and I think I have to go for the CF-Root-SGS2_XW_O2U_LP3-v5.4-CWM5 one...
So, once my phone is flashed with this one, what are the possibilities / opportunities, except installing apps that require root ?
Are there any guides or threads to introduce new people to this ?
I have no idea if the LPS kernel your 'contact' sent you will work or not. At worst your phone won't boot (you'll still be able to get into download mode & flash something else). As to what kernel you should use, all the info you need is in that section 'Help ! Which file do I use ?' which is why I drew attention to it. If you're apprehensive or unsure of what you're doing, don't until you are sure.
What are the possibilities/opportunities once you've rooted your phone ? Basically it gives you control over your phone. You can freeze or uninstall apps that carriers/Samsung have put on the phone for starters. And obviously if you use CFRoot to root your phone, you'll have CWM installed which makes flashing roms/kernels, backing up & restoring really easy (among other things).
As I said in another thread all of 5 minutes ago, I very much recommend you read the Stickies, just about everything you could ever want to know is in those threads. You just have to read & learn.
Edit - Re: your question 'What is strange is that no one can tell me why this happened or what the problem is exactly ?' in your earlier post, the reason for this (root failing) is we don't know. We're not there with you to know exactly what you did/didn't do, and besides, the method you used isn't from this site.
Well, thx a lot for tips and explicarions!
I'm still informing myself...
I'd go 4 cf-root, but still hesitating becoz my device looks "semi"-rooted, but is that possible? Some apps are 'seeing' root, but can't have access to it...
Oh and the method i did use initially comes from this forum, really. Thread by user LiquidPerfection...
Sent from my GT-I9100 using xda app-developers app
Edit:
These are the results of the root checker-tool. Can some1 please explain or tell me what to do mow? Thank u
Superuser Application Status:
Superuser application - version 3.1.3 -is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: No such file or directory
Analysis: File /sbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root shell 22228 2011-09-27 23:12 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your GT-I9100 device by Root Checker Pro version 1.2.7 from joeykrim in the Android Market - http://goo.gl/NcnHn
Hey guys, i know there are many ways to root different devices.
however when the hackers hack the new devices, how do they root them?
leonwu127 said:
Hey guys, i know there are many ways to root different devices.
however when the hackers hack the new devices, how do they root them?
Click to expand...
Click to collapse
Rooting in itself, is gaining administrator access to the device. Also known as su, sudo, root.
Phone manufacturers and carriers don't want you doing that, partially because of security, but really mainly cause they dont want you to be able to remove all the bloatware and skins they use to make a few bucks out of you.
So they put blocks on every way you could use to gain administrator access. The "general" way is that you look for exploits, anything they overlooked. its really a cat and mouse game, some care more than others; and are harder to crack than others.
Basically what they do is put you on a limited user account on the system, kinda like those guest accounts on a computer, or the limited accounts you give your kid. The most common ways are exploiting the built in system update with a fake verification certificate to *update* your system, with a change that upgrades you to admin. A lot of phones to additional verification on boot, and will on reboot kill this. On these occasions you have something called temp-root. when you have root you can override any part of the system. If you use your temp root to override the part of the system that kills invalid updates, you gain a "full-root".
Root only lets you change the core system files, not install a new ROM, for this you need to change the recovery, and to change the recovery, you need to unlock the bootloader, which carrier's and manufacturers like to block as well, but thats another story for another time.
thank xlexi,
i have read some files which mention that making ro.secure=0 in default.prop is the main purpose of rooting.
as u said, the fake "update" would change the ro.secure and delete the checking invalid update system.
is that right?
Now days many manufacturers actually promotes the use of custom images, using open bootloaders. This is of course a nice strategy to compete with other manufacturers locking their devices. Still there's a conflict between the music industry and the consumers. To use Digital Rights Management (DRM), the phone must be tamper proof, but we consumers want to be able to "own" the device we bought. To mention an example solving this, Sony Xperias are shipped with a locked bootloader, possible to unlock by the end users, but at the same time erasing all the DRM information. I believe this is a good compromise, and I guess many other manufacturers are using similar solutions.
If the bootloader is open, rooting the device is trivial and no need of "hacking". The generic way of modifying such a device, is just to reflash it with whatever you'd like, everything from an insecure image (i.e. ro.secure=0) to a complete custom ROM. This is using the open bootloader supported by the manufacturer. Using ro.secure=0 is not really recommended more then a means to become root so you can add su, busybox etc. Once this is done, it's best to reset ro.secure=1 again, I would say. No need to have the device too insecure.
In the case with the locked bootloader, the flashable image must be cryptographically signed to be accepted by the device, and such a signature can only be generated by the manufacturer. To hack such a device, some exploit must be used. This is seldom a problem, but makes the rooting procedure specific for that phone model, not being able to use the standard tools such as fastboot etc.
leonwu127 said:
thank xlexi,
i have read some files which mention that making ro.secure=0 in default.prop is the main purpose of rooting.
as u said, the fake "update" would change the ro.secure and delete the checking invalid update system.
is that right?
Click to expand...
Click to collapse
That is correct
Hi. May I ask for your opinion about this ???
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.0 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: ls: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x 1 0 0 64412 Jul 17 08:48 /system/xbin/su
Analysis: Setuid attribute present BUT root user ownership NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: ls: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: ls: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /bin /usr/bin /usr/sbin /system/_install/sbin /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Click to expand...
Click to collapse
This is what I get from my tablet. When using ADB and I type adb shell ... I'll get the # sign. But I'm not rooted - according to this.
Any recomendation/idea what's happening there ???
Thank you in advance.
zholy said:
Hi. May I ask for your opinion about this ???
This is what I get from my tablet. When using ADB and I type adb shell ... I'll get the # sign. But I'm not rooted - according to this.
Any recomendation/idea what's happening there ???
Thank you in advance.
Click to expand...
Click to collapse
The "ls" command producing the root user id numeric. I guess this is confusing the script above, not realising "0" is the same as "root". My guess is that rooted app's works just fine on your device, using the Super User app.
kuisma said:
The "ls" command producing the root user id numeric. I guess this is confusing the script above, not realising "0" is the same as "root". My guess is that rooted app's works just fine on your device, using the Super User app.
Click to expand...
Click to collapse
Well, notg exactly. I can install SuperUSer app from PLAY ... but then I can't instal BUsyBox because it doesn't have root access. Neither Titanium Backup doesn't work ...
Any advice, what to do / what to check whether it's correct ???
Thanks in advance
zholy said:
Well, notg exactly. I can install SuperUSer app from PLAY ... but then I can't instal BUsyBox because it doesn't have root access. Neither Titanium Backup doesn't work ...
Any advice, what to do / what to check whether it's correct ???
Thanks in advance
Click to expand...
Click to collapse
Have you tried if /system/xbin/su actually works? Tried it from the shell?
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?