Related
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
Hey all,
I would just like to say I am new to this whole thing, and HAVE searched the forums, and found this link to be most helpful:
http://forum.xda-developers.com/showpost.php?p=12029729&postcount=12
I am merely trying to install the new swype beta, I am currently trying to uninstall my current version of swype, now I have done the majority of the steps the only thing I am having trouble doing is giving the phone read/write access
as when I try: mkdir /mnt/sdcard/swype_backup I get an error because it's a read-only file system.
I am using ADB; the first line of the post I linked to says to enable R/W access if you're using Root Explorer... but I am not, so how can I accomplish this through adb?
Am I missing something glaringly obvious?
Thanks for your time and patience
Edit: I believe adb is working to the extent it should... after I type in adb shell I do infact get a '#' before each line.
It's all fixed, re-did gladroot and now everything worked perfectly, not sure exactly why it wasn't before
thanks anyways!
Hi im trying to change my wifi mac address.
i tryed this one
http://forum.xda-developers.com/showthread.php?t=1385577 but it's not working and many other way and almost any app on the market .
so please if anyone change his mac on Mini pro Please help.
Got root and busybox?
Sent from my WT19i using xda premium
I did and it's not working not on Xperia Mini Pro.
REQUIREMENTS
1) ROOTED PHONE
2) BUSYBOX INSTALLED
3) Terminal App
OPEN UP TERMINAL AND WRITE
:su
:busybox iplink show eth0
(THIS WILL SHOW YOUR CURRENT MAC ADDRESS)
NOW TYPE IN
:busybox ifconfig eth0 hw ether 00:11:22:33:44:55
(INSTEAD OF 00:11:22:33:44:55, YOU CAN WRITE YOUR WANTED ADDRESS)
Click to expand...
Click to collapse
And what happens then?
Explain, what does it show, what error or what message comes up.
Code:
Ifconfig: SIOCSIFHWADDR: Operation not supported
Thank you for your relpay.
@ murders10: are you sure the root worked? what firmware are you running? are you using the right interface, is it eth0 that you wanna change?
Yes im sure root it's working fine Stock Rom .62.interface Wlan0 There is no eth0 on Xperia.
I did the same thing but it replied me:applet not found...
I need some help
I hope someone can help as.
Sent from my SK17i using xda premium
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
it won't work with me what ever i did remove reinstall
But after all i fix my god dam router mac address problem. so i don't need to change any mac . thank you for the help.
Need to change MAC Address to try if Heywire works on a custom rom
urra901109 said:
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
Click to expand...
Click to collapse
I'm trying this, but get a message error in terminal emulator, when i type :su, theres a message that says :su: not found, or :busybox ..., the same :busybox: not found error displays.
I'm runing Real ICS lite r2, on my Sk17a, with locked bootloader, stock kernel, rooted, with busybox 1.20 installed,
Im trying this because i use heywire a lot, and this rom is the best ive tried, and its awesome, lighting fast, but heywire says this phone has a previous heywire number, and as i investigated, it has something to do with the MAC address, give me some light here please
ipconfig: applet not found - MAC spoofing
Someguyfromhell said:
And what happens then?
Explain, what does it show, what error or what message comes up.
Click to expand...
Click to collapse
Hello, I've been trying to follow this guide at:
http://forum.xda-developers.com/showthread.php?t=1385577
My phone has CM 7.2,busybox installed too.
Entering
Code:
busybox ifconfig
in terminal (not in su) gives me the local loopback address, and when I turn on my wifi, it shows my wifi card details too. (It's named tiwlan0 though)
Anyhow, since ifconfig needs to be run as root, I get ifconfig: applet not found after I enter following commands:
Code:
$su
#busybox ifconfig (and anything starting with this)
So it looks like ifconfig runs fine without su but is not detected at all after I make the switch to su. And since the line of code that changes the MAC cannot be run without su(then I get - SIOCSIFHWADDR: operation not permitted), I am stuck!
I tried other methods such as and similar to the one on
http://forum.xda-developers.com/showthread.php?t=1343695
where, after editing some configuration file, one could change his MAC address. Is there any such known file/method for the LWW?
Thanks!
Simple Tutorial to spoof MAC address
So I finally figured this out and it actually works for the purpose u needed, I will write down step by step guide, and write me if you need some help
1. You need your XMP to be rooted, with SU intalled, busybox installed and with terminal emulator app
2. Open terminal emulator app, and type: su
3.Allow terminal app to have super user access
4.Now type: busybox ifconfig (with your WiFi on)
5.Locate the text on the left side "wlan0" and in that paragraph locate HWaddr, write down this address just in case.
6.Now turn your WiFi off
7.In terminal write down this: busybox ifconfig wlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
8. Turn on your WiFi, And your MAC address should be the one you created (you can check that by typing in terminal: busybox ifconfig)
And ther you go, you spoofed your WLAN MAC address, tested by me in a simple tutorial, hope it helps
---------- Post added at 01:58 AM ---------- Previous post was at 01:52 AM ----------
In your case step 7 should be like this:
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
Click to expand...
Click to collapse
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
blackstallion1234 said:
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Click to expand...
Click to collapse
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Problem with busybox probably...
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
pikpok said:
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
Click to expand...
Click to collapse
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Xtrifer said:
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Click to expand...
Click to collapse
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
nice
blackstallion1234 said:
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
Click to expand...
Click to collapse
Good, I was sure it was busybox, don't forget to hit the thanks button, happy modding lol
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?
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..