Related
I followed http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/ and rooted my phone successfully.
Afterwards i installed the SU and Superuser.apk as suggested on other tutorials, verified it from the computer (shell su) and clicked always allow on the window that popped up on the phone.
But every time i tryed to use the su (for instance with g1teather) i get a black empty window named "SU Request" that wont load.
since i figured i failed with a unknown part of my previous experiments, i threw in modaco´s updated rom image as described here:
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
And still the SU Request window wont load properly.
This is quite irritating since i cant turn on/off wifi teather or any of the other stuff for witch i rooted my phone (and voided warranty), so i feel a bit pissed off atm..
Can anyone plz help me figure this out?
Try turning on USB Debugging in Settings > Application Settings > Development
I'm pretty sure I remember that helping someone else
i was a bit vauge..
the first time the SU Request window loaded, it loaded fine.
But that was the last time it worked..
will try the usb debug and post feedback in a bit
the usb debug worked like a charm!
on/off tethering works flawlessly now, thanks a bunch for your help!
no problem matey :]
I left my TPT unattended for two days on.
When I've tried to use it again I got a message that Encryption did not end correctly to make a reset to original values.
This was strange and because recovery was not working I did tried that step as well without success.
Due to low battery, I manage to access settings and came to realize that there are strange certificates install like TURKTRUST Digital Certificate which I came to realize is reported to be a virus http://eromang.zataz.com/2013/01/04/fraudulent-turktrust-digital-certificat-used-in-active-attacks/
In recovery I see that I cannot mount the internal SD or data. I can connect trough ADB but I'm not an expert able to use it properlly.
Any ideas on how to recover my TPT?
Thanks in anticipation.
EDIT:using adb I manage to get the catlog ...hope someone is expert enough to go around this problem.
I only need to format / mount SDCard and data which is blocked now ...
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.
The option to mount network shares is nice but only grants read permissions to the shares.
I know it's because of security concerns, I also know there's some api and app whitelisting allowing Plex app write permissions.
I don't use the Plex app.
My Shield is rooted through Magisk.
I want all my installed apps to have write permissions to the shares. Imho Shield Experience should allow the user to make this decision.
Without write permissions, for me the mount option is useless.
Can anyone help me to get write permissions to my mounted shares?
ABSOLUTELY ++++++1000000 for this.
Did you get this working @trohn_javolta !??!
That's exactly my problem !! I have two ShieldTV (2017 / 16GB / 8.0.1). Both successfully rooted with Magisk.
How can I give all my installed apps WRITE RIGHTS to my network drive (NAS)?!? Or even specific apps I CAN CHOOSE !!!
It is very annoying that eg RetroArch can not save the scores, savestats, controller settings, ...
Or even xFile Explorer can not write to the my NAS.
IMHO, as long as i am rootet, i should decide by my own how "secure" i want my system !!
Please help us to write on a network drive as normal.
On my Phone i can write to my NAS (ES File explorer) without any problems... So why is the shield not allowed?!
Thank you
Kamikaze01 said:
ABSOLUTELY ++++++1000000 for this.
Did you get this working @trohn_javolta !??!
That's exactly my problem !! I have two ShieldTV (2017 / 16GB / 8.0.1). Both successfully rooted with Magisk.
How can I give all my installed apps WRITE RIGHTS to my network drive (NAS)?!? Or even specific apps I CAN CHOOSE !!!
It is very annoying that eg RetroArch can not save the scores, savestats, controller settings, ...
Or even xFile Explorer can not write to the my NAS.
IMHO, as long as i am rootet, i should decide by my own how "secure" i want my system !!
Please help us to write on a network drive as normal.
On my Phone i can write to my NAS (ES File explorer) without any problems... So why is the shield not allowed?!
Thank you
Click to expand...
Click to collapse
Hi, yes I managed to do so Idk if I recall all required steps but I'll try. Let me know if it worked.
First in Magisk Manager Settings under "mount namespace" set "global namespace".
Then under Download, search and install the Busybox module and restart your shield.
Now open up a terminal, I prefer Termux. Type su, enter.
Now you create the folder where you'll mount your smb share to. Make sure it's in /mnt/cifs:
mkdir -p /mnt/cifs
mkdir -p /mnt/cifs/hdd
chmod -R 777 /mnt/cifs
mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp,rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
Since this has to be executed after every reboot, I set up a profile in Tasker App that does this automatically after a reboot. Hope this works for you :good:
trohn_javolta said:
Hi, yes I managed to do so Idk if I recall all required steps but I'll try. Let me know if it worked.
First in Magisk Manager Settings under "mount namespace" set "global namespace".
Then under Download, search and install the Busybox module and restart your shield.
Now open up a terminal, I prefer Termux. Type su, enter.
Now you create the folder where you'll mount your smb share to. Make sure it's in /mnt/cifs:
mkdir -p /mnt/cifs
mkdir -p /mnt/cifs/hdd
chmod -R 777 /mnt/cifs
mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp,rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
Since this has to be executed after every reboot, I set up a profile in Tasker App that does this automatically after a reboot. Hope this works for you :good:
Click to expand...
Click to collapse
WoW !! Thank you thausand times !!
I will give it a try at home later and report back
Kamikaze01 said:
WoW !! Thank you thausand times !!
I will give it a try at home later and report back
Click to expand...
Click to collapse
No problem, hope it works.
It's a shame that this still isn't possible without root on latest Shield Experience!
Btw: Are you on latest Shield Experience 8.0.1 (Android Pie) or did you also stay on 7.2.3?
trohn_javolta said:
No problem, hope it works.
It's a shame that this still isn't possible without root on latest Shield Experience!
Btw: Are you on latest Shield Experience 8.0.1 (Android Pie) or did you also stay on 7.2.3?
Click to expand...
Click to collapse
Many thanks for the help !! I am already at 8.0.1 ... Hopefully your workaround will still work: - /
Yes, it is really a shame for nvidia that it is still not possible to have write access to its own network drives.
Above all, this restriction is not widely publicized. I had to deal with it for a long time and I've been looking for the bug for a very long time ON MY SIDE, until I read on the Internet that this problem (write permission on network) is caused by the shield.
Anyway thank you very much for your tips - I'll try it that way and maybe later in the evening i can report.
Currently i am at work and come home later... :good:
Okay... I just tried your tips but got an error from Terminux, that my NAS is read only
So same problem as before... Damn.
Terminux output:
https://imgur.com/a/8gTQYWe
Kamikaze01 said:
Okay... I just tried your tips but got an error from Terminux, that my NAS is read only
So same problem as before... Damn.
Terminux output:
https://imgur.com/a/8gTQYWe
Click to expand...
Click to collapse
Hmmm.. and you did use username and password? Cause it's not in the command on the screenshot.
The message suggests that the share you're trying to mount is read only.
Hello and thanks for the answer.
I have entered the commands exactly as you told.
Terminux does not display the complete command, but I entered PW and USER correctly
I had to do it with controller, because I had no keyboard and mouse available. But i don't think i did any mistakes.
At the moment I use the app "FolderSync" and matched the required folder directly under the two shields.
That's an ugly workaround, but it works ...
Anyway, I thank you very much for the tips and the hint. I will try again with keyboard later maybe...
Still find it very sad from nVidia that they does not give us the freedom (write on NAS) on our own devices
Kamikaze01 said:
Hello and thanks for the answer.
I have entered the commands exactly as you told.
Terminux does not display the complete command, but I entered PW and USER correctly
I had to do it with controller, because I had no keyboard and mouse available. But i don't think i did any mistakes.
At the moment I use the app "FolderSync" and matched the required folder directly under the two shields.
That's an ugly workaround, but it works ...
Anyway, I thank you very much for the tips and the hint. I will try again with keyboard later maybe...
Still find it very sad from nVidia that they does not give us the freedom (write on NAS) on our own devices
Click to expand...
Click to collapse
Make sure to hit the "reply button" under my post, this way I get notified upon your answer :good:
Did you unmount the share via the offcial way before trying to mount in terminal? I mean go to settings -> storage and unmount the share there?
I'll take the leap shortly and will update to latest shield experience version...I just have to decide whether to wait for another update or not.
I'll report back but I see no reason why it shouldn't work on pie.
trohn_javolta said:
Make sure to hit the "reply button" under my post, this way I get notified upon your answer :good:
Did you unmount the share via the offcial way before trying to mount in terminal? I mean go to settings -> storage and unmount the share there?
I'll take the leap shortly and will update to latest shield experience version...I just have to decide whether to wait for another update or not.
I'll report back but I see no reason why it shouldn't work on pie.
Click to expand...
Click to collapse
Hello and thank u for your answer.
I tried again WITH keybord *g* and unmount my NAS before.
THIS time something seem to work, cause Terminux Output sais "Operation beeing performed..." (or beeing executed or something like this).
But another 2 hourl later nothing changed... i restart my shield but only the cifs folder disapeared.
No write access
Did you tried with Shield experience 8.0.1
Thank you
Kamikaze01 said:
Hello and thank u for your answer.
I tried again WITH keybord *g* and unmount my NAS before.
THIS time something seem to work, cause Terminux Output sais "Operation beeing performed..." (or beeing executed or something like this).
But another 2 hourl later nothing changed... i restart my shield but only the cifs folder disapeared.
No write access
Did you tried with Shield experience 8.0.1
Thank you
Click to expand...
Click to collapse
Hmm.. ok. It is expected behaviour that the cifs folder is gone after reboot, that's why I use Tasker to automatically create it and execute mount command after every reboot.
Is it possible that maybe Termux didn't get root rights? You can check that by opening Magisk Manager app and going to "Superuser" tab. There should be Termux entry and root rights enabled, if not do so and try again. I always go to the settings in Magisk Manager first and set "automatically grant root rights".
trohn_javolta said:
Hmm.. ok. It is expected behaviour that the cifs folder is gone after reboot, that's why I use Tasker to automatically create it and execute mount command after every reboot.
Is it possible that maybe Termux didn't get root rights? You can check that by opening Magisk Manager app and going to "Superuser" tab. There should be Termux entry and root rights enabled, if not do so and try again. I always go to the settings in Magisk Manager first and set "automatically grant root rights".
Click to expand...
Click to collapse
Yeah... I remember - you already told me about this problem at reboot.
Is it possible to get your Tasker Profile for that *g*
I know Tasker and already use it on my phone...
Kamikaze01 said:
Yeah... I remember - you already told me about this problem at reboot.
Is it possible to get your Tasker Profile for that *g*
I know Tasker and already use it on my phone...
Click to expand...
Click to collapse
It's a really simple one. As event I chose "booting device" and as task I use a simple execute shell task.
I did more digging and maybe can give more info. Just as a quick checklist:
You installed busybox magisk module? (maybe not required for mount command)
SE Linux mode is set to permissive? (maybe not required anymore, if successfull can be disabled later)
In Magisk Manager settings set "global mount namespace"?
By having magisk flashed, you should already get su and mount commands..
You can try changing the mount command a bit, I found sth. that might work:
su -mm -c mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777 ,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp, rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
mm means mount master and should force everything to run in the global mount namespace (so the share can be accessed by every app with read/write permissions, not only with Termux)
Hi,
This last days I have stranges things with my phone, and it is the first time that happened.
When I reboot after install magisk modules or adaway file host, my phone cannot be unlocked.
I type the pin code for unlock my sim card, and after the pin code for unlock the phone.
At this moment I have a black screen and I must retype my code ever and ever.
Nothing to do, just reinstall all the rom. Unable to use a clean backup, this is the same problem.
If anybody knows this issue and can save my life, you're welcome.
Thanks a lot, cordialement
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Lethalben said:
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Click to expand...
Click to collapse
Hello, I am updating my mom's phone and saw your post.
Unfortunately that bug has been around for a few months, I have a quick temporary fix for you but unfortunately the bug will return, if you can live without a screen lock that may be you only solution for now.
Lock Screen ( delete the lock)
Boot to Recovery
Go to Recovery File Manager
Navigate to the /data/system folder
locate and delete the file called : locksettings.db
Now you no longer have a screen lock and you can easily get into the phone.
FYI : If you want the lock again , simply create a new key or pattern
This issue could be anything such as corrupted permissions, It seems that it pops up after installing audio mods and substratum. But I don't think it is caused by either one.
If your phone gets hot while experiencing this issue flash the thermalfix 7 file, located on the thermals thread https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
This morning I've formated my phone to be sure is not an error from me. I will try your solution if it happens again.
Thanks for your response my friend!
Is it possible f2fs formating data partition is the issue?
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Forsaken75 said:
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Click to expand...
Click to collapse
I'm go back to ext4 and everything is OK.
I saw a magisk module who's made for stop this issue.
If there is a magisk module for that I think the problem is f2fs!
Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
I don't think so because I only use Ext4
Well, I think I finally found the true origin of this problem: Magisk Hide interferes with newer Webview implementations, as explained here:
https://www.didgeridoohan.com/magisk/MagiskIssues#
I also found several workarounds:
1) Disable Magisk Hide. I need some banking apps, so for me this is not an option.
2) Use Chrome Beta and select its engine as default Webview in Developer Options. Chrome Beta signature is not buggy, so it works as it should. This is the solution that I've chosen, by the way.
3) Ask our developers @codeworks @mosimchah and the others if they could include this commit that fixes invalid signatures in their future releases:
https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
txiscoman said:
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
Click to expand...
Click to collapse
It's some app compatibility issue with Android Pie/Webview for sure. In my case was my banking app, changing to Chrome beta fixed the problem (app still crashes from time to time, but I'm not having the damned screen lock problem anymore)
You can try using Webview component alone from Play Store (I notice that in my case it's working too) or do some research to find out which app is causing the issue and uninstall it (if you can live without it, of course)
Deleted