Hey guys, I just got a Focus i917R, and after updating through Zune, it seems like my keyboard isn't keeping up with my typing. The keyboard doesn't miss anything I'm typing either, it just takes forever to catch up with me.
For example, I'll type "Hi how are you doing today?"
And by the time I'm done, I'm watching the keyboard type by itself at "you doing today?"
Any idea how to fix this? It's kind of annoying.
ShensMobile said:
Hey guys, I just got a Focus i917R, and after updating through Zune, it seems like my keyboard isn't keeping up with my typing. The keyboard doesn't miss anything I'm typing either, it just takes forever to catch up with me.
For example, I'll type "Hi how are you doing today?"
And by the time I'm done, I'm watching the keyboard type by itself at "you doing today?"
Any idea how to fix this? It's kind of annoying.
Click to expand...
Click to collapse
What version do you have, 8107?
Yes, 8107. The problem gets better when I disable keyboard press sounds.
ShensMobile said:
Yes, 8107. The problem gets better when I disable keyboard press sounds.
Click to expand...
Click to collapse
You need to read this and this. Not a fix, but at least gives you an idea: it's because of the "Samsung update" from AT&T, so you'll need to restore.
Well that's ridiculous, why would Zune install an AT&T update onto my Rogers phone?
Is there a guide on restoring to an earlier update? What will I lose by not having this update? I don't want to go pre-mango.
ShensMobile said:
Well that's ridiculous, why would Zune install an AT&T update onto my Rogers phone?
Is there a guide on restoring to an earlier update? What will I lose by not having this update? I don't want to go pre-mango.
Click to expand...
Click to collapse
The point I was trying to make is that the updates released from the carrier (in those cases AT&T, in your case Rogers) affected the phone's performance. The specific update we are talking about is NOT any of the WP7 OS updates but the "Samsung update".
For restoring, sync first in Zune. Then, when connected, go to Settings (top) and then click Update (left). I should say "your phone is up to date" and in the lower part of the screen you should have a "Restore" option.
Alright, thank you for clearing that up.
As for restoring, won't that just restore my phone to the same 8107 update? Or does restore downgrade me somehow?
ShensMobile said:
Alright, thank you for clearing that up.
As for restoring, won't that just restore my phone to the same 8107 update? Or does restore downgrade me somehow?
Click to expand...
Click to collapse
Restore is downgrade to the version you had just before the update, which in your case it's probably 7740. After that, you can try to update again and see if the update is good this time? Sometimes the update is "upgraded" (updated for compatibility, stability etc).
A backup is performed by Zune, for your phone, each time you update, exactly so you can restore in case something goes wrong.
Well, ****, I just restored my computer and no longer have the backups. I guess I can't use restore... Is there any way I can flash an older version on, like on Android phones? Or am I just stuck waiting until a new update comes out?
ShensMobile said:
Well, ****, I just restored my computer and no longer have the backups. I guess I can't use restore... Is there any way I can flash an older version on, like on Android phones? Or am I just stuck waiting until a new update comes out?
Click to expand...
Click to collapse
You can downgrade and then go through the whole update process again. See point 1 in this thread.
However, I suggest that before you do the downgrade, first you:
- sync all your files in the phone so you can restore later
- make a list of all the apps you have installed
- save all your important SMS, read here
- you read how to make a backup and make one (see point 0 in the noob thread)
Alternately, you can consider a custom ROM. See this post.
Related
Hi,
I was running 7712 and tried to restore a NoDo Restore Point I had. It failed. Now, it shows the samsung screen and eventually gets to the connect to PC screen but it doesnt fully bootup anymore. It can still connect to my PC and retries using the restore point but never works. Help is MUCH appreciated. Thanks
wilcoholic5 said:
Hi,
I was running 7712 and tried to restore a NoDo Restore Point I had. It failed. Now, it shows the samsung screen and eventually gets to the connect to PC screen but it doesnt fully bootup anymore. It can still connect to my PC and retries using the restore point but never works. Help is MUCH appreciated. Thanks
Click to expand...
Click to collapse
Had this problem too, and didn't manage to restore.
I suppose it happened because I filled more than half of the available capacity (or so I think).
I even tried downgrading to 7004 and retry the backup then, that didn't work either.
You can try that, if that doesn't work... you'd be out of luck, like I was.
Try again and again different scenarios, be imaginative, maybe you can find a solution that works in your case.
I tried flashing 7004 to it with the WP7 USB Image tool and that did not work either. I keep getting an error..something about the phone not matching? The error descriptions cuts off and I cant see all of it..and I did use the correct one for my hardware rev. Help?
wilcoholic5 said:
I tried flashing 7004 to it with the WP7 USB Image tool and that did not work either. I keep getting an error..something about the phone not matching? The error descriptions cuts off and I cant see all of it..and I did use the correct one for my hardware rev. Help?
Click to expand...
Click to collapse
Can you detail a bit more about your phone?
Revision (1.3/1.4), card installed (type/size)
When the error started to appear etc. Anything you think might be useful/relevant.
I have hardware rev 1.3. I do not have any SD card in my phone at the moment, nor have I ever. I can get to the download menu and restoration menu in zune, but it all fails. I think what messed things up was I tried to format while on 7712 to try to get back to factory default. This took me to a "new" 7712 with the default settings. I even tried formatting by holding PWR + Vol DWN + camera to no avail. When i was stuck with 7712, I tried to use my restore point to get back to NoDo. Thats when it all came crashing down. I think I need to wait until newer roms become available. Help?
wilcoholic5 said:
I have hardware rev 1.3. I do not have any SD card in my phone at the moment, nor have I ever. I can get to the download menu and restoration menu in zune, but it all fails. I think what messed things up was I tried to format while on 7712 to try to get back to factory default. This took me to a "new" 7712 with the default settings. I even tried formatting by holding PWR + Vol DWN + camera to no avail. When i was stuck with 7712, I tried to use my restore point to get back to NoDo. Thats when it all came crashing down. I think I need to wait until newer roms become available. Help?
Click to expand...
Click to collapse
Not being able to hard reset suggests some kind of problem, which either points to the hardware or the flash. Let's leave the hw for now, so you can easily assume it's a flashing problem.
I would go with a 7004 ROM and start from scratch. If everything works well, you might be able to use your restore.
However, if something's really wrong with your phone, flashing might actually do more damage and possibly brick your phone. Not to scare you, but to make you aware of alternatives.
I have already tried flashing with the 7004 rom and it did not work. I kept getting an error about the devices not matching. I am thinking that I need to flash with at least a 7712 rom, since it seems that is now the phones default version. weird.
Bump. I think that if i were to have a restore point that was 7712 or above, I can get the phone back in operating condition. I'd be willing to pay if anyone is interested. However, it has to have no windows live account attached to it. I.E. restore, and skip entering in account info.
samfirmware.com has couple firmware for Focus. If you can get your phone into download mode (connect to PC screen), you can flash the firmware to it. Not sure which tool to use (ODIN or else) for flashing firmware. Check the dev forum for help.
Thanks for the reply. I checked out samfirmware.com and didnt see any specifically for the focus..any chance i can get a link to them?
Edit: Nevermind, I found them. Ill try them out.
I tried flashing with the roms on samfirmware.com, I got the same results with those roms as the ones posted in the forums here. I assume I need at least a 7712 rom to flash to, as my phone has essentially "forgotten" that anything before that exists and doesnt know how to go back to it. I can still use a fresh restore point from 7712 or beyond please. I am stuck using some horrible old phone while i fix this lol.
Edit: Grammar
Happy to report that after various configurations of my process, I finally got it work. I used the roms that are up on these forums. If anyone has the same issue i had here... try different computers. try different cables. try different ports. That's how I got it to work. Thanks to those that gave me suggestions.
I sense that when official Mango finally hits, we will see a lot ppl hitting the same issue as you because you must roll back to NoDo firmware before you can apply official Mango updates if you're on 7712 Mango beta, IIRC.
foxbat121 said:
I sense that when official Mango finally hits, we will see a lot ppl hitting the same issue as you because you must roll back to NoDo firmware before you can apply official Mango updates if you're on 7712 Mango beta, IIRC.
Click to expand...
Click to collapse
If I read this (http://forum.xda-developers.com/showthread.php?t=1215501) correctly, you should be able to start with 7712... just jump to step 16 as indicated by step 5a.
schahr01 said:
If I read this (http://forum.xda-developers.com/showthread.php?t=1215501) correctly, you should be able to start with 7712... just jump to step 16 as indicated by step 5a.
Click to expand...
Click to collapse
I'm not so sure about that. Just ask those who walshed their Focuse try to get to NoDo faster(which is actually also from Microsoft). There are likely firmware updates accompanied by the official release for Focus. Anything that's not running official NoDo updates will probably have a tough time getting that official update, or anything after that.
Just started to have a strange keyboard issue start.
I am using the stock Android Keyboard and whenever I click on anywhere to type anything the keyboard pops up fine but no keyboard input works. I can click on any key but no text is generated and the blinking cursor doesn't move.
A reboot solves the problem for a while but not for long.
This has only started happening since the last 3.2.1 update but am not sure it's connected.
Anyone else having this happen or have any thoughts.
I should also add that I have cleaned the screen well so a dirty screen is not the cause.
Thanks
spud357c said:
Just started to have a strange keyboard issue start.
I am using the stock Android Keyboard and whenever I click on anywhere to type anything the keyboard pops up fine but no keyboard input works. I can click on any key but no text is generated and the blinking cursor doesn't move.
A reboot solves the problem for a while but not for long.
This has only started happening since the last 3.2.1 update but am not sure it's connected.
Anyone else having this happen or have any thoughts.
I should also add that I have cleaned the screen well so a dirty screen is not the cause.
Thanks
Click to expand...
Click to collapse
Saw the same behavior problem on one ACER a500. We reloaded 3.2.1 clean and the problem went away. Not sure if it was an application, the update, sun & moon alignment or what.
After a clean install it never happened again.
TD
Thanks. I'm new to android so can you please tell me how to do the fresh install?
spud357c said:
Thanks. I'm new to android so can you please tell me how to do the fresh install?
Click to expand...
Click to collapse
Download it here: http://www.multiupload.com/NS0X5TK4D1
Read the pdf inside
Thanks timmyDean, process doesn't look all the complicated but I do have one question.
It refers to the install as being a "root" - if I do this do I lose the opportunity to get the ICS update should Acer ever release it. I recall reading that OTA updates aren't available to rooted tablets.
Thanks
spud357c said:
Thanks timmyDean, process doesn't look all the complicated but I do have one question.
It refers to the install as being a "root" - if I do this do I lose the opportunity to get the ICS update should Acer ever release it. I recall reading that OTA updates aren't available to rooted tablets.
Thanks
Click to expand...
Click to collapse
No. Rooting doesn't break OTA's, and you will still get OTA's.
Most people root and then install CWM which stops OTA or install a custom ROM which would stop OTA's. This root will NOT stop OTA's
Hope this helps
It sure does help, and thanks for explaining so clearly.
I really appreciate the help.
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice
This guide is for use on rooted stock roms to restore the phone to a position where it will accept OTA updates.
Please note the following:
1. It does not wipe the /data/ partition of your device.
2. It will reinstall any bloat you have uninstalled including those apps that you carrier put into /data/
3. It will remove any files you have added to /system/ including root or other modifications
4. Any files you have "frozen" will stay disabled, you cannot unfreeze them without rooting again - this guide will be for a "full unroot" so there is an optional step below to unfreeze apps.
The Guide
1. Download LG PC Suite from LG's website - you must select model type before you do so, but as far as I can tell it downloads the same version regardless.
2. Update the app so it recognises the G3 - this should ask you to update automatically on opening the app, if not you can do it from the "help" menu.
(NB: if you have used some of the KDZ flashing methods on here you may have issues updating as your hosts file is probably altered to block the PC Suite gaining a connection).
3. Connect the phone via USB (the app allows for a wifi connection but this is very restrictive, you require a USB connection for this).
*OPTIONAL STEP* If you want to go back to a truly stock experience then unfreeze any apps you have frozen (I am unsure if having apps frozen will effect OTA installations, it should still work fine, in theory).
4. With the device connected go to the "phone" menu in PC Suite and select the option that says "Restore Upgrade Errors".
5. It will then scan your device, download the rom and begin flashing, this is all automatic without any further input from you, do not cancel it.
6. The phone will reboot when finished. You are now unrooted and unmodified and OTA's should work.
*OPTIONAL STEP* If you want to go back to 100% stock then its probably a good idea to factory reset your phone at this point - this will wipe your whole device (of course).
And there you have it, your quick(ish), painless method for being able to unroot to accept OTA's without requiring a wipe.
Nice thanks Lenny, that may be handy. I'm supposed to receive mine today from Amazon.de, will play around a lot with root / unroot
Strange. Every time I click on restore errors it hangs for 30 secs and then LGpcsuite exe stopped working message and it stops. Any ideas ? I'm using windows 7 64bit and all drivers installed, pc recognizes phone.
Tarzan- said:
Strange. Every time I click on restore errors it hangs for 30 secs and then LGpcsuite exe stopped working message and it stops. Any ideas ? I'm using windows 7 64bit and all drivers installed, pc recognizes phone.
Click to expand...
Click to collapse
Could be a conflict with something else - to get it working for me I had to delete all traces of LG from the pc - all LG apps, drivers (including using USBDeview) and start over.
First of all, thank you for your detailed tutorial. Yesterday I have had the same idea... can someone confirm this theory... though there is no update for international version yet, someone with the korean model?
medicus07 said:
First of all, thank you for your detailed tutorial. Yesterday I have had the same idea... can someone confirm this theory... though there is no update for international version yet, someone with the korean model?
Click to expand...
Click to collapse
I tested this theory yesterday, albeit without an OTA - it does replace all modified and removed files in /system/ as well as removing any files you have added such as root or xposed.
There is no reason for the phone to continue to report that it has been modified, certainly if you take my final optional step and couple this restore with a factory reset.
Gotta love it when manufacturers make it simple to go back to 100% stock without any real messing around. Thanks for this :good:
Lennyuk said:
I tested this theory yesterday, albeit without an OTA - it does replace all modified and removed files in /system/ as well as removing any files you have added such as root or xposed.
There is no reason for the phone to continue to report that it has been modified, certainly if you take my final optional step and couple this restore with a factory reset.
Click to expand...
Click to collapse
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Tarzan- said:
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Click to expand...
Click to collapse
fixing errors is a reflash to fix a problem, it shouldn't matter what version your on, are you sure you didn't click the check for updates button by error?
Tarzan- said:
Ok I fixed my issue, PC suite crashing by running it as admin on windows. When I run to "fix errors" it says I'm running latest version. When I check OTA on my phone there is an update which obviously don't run after download because I'm rooted. I'm out of ideas
Click to expand...
Click to collapse
You should't have root access after using the fix upgrade function...
medicus07 said:
You should't have root access after using the fix upgrade function...
Click to expand...
Click to collapse
No, before fix upgrade. Actually I never get to download the firmware.
Lennyuk said:
fixing errors is a reflash to fix a problem, it shouldn't matter what version your on, are you sure you didn't click the check for updates button by error?
Click to expand...
Click to collapse
As I said I never get this option. It keeps on saying you have the latest version and that is it.
Tarzan- said:
No, before fix upgrade. Actually I never get to download the firmware.
As I said I never get this option. It keeps on saying you have the latest version and that is it.
Click to expand...
Click to collapse
Can you screenshot the "phone" menu you are seeing on LG PC Suite and upload it here?
Lennyuk said:
Can you screenshot the "phone" menu you are seeing on LG PC Suite and upload it here?
Click to expand...
Click to collapse
Attached both, before running and after running.
Tarzan- said:
Attached both, before running and after running.
Click to expand...
Click to collapse
The latter screenshot, did it give you that message after "scanning the device"? It might be that it scanned your device, found nothing altered so then said you were ok?
Perfect
Lenny thx alot. I was waiting for that. Because I wanted to make sure I can have OTA and root.
great :highfive::good:
Lennyuk said:
The latter screenshot, did it give you that message after "scanning the device"? It might be that it scanned your device, found nothing altered so then said you were ok?
Click to expand...
Click to collapse
See update available and I'm rooted.
Sent from G3
Tarzan- said:
See update available and I'm rooted.
Sent from G3
Click to expand...
Click to collapse
What happens if you go "check for updates" from PC Suite?
Lennyuk said:
What happens if you go "check for updates" from PC Suite?
Click to expand...
Click to collapse
Same, You have the latest version.
Tarzan- said:
Same, You have the latest version.
Click to expand...
Click to collapse
Weird, no idea why it won't be working for you, I have only been able to test on the D855 and have had no such issues.
Hopefully someone else who has the FK versions can shed some light.
Thats the thing. If its the phone version's (using Korean version) issue then how come the PC Suite recognizes it ?
Sorry for the post first.... I am sure the answer is here somewhere and I am going to start reading up.
But if anyone happens to know the quick and easy answer.
My V20 was in a drawer after doing a nice job for a few years. But I pulled it out as a backup phone and got it a cheap MVNO sim on ATT towers.
Didn't think much of it - but apparently I haven't had it on ATT towers for some time and it found a OTA update. It has downloaded it I guess and says it will install it in 10 seconds... no options to quit or delay or nothing.
I am rooted, unlocked and flashed - honestly don't remember exactly where... but I'd guess in the AO Rom at 20H and TWRP.
BTW - Don't need to really update to anything as the use case is backup really. I need WiFi calling so flashing Lineage is out too.
Open to thoughts and ideas.
Thanks in advance.
AT&T has update towers specifically to do updates. They're are fast. Get within range and bam.
Disable the OTA update app or ask AT&T tech support to disable OTA updates on their end... they can.
Yep - thanks but they got me already. It won't complete the update because when they execute the script TWRP loads instead - which is nice. But if I reboot - it stays live for 20 seconds and says rebooting to complete update, to twrp boot, to shutdown to reboot - stays live for 20 seconds and says rebooting....
Not exactly a handy backup phone...
Any ideas how to get out of the boot loop.
Looking at all my old notes now - just gonna flash it again I think but can't remember where/what...
Anyway - thanks and my studying continues.
Oh and - I had no idea folks were pushing uphill on getting Android 12 on the V20. That would be amazing. Great phone to get this on.
What if you disable the updater while in TWRP using adb?
Arealhooman said:
What if you disable the updater while in TWRP using adb?
Click to expand...
Click to collapse
YES - exactly what I am trying to find out how to do?
I'm in TWRP now looking for the file that I presume it downloaded that it is trying to install. Presuming the OS looks for a file and when it is there it does the prompt - "Shutting down in 10 seconds to install update".
Found some notes and TWRP backups - so restored my backup of AlphaOmega.
Then - enabled developer options and disabled automatic updates from there
I think that is all I have to do.
wantpizza said:
Found some notes and TWRP backups - so restored my backup of AlphaOmega.
Then - enabled developer options and disabled automatic updates from there
I think that is all I have to do.
Click to expand...
Click to collapse
On Samsung's that won't do anything except not auto update when the phone restarts. OTA updates is still active and can hijack control of the phone. It has every permission under the sun, might as well be malware.
If the app is still running it's likely going to screw you up...
Yah - I wasn't satisfied either...
I installed Magisk and installed some root app uninstaller. Not exactly sure what I am looking for - but the only apk with OTA in it was something FOTA - so sounded Forced.... I uninstalled.
Heck - haven't customized much yet - figure it is time to try and break it...
We will see what happens.
wantpizza said:
Yah - I wasn't satisfied either...
I installed Magisk and installed some root app uninstaller. Not exactly sure what I am looking for - but the only apk with OTA in it was something FOTA - so sounded Forced.... I uninstalled.
Heck - haven't customized much yet - figure it is time to try and break it...
We will see what happens.
Click to expand...
Click to collapse
Does the update option appear in the settings menu still? If not you got it.
Look for apps with the word update in them
I did completely blow up the phone and biffed it while updating TWRP.
Posted here: https://forum.xda-developers.com/t/bad-day-kernel-panic-trying-to-update-twrp.4534615/
But I have it all back up and running. I didn't delete anything yet but it runs and isn't boot looped in the update cycle. I did disable updates inside developer options. But now I don't have any cell service where I am currently staying so I am probably going to put this aside for a while. Thanks all for the help.