Database Develop

I can only download <3mb Apps . What can I do?

Hey guys. I am running [ROM]Super D 1.11 "Rehab is for Quitters" (4/28) and for some reason I cannot download any app that is >3mb .. I don't know why is it happening. I removed the update on the market, as some people have suggested but that didn't seem to fix the problem. Any ideas?

Are you using cmtd by chance?
Sent from my T-Mobile G2 using xda premium

Unzip the file in the attachment, then do**:
Code:
adb push 06BindCache /system/etc/init.d
chmod -R 777 /system/etc/init.d
reboot
It is Firerat's script from custom MTD boot patcher. It will bind /cache/download to /data/cache or /sd-ext(/system/sd)/cache if it is present.
**Note that init.d might be /system/init.d in some history roms

Thank you so much bro! It worked flawlessly !!!

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

[GUIDE/TOOL][ALL VARIANTS] SamsungTool - EFS backup tutorial

{
"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"
}
SamsungTool
Just a quick guide on how to backup your EFS partition for the N4 all variants.
My SamsungTool supports every device aslong as busybox is installed.
This means with busybox installed my tool will support every device regardless of if i update it, when new devices get released etc.
Without further a do.
Step 1. root your device(im not gonna explain in detail)
Step 2. install busybox - Stericsons Busybox installer
Step 3. open Stericsons Busybox installer and press install(after is installs you can unistall the app)
Step 4. install SamsungTool, open it and press backup - SamsungTool By Ricky Divjakovski​
Click to expand...
Click to collapse

Help: "closed" message when trying to use sdb

Hi everyone!
I'll go right to the issue, I'm trying to change the icons on a Samsung Gear 2 Neo following the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=2782669. So far I had to change the firmware so I could root it, fight with drivers, ROMs, Odin, and all that stuff, and finally could root it, but now that I run the command "sdb shell mount -o remount,rw /" I get the message "closed" and can't proceed. I tried changing firmware, resetting to factory, rerooting, everything to no avail. So I'd like to ask for your help to solve this issue. I'll leave a screencap of the command window 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"
}
Thanks in advance.

TROUBLE MOTO E5 (XT1944-3)

Hello everyone, I'm new here. Hope you take care of me.
People I have an issue with my phone the imei is reported and I'm trying to fix it. I have already rooted with magisk and now I'm doing this (
) but when I try to enable the DIAG port in my phone doesn't let do it... Just installing the drivers it should appear in device manager but don't, by the way I was trying to enabling it by ADB writing this
Spoiler: THIS CODE
Code:
adb devices
adb shell
su
setprop sys.usb.config diag,adb
but when I try the answer is other.
{
"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"
}
Does somebody knows what I have to do?
Thank you.
PD: Sorry if this is not the place where I have to put this post.

Bootloop after installing Busybox for Android NDK

After installing BusyBox for Android NDK, my device bootlooped. I tried several times, flashing Original ROM, flashing Magisk, then tried to install BusyBox. Without exception, I failed over 5 times.
When I used some one-step installers, I found the problem. It seemed that default path is /system/xbin , but my device has no such a directory. Then how can solve this problem? Or if there was something wrong I did?
Details of my device will be uploaded in some minutes. Thanks to everyone who might help me or focus my problems.

{
"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 directory like /system/xbin

If there's no xbin directory the busybox module installer reverts to using bin instead, so that shouldn't be the problem.
Logs?

Thanks, I see. Then how could it be bootlooping? If there is something wrong I did?

Easiest way to tell would be if you could provide logs (module install log, boot log when looping, etc). There's a link in my last post with some tips on how to collect logs.