Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
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
So today (10/06/14) I checked on my Nexus 5 (Rooted) for any software updates and low and behold, there it was, "4.4.3". So I click download (takes about 30 mins) and when it's done it says it will reboot and install. Great, sounds perfect. So I click the button and it begins a countdown. The phone shuts off and then the problem occurred.
When the phone turned back on, there appeared an android, with a loading bar. It then states whether I want to install untrusted software, which was called ClockworkMod. Now this isn't a virus or anything, it's from an app called ROM Manager. So I click yes and it shows another screen. Sadly my memory is useless and I forgot what this said or if I clicked Yes or No. It then went to a screen (after whatever I did) and said this may flash my ROM and cannot be undone. This scared me so my human instincts kicked in and I clicked Go back.
After I clicked go back the phone turned off once again and began like normal. Great! But then when it turned on again, I went to the Settings, looked at the version number and it was 4.4.2. Fantastic! I went on to check for system updates once again but it says my phone is up to date.
So what has happened? If you could please help, that would be great.
Here is some information that may be useful:
- I am using a Rooted Nexus 5 (Unlocked, obviously)
- I have a custom Kernel (Franco Kernel)
- I live in the UK
- I'm not particularly good at art
Thanks in advance, Peter
As an introduction: When it comes to mobile platforms I'm more or less as green as they come - so forgive my ignorance regarding... Everything
I recently misplaced my beloved Nexus 4's flipcase. The day it went missing, I managed to stumble and drop my phone a distance onto tiles . It landed at such an awkward angle that the screen not only cracked but pretty much shattered - killing what I believe is known as the digitizer with it. It won't respond to touch.
Distraught I took up my dad's old Galaxy S3 - which was only cracked and a bit eaten (puppies). I went straight into using it and due to a demanding schedule I didn't have time to recover any of the data of the N4 - which I don't know how to do anyway. I quickly learn that I hate Touchwiz and the lack of personal details wakens me to how reliant I am on my phone.
So I set aside some time to get root - load a custom ROM (pa) - and transfer all my data from the N4 to the S3. The first difficulties appear when the S3 rejects towelroot. I install the towelroot apk from the official website and run it. Towelroot tells me it's currently an unsupported device. I google the model number (i9300) and apparently it works with Towelroot. Weird - I guess I'll do it manually.
So I install odin and download what I need and get the drivers for the S3 working and get root. It works without a hitch (I think until later ). Next I look into how to get a ROM on my phone. This happens: http://forum.xda-developers.com/par...s-7-error-installing-pa-t2844044/post54744770 (that's my post btw so it's the exact scenario). I will say that while I was going through this issue I tried many things to try and get rid of the error - I played with CWM a lot - tried to update it - updating failed with unknown errors. - I tried to flash my recovery - it couldn't flash my recovery. Earlier I had tried to install the CWM recovery on it's own from the play store (again - total noob) I only got related versions of CWM from 2011-2012. All of these problems were pretty confusing - and eventually due to the generic error about not being able to flash my recovery I had no idea how to proceed so I did as advised in the thread above and installed Flashify.
Flashify told me I had root, but that it couldn't get access to SuperSU - and to delete SuperSUs memory of Flashify. I went to SuperSU and SuperSU told me that it needed to update my binaries (I don't even know what my binaries are?!). I tell it it can go ahead and it just says "installation failed" so I install SuperUser to try and replace SuperSU - and delete SuperSU. And Flashify is clinging to the remains of SuperSU. Between my odd model identification (TowelRoot - Status 7 error) and my devices seeming lack of compatibility with.. Anything really (I imagine the two are related). I decide to clean slate it with a factory reset. Which I do from the CWM BIOS (?? Volume up + Home + Power?).
So of course unlike any phone I've ever worked with - a factory reset now means wipe my SIM. (Okay that was laziness and stupidity I should have taken it out first but allow me to grieve). As I should have predicted but didn't it wiped all my backups (foolishly saved onto the internal SD card) and leaves me in the fetal position on the ground making howling noises shedding tears onto the floor.
I can't afford a new phone - or to repair my old one. I need the data off my N4 - who's touchscreen doesn't work - which is problem number 1. And I would really rather not live with touchwiz, or have to do half the process again when I otherwise find the time to get rid of it, so I want to do that now but there are so many errors and I have no idea what I'm dealing with - which is problem number 2.
So please, if anyone can help me out with a)Getting the data off my N4 (it is properly set up as a mass media device) and b)Fixing this seemingly banjaxed S3 and getting pa onto it.
Any help would be really gratefully received. It's been an awful weekend - I also lost a hard drive with all my work and a lot of personal data on it to natural causes.
Thanks - I eagerly await my knight in shining armor.
Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.
[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?