error deodexing 4.2.2 - Sony Xperia L

i can't apply deodex por 4.2.2!! please help me! it shows me that error. what can i do??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

looks like you don't have a full root. how did you root? when the batch tries to remount system as r/w, it makes the device reboot, and that's why you get the device not connected error. The push to local is fine because data is always read/write, so it makes it an easy dump ground for exploits and such, but you need root to mount system.

getochkn said:
looks like you don't have a full root. how did you root? when the batch tries to remount system as r/w, it makes the device reboot, and that's why you get the device not connected error. The push to local is fine because data is always read/write, so it makes it an easy dump ground for exploits and such, but you need root to mount system.
Click to expand...
Click to collapse
i have full root bro I use vroot method and it get's fully not reboots when I remount r/w, and I install busybox all correct!
but I still have this problem
EDIT: bro i solved the problem I install remountrebootfix now my xperia is fully deodexed thanks

Related

[Q] Tab neutered.

Today when trying to update the busybox binaries it failed. Whereupon I lost root and wifi stopped working and I couldn't root the device again.
I did factory reset/wipe to no avail (wifi still dead and couldn't reroot). Then I restocked using odin doing wipe again. After the restock wifi worked again but now I'm not able to root the device (I'm using the root.zip method from recovery). Superuser can't update the su binary and neither can SuperSU.
Any help with this dilemma (getting root back) would be appreciated. Thanks.
First uninstall the update of version 3.0 of superusers. In the handler for app not see more' the application but if you go in the menu you will notice it is still there, given that many ROM cook have a default. Then the total uninstall does not, you can do. Now download the package of the binaries and flash using Recovery http://www.mobilegeek.it/?dl_id=397 once finished initiated the device and download from the market the update to version 3.0 . Now open superuser /settings and select "Track on v3.0 " to update correctly the rails. If the process give you all the "OK" green vul say that everything is alright. If by some red writing reboot the device and try to reflash the rails ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CM File Manager access mode option unavailable

I have a Nexus 4, rooted, Franco kernel, and factory stock rom. Downloaded CyanogenMod mako build, extracted CM File Manager, installed the apk successfully, but am unable to access the advanced options in the settings menu - specifically access mode. Also tried reinstalling it by copying to /system/app, changing permissions rw -r -r, but the app's advanced options still remained inaccessible. When I first open up the app, SuperSU never prompts me to grant root access. I'm assuming it does that if I was able to change the access mode from safe to root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
Your devices must have all the command listed at https://github.com/CyanogenMod/android_packages_apps_CMFileManager/tree/cm-10.1(property shell_required_commands). Otherwise, you shouldn't be able to access root functionality.
The link doesn't work, can you explain me what are the command required to enable the root mode? Thanks.
- sorry for my bad english -

Twrp + root for l190 blu life play mini

Root Blu life play mini like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download file from here:https://drive.google.com/file/d/0B9DmzLnUt5tuNzJyc3NNTHVXdUE/view?usp=sharing
unzip and find three more zip files, one is drivers. I don't know which ones did the magic cause I was screwing around for days so just install em all like I did.
Then install and run Vroot with USB debugging enabled....That'll get you root.
Then run the beautiful twrp magic installer I found somewhere else, you'll be warned about potentially losing your IMEI due to space issues, if concerned, back up with mobileuncle tools first. I didn't lose my IMEI though.
after TWRP installs, install supersu from the app store and update the su binary through recovery when prompted or using the supersu update zip through recovery (not included) and you're all done.
Thanks to everyone who originally made these files, I can take no credit. but u can jock me for spoon feeding you if you want
Will this root method work on life play mini L180b?

insert an sd card before using the camera

Hello Guys
I have this Moto G xt1032 (version whitout sdcard slot)
I used this cm-14.1-20161225-NIGHTLY-falcon.zip and open_gapps-arm-7.1-pico-20170928.zip
I got this message when I tried to use the camera:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My guess is the mount point do not worked fine
So I made a ssh connection:
$: df
$: Vim /fstab.qcom
I tried other snapshots from lineageOS and CyanogenMod but the error is the same
I know some versions of this phone has sdcard slot, but mine don’t.
You guys have any clue to solve this? Thank you
I discover that /storage/emulated/0 or /sdcard has no DCIM folder, so I tried to create with no sucess this fodler, i got no permissions, even root on Terminal.
so I boot on TWRP and create folder there, sucess, but when android boots again I cant write any files there
falcon:/storage/emulated/0/DCIM # chmod 7777 /storage/emulated/0/DCIM -R
falcon:/storage/emulated/0/DCIM # touch 34
touch: '34': Permission denied
Solved!
Hi man, I had the same, the problem was I did format internal storage with that every folder was deleted, but I fixed, how come?
Install de rom stock and this fixed the folders problem and then you could flash your favorite rom

Can't give SU permissions to ADB

Before anything, I'm pretty bad with all these stuff, so if I'm doing a stupid mistake sorry about that
I was trying to install Island (by Oasisfeng) on my rooted Galaxy S7 (stock) as I needed something to replicate Secure Folder. My device has root access, and has Magisk Manager installed. However, apparently Samsung won't let me install it due to having custom OS (which is just TWRP I believe)
So, the setup guide for Island says I could manually install it like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADB recognizes my device, however, I get an error while trying to create a user as well as trying to change the limit. I've looked up for a while, and found out that my ADB doesn't have root access, as I get "Permission denied" if I type "su". In addition, my command line shows a $ instead of #.
Now, I've also gone through forums to find a reason why this is the case. Obviously my USB debugging is enabled, I have rooted my phone, and in my Magisk Manager settings Superuser Access is set to "Apps and ADB", which I thought would be the fix for this but apparently not.
Am I missing a step or trying to do something meaningless?
Thanks in advance.

Categories

Resources