AdAway fails on rooted stock - ZTE Axon 7 Questions & Answers

Anyone know why AdAway does not work on rooted stock B29? It works in systemless mode but not sure if that's the same thing. Anyone know how to fix this? Tried changing the path to data/data/hosts but then get another error. Saying a sibling is needed. Then it tells me to create something in recovery. Is this normal?

Here are the other errors after changing the path

macboss said:
Here are the other errors after changing the path
Click to expand...
Click to collapse
You have write protection enabled mate.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE
This is how you disable it:
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
Source: http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/

Iam using this on Axon G
https://forum.xda-developers.com/showthread.php?t=1916098

great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
nfsmw_gr said:
You have write protection enabled mate.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE
This is how you disable it:
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
Source: http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
Click to expand...
Click to collapse

macboss said:
great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
Click to expand...
Click to collapse
I'm not really sure actually, although I think ZTE phones have write protection enabled by default.
It's 50/50 really.

macboss said:
great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
Click to expand...
Click to collapse
Write protection is enabled by default.

ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?

OK so I'm trying to run this on my phone I'm terminal emulator and I'm getting this
what am i doing wrong?
macboss said:
ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?
Click to expand...
Click to collapse

I tried a different emulator. All I'm getting is found. How should I do this?
macboss said:
ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?
Click to expand...
Click to collapse

OK. i got it to work. Write protection is off on my Axon. It rebooted. I was create a symlink with adaway. Not having to use systemless mode. I think we did it. Thank you for your help.
Im just not sure about the mac thing though

macboss said:
I tried a different emulator. All I'm getting is found. How should I do this?
Click to expand...
Click to collapse
On that first terminal emulator you showed, type "su" and press enter. Then write "reboot disemmcwp" and tap enter. Your phone will reboot immediately.
That's how I did it.

ok. i just did it through terminal on the mac "./adb reboot disemmcwp" and that worked.
what do you think happened when I disabled write protection on my mac? I typed "sudo reboot disemmcwp" and the machine just rebooted...? Everything looks and works fun but im not sure if what I did was bad or not. Or if I need to turn it back on?? Note sure. But hey, adaway works!!

The checkbox in AdAway preferences to use systemless mode works well for me, without having to remove write protection.

macboss said:
ok. i just did it through terminal on the mac "./adb reboot disemmcwp" and that worked.
what do you think happened when I disabled write protection on my mac? I typed "sudo reboot disemmcwp" and the machine just rebooted...? Everything looks and works fun but im not sure if what I did was bad or not. Or if I need to turn it back on?? Note sure. But hey, adaway works!!
Click to expand...
Click to collapse
Lol it just rebooted and didn't disable anything. diseemcwp is ZTE specific.

Related

Permission issues with su and rom .3

Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen
vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.
adb shell
su
look at phone, click allways all
...
..
.
jcase
jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice

Froyo ROM

Hi there,
I made a preliminary port of Froyo for the Liquid.
It needs the Donut radio rom, so it won't work on LiquidE.
You can test it on an Eclair radio, but usb and GSM/3G won't work.
IHMO, It works fine for daily use (I do use it daily.), current known bugs:
-Random lines appearing on the screen on refresh
-No wifi
-Wiping data kills radio
-No tethering
-Unsigned
Hint: to enable App2SD to all apps (by default, only some apps accept it), do
Code:
pm setInstallLocation 2
This will install all apps to SD, you can move them back to phone.
Please use http://code.google.com/p/acer-liquid-froyo/issues/list as bugtracker
(Donate link in my sig also works for my Liquiid's work )
Here's the downlink link:
http://code.google.com/p/acer-liquid-froyo/downloads/detail?name=Froyo.zip
Update:
Full: http://www.megaupload.com/?d=S9P799GO
Update: http://www.megaupload.com/?d=UPAF7YD8
-880MHz
-ramzswap
-USB OTG (seems not fully working)
-working iptables (droidwall works)
-usbnet (tethering kind of works)
-changed H264 resolution limit to 720p
To get tethering working, do echo 1 > /sys/class/usb_composite/rndis/enable
Then go in the appropriate menu and tick the usb tethering option.
The results are random, I don't know why yet. The released sources might help understanding that.
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
akira.pwr said:
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
Click to expand...
Click to collapse
Install connectbot
Launch it on the "local" protocol, do
su
(the su manager will ask for permission, allow it)
pm setInstallLocation 2
And it's done.
Ok, i'm doing it, it create a partition for apps?
After doing what you posted above, all apps go in my sd automatically?
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
akira.pwr said:
Ok, i'm doing it, it create a partition for apps?
Click to expand...
Click to collapse
Apps go to the normal vfat partition
After doing what you posted above, all apps go in my sd automatically?
Click to expand...
Click to collapse
It should
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
Click to expand...
Click to collapse
You must put su on the console, not as a nickname, the nickname doesn't mean anything.
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
akira.pwr said:
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
Click to expand...
Click to collapse
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
rafyvitto said:
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
Click to expand...
Click to collapse
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
akira.pwr said:
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
Click to expand...
Click to collapse
Weird..check on malex recovery to see if your device is rooted, without root you cant run superuser command's, but since your running phhfroyo it should come already rooted...

2ndInit_Installer

Found by laidaxin , from w.w.w.591fan.c.o.m
for us that are noobs, what exactly is this?
dingding2012 said:
Found by laidaxin , from w.w.w.591fan.c.o.m
Click to expand...
Click to collapse
Doesn't work for me.
Sent from my MB860 using XDA App
thebluetoothkid said:
for us that are noobs, what exactly is this?
Click to expand...
Click to collapse
Its supposed to be a working recovery for flipside. I can't get it to work however.
Sent from my MB860 using XDA App
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
dingding2012 said:
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
Click to expand...
Click to collapse
I am able to do all that also, but can't backup and can't install anything. I get error can't mount data/recovery and aborts.
ok... so i'm trying for the 100th time to install this silly thing... and for some reason... when i try to run it... it kicks me out...
i'm not sure what i'm doing wrong...
when i attempt to pause the install process... i get a screen full of if i type adb without an argument...
if someone could gimme a hand with this or tell me what the hell i am doing wrong... i'd appreciate it...
i wanna try to get laidaxin's cm7.2 working on my phone...
i dunno if it matters... but i am attempting to install from a windows xp machine...
Hello!
First, Thanks to all people around this work, specially Laidaxin for good work.
Well, sadly... I also still stuck on install the FlipSide recovery option of the first post... I did all te proccess by eleven times, testing different details that may be not clear for me (as run as administrator, with abd CMD screen closed and opened, if the version of adb never shows me the logs that appears in cmd screenshot... several times I got on the FlipSide the screens talking about su and later 2ndinit script got superuser permissions... but the screens of cmd generated by the script are so fast that was not able to read or check if the 2ndinit script was succesfull or if there something else that may be failing/missed... so by now still no luck)
as a resume, in hope that may help to test from new friends around here:
1) I reflashed my FlipSide to stock with sbf from the other thread tutorial (I use sbfflash in linux and everything works fine, using Power+UParrow in keyboard to enter in bootloader mode my Flipside)... and then I insert my SIM and SD card wiped with only the CM7-Laidaxin.zip file on it, ...complete setup as minimal possible in order to be able to set USB mode to memory access, and turn on usb development in applications menu.
2) Then I ROOT with SuperOneClick version 2.1.1!!! and connect my phone in normal use screen home (NOT bootloader mode!) with UBS debugging turn on and with USB mode set to memory card access (NOT Moto Portal No Media access...), the other methos with Z4root and newer versions of SuperOneClick FAILS for me...
3) I then try to install recovery with Laidaxin installer and procedure, but as I said after some attemps I still not success in get the recovery working, also try diferent ways... removing battery then reboot with VolumeDown pressed, Turn off normal and repeat, turning ON AND AFTER see the Red Moto press the VolDown key short time, later maintained it long, then pressing it several times, etc...
So, I made this resume in order to share info from my side and hope to save some time to other friends that may want to test the CM7 from Laidaxin, than in fact seems like a GREAT work for our Flips... so please if any help to get this fully working and tested will be very gratefull...
Best regards!
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
rignfool said:
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
Hi!
Ok, I am not totally sure, but I suspect that this is the original link of this recovery, however, just now I need to go to my work, so, I do not have chance right now to check it, but hope may be usefull.
http://forum.xda-developers.com/showthread.php?t=944543
Best regards!
You should be able to install it like this:
- Extract everything in the "data" folder into a folder called "bootmenu" on your sdcard
- Then use either "adb shell" from a command prompt, or Terminal Emulator on the phone should work:
Code:
su
cp -R /sdcard/bootmenu /data/bootmenu
cd /data/bootmenu
chmod 0755 *
./install.sh
And it should say "Install complate...."
You can also remove the folder(s) if you want:
Code:
rm -R /data/bootmenu
rm -R /sdcard/bootmenu
Then to get into it, reboot the phone and once the notification light turns on, hit volume down
You my friend.... are the ****ing man...
FYI
Use the touchpad to select
Sent from my MB508 using Tapatalk
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
I ran into the same problem but mine also stopped me from installing any other rom to test, run, or otherwise. I'm at a standstill in terms of helping test.
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
laidaxin's rom replaces this recovery with one that doesn't quite work perfectly yet...
You should be able to boot back into CM7 and re-run the above commands and it'll work again
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Maybe try "rm -R /system/bootmenu" then install it...
rignfool said:
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
It does the same for me, which is what's keeping me from trying CM7, as I have no way to restore my current nandroid. The defy installs their recovery to /system as well and I gather that it works as intended, I wonder if it's that we need our own build of CWM. Do we know if whoever built CWM for the defy has their source tweaks available?
Unless you have something irreplacable in your /system or /data... I would just have RSD lite and an sbf ready... and take the plunge...
Because....
When you use CM7... apps2sd moves not only the apk... but also the lib files to the sd card...
As long as you switch the 'network operator' to GSM only (in wireless and networks)... laidaxin's kang runs beautifully... much much faster than stock
Sent from my Filpside using Tapatalk
Link2SD has no problem moving the lib files in our stock rom... I'm no stranger to reflashing with RSD Lite, it's just tedious to get everything set back up JUST right, and this is exactly the kind of thing nandroid is great for.

Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error

Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error
I am out of all tricks now for reviving my Note which boots into download and recovery mode. I conclude that from what I have experienced, that factoryfs is the partition which fails to take any write commands when I odin a ROM, as it gets stuck at the factoryfs message. I have tried all the flashing of kernels and ROMs with no luck.
Working with adb seems to be the only option, to configure the partitions on my device manually. The big issue is that I am not able to execute "adb shell" command using Forest1971's guide.
So far, I have had no luck going beyond the "exec -/system/bin/sh...:No such file or directory...(2)" error message, when I type the "adb shell" command.
Can someone with the know-how of how to work through adb help with this? This is my last effort of trying to recover my Note, and if it fails, I will have no choice but to sent the device out of the US. I dread sending my phone out of the country for repairs, as I don't know just how long it will be before it gets fixed and is shipped back to me.
Please do not suggest any flash options, because as I said, I have tried all there is to do with flashing - nothing has helped.
First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.
paulshields said:
First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.
Click to expand...
Click to collapse
Suggestion ignored. Any more?
Get an iPhone?
Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk
paulshields said:
Get an iPhone?
Click to expand...
Click to collapse
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
zviki said:
Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.
incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.
Click to expand...
Click to collapse
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.
matiasg85 said:
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.
Click to expand...
Click to collapse
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?
incisivekeith said:
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?
Click to expand...
Click to collapse
Yes, unfortunatelly i did everything as stated on adb, but had no luck. If ssc don't replace it, i will try using the memory blocks used by the "internal sd card".
You must try it anyway, there were some users that succesfully unbricked the phone.
Did anyone try this mk2efs command with -c option ON ??
Sorry Incesivekeith
I was out of connection for past 2 days.
We have to pull Mr Forest1971 for doing this.
Let me sum up :
parted is not able to solve your issue.
mk2efs is another formating tool that comes with CWM
You are stuck up in executing commands.
Now the idea of flashing the cwm kernel is fine. Did u try that ??
Mr Forest1971 :
Did you see Dr Sumralls comments for this bug.
''He says that we have to go for a full wipe. I have a tool but I dont know I couldnt share it.''
incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
Click to expand...
Click to collapse
I asked you to ignore the initial suggestion as you've obviously not got any functioning recovery. You've not provided much info about how you got to this position, but in my similar situation I got out of it by successfully flashing a FULL WIPE factoryfs (LA4 in my case) and doing the factory reset as I mentioned in my first response. I lost a few GB of my eMMC storage but got a working device. May not help you, but may be useful info for others. Share and share alike. Good luck dude .

[SOLVED] Can't disable write protection

Hi there,
I am running my A7 on official RR. I tried to get war mod and Adaway running, but can't get /system get writable.
I executed 'reboot disemmcwp' appr 10 times, but no success. I also formatted data in TWRP and tried again to disable write protection, which wasn't successful.
I don't know if there is a correlation, but in Developer options I also cannot activate OEM unlocking.
Does anyone had this problem before and can tell me how to disable write protection?
Thanks a lot!
EDIT:
I ran the command once via adb and it worked as charm. I don't understand the difference, because I also tried different terminal apps. Nevermind, it is working now

Categories

Resources