Missing system/bin/su - T-Mobile LG V10 Q&A, Help & Troubleshooting

I recently rooted my device. ( my first time, go figure) After many errors and even a bricked device, I finally managed to root the device and unbrick it. I believe the opperating system was deleted in the process along the way and I had to flash a stock ROM onto the device, resulting in a downgrade from 6.0 to 5.1.1. I still had TWRP on the device and was able to put the needed superuser zip files on the SD card when in TWRP mode because that's the only time the pc recognized the phone. After install in the Superuser files in Twrp the device rebooted up and I ran a root checker and it says that superuser was installed correctly and I have root access. Now here's the issue, I went to go and turn on unknown sources and when I click on fingerprints and securiry, I'm met with an error message saying com.android.settings has stopped . this happens In a few other areas of the settings but not all. I also had downloaded another app (NT Hidden Settings) that I was hoping would allow for me to turn on unknown sources and when I click on the option to turn on unknown sources, I get anmessage saying system/bin/su missing. I now am lost and have no idea what to do. I tried copying a file named su from the xbin folder thinking that may fix the issue but it didnt. Any tips or ideas? If I have to unroot the device and reroot I have no problem doing so (although I'd probably need a concise tutorial because I had very poor luck getting as far as I did..)

Related

[Q] Samsung I9000 proximity sensor problem

Hi guys!
I rooted my phone and got cyanogenmod jb. I found that my phone's screenlight turns off during talking but after that it doesn't turn back on.
So I try to solve the problem, and I found this
"I did some more research on this issue and it seems that (for some people) even flashing a new firmware/ROM did not solve the problem.
The reason for this problem is most probably some corrupted sensor calibration data files. So the solution is to recalibrate the sensors.
There are two requirements
1) You will need ADB (Android Debug Bridge), you can download it from Google
2) You will need to root your phone (using Super One Click or ChainFire root)
once ADB installed and you have a rooted phone, you can try re-calibration as follows:
adb.exe shell
su
# /system/bin/sensorcalibutil_yamaha
If you get errors on your phone like "msmachdep_Init failed" and "calibration utilities failed", then you need to delete the file “ms3c_yamaha.cfg“ in data/system. This file resides in your phone so you will need a Root Explorer App to explore the root areas and delete this system file.
I am sure this will solve your problem."
Unfortunately I can't use adb and terminal.
Could you help me what I should do, and how I can do it?
Thanks a lot!

Nabi 2 1.9.12 wifi issue

Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!

[Q]Can't access internal SD storage

So the other day I was trying Cyanogenmod 9 on my galaxy pocket, however I didnt realize it wasn't an official release and it was REALLY bugged and I made a huge mistake because i forgot to install CWM. Thing is installed this rom and I belive i pretty much bricked my phone because now I can't get access to any of my networks, wi-fi, bluetooth, or usb mass storage or my sd card are not being recognized either...
What I've tried so far was sending the stock rom through Quick ADB Pusher, but it tells me that even though my phone appears to be root It wont allow it to access, then I tried different ways to root and unroot because apparently SU is not giving me the permissions. So finally tried my last option with ADB (I'm really new to it ) and was trying an adb push but I keep getting permision denied if I send it to /root or read only file if I send it to /system also tried Asb shell $su but I keep getting a denied message. I would really apreciate if anyone could help me to find a way to copy my rom back into my internal storage, thanks a lot!
DIAZEPUNXX said:
So the other day I was trying Cyanogenmod 9 on my galaxy pocket, however I didnt realize it wasn't an official release and it was REALLY bugged and I made a huge mistake because i forgot to install CWM. Thing is installed this rom and I belive i pretty much bricked my phone because now I can't get access to any of my networks, wi-fi, bluetooth, or usb mass storage or my sd card are not being recognized either...
What I've tried so far was sending the stock rom through Quick ADB Pusher, but it tells me that even though my phone appears to be root It wont allow it to access, then I tried different ways to root and unroot because apparently SU is not giving me the permissions. So finally tried my last option with ADB (I'm really new to it ) and was trying an adb push but I keep getting permision denied if I send it to /root or read only file if I send it to /system also tried Asb shell $su but I keep getting a denied message. I would really apreciate if anyone could help me to find a way to copy my rom back into my internal storage, thanks a lot!
Click to expand...
Click to collapse
try this. download stock firmware of your device flash thru odin link http://samsung-updates.com/
thanks a lot, yes actually odin was my first choice (i forgot to mention it) but it gave me a failed message everytime i tried it, however i don't know what i've done because i just tried again a few minutes ago using the same rom and this time it worked

[Q] RCT6573W23 Recovery

I am using a RCT6573W23, I have rooted it using Kingo and editing the ADK file... Everything went well, and I had installed SU and Busybox, Developement was on, but I don't think it remains on... I did some build.prop tweaks, and when messing with the LCD I messed up my system, disabling it from booting up.
I boot into Recovery just fine, and I DID BACKUP AND HAVE my original build.prop file, however, good ol' RCA doesn't provide any "files" for support at all, and connecting ADB is "SIDELOAD" only... I've read several places but everyone suggests going INTO recovery, which, I can do, or using ADB, but fail to realize it's sideload issue... I've pushed several files, but every single file is a bad footer, and wrong signature... I'm at a loss... Does ANYBODY have a recovery.zip from their Apollo 8" who could make a backup for me, so that I could sideload an official zip file. I would MUCH appreciate it... Thank you.
I have the same model... you're the only one I've heard of that has successfully rooted this one... is there a way I could get my official stock ROM copied without root?
Rooting it was simple, I believe you can go to settings backup and restore to get a .zip of your stock.. If you could shoot me a copy that'd be great. I can share how it was rooted, although it was super easy to look up.
There's not an option to backup entire system just app files.
What recovery did you use? and did you use the kingo universal rooting tool? And what edits did you have to do to the ADK?
I've successfully rooted but have no way, as of yet, to zip up my ROM. Any thoughts?
Anybody know if xposed framework or clockworkmod will work on this device?
-- Rooting your RCT6573W23 --
Install your USB drivers... If you don't have them, or you can't make your system acknowledge them, use the SDK-Method to fool your computer into reading the correct USB for your device... That method can be found at: addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Once you've got your drivers, before even plugging in your phone, make sure you have all of these options checked... From the developer's menues: "USB Debugging" "Allow Mock Locations", and in your security & screen lock settings: "Device Administrators", and "Unknown Sources" need to be checked...
Install Kingo from kingoapp.com
NOW, simply plug it in and click root on the pc... It'll install SuperUser and enable you to use just about any feature a rooted device can use, but without flashing roms... Still nice for cheatengine and stuff.
----------- Finished, Now... -------------------
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
I've acheived root and have SU, but Here's no way to make a nandrid without some sort of recovery...
Edgia said:
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
Click to expand...
Click to collapse
I believe these tablets have the RK3188T chipset, and I found These CWM Recovery images: http://androtab.info/clockworkmod/rockchip/
I don't have time to mess with it right now but I thought I'd share. I'm going to do some more reading on the subject before trying anything real crazy. Let me know if this works out for you...
Any luck on this? I was hoping to install a mod on this tablet myself

Azpen A743 - Root or help with hosts file

Like everyone else, I picked this Azpen A743 up at Microcenter for $20. It was advertised as having 5.1, but came with 6.0.1. I bought it to stream music from my Asus router with samba share drive. Other than that, just plan to use Google News, weather app, and light web browsing. Tried a couple rooting methods but no luck. Reluctantly tried Kingo Root, but it never finished the process. (I've read these devices come preloaded with malware, so some more from kingo root won't hurt). From what I've read and searched, there isn't any custom recovery for this tablet. Anyone know how to root it? I did manage from stock recovery to sideload SuperUser.apk, but it doesn't work.
I have USB debugging on, and bootloader unlocked.
Specs are: Allwinner 1.3 GHz A33 4core
The recovery lists the tablet as:
A33_86v/astar_xr819/astar-xr819
6.0.1/MOB30R/20171221
and firmware version v6.0rc3 (I have found references to OxygenOS for that FW version)
If there is not a root method, is there a way to alter/replace the hosts file? I would like to transfer the hosts file from my phone generated by adaway. I have copied my phone's hosts file and tried:
adb reboot download - reboots to OS, doen't seem to have a download mode, but it would almost have to in order to update the FW
adb reboot bootloader - boots to Azpen screen buring bootup, but just hangs
adb push - system read only
adb shell - cp hosts (read only)
adb shell, then su - SuperUser pops up saying ADB need SU access, grant it but nothing happens. can type, but nothing happens.
from recovery, if I mount /system, then device no longer detected by adb.
Didn't try any fastboot commands, scared of losing data, and I don't see anyway to back up the current FW
Also tried the Phoneixsuit software to install apks, but it didn't work
created my own update.zip - 255 error (or not verified even when using various methods to sign the .zip file-Sign-em, Auto-Sign)
Is there a way to create a .zip or apk that is signed that will copy the hosts file to /etc/hosts?
Any advice or guidance would be appreciated.
Have you had any luck since posting this? I'm trying to root the same device, but no luck so far.
Nope. Somehow managed to push Superuser to it, but still not rooted. SU app pops up asking for SU if "adb shell SU", can grant permission, but still nothing. Can't make permission changes to RW. I finally got fed up and tried flashing the wrong firmware to it, but even that wouldn't work. PhoenixSuit, PhoenixProUSB, PhoenixCard would not work to flash different firmware... and no response from Azpen about lollipop firmware or any firmware for that matter. Won't return emails or answer the phone.
I don't know if by pulling the /system folder ,making changes, then using a tool like Dragonface to build a prerooted image would work or not. Can't really do anything without the right firmware for the device.... and I'm not counting on that happening.
This is a good place for info on A33 info and tools:
http://forum.gsmhosting.com/vbb/f906/
I finally got widgets to update after a month of tinkering.... everyday it tells me the SD card is corrupt... other than all of the above, it is a decent little tablet for the $20.

Categories

Resources