(my question lies offset below, incase the reader wants to skip my paragraph and use it as reference. I had to type it all to give background to where I am now)
I have a DROID2 from Verizon Wireless running Android 2.2.3 Froyo, and have owned it for ~a year. One Day in early 2011 things started going wrong, like vibrate wouldn't work on messages (sms and email, using GoSms), my stock battery manager that told me % usage since last charge would crash when clicked, gmail and calendar wouldn't sync. I talked to a friend, backed up my phone, and reset to factory settings. then, he said that rooting was amazing, so I broke down, rooted my phone, backed it up with Droid X bootstrap recovery, and thought it was great. then my phone started to continually boot in recovery mode, even after I removed root and bootstrap. it also ran strangely sometimes and would be slow, but I figured that was my impatience. so i decided one day to root my phone (using z4root), use a root explorer, search my system files for ANYTHING with "recovery" that to me looked like that stupid bootstrap placed (because i read somewhere it made a file and it stayed in my system) and deleted those files. now, I have new problems:
apps that I had a few days ago (8-16-2011) and have NOT updated won't work on my phone from the market. the market app does not give me the ability to download, and online it says its not compatible with my phone, which is bull crap because I downloaded AND used the apps the day before, but deleted and wanted them back. some apps include: facebook, Heywire (2.6.1), and Adobe Flash 10.3. I reset my phone to factory TWICE yesterday in attempt to fix. when the phone first loads, the OLD market is installed, which I used to download Heywire before the new update came, which then said the SAME VERSION of Heywire is not compatible. there are also a few minor errors I have, the stock email app picture doesn't show in status bar, it is very slow, etc. I am currently NOT rooted and NEVER flashed a Rom. My friend said that I could just replace some files and it should be fine. Also, I have issues when powering on my phone. when I turn it off, to turn it back on I must 1. turn on 2. wait for Motorola "M" screen to dim 3. remove battery 4. turn on and wait for boot up My question is:
1. How do I figure out all the files I need?
2. Where can I get these files?
3. Is there a way I can get root access and just copy paste ALL system files back to the phone as if it is fresh out of the box?
First, Lonnnng time reader/modder/hacker/technut, first time poster.
Secondly, my questions are: 1) Anyone else had such a positive experience as I did? And 2) Anyone else reproduce or trigger this ‘update’ in ICS?
Story below:
So I just purchased TF101 used, brought it home, and found out the long and hard way about the SOD/RR/DOCK/BATTERY/KERNEL issues that are plaguing a lot of users. So I researched for the past week (I'm a new owner), tried JB, ICS, etc, rom after rom. Still had same issues, and new ones (no wifi, sound, docking support gone, etc).
So, I went BACK to honeycomb 3.01 by flashing official update (WW version as I am in Canada) zip via CWM. I wiped cache, dalvik, data via CWM. Installed the zip. Tablet booted up perfectly. I did not sign into the google store. Turned tablet off completely WITHOUT being docked. Cold booted. Shut down. Used it for about 1.5 hrs, no reboots and could not repeat SOD/RR. However, HC is very slow compared to ICS. I then looked for the 3.2.1 update as it apparently makes the dock work correctly, and could never find it ANYWHERE (one rapidshare link and it was dead), all links were dead as the JP vers is the only one on Asus official site. 'check for updates' within the tablet did not work.
Next, I downloaded official xx.27 ICS off Asus website (around 253mB). Same procedure. wiped all cache/data/etc, flashed in CWM still (never put stock recovery as many recommended, didn't see the point). Booted tablet. Signed onto wifi, skipped signing in google account. Once in, turned off and cold booted back on. Used it for maybe 10 secs, and Asus updater pops up in task bar. The update had the same file-name of the update I just flashed however it had a July 27 date on it, and it was 302 mB (noticably larger than the 250~mB) update. NEVER saw this dialog before, even with my many attempts previously and all the different flashes/roms. Updater rebooted, installed itself (maybe 2 mins). I shut down completely once back in. Also, I still have not signed into my google account.
Following ICS update and shutdown, I then plugged my dock into wall outlet. I then finally docked (while off and for first time during entire process) the tablet, which then booted up. It immediately recognized the tablet, and made that ping sound confirming it was connected. Tablet booted up. I shut down, cold booted one last time. I then put it away on my shelf, lid closed. I opened this morning and 0 SOD or battery drain, which happened with EVERY SINGLE kernel/rom I tried for the past week. It would either SOD or RR. I left it open on 'about tablet' with uptime counter. It is still going. I checked various emails this morning, and ran some videos, etc, etc. Trying to reproduce RR/SOD. Usually it would occur within 10-15 mins of actually using it unit/being on wifi/etc/sleeping and waking.
I have a feeling that somehow Google is sending code (since you authorize OTA updates when you sign in) via being signed in that is somehow RR/SOD'ing (my theory), or there is some mysterious update I somehow triggered through this process. If anyone has reproduced this please let me know. But for now, this seems to fix battery drain at the very least, however I am running stock CPU clocks.
As i and many other are familiar with the RR/SOD troubles i have to say since i've updated with stock rooted .27 i haven't got the trouble anymore
Just checked and my transformer is still 86 % of battery capacity with an standby time of 1 day 18 hours
Before this update it almost always RR after using it when it was in standby mode again !
Ever since this update procedure my RR/SOD problems went down to near 0. I had one reboot in 3 long days of using my device, and that was from the stock browser. Which crashed before as well, anyways. I think this is a definite fix, which DOES NOT rely on external apps.
Not sure exactley how I triggered the update process. Please someone reproduce this 300~mB update that I triggered using CWM the entire update process!
Also, I have since extesively installed Google Play apps, and non-market sources. Not one crash, SOD, or RR. Dock work, charges excellent. Been using the unit for 2-3 days off and on with cbr viewer, movies n music playing, tonsof web browsing, etc. NO RR! NO SOD!
Hello everyone,
Around the black friday weekend, I have purchased a LG G Flex 2 LSS996 on a ebay store. It was unlocked and worked as advertised on 5.1.1.
I could never install any android or firmware updates, which didn't bother me until I also got the throttling/ overheating problem. That's when I noticed that the phone actually is rooted. I wish to upgrade my Android now, which is why I am thinking of unrooting the phone. I thought of ROMs as well, but I haven't found any and I don't have the time and knowledge for ROMs or Xposed Framework.
I'm not sure why or how this phone was rooted, but I fear it has something to do with the carrier unlock since it is a LSS996 for Sprint. Because I want to use this phone outside of the US, the phone would be unusable for me in case the phone gets the carrier lock again if I unroot. Would this be the case?
I'd be happy about any reply! Thanks!
EDIT: still looking through this forum.
Just found this: http://forum.xda-developers.com/g-flex2/help/managed-to-gsm-ls996-awaited-apn-t3090484
Meaning that the seller probably did the same thing right? Will unrooting lock the phone again? I'm not sure what exactly what unrooting does to the phone in regards to these files. I would unroot via SuperSU
Some other things worth mentioning:
- The "hands-free activation" (not sure what it's called in English, I use the phone in German), which starts on every phone start up, never finishes properly. I can let it run through its 5 cycles or press activate, either way it fails.
- When I press "activate this device" in the system settings, a black screen with "self service" on top opens and the immediately closes.
- When I want to update PRL, profile or firmware in system settings -> software updates, I always get an authentication error.
Other than that and the throttling/ overheating issue, the phone works just fine.
I also have the same device. The phone is rooted because someone modified system files to unlock it. You can flash an unrooted system image for your software version and update the phone, and you wont lose carrier unlock. The things you have mentioned are normal for such a device, since it is not unlocked by Sprint.
Thanks for the reply!
How do you suggest flashing? I'm not finished researching, but so far flash fire looks like the most convenient option.
Hello,
I wanted to share what I had to do in order to fix my phone after it took the July 27 OTA update. The update somehow corrupted my display and the white portions of the display were now pink and red. A google search has info and pics on this display problem so I won't elaborate on it. The first thing I tried was power cycling the phone, the red and pink remained. The next thing I tried was factory reset the device, that didn't work either. I simply wanted to revert back to the previous firmware and hopefully that would fix it. I liked the new firmware features, but that pink screen had to go! I foolishly flashed the US unlocked firmware (XAA) from SamMobile site with Odin. The pink screen probem was fixed but this definately was not the firmware that came on this phone. Gear VR didn't work, Samsung pay was borked, and there were all types of problems with the software.
At this point I called Samsung Tech Support. The guy was really nice and after a bit of explaining he offered to have the phone flashed at no cost to me. However I would have to send the phone in to be repaired and I would be without my device for a week at least, maybe 2 weeks. I thanked him and hung up. Why couldn't he simply make the firmware available to me so I could fix this without having to send it in and be without my phone for over a week. Not really a acceptable solution. I went online and did some reading. That's when I found the fix!
To anyone who is having problems and would simply like to get back to original factory firmware Samsung has a program called " Smart Switch ". It's available as a App for your phone or as a PC software program. The phone app helps sync devices, but the PC program can do much more. I'm not going to go over in detail how to use the software because a google search has videos and tutorials on how to use it. For me I was able to enter my phone model and serial number and Smart Switch went and downloaded the "correct factory firmware" and installed it to my phone. Now I have the latest firmware (7/27) full factory install and the pink / red display problem is gone. So what I'm getting at is if you are having problems after taking the OTA update like I did, you can try using Smart Switch and install the complete factory firmware from scratch to your device. Make sure to follow instruction on how to use the program, I had to put the phone into download mode for it to work for me. Also be sure you understand about "Google lock" before flashing your phone. This program claims it can un-brick a Samsung phone, and will also over-write a rooted phone to get it back to stock. I'm sure Smart Switch has been discussed before, but for a new Samsung user (like myself) it sure got me out of a bind!
I'm on stock rooted ROM 20H sep 2018. Last time I checked (just now) this is still the latest verion.
However my H910 keeps bugging me about new update available from AT&T.
Does that happen to you guys?
It didn't give me any info about versions and so on.
Should I proceed?
I got it too. Came here to see if it was just me. I'm on H910 Oreo stock rooted.
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running RootedStock, you'll end up in a slow semi-bootloop where Android boots, you'll have about 3-5 minutes, then it will forcibly install the update, reboot, you'll end up in TWRP, and when you reboot to system (or power off, then power up later), the whole cycle will repeat.
I'm not sure how robustly my solution worked, but here's how I broke out of it. So far, about 15 minutes after rebooting, it seems to have worked. Since I'm writing this AFTER seemingly fixing the problem, I'm writing it from memory, and can't say with 100% certainty which step was actually the one that fixed the problem for me. I actually began the process of installing Titanium backup about a half-dozen FOTA-reboot cycles before tripping over another post here that advised deleting /cache/FOTA. Titanium Backup might, or might not, be an essential element of my apparent success. I honestly don't know. If you own it, use it... you have nothing to lose. If you don't already own it, try just deleting /cache/FOTA first from TWRP's file manager and see whether it works (temporarily or permanently).
Anyway... here's the approximate path to slaying the FOTA beast:
1. I installed Titanium Backup from Google Play. It actually took two reboot cycles to do this... you REALLY have to be ready to unlock the phone, launch Google Play, search for Titanium, and trigger its installation while standing a few feet from your wifi AP for it to finish the download and begin installing it before the next forced-update attempt begins. When it does, swear violently. It'll make you feel a tiny bit better.
1b. When FOTA forces the reboot into TWRP, try deleting /cache/FOTA before rebooting. It might work to temporarily slay the FOTA beast, it might not. If it does, it'll save you about 30 minutes of FOTA-reboot misery for the remaining steps. Feel free to repeat this after each of the following steps. It can't hurt.
2. On the next cycle, launch Google Play the moment your phone finishes booting, and go back to Titanium Backup. Hopefully, it'll be installing. With a little luck, installation will finish before FOTA begins. Then sigh, and let FOTA waste another 5 minutes of your time.
3. On the next cycle, launch Ti backup, give it permanent root permission, and give it permission to do everything it wants. Then, try to launch Google Play, search for Titanium, scroll down, select Ti Backup pro key, and try to initiate installation before FOTA kicks in yet again.
4. On the next cycle, launch Google Play, search for Titanium, scroll down, select the pro key, and begin installation if it isn't already downloading and/or installing. 99% likely you'll end up going through another round of FOTA misery.
4b. If FOTA is still forcing reboots up to this point, repeat step 1b before step 5.
5. On the next cycle, launch Titanium Backup, give it any additional permissions it wants, then select Backup/Restore, scroll down to "FOTA Update 8.0.0", and freeze it.
5b. If FOTA kicks in again, repeat step 1b.
If, despite deleting /cache/FOTA, then freezing FOTA Update 8.0.0 using Ti backup, then deleting /cache/FOTA again, it's still happening... well, then my solution didn't work for you (and possibly not for me. I'll start breathing again normally if my phone is still working normally tomorrow).
Anyway, hopefully this will help someone. I suspect a lot of people running RootedStock Oreo are going to get stung by this. I'd guess that more than a few v20 owners actually bought theirs long after AT&T's previous forced update, and have never actually HAD to deal with blocking forced updates with their current ROM.
It's entirely possible that purchasing Ti backup (I don't think the free version can freeze apps) will be essential for the H910 going forward if you want to keep using what was, prior to yesterday, the newest rooted-stock Oreo ROM without having AT&T's FOTA harass you every few hours (or wipe your phone and reflash once someone releases a newer build based on the current update). Trust me, you can't swat it away forever. I went through this forced-update nagging bull**** years ago with my Motorola Photon. Someday, when you least expect it, the dialog will come flying at you when you're driving and trying to select a song using Amazon Music, or in the middle of a phone call, or semi-distracted, or scrolling down a web page while the phone is bogged down because it's grinding its wheels in the background preparing to harass you about updating again, and you WILL accidentally click "ok" & have your life go down the toilet for the next few hours until you're able to dig yourself out of the mess.
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
For those finding their way here, make sure to back up in the brief period of time before you get hamstrung if you can't freeze the process. I am/was bone stock H910 and after ATT forced the update on me, my phone now won't finish starting up and functionally boot-loops now until I pull the battery.
It will start, get to the home screen, I might get 5-15 seconds of actual usable time with the phone before it freezes, goes back to the bootscreen and will get warmer and warmer and give me less and less time until it freezes in the middle of the ATT logo. Tried pulling SD card and SIM card, just in case. The sim card removal bought me enough time to get the phone to tell me it was "finished updating" but upon attempting to power down and start re-inserting cards, the phone locked up and bootlooped.
No idea what this update is for but it seems to have killed my phone rather handily, beware.
FWIW, airplane mode does not stall the update either.
bitbang3r said:
Warning: DO NOT try to silence the nagging by blocking the notifications. AT&T/LG will treat "quit bothering me" like "go ahead, have your way", and simply go ahead and try to install the update without even bothering to ask you next time. If you're running Roote
Bite the bullet, and freeze FOTA Update 8.0.0 now, while you can still do it without burning an hour of your life waiting for reboot after reboot.
Click to expand...
Click to collapse
Hope I'm not jinxing myself, but this appears to have worked for me.
I have gotten a "update could not be installed" popup, which I'm taking to be a good sign.
Still annoying, since I have auto-updates turned off.
Ugh, it popped up again. Confirmed, FOTA is still frozen.
It initiated the update for me on its own. Luckily I noticed and plugged it in or it would have died and maybe bricked the phone.
I don't notice a difference. Same Android version (8.0) same security patch (Sept 2018). The ATT version might have gone from H to I.
Yep, it started nagging me again, too. Goddamn it, this is really starting to piss me off.
Okay, on mine I think when I delete /cache/FOTA while in TWRP, it might not actually be deleting the folder.
I deleted the folder in recovery mode, then rebooted and went straight to X-plore file manager. The FOTA folder was either still there, or it just recreated itself on boot. I deleted it again in X-plore and it's now been working since my previous post.
Fingers crossed.
I just rooted a H910 yesterday, and this morning the same "slow boot loop" with the update started. I tried different things, and what so far seems to have worked was:
1. Entered TWRP recovery (from the last "update cycle." (Not like I had a choice.)
2. Wiped everything and re-installed Oreo, and all other zip and img files back to the way I originally set it all up.
3. After phone was booted up, I DID NOT have a SIM card in it, nor did I enable WiFi.
4. Temporarily skipped all the Google sign in stuff.
5. Enabled Developer options, and turned off "automatic system updates." (Not Google Play Updates!)
6. Re-booted phone and then confirmed that the above setting still showed "off."
7. Enabled WiFi and connected.
8. Set up Google account and other misc settings.
9. Restored a backup that I had made prior to the phone doing the update reboot loop, but was careful to uncheck settings. I did not use Titanium Backup. I used the built in one.
NOTE: This is not my daily driver phone. It is meant to be used as an emergency backup phone in the event that my regular phone (Samsung Galaxy S Series) falls in a canal or gets run over by a truck. (Or City Bus)
So far so good. I will use the phone for the day and check again the following morning to see if it starts the forced update. I will check back here in a few days and let everyone know what the end result was.
My theory is that if the phone does not have a chance via cell data or WiFi to get any FOTA updates prior to me turning off the "automatic system updates" that is in the Developer Options, it will never check in with AT&T's update server.
I am not sure about this, and if someone else knows, please correct the following:
I don't think AT&T "pushes" updates out. At least the type of updates we are talking about. I believe the software in the phone periodically polls an AT&T update server, and "pulls" any update at a schedule time, or time interval. My working theory is that turning off the automatic system updates will disable this automatic check, or polling routine. If it already has an update that it downloaded prior to turning off automatic system updates, its too late.
Thanks for everyone's input on this in advance.