Related
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
Hello,
I have an external USB camera(endoscope) that I'd like to use with my Huawei Mediapad tablet. I've been googling and its possible, there is no hardware restrictions since USB OTG is working(tested with thumb drive). I'm not sure about UVC drivers but there are a few other problems that might be causing the problem.
Reading a blog i discovered that since KitKat(this tablet has 4.4.4) the SELinux policy is set to "enforced" and therefore apps can't access external USB camera feeds like they used to straight out of the box. There are 3 workarounds which all require rooting.
1. Start the app with superuser rights
2. Configure SELinux to allow USB cam feed
3. Custrom rom
Blog link: htt ps://droidperception.wordpress. com/2013/12/01/webcams-on-android-4-4/
So it all comes down to this - I need to have this device rooted but I haven't even found a single thread about this model in this forum.
NB! I don't have room for experimentation(read: bricking the device) since the device is not mine.
Thanks for you attention,
Pask
You ask quite a while ago and I see no answer. So, just in case, I did root mine in a way I not necessary would recommend, but ... KingRoot latest version can do a trick, but it definitely not kind of software I would keep on my tablet. So after that I install SuperSU, Link2SD ( using it to get rid of applications I do not like) and RootExplorer + Terminal. Give all of them root access using KingRoot manager and with help of Super-Sume App (will cost you some money) start a process of getting read of all related to KingRoot and Co. It is more tricky that one may think but by freezing and killing some processes in "write" time I manage to install SupeSU binaries and remove left overs. I still have problems to get su requests, so just copy config files from my phone with access rights already given to specific applications and deny access to anything else. So far do not see anything I cannot identify running, so my hope KingRoot is completly gone.
So far I did not fine any other tools/methods to get root
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT. Flashed with Odin3.
Magisk 18.1 thx topjohnwu
[*]Xposed 90 beta 3 thx rovo89
Xposed systemless over Magisk module "Xposed Framework"
TWRP 3.2.3 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
There are two ways to solve this problem.
You lose all of your saved Wifi passwords and you need to pair all Bluetooth devices again.
First Method:
Go into Magisk and look for the module:
libsecure_storage companion for rooted Samsung devices
Follow the instructions that are given with the module. It works fine with my SM-A320FL.
Second Method:
First of all you need ROOT access and a root explorer (e.g. ES File Explorer) on your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. That's because the Wifi passwords are stored encrypted.
simple_s said:
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT rom. Flashed with Odin3.
Magisk 16.4 thx topjohnwu
Xposed 90 beta 3 thx rovo89
TWRP 3.2.1 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
To solve the problem I did the following steps:
First of all you need ROOT access to your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. This is because the Wifi passwords are stored encrypted.
Click to expand...
Click to collapse
cool, i mean nice fix...working also on s9+
thx for this
Working here too!
Galaxy S9 with Magisk root.
Installed Xposed v90-beta3 yesterday, problem that BT connections were gone. Also WIFI passwords were incorrect. Not a problem that I had to re-enter WIFI passwords, but BT connections were gone each (re)boot.
This fixed the problem.
Thnx!
Deleted
Thanks works for my S9
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Dante63 said:
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Click to expand...
Click to collapse
I put the files in system / lib
And but pairing stays now
Alex-V said:
I put the files in system / lib
And but pairing stays now
Click to expand...
Click to collapse
Same, pairings stay for system vendor lib...
Maybe as long it's lib, doesn't matter which one ?
Deleting WIFI Passwords is not mandatory (at least for me). I had to reinstall Xposed and clear Cache (not Dalvik/ART) in order to get it working again. Without reinstalling Xposed and clearing cache the lib files got deleted every reboot.
Thanks.
For S7e with Oreo, beside forgetting paired devices on every bluetooth off/on, enabling bluetooth took noticeably longer time.
Placing libs in /system/lib and /system/lib64 did not work (build.prop edited, of course), placing them in /system/vendor/lib and /system/vendor/lib64 helped.
Is there a way to avoid replacing the files? On the xposed issue page (https://github.com/rovo89/Xposed/issues/294) ahronshor mentions backing up /data/system/secure_storage/com.android.bluetooth/, and then copying it back in place. Maybe that's the way to go, provided you are before rooting a freshly installed original firmware.
Another thing. I have flashed a new firmware (G935FXXS3ERKE), then flashed TWRP back even before rebooting. Then booted to TWRP and installed "remove encryption.zip", SuperSU and xposed, and finally booted the system (for the first time after update).
Bluetooth works now, on new firmware's original libraries and build.prop (btw, .so files are identical with previous G935FXXS3ERJ2, build.prop has just dates and versions changed). Off/on, restart - paired devices stay where they should, bluetooth enable time as usual.
Maybe the libsecure_storage.so patch (jnl was not modified at all) was to stop trying to read encrypted bluetooth data and to create an unencrypted container. It seems once the Bluetooth data file on /data is unencrypted, original code manages it correctly.
Thanks! Works on Note 9 Oreo 8.1
Reporting this solved my problems on J7 2017 with Oreo 8.1. Magisk 18 and Xposed. Thanks.
simple_s said:
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
Click to expand...
Click to collapse
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
There is a magisk module that can do the trick without need to xposed.
Sent from my SM-N960F using Tapatalk
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Ninolina said:
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
Click to expand...
Click to collapse
I couldn't solve it.
iltoffa said:
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Click to expand...
Click to collapse
I don't think so.
I added new informations to the guide.
Apparently there is a Magisk module for some phones who does the same thing. You find it in Magisk under
libsecure_storage companion for rooted Samsung devices
It works perfect on my SM-A320FL.
My personal solution has been to remove IFTTT which was installed. From that, no disconnections found at all
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.
So I recently got the idea of playing games on my Huawei P20 lite. I sucessfully connected my controller (Nintendo Switch Pro Controller) over bluetooth and then i tried multiple games without sucess. The controller itself gets recognized but the button layout is completely wrong and the right stick doesn't gets recognized, even not with retroarch. So I made a custom Keylayout file but I can't push it into the system directory. Is there a way to install it or get it into the system directory without rooting and without unlocking the Bootloader?
I'm running EMUI 9.1.0.306 and I'm having the ANE-LX1 Model.
Kuhweit said:
. Is there a way to install it or get it into the system directory without rooting and without unlocking the Bootloader?
I'm running EMUI 9.1.0.306 and I'm having the ANE-LX1 Model.
Click to expand...
Click to collapse
It won't be easy without root... On Emui 9.1. the system and vendor partition does not go in r/w mode due to the new filesystem called EROFS (Extendable Read-Only File System).
Try ADB & "SetEdit" application by "4A":
https://play.google.com/store/apps/...itor)&pcampaignid=APPU_1_GfnPXqyUBcitkgWboZAY
Thanks for the answer.
I downloaded the app and had at look at it.
I don't know exactly what to do here.
I fear messing up something. So what must I do in order to move this data?
Kuhweit said:
So what must I do in order to move this data?
Click to expand...
Click to collapse
I can't help you anymore,*keylayout file is Greek to me , sorry...