Hi guys,
I found a method to change System Status in Odin mode to 'Official/Samsung' that is very simple and only using the busybox application "devmem". Use this command in adb shell or terminal emulator. Just type it in, hit enter, and reboot. Bam.
Code:
devmem 0xF91CF8C 32 0xFF000000
This will change your status to Official and remove the padlock with 'Custom' on it. If you want 'Custom', replace FF with EE.
Immediately upon reboot, Odin mode and the device recognize the device as official.
The explanation is that this is from a small region of memory that stores what's known as DDI data. I don't know what that means yet, but some other information like the CC Mode flag and device name/product number are stored here. I'm still doing further research on what else resides here.
Enjoy.
Seem that "DDI" can be either:
A "MAC-e header parameter" as specified HERE.
Data Description Indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d
PDUs concatenated into the 3GPP associated MAC-es PDU. The mapping between the
DDI values and the logical channel ID, MAC-d flow and PDU size is provided by
higher layers. The length of the DDI field is 6 bits. When, due to the
quantization in the transport block sizes that can be supported, the size of the
data plus header is less than the TB size originally selected by the E-TFC
selection entity minus 6 bits, the DDI value [111111] shall be appended at the
end of the MAC-e header to indicate that there are no more MAC-es PDUs
concatenated into this MAC-e PDU. In any other case it will be understood that
another MAC-es PDU would not fit and it will therefore not be necessary to
reserve room in the transport block for this additional DDI field.
Click to expand...
Click to collapse
QVGA Display Driver IC (DDI) chip that incorporates QUALCOMM's Mobile Display Digital Interface (MDDI).
I'd vote its the second, as it also contain a good chunk of SRAM memory.
Couldn't get this to work. Anyone else have any luck?
coreydkoster said:
Couldn't get this to work. Anyone else have any luck?
Click to expand...
Click to collapse
What didn't work? Do you have busybox installed?
ryanbg said:
What didn't work? Do you have busybox installed?
Click to expand...
Click to collapse
I havent got it to work either. Though im guessing its only good til a reboot before it gets rewritten?
I thought I read in passing that syscope was the app that checked to see if the system was modified or not. I think it said if you get your phone to say official and freeze/uninstall syscope you won't have the padlock show up anymore.
Sent from my SM-N900V using XDA Premium HD app
Triangle away app gets rid of the padlock.
Sent from my SM-N900V using xda premium
Wanam Xposed module also can get rid of the custom status padlock also.
I get to here but not anywhere else. Am I on the right track.. If so what next?
Sent from my SM-N900V using XDA Free mobile app
---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------
Sent from my SM-N900V using XDA Free mobile app
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Deansmithok said:
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Click to expand...
Click to collapse
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
donc113 said:
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Deansmithok said:
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Click to expand...
Click to collapse
This is what I get running devmem
[email protected]:/ $ devmem
BusyBox v1.24.2-Stericson (2016-04-23 13:23
:09 EDT) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/ $
To actually use it, you need to su first to get the # root prompt like this:
1|[email protected]:/ $ su
[email protected]:/ #
Then try the command /dev/mem isn't writeable by ordinary users
Sent from my SM-N900V using Tapatalk
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Deansmithok said:
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Click to expand...
Click to collapse
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
donc113 said:
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Deansmithok said:
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Click to expand...
Click to collapse
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
donc113 said:
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I don't have the play store because I don't have android.
The apps need android, but my phone won't even boot. I have "custom rom blocked by cc mode"
Download is blocked by it too.
All I have left is TWRP in recovery mode.
Regards
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Deansmithok said:
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Click to expand...
Click to collapse
You just need devmem and the address. Not busybox devmem and the address.
The only thing I can suggest is that you use ODIN to flash back to whatever the latest stock ROM you were on and go through the rooting process all over again.
The bootloader won't allow you to boot with a non stock recovery unless you unlock the bootloader.
Sent from my SM-N900V using Tapatalk
Related
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
theMaDHakkeR said:
Hi everyone,
I'm really baffled by this error im getting now. Just re-did the root on my X10a and everything is working great. SU is advising me when things request root access and it sets to UID 0. FINE. But when i go into terminal and hit whoami i get unknown command. Last time i had this i did ttxdragon (i think is his name) method and it fixed it but now nothing gets it to work. When i hit su i get the # and am able to mount the os in adb and in terminal, also to delete system apps using #6 in the root guide but the whoami command comes up as unknown command. This is driving me nuts because everything seems ot be configured properly and i have proper root access from what i can see. Please someone help if you know what i might be doing wrong.
Also i just re-rooted using the new 5 Step method for X10a.
Your help is much appreciated.
Edit: Also wanted to mention i got the busybox app from the market also and it installed fine as uid0.
Regards.
Click to expand...
Click to collapse
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Haha! Thank you your a saint! I'm still learning everyday
Thanks again.
Sent from my X10a using XDA App
biktor_gj said:
Easy, instead of running simply:
# whoami
Run:
# busybox whoami
Done!
By the way, you can simply type
# id
too
Click to expand...
Click to collapse
Simple, amazing solution. Thanks !
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Rydah805 said:
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Click to expand...
Click to collapse
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
k2buckley said:
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
Click to expand...
Click to collapse
Thanks, I'll test that out. I have a pin set on superuser. Maybe that's the issue.
Just checked, and it does it right away, and does not prompt... Sigh...
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
Very strange. I'm not sure. Has it happened on all roms, or just the one you're currently on?
Sent from my PG86100 using Tapatalk
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Yep that does work on his rom the "type su" thing and thanks for your root check app Joey it's been super useful in trying to figure out stuff lately on the photon.... really appreciate all your contributions
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
joeykrim said:
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
Click to expand...
Click to collapse
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
xHausx said:
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Click to expand...
Click to collapse
Rydah805 said:
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
Click to expand...
Click to collapse
Ah! Your question in the first quote above could be intrepreted two different ways. I provided one answer for one intrepretation and Haus provided the other answer for a different intrepretation!
I'll try and bring both together. There are two primary ways to access the shell interface on an android device.
1) Via adb shell. When typing adb shell and it opens the connection to the device, by android standard, it drops you to a shell with non root access reflected with the $ prompt. As Haus articulated above, this can be modified in the /default.prop file inside the ramdisk of the boot.img file. There are two options, have adb shell drop to root access or have adb shell drop to non root access. Many custom kernels modify this option so the user drops to root access.
In my kernel I'm using a non-modified stock kernel so it drops to non root access. I prefer to have to type su, once in the shell, to elevate to root access. Mainly because most functions I perform in adb shell I don't want root access for.
2) Via terminal emulator/connectbot. When accessing the shell directly on the device thru one of the common android applications, these generally open up a standard "sh" or non root shell. Then by typing "su" the user can elevate to root access (if the device has the su binary, etc.).
There are two main options for how to handle the "su" command inside a shell on the android device.
1) Superuser.apk - this application provides its own su binary, which hooks into the android application. Whenever su is called, the Superuser application is therefore called and allows the user to accept/deny root access requests.
2) su binary - from aosp or busybox. this is a version of the su binary more common to android developers in aosp, or the busybox version is more common to a generic linux version. the aosp version of su will grant any user/application root access. the busybox version will grant any user/application root access but does rely on an /etc/passwd and /etc/group file for permissions.
To answer your previous question, why you haven't had to type su on other custom ROMs, as Haus explained, they probably modified adb shell access in the /defult.prop file to automatically elevate adb shell to root priviledges.
To answer your last question regarding Superuser.apk and aosp su. Once you install the Superuser.apk file and it properly installs its own version of the su binary, it has now overwrite the previous aosp su binary. Superuser will now control all root access requests. Once you grant an application, adb shell, titantium backup, root explorer, or whatever application root access with Superuser, it will not prompt again and will handle every future request with the default action (grant/deny) provided.
Hope the extra details help!
Thanks, wasn't trying to be a pest. Just curious. The info in this thread is a nice thing to know.
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
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..
I have an Amazon Kindle Fire 7 inch 5th generation tablet running the unofficial build of Cyanogenmod 12.1 for this device (main thread). I've got root, I'm running without GApps, and my setup is working great. The only thing I have yet to resolve is that I cannot spoof my MAC address. If I try to do so with something like:
Code:
su
busybox ifconfig wlan0 down
busybox ifconfig wlan0 hw ether 00:11:22:33:44:55
busybox ifconfig wlan0 up
it will fail on "busybox ifconfig wlan0 hw ether 00:11:22:33:44:55" with the message:
Code:
ifconfig: SIOCSIFHWADDR: Operation not supported on transport endpoint
I also tried two similar approaches:
Code:
su
busybox ifconfig wlan0 down && macchanger -r wlan0
fails with
Code:
[ERROR] Could not change MAC: interface up or insufficient permissions: Operation not supported on transport endpoint
while
Code:
su
ip link set wlan0 address 00:11:22:33:44:55
fails with:
Code:
RTNETLINK answers: Operation not supported on transport endpoint
From the googling I have done, it seems that this may be due to a limitation of the hardware, kernel or wifi drivers? Hopefully that doesn't mean there is nothing I can do and nothing more to try. Are there perhaps other methods that would bypass this problem?
For a bit of additional info, the application "Dalvik Explorer" shows under device details "Hardware: MT8127", which I hope is a useful piece of information to someone with more technical expertise than me. If it is a driver issue, are there perhaps newer drivers for that I could manually load somehow? If it is a kernel issue, is there anything I can do to modify the kernel (not something I have the slightest bit of experience with, but I'll be damned if I can't try). Any guidance or ideas would be extremely helpful.
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
cyanogen_aw_yeah said:
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
Click to expand...
Click to collapse
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Working On FireHD 10 2017
jrodat said:
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Click to expand...
Click to collapse
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
AustinR66 said:
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
Click to expand...
Click to collapse
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
saupe2005 said:
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
Click to expand...
Click to collapse
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
These directions are for my Fire 7 2015. Screenshots included at the bottom.
Go to your Settings app and click "About tablet"
Find the line that says "Build number" and tap repeatedly on it. Eventually it will say "Developer settings unlocked" (or something like that).
Now go back to the main Settings page and open "Developer options". On this page you must enable 2 things:
"Root access" - enable this for 'apps'
"Local terminal" - enable this too.
Then reboot the device.
(This is needed for enabling root access.)
The Terminal app may not show directly on your launcher, but you will see it if you list all your apps.
Open the Terminal app, and enter the following commands, on separate lines:
Code:
su
idme mac_addr 4c0b3a000002
idme print mac_addr
(The "su -c" version wasn't working for me with the built-in Terminal app, I had to enter "su" by itself)
- The first line ("su") may show a popup asking you to confirm Root access
- The second line should display to your screen "Writing idme data..."
- The third line prints the mac address to make sure you set it successfully.
After this, you must reboot your device, to activate the new MAC address.
Sometimes the kernel will ignore the new mac, if the first 6 chars (the oui) are unrecognized. The prefixes "4c0b3a" and "38aa3c" both work for me. Or you can use the 6 chars that are built-in for your device. (run the "idme print mac_addr" line to see what they are.)
A mac address is all Hex chars, so only 0-9 and A-F are valid characters.
Check your Wi-Fi settings -> Advanced to make double-sure that it worked.
Hope this helps
Here are the screenshots (Click to zoom)
jrodat said:
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
Thanks for your reply.
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
saupe2005 said:
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
jrodat said:
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
Click to expand...
Click to collapse
You gotta root it but if there is no root available then your out of luck. Sorry mate.