I've got a rooted (Super User) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box, Super SU, and a couple others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home in on time. Please help! I'm open to suggestions.......
Did you do a Nandroid backup? If not, I would try reinstalling whatever ROM your running, see if that helps.
Why did you want to move the apps in the first place? Did they not install/run properly? I'm not certain but I believe that some apps prefer/require running from system, others from the SDcard. I don't think you can just assume that all apps should be moved to your card. Normally, wherever they install to, is where they are supposed to remain.
I can't even........
My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts into that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it had a what the exact numbers were but I want to say it was 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.
Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob
Resolved!
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:
1. Download & install the Galaxy Nexus Toolkit and MyPhoneExplorer to your PC
2. Goto the Google Play Store on your PC and remote install MyPhoneExplorer and AF Rescue 2 apps to your phone. Wait 10 minutes or more so that this step has time to complete before continuing (longer is better)
3. Next you have to boot your phone into Recovery mode... pull the battery and usb cable out (so you can be sure your device is off). Put the battery back in, plug in the usb cable (I do this now so I can hear when the device is connected and later so you can hear that the command/reboots are working). hold down both vol up and vol down AND then hold down the power button... I do this for about 10 seconds. After releasing the buttons, your phone should be in bootloader mode, but I give it a minute just in case. now hit the vol up button 2 times then the power button. You will hear the usb connection go on and off several times and when it's done, your device will be in Recovery mode.
4. Launch the Toolkit, answer "no" to the initial question about checking for updates, then choose your device from the list
5. on the next screen (main menu) you should see your device ID listed under ADB mode list with the word "recovery" after it. If so, you have done everything correct so far. (if not, close the toolkit window, go back to step 3 and try again).
6. Next choose option 2 for Backup/Restore. Then select option 3 for "Backup your Internal Storage"
7. This is crucial. On the next screen choose option 2 "manually answer the question". Then when it asks if you are using a custom rom or recovery image, ANSWER "NO" (even if you are). This is the most important step in the whole process because it will then boot your phone into fastboot for you and install an insecure recovery image bypassing the 4.2.2 security!
8. When it tells you that the backup will take a long time and are you sure you want to continue, I recommend doing so. It will take hours (I left mine to run overnight.) Either way, when you get back to the main menu DO NOT REBOOT YOUR PHONE. YOU NEED IT IN THIS STATE.
9. Now if all has worked properly, you can launch MyPhoneExplorer on your PC and choose setup your connection via wifi. Cross your fingers, but if all worked as it did for me, your phone will appear on the screen (if it is all black, just hit the power button on your phone to wake it up). Use your mouse to enter your lock pattern or pin number if you have those set. At this point you should be using your phone through your PC. Just remember that as soon as you reboot the phone, it will revert back to it's secure state and you will have to go through this process again. I hope this helps you and others (and saves everyone the hours of frustration and research I went through).
jakbold said:
Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob
Click to expand...
Click to collapse
themadczar said:
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:...
Click to expand...
Click to collapse
Thank you very much for your time and effort, I will try this soon!
Sadly I am in the same position as the OP. My screen is cracked and I need to access the phone via adb, unfortunately, it is appearing as offline. Does anyone know a way to bypass this RSA-fingerprint issue?
Just got done rooting my Droid Maxx, this will be about the 8th phone that I've rooted so I'm not a complete bozo when it comes to rooting. I appreciate those that have come up with the root and have donated when ask for. This last root has done some weird things to the phone
1. Bluetooth commands wont work, answer and call cancel work, but no voice commands. When asked to choose what program I want to use, which it shouldn't, I press google voice and it says program illegally installed.
2. I've change the entitlement to take advantage of my grandfather rights, but it seams like I have to on/off airplane mode to reconnect to 4g to get internet pages to come up , this happens anywhere frome two to 10 minutes on the internet.
3. I've also installed Titanium back up. want to remove allot of the blot, [I never get rid of proprietary programs] after removing programs like NFL football and the like, those programs come back and are re listed in the app pages.
Any thoughts to whats going on. ?
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.