Related
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
dialbat said:
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
Click to expand...
Click to collapse
You're in recovery mode right? I rooted before the tmobile update so I used the original method not the one you're using. I assume that for the most part you need to have your phone in recovery mode.
The /system/ directory is read only unless you're in recovery and I believe that's were that method attempts to write. You usually only get that message when you attempt to write to the system when not in recovery.
Thank you, but there is not a single word about puting phone into recovery mode in the instructions. Unless they mean it my default
i will try though.
Yeah, some steps are left out in certain 'common' tasks like rooting. It's assumed to be common knowledge or that if you don't know to automatically do a step then maybe you shouldn't be attempting it. At least that's the feeling I get sometimes but that's why it's important to search and ask if you don't find the answer.
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
If it's under/system, you need to be in recovery. I rooted with the original method though, so I can't really tell you much.
guitarist5122 said:
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Well, i've followed steps to the point. I have rooted my phone before, so even though i am a newbe, i do have a general idea of the process.
But i have no idea why it just won't work for me.
I have tried putting it into recovery using loop script, otherwise it just states that it's in recovery and still won't let me write to it
KCRic said:
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Click to expand...
Click to collapse
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm... Allow me to copy and paste a few lines from that thread, written by the developer:
1:After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
2:Important: If you do nothing after step 12 then you are not "rooted." This program grants itself root permissions in a shell, that is ALL. If you want system-wide root access (what most people consider "rooted"), you MUST flash a custom ROM since the NAND protection on our device prevents us from giving global root access while inside the ROM. When following Eugene's instructions on flashing ENG, make note to NOT run the command 'su' if you already have a pound symbol (#) at your command prompt!
Basically, this 'root' method is actually a program that allows you to flash the ENG package to give you root. By itself, the program does nothing but allow you to operate inside the shell as root for a short time. Sort of like the 'sudo' command in linux - at least from what I can tell.
I'm aware of what the developer said. I'm also aware that I disregarded not having the phone booted since it would be a little tough to toggle wifi without being booted. If you don't believe it can be done, do a nandroid backup and unroot your phone and try rerooting. Pushing exploid and do the root whole process before flashing the eng-build while booted. Or just take my word. Personally I figure out for the life of me how anyone toggles the wifi (which is one of the steps) if not fully booted.
I don't argue just to be right. I just don't want people to be given incorrect info and never solve their problem. Rooting and can be frustrating on this phone if your not too familiar with rooting or using command prompt.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I wan't saying the files can't be pushed while it's on, I've done that before but NAND will undo or not complete it once you reboot. It's the same reason that you can't delete a system app while the slide is booted - well you can but it will still be there, and once you reboot the delete is undone - unless you're in recovery.
All I was saying is that it's not a permanent write to the system, if that's where it's even being pushed and he still has to flash the ENG build to gain full root. I think this guy needs to just redo the steps, maybe read the old root methods to gain some insight too. It might help.
btw, I think there actually is a command to toggle wifi through adb, not sure if it does much in recovery or not. Also, not a chance in hell am I going to unroot - it was a pain in the a** catching my phone in recovery even when I used the loop.bat file
Good to know that's why my apps didn't stay deleted.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Thainfamous20v said:
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Click to expand...
Click to collapse
rm, rm -f or any other commmands will not work with terminal emulator because in order to use that program you phone has to be on, and since we can only write to the /system in recovery I'm sure you see what I'm getting at. You can still pull from the /system when the phone is on. The command isn't 'pull' though, it's:
Code:
cp <path to file> <location to copy to>
As far as the unroot thing, use the search bar [slide rom bible].
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
PunkRockJesus said:
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
Click to expand...
Click to collapse
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, windows uses \ for local and local network file paths, it only uses / for remote locations and networks.
I'm not sure if this would work without already having root (I received my phone already rooted, never had to do it)
In command prompt, try
adb remount
You can also try this:
adb shell mount -o rw,remount /sqlite_stmt_journals
See if any of those work. Like I said, it may not, since those might be things that need root.
Any updates on this? I cannot push the file either. And "adb shell mount -o rw,remount /sqlite_stmt_journals" does nothing.
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?
ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.
Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.
did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons
thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.
I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas
No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun
Have you enabled USB debugging in the developer options on Android. And are you using sudo or su with adb on Linux?
Sent from my LG-ls990 using XDA Free mobile app
smokey_circles said:
No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun
Click to expand...
Click to collapse
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.
mister_no said:
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.
Click to expand...
Click to collapse
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
I also discovered my fatal mistake was using a kit kat guide that was butchered to be a lollipop guide. Lack of sleep and over-excitedness led to a bootloader lock. Flashed the stock kit-kat ROM, rooted and I'm finally running CM12 nightlies.
No major bugs that irritate me, smooth and responsive. Very happy with the G3
smokey_circles said:
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
Click to expand...
Click to collapse
Not to my knowledge.
Actually when the device is in bootloader the connection protocol is MTP.
You can check it yourself with lsusb command that device's USB ID (idVendor & idProduct) is different for PTP than for MTP. In bootloader device has the same USB ID as when it is running normally and MTP mode is selected.
I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
dashlatrell said:
I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
Click to expand...
Click to collapse
Which Android version is your phone running? Where did you download the zip file? Search for the right rooting method in this forum, never trust those unknown sites found in Google
Yes I downloaded the Zip file and my android is 5.0.
A good and bad news, I was able to activate root but I'm trying to use the emulator terminal to change my MAC address and the message that appears is "tmp-mksh NOT FOUND"
I use the "su" command and soon after when I will use the "busybox iplank show wlan0" and this message appears above. Can you help me?
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Reply
kenbo111 said:
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
dashlatrell said:
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
Click to expand...
Click to collapse
That's why your fastboot commands were not working. As far as the other MAC address problem is concerned, I don't know about that
Sent from my ASUS_Z00A using Tapatalk