Hi all, originally this was to be a plea for help since I installed LBE Security only to have it lock up my device (AOKP 5.1 Preview ROM)
I failed to uninstall it via ADB (probably because I am an idiot rather than it being uninstallable) and I couldn't use my phone.
My phone would boot fine and operate normally until LBE started, as soon as that happened it froze and returned me to the lock screen. Lock screen would be unresponsive and crack (go black) and relaunch, This loop continued for a while before the phone would reboot to CWM. Attempts to uninstall via ADB were fruitless although that's probably because I am a muppet and was not doing it right!
HOWEVER I managed to fix it, so for anyone in a similar position try this.
Reboot Recovery
Fix Permissions
There, that was simple wasn't it! Don't know WHY I decided to try that but it had rebooted to recovery so I thought might as well try! Permissions has previously fixed a few spontations issues for me so this is a reminder to all. If you have a problem! Try fix permissions!
Anyway, this thread will most likely be buried deep into XDA never to be seen again but on the off chance it helps someone I'll post it here.
Cheers for being a great community XDA
Auzeras
Related
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
kratanuva said:
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
Click to expand...
Click to collapse
You are not the only one with that problem. I have the exact same issue. Process chewing up the CPU and if you kill it the process comes right back. Hopefully someone has a good answer as to how to fix it. I actually have 2 of the phones and one is rooted, second one is not. The unrooted phone does not have the same issue as the rooted phone.
I'm having the same problem with my Atrix. Phone is stock and unrooted. Never had an issue until I installed the latest update.
Well I got a response back from Motorola about the issue. These were their recommendations.
1. Reboot phone. Duh....
2. Uninstall any apps that you installed when the problem started. Uh, it was the OTA update... Cannot be uninstalled I do not think.
3. Clear Cache partition from Fastboot menu. That did not do anything.
4. Factory reset the phone. I hate doing that. Doubt it fixes anything but I will do it anyway.
I asked them about option 5 if 1-4 did nothing and he said call and talk to support.
Just an update...
Maybe someone knows how to just kill the process. It is obviously doing nothing as the phone is already updated to 4.5.145 according to the phone info.
I've just had a quick look around about the 'apply patch' process. Not that it helps you but this problem has been ongoing since at least android 1.6!!! Unfortunately solutions to the problem were few and far between - the main one would be to roll back the update you received (if you can).
Rooting and then trying to find the process and freezing the 'apply patch' process is another (again, I didn't find much about how to do that) as is unlocking the bootloader and putting installing a custom rom is another option for you. I know you don't feel comfy unlocking your bootloader but it isn't as bad as it sounds.
If you do decide to go the unlocking way then there are guides on here which will help you.
Edit: just seen this over in the 'general' section http://forum.xda-developers.com/showthread.php?t=2145316 ... the very same problem you are having.
Ok, just to hopefully keep this going I have tried these additional steps.
Root phone.
Unroot phone
Re-root phone
Try multiple startup program apps to kill it, none show anything besides installed apps.
None work. applypatch still taking 49% cpu
Maybe there is a way to edit androids startup config file to make it stop? Not a Linux/android guy so hopefully someone smarter than me has the answer to that.
If you've rooted the phone, you might as well have deleted or renamed that program... That's what I would do.
Same problem with my Atrix........I've been following this thread and have found a temp fix that works for me. I say temp as the applypatch process will show up again on reboot
1.) Gain Root Access
2.) Download OS Monitor from PlayStore (this will show you all processes running on Android OS)
3.) Run OS Monitor ...."applypatch" should be at the top of the list with a high Load % (Note: Under Settings enable ROOT mode)
4.) Long press on applypatch process and select kill process and allow superuser/root access...should terminate
This has been working for me so far so I signed up to share with you all.....hope it helps.
And heres to hoping for a more permanent:good: solution to this issue
Hi everybody thanks for your help in advance,
My SGs2 is currently running siyah kernel v6.0.0.12 (the fancy one with touch recovery and dual boot).
The problems started when i recently switched from SuperSu to the open-source alternative Superuser. I'm using an app called live logcat (by Chainfire). It shows the logcat entries live as a boot animation. It was all hassle free when I used SuperSu with it. After switching to Superuser it kept getting root permission over and over for at least a minute (a previously common problem). So I was looking forward to getting it fixed since other users reported the same problem. So whenever a new version came out, I tried if it was finally fixed.
After updating to the latest version yesterday and starting the app once again, the phone crashed with the screen turning black (status bar still visible). It then rebooted and a message stating
Android is upgrading..
Starting applications
Click to expand...
Click to collapse
appeared. Whenever I reboot my phone this message appears and won't go away. I can access recovery but clearing cache and/or dalvik cache makes the window say: Optimizing application <x> out of <y>. When it is through with optimizing, 'starting applications' reappears.
I honestly have no idea what else to do.
So my question is how can I get that darn thing to boot correctly?
I'm looking for a solution which doesn't involve factory reset.
If anybody can help he/she is much appreciated.
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
I ordered my Kyocera Hydro Icon from Freedompop and got it yesterday. I tried Root Genius, which seemed to work (by which I mean it asks me if I want to give root access to apps that need it, but does not allow user of the "su" command in Terminal Emulator). I then used a root app uninstaller and uninstalled a couple very harmless seeming things that the app said was safe to remove. Various forums said safe to remove. However, after doing that I'm now on a boot loop.
I did a factory reset from the boot menu (hold buttons, go to wipe data, etc.). However, my system still has the same issue and reboots unless I'm in Airplane mode (for the record, many people have reported this, and it's pretty obvious that some company triggers a reboot remotely when they don't like what they see on your phone, and that's why disconnecting prevents reboot). There were some Freedompop apps I uninstalled before, and they are still uninstalled after factory reset. I probably can't even return the phone because the KingoRoot app is installed and I can't remove it. I installed SuperSU, not sure exactly how it works, but it keeps telling me it wants to update and I can't go out of airplane mode to use the Internet.
So, after spending over 24 hours straight on this problem, frustrated the entire time, I found my way here. Though I was skeptical (having had much bad luck so far), I thought maybe a stock ROM would work. However, all links to any kind of ROM for this device on these forums were dead.
My understanding is the source was released for this device here:
tiny url .c om / ppbnlwo (used tinyurl to make it shorter so I could post it; goes to Kyocera Developer Support Downloads)
I'd like to know the following:
1) Will a ROM fix my device, removing Kinguser and all root-related changes I made?
2) Is there a ROM that someone can provide me with (along with instructions hopefully) to help me with this?
Thank you.
[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?