After I rooted my phone, I found that it took too long time on the boot screen(the unlocked bootloader warning screen), like more than 30 seconds. Could please someone tell me how to fix or improve this?
I heard from somewhere that it is because of the "parallel apps storage" which causes the TWRP take longger.
How can I remove the parallel apps storage? I already disable the parallel apps in the phone settings.
Related
Hi all,
I recently tried changing the wallpaper on my phone from a live background to regular image. The background went black and the phone froze.
I removed the battery and restarted the phone but it now often freezes on the LG logo. When it does occasionally start up the touch screen will not respond so I cannot get past my lock pattern. If I press the stand by button at the top of the phone, the screen goes off and cannot be turned on again, but the phone is still running - as I can tell this when connected to the computer.
I don't have my phone rooted and do not know much about that. I was hoping there was a way to fix this without having to lose all of my data or root/mod my phone. Otherwise I would be happy just to have my phone working.
Can anyone please help with this problem or tell me why the touch screen will not respond the times it does start up?
Cheers
UPDATE - I started the phone holding the volume button down and went into the recovery mode. I'm not sure exactly which option I then selected, as I hit the home key a couple of times, but I think it was "Clear cache and recovery" or something similar.
The phone managed to start back up with all my apps and photos, etc. Although I had to go through the startup wizard again and sign into the Market, LG World, etc.
Now I have a problem with quite a few of my apps. Whenever I click on them, they start very briefly and then I get the message "The application had stopped unexpectedly. Please try again" and have to force close. This happens with apps such as Adobe Reader, GTA 3 and Viber, so it's not a specific type of app.
I also noticed with the few apps that work, data is missing from some and not others. For example, I still have high scores in one game, but not in another.
Does anyone know what the problem is here or why this recovery is maybe causing this?
Thanks very much
Still haven't fixed this problem if anyone could please help. Most of the apps before the recovery still force close upon starting.
Some of these can be fixed temporarily by moving to phone/SD depending on location, but this only lasts for so long, before I have to move again. Others will open up each time as though it's the first opening of the app, e.g. Do you accept....
Apps downloaded after the recovery seem to work fine.
Any suggestions people?
I've got a rooted (Super SU, but the original root manager was Superuser) 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 Lite, Super SU, and a quite a few 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 and turned in on time. Please help! I'm open to suggestions....... 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 off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in 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? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 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.
Have you tried booting into recovery?
(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.
One of the first things I did on buying my new Galaxy Tab 2 7" (GT-P3100, Wi-Fi and 3G; Spanish market "PHE" identifier, came with ICS 4.0.3, no updates available either through Kies nor OTA) was to encrypt the Device. It worked.
Then I rooted the device with CF-Auto-Root, which had the side effect of performing a factory reset, and as I understand it from a brief conversation with the author of (the excellent!) CF-Auto-Root this was an expected side-effect of the device having been encrypted at the time of applying CF-Auto-Root.
So, the Tab 2 is back to un-encrypted.
Here are the details:
Android 4.0.3
Baseband version 3.0.8-CL448962-user [email protected] #1
Build number IML74K.P3100XWALD2
But now I'm trying to encrypt again (either/both the SD Card and the Device itself) and I'm having no success at all.
On trying to encrypt the SD card, each time it always returns "SD Card Encryption Error" within a few seconds. (And indeed thereafter I always get a Notification about "SD card encryption error" any time the SD card is mounted by the device). If I go back to Settings -> Security -> Encrypt SD card and select to decrypt the card (even though it's not really encrypted), then I can access the SD Card again - no damage was done (and no encryption either).
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
One of my main reasons for getting the newer device was to have encryption :-/
Is Encryption (Device, and SD Card) supported/ functional when CF-Auto-Root is in use on a Samsung Galaxy Tab 2 (Android 4.0.3)?
How do I get encryption to work, for both the Device and the SD Card?
Is there a way to get more detailed logging (the Tab is rooted, and I have command line access) and/or to command the encryption from the command line, to see what's really happening?
Thanks!
Hm, I tried encrypting only NEW files on the SD Card now, and that seems to work.
I stored a new file on the SD Card, unmounted the card from the Tab, put the card in a card reader on a desktop computer, and indeed the contents of that file are just "data", not readable. Back in the Tab, the contents are the picture which I'd saved to the card.
But still attempting to encrypt the existing files on the SD Card fails. And still attempting to encrypt the device does nothing (green android appears, but no % complete ever displays, etc, just as I posted before).
One step further with the external SD Card; I copied off all of the data, formatted the card, and then was able to fully encrypt it (and copy back my data).
But the Device itself, I still can't encrypt at all - just the same as before.
No ideas? None? Nobody? Please....?
Thanks,
-Jay
Bump?
sigh
Try the same thing with the device itself.
Do a factory reset.
Not once,twice.
I know u lose all data.
But try it.
And do this without android to start.
Keep press power+vol up.
Get into menu and do factory reset,wipe dalwik...all.
Hope this help.
libove said:
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
Thanks!
Click to expand...
Click to collapse
Did u solve the problem?
i have the same problem
MasterBrush said:
Did u solve the problem?
i have the same problem
Click to expand...
Click to collapse
This was over a year ago, and I don't even use the device anymore. Sorry, can't help.
I've since then tried a ZTE "Skate Pro" (the Movistar Spain branding of the "Blade III"). Piece of Sh*t phone. Support encryption natively under Android 4.0.4, but if you do encrypt the phone, the performance of the touch screen becomes unreliable, frequently so bad that swiping (including Swyping) actions don't work right, and you end up less moving things on the screen and more, effectively, tapping things you absolutely did not intended to tap. I discarded the ZTE Skate Pro/ Blade III.
Then I tried a Haier W708, dirt cheap; not a powerhouse, but satisfatory.
And a Nexus 5 which kicks *ss all over the place.
I can't help any more with this thread, and any results in this thread would not longer help me, so I'm dropping off the thread now.
Best of luck to all.
Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.
mazzuli said:
Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.
Click to expand...
Click to collapse
Did you wipe your data partition when you updated frowm 4.4 to 6.0? Its most likely that all the apps are crashing due to incompatible data files.
I've once had the same problem and i managed to fix it with deleting data for every crashing app, so this might be an option.
Otherwise you might fix your phone by factory reseting from recovery.
Edit 2 :
After third time re-install my conclusion is it happens when adding extra languages.
So the Superlocale was the trigger but not the cause as it happened without having either of the 2 mentioned apps installed.
The only "special" thing i did was using adb to get rid of some pre-installed stuff like Google Youtube, Keep, Films etc (some more than i did in the past. Wonder if that could be causing the "stuck on flashing unlock screen"?
Edit : allready managed to enter Oppo recovery and resetted my phone.
BTW it wasn't the Insular app but SuperLocale to quickly switch languages. After granting the special permission the same thing happened again and i had to do another reset again .... ouch.
I've been playing around with the Insular app yesterday (which creates a sandbox envorinment by means of the Android work profile) and this morning I found the phone flashing at the unlock screen.
Guess the app really messed up. But even worse is;
- I cannot unlock the phone
- I cannot power down the phone
- I cannot enter recovery
I can use the Power + Vol+ combo but it just restarts the phone leaving it flashing at the unlock screen without any means to unlock
Meaning I cannot factory reset the phone....
What else is there I can try to get my phone back?
Oppo Find X2 Pro