Hi all,
I've got a new tablet with a broken battery. Everytime I power on the tablet and android was bootet the tabled is shutting down because of the critical charging level. This is something I cannot change because the battery is fully down. So with connected charger in recovery mode the tablet does not have any issues because of connected charger.
Now I have to disable the critical charge autoshutdown of android. Installed is android 4.2.2 and xposed framework would be my solution with activated disablecriticalbatteryshutdown module. BUT I am not able via booted android because of auto shutdown ... so I've googled some days and found a possibility to install framework via ADB. First I've installied the 2 apks via adb (xsposed framework and disablecriticalbatteryshutdown module). Then I've installed xposed via recovery mode and it rouns through successfully.
But how do I activate the installed module?
Kind regards,
Thomas
Try adding the APK's path to /data/data/de.robv.android.xposed.installer/conf/modules.list, for example:
Code:
/data/app/com.zst.xposed.disablecriticalbatteryshutdown-1.apk
Fully worked for me and finally my tablet is working fine with the defective battery. Thanks a lot!
Related
I have a Z here with broken screen/digitizer. ADB is not enabled, I want to enable through any means and then config it via vnc or similar with the long term goal of turning it into a headless mediaplayer(xbmc).
I am able to control it using the painstaking method of plugging in a usb kbd or mouse, doing some blind movements and then swapping that out for an mhl/hdmi cable so I can see where I am at.
With that I have been able to disable the lock screen, start terminal emulator, get into developer options and some other things.
The phone had previously been rooted and had adb enabled but my SO had updated it to stock OTA 10.4.B.0.569 (4.3)before The Drop without my knowing so I lost both of those.
So, the problem...I cannot enable adb. I can get into the developer menu but the options are greyed out. I cannot select anything. I don't know why. I suspected it was because there was a usb device plugged in (either mouse/kbd or screen) but I have checked a Z tablet running 4.2 and a Z1, which is running 4.4.2 and you can enable usb debugging with a device plugged in on both those. I tried toggling dev options off/on, but no difference. Annoying.
Because I have lost root I cannot enable it via terminal either.
I unlocked the bootloader and installed a custom recovery (Advance Stock Kernel with Recovery v11 (FW:*10.4.B.0.569}*) from this this thread, linked from [HOW TO] Root 10.4.B.0.569 [ONLY UNLOCKED BOOTLOADER]
In doing this the phone was reset to defaults, but it made no difference to the Dev Options being disabled. I can get into it, but most options are still greyed out, so still no adb
So now I am stuck. With no screen, I have no idea what steps to take to flash the SuperSU zip file from recovery. This is where I need some help
I have no problem wiping the phone, installing custom roms etc. but I need to get root and adb working somehow.
Is there any reason why USB debugging, amongst others, in Developer Options might be disabled?
Possibly a permissions problem? Fixable without root?
Could someone running the same recovery possibly detail the steps needed using the hardware buttons (up, up, power, down, power, etc) to flash supersu so I can get root?
Assume blank external sdcard with only that zip on it
Could someone recommend a custom rom that is safe to install on that software version that has root and maybe adb enabled?
Would it be possible to flash that from fastboot?
afaik, only stock/signed roms can be installed that way?
If I got adb working, could I sideload a rom/zip from that recovery or another non-touch recovery(swipe to proceed is definately out)?
Does anyone have any suggestions, ideas or alternative methods to attempt, in order to get control over the device?
thanks in advance to anyone that can help!
Hi everyone!
My nexus 6 got a problem today. After a reboot without plugin, it's won't charge when I connect a cable, won't connect to PC (my cable still work fine), nothing happen, no bolt on battery icon. I turn it off then plugin and it start charging, I turn it on again (with plugin) and everything work fine, but this problem happen again when I take a reboot (without pluggin).
I try both stock 6.0.1 (mob30d) and n beta 2 (npc91k) via fastboot but it still happen.
Can anyone help me? Thanks for reading.
Did you try to roll back to stock using Google's original *.tgz image ? Only then can you be sure that something is wrong.
Does the PC recognize your phone when it's fully booted up (enable USB Debugging in Developer's Options by tapping "build" option 7 times to enable Developer's Options)?
If your device is rooted and has TWRP, does your PC recognize your phone in TWRP mode?
Does it charge in TWRP mode (has a percentage with plus sign next to it indicating charging)?
Does it charge using a wall charger? using a different, known to be good microUSB charging cable?
HueyT said:
Did you try to roll back to stock using Google's original *.tgz image ? Only then can you be sure that something is wrong.
Does the PC recognize your phone when it's fully booted up (enable USB Debugging in Developer's Options by tapping "build" option 7 times to enable Developer's Options)?
If your device is rooted and has TWRP, does your PC recognize your phone in TWRP mode?
Does it charge in TWRP mode (has a percentage with plus sign next to it indicating charging)?
Does it charge using a wall charger? using a different, known to be good microUSB charging cable?
Click to expand...
Click to collapse
I use stock rom from Google's original tgz file, I dont use cooked rom or custom recovery or custom anything.
When it's happen I turn it off then plugin, my N6 start charging(battery icon show up). Turn it on again with plugin and everything work fine. It just happen when I reboot without plugin.
I dont have wireless charger so I cant try it.
muabaylentroi said:
I use stock rom from Google's original tgz file, I dont use cooked rom or custom recovery or custom anything.
When it's happen I turn it off then plugin, my N6 start charging(battery icon show up). Turn it on again with plugin and everything work fine. It just happen when I reboot without plugin.
I dont have wireless charger so I cant try it.
Click to expand...
Click to collapse
If still within 1 yr warranty, I'd exchange it. If not, try wireless charger ; buy local so u can return if doesn't work
this might be a pain and idk if you have done this yet but have you tried a factory reset?
This is a very strange issue that I have been struggling with for a few months now. I have two Motorola XT1572 (Moto X Style), both on official 7.0 Nougat (25.11.15) received via OTA. The bootloader is unlocked on both devices. After the Nougat update I verified that USB worked fine and installed Magisk 13.3 on both devices, by sideloading TWRP via USB while keeping the stock recovery. Magisk worked fine and I eventually updated to 14.0 via the Magisk app.
At some point I realized that both phones are not connecting via USB any more - neither on Win7/8, nor on Linux. They are not recognized at all - no toast message asking for "Charging" vs "MTP". I have tried different cables and computers and played around with the drivers until satisfied that this is not the cause.
Both devices are charging fine, even though they are not turbo charging anymore after the Nougat update. However, both devices are also NOT connecting via USB in ADB or Fastboot modes. Since both devices are affected in an identical fashion at the same time, a hardware issue is unlikely.
I don't know if this was caused by Magisk 13.3 or 14.0 , since I don't remember when I first encountered the issue (before or after the update).
To top it off, I removed Magisk on one of the devices vie the uninstall option in the Magisk app. I did it originally to receive the next OTA security update, which didn't work (obviously Magisk 13.3 has modified the boot partition). Now, on that phone root is gone, but the USB issue persists - no way to connect to anything. Since I have no TWRP and cannot connect via USB, I cannot get Magisk installed again and am stuck with an unrooted device...
Has anyone encountered something similar with Magisk 13.3 (or maybe 14.0)? Any ideas of how to solve the USB issue? If not, at least an idea how I can get Magisk installed again on the unrooted device (then I could flash TWRP, which would open up some additional options)? Thank you!
Try flashing TWRP via fastboot, I have the same problem and currently the only way for me to transfer files is TWRP sadly.
Edit: Just disable USB debugging actually, and I may be too late for this fix x)
I have tried flashing with USB debugging on and off. Both phones do not connect via Fastboot at all (nor via ADB).
help me please
can u patch my file google pixel
Hello guys,
Recently I bricked my Oneplus 2 by trying to flash a custom Kernel. That would all be no problem, however my PC doesn't recognize my phone. Tried multiple USB ports (multiple PCs) and got the official oneplus drivers installed, still no connection (tested on Windows and Linux) . That got me believing that my USB port was broken (charging still working), so I replaced the USB module however still not working. (Could it be the cable?)
The current state is that I can boot into recovery (TWRP) and fastboot, however trying to boot normally just shows me the android logo forever.
So well my questions are:
1. What could possible be broken at my phone, that the USB connection is not working. (It worked before)
2. Is there any way to push a rom towards my phone without using a USB connection? So without adb?
Thanks a lot in advance!
EDIT: It was the cable ... I think the data pin broke somehow ... and me stupid as a was replaced the USB module 2 times ... Well transferring CarbonOS right now and will flash real so so thread closed!
I bricked my device flashing magisk. So, I bought fastboot cable and restored it using KFHD_SRT_v1.3.5- 7.3.0: https://forum.xda-developers.com/showthread.php?t=1951254
After this I flashed custom ROM (lineage OS 13) that I was using before my device got bricked. I faced so unusual problems with USB connection and charging (described below). So, I restored stock firmware again but this didn't help at all....
Problem I faced after restoring tablet:
1) Usb connectivity and charging.
After connecting device to computer there is no reaction on computer or tablet (even no sound and charging!). Same with connecting to charger. Tablet is charging but the proccess is not displayed anywhere (even in battery options in settings), except increasing battery percentages in the status bar. If I connect device to computer or charger and will reboot it (tablet, not PC) it will be recognized and charging process will begin! BUT after disconnecting device it will show still connected to the PC or charger until next reboot...
2)Wakelock and battery draining.
So, the next issue is that device doesn't go to deep sleep and even sleep. I installed BetterBatteryStats to check the processes and wakelocks and found "usb3v3_wake_lock" in kernel wakelocks which prevents tablet to go into sleep mode. It's always in active mode, aproximately 98% of time, so battery draining really fast...
First of all, I thought that problems was caused by installing TWRP, but after restoring to stock had no sense. Even after restoring stock recovery and boot via KFHD_SRT_v1.3.5 it does't help. Also I've tried to flash diffrent Roms with different android OS versions (RR, lineage, AOSP). For now I am wondering what could cause described problems and would like to find solution