Database Develop

[Q]Always booting into recovery, any ideas?

I don't know that I can be terribly specific as whatever I did, I did a long while ago when the touch pad was still new to android. I was running a rom that had an available update, so I selected the automatic update option. I didn't realize my recovery wouldn't handle whatever script it was running after it booted into recovery. Something got interrupted when it shouldn't have. Now anytime the device starts it automatically boots to recovery. I bypass this by holding the volume keys as it boots.
I have reset the device using webos doctor, but the problem persists.
Thanks in advance!
Edit: attached a photo of startup
{
"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 cm_tenderloin using xda premium

Sounds like it's set to boot into recovery all the time.
Get it loaded up in recovery, then using ADB, mount /boot and look in there. If there's a file called moboot.next, delete it. Also, type the following (without the quotes):
"echo CyanogenMod < moboot.default"
That should set your default to CyanogenMod (assuming you have that on your tablet)

[Q]CWM The system cannot find the path specified

I'm having a problem installing CWM on my unit
XPERIA SP C5302 running on stock .205 rooted with towelroot ( this is my first time rooting )
i have my phone connected to my PC with USB Debugging checked
and followed the steps on this thread
but whenever i run the install.bat file and choose the 1st option
i always end up with "The system cannot find the path specified
{
"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"
}
Help please~

help
someone help! im facing the same problem

Hi, go DOS mode in the directory where you extracted the archive .. there is an ADB directory. Steps in this directory the command: adb devices .. if you have an answer with number, then your phone is connected...

Problem is not with the device. It is with the recovery. Retry the download. Some file might be deleted by antivirus or something? Check it out. It can't find a file it is looking for.
PS: Press thanks if I helped you!

Check if you have the ADB directory .. Option 1 uses. Look Attachment

Problem with some Facebook leftovers

-------------------------

-------------------------

axl409 said:
Hello, I have recently installed the twrp recovery, but when I tried to do a backup it give me an error about a path that can't be read. That path refer to the Facebook folder in /data/data/facebook-katana.
There is one file ( 6-lxk7_g5koNUrLwO82eQTzq6_w.cnt ) that can't be deleted. I tried with several file manager, like solid explorer, es file manager and the file manager from rom toolbox. Same result from the picture that I will post in this thread.
Also tried to go in recovery and use the recovery built in file manager to delete that file, but same results. How can I solve?
Here's the pic.
{
"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"
}
Click to expand...
Click to collapse
Thinking off the top of my head, this may not work:
Download a terminal emulator from play store.
Enter the following commands, one after each other:
"su"
"cd data/data/facebook-katana"
"rm 6-lxk7_g5koNUrLwO82eQTzq6_w.cnt"
It may not work, but try it anyway!
Do post your results.
Sent from my XT1068 using XDA Free mobile app

-------------------------

Magisk download didn't root my phone

Hi !
I have recently decided to root my Samsung Galaxy s7 and followed a couple of tutorials on internet. But now I have a problem. I installed via twrp magisk 12.0 and Samsung antiroot removal and... my phone isn't root at the moment. I didn't had super su installed and hadn't any permission granted... someone could help me to solve my problem ? Thank you very much ! (I run 7.0)

Did you also install the Magisk Manager? You'll find a link to download it in the release thread.

Yes I did
But when I open it says that I have the last version but nothing else

Recovery log from the installation and a Magisk log, please. The recovery log you can save after flashing, go to Advanced - Copy log. The Magisk log you can find in /cache when you're in TWRP.
Attach the two files to your post.

Here
{
"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"
}

No... You haven't installed the Magisk Manager from the release thread. That's v5+ of the Manager and it doesn't work with Magisk v12. Uninstall and install the correct Manager.

Glase and Magisk

I want to use TAP & PAY with Glase. But every time it comes, no use because Root and customROM. I have one plus one with lineage-14.1-20180503 and magisk v 16.0. SafetyNet-Test true/true. Did somebody know whats happend?

Have you tried adding Glase to the (active) Magisk Hide list (tick it in the MH list), then hiding Magisk Manager with the appropriate function (you have to repackage it from the settings? What it will do is it will create a new APK file with a random package name but same icon, content and friendly name, install it and uninstall itself. An issue I noticed with this is that you have to repeat the procedure after every Manager (not SU binary) update, but it's not hard. Try and let me know if it worked
Edit: also remember to erase Glase cache, full-restart the device and - if needed - wipe Glase data

Anyone had any luck with this? Completely removed Glase, then proceeded to repackage Magisk, reinstalled Glase, selected it on Magisk Hide (while rebooting at every step) but it still recognizes the root :/
PS: on Oneplus 6.

This is Stock ROM on my S8+
{
"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 SM-G955F using Tapatalk