I installed a SecondScreen app, and it obviously didn't do me well, when the phone boots it boots to a black screen and no icons or anything, simply an error that Com.android.systemui has stopped, and I can't tap OK. I also tried rebooting into safe mode, which it does, but the error still appears on top of a blank blue screen. So, I can't uninstall the app or anything. I can still get into recovery. I do have a back-up but it's old. Is there anyway to simply uninstall the app from recovery, any other options?
Thanks,
seanvree said:
I installed a SecondScreen app, and it obviously didn't do me well, when the phone boots it boots to a black screen and no icons or anything, simply an error that Com.android.systemui has stopped, and I can't tap OK. I also tried rebooting into safe mode, which it does, but the error still appears on top of a blank blue screen. So, I can't uninstall the app or anything. I can still get into recovery. I do have a back-up but it's old. Is there anyway to simply uninstall the app from recovery, any other options?
Thanks,
Click to expand...
Click to collapse
You could try browsing to the SecondScreen apk installation path within your recovery's file browser and delete it. You can also try dirty flashing whichever ROM you're using over your current set up, as it sounds like some of the system my have been corrupted.
Restore your backup.
Safe mode (seems you tried that).
Recovery mode and disable e.g. rename the app.
ADB shell session and disable or rename the app.
Possibly (not guaranteed), clear the cache from recovery and reboot.
Odin flash anything from a dirty flash to wiping user data to a full firmware image, depending on what seems expedient to you.
.
Related
I flashed the following KA6, and I didn't realize it would wipe my apps and contacts. I took a nanroid backup using CWM beforehand, and I'm trying to boot into CWM to restore my backup. However whenever I tell CWM to reboot into recovery or to restore the backup, the phone reboots into the standard Samsung Andriod e3 recovery, which does not allow me to restore my backup.
How can I get CWM to boot up so I can do a restore?
http://forum.xda-developers.com/showthread.php?t=919760
I figured it out.
I'm having the same problem. How did you fix it?
I have flashed, deleted the clockwork recovery files, re-flashed, rebooted, etc, etc.
I can only get the standard blue recovery mode. I run reinstall packages and all it does is quickly shows it's attempting to install the clockwork update.zip file but just boots back into the blue standard recovery mode. Yes I have confirmed the update.zip file is there. I have removed it, reflashed, rebooted, etc. Running reinstall packages takes me into a constant loop.
This really sux.
Anyone got ideas on what my problem might be?
Thanks
Getting the same, and when I go check on my rom backups of my default OS there are no roms to be found after it says it created them successfully.
I erased any existing update.zip, then I told clockworkmod to reinstall, boot into recovery, in the blue menu I selected reinstall package, it rebooted into blue recovery again, and I selected reinstall package for the second time and then it finally rebooted into clockworkmod.
If this doesn't work you can try to follow this guide to get clockworkmod working again.
http://forum.xda-developers.com/showthread.php?t=925400
In the mist of my experimenting trying to get this to work, I did use the app Quickboot which is on the phone already to boot the phone into download mode. Then I did a hard reset (hold power button for 10 seconds), and tried the whole process I described in the previous post. I would guess this is not necessary, but it's just what I did.
I tried to install a new theme on jasmine rom. I rebooted and phone said updating app, and remained on update app for over 5 minutes.So I rebooted and the phone remained in the jasmine boot screen. I knew I had a problem so i rebooted into recovery, did a complete wipe and installed my backup and rebooted. The phone started to reboot (Lg splash screen) and then stopped. The screen went dark and my red and blue LED lights started blinking. I tried to get back into recovery manually. I was able to get to stock recovery, hit factory reset and instead of going to TWRP, it went back to the black screen and the blinking LED lights. Same results occurred when I hit safe boot.
I also tried to get in DL mode with the volume up button. Instead, the LG splashscreen came on for less than a second, the screen went black and the blinking lights came again. I tried ADB but it won't recognize my phone. Any suggestions, or is this a goner? Thanks for your help.
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
rp201 said:
So to install jasmine you had to have twrp installed. Then you said you booted into recovery and the stock recovery came up and you said yes to factory reset. that scenario of booting into stock recovery and saying yes was only the first time after installing twrp. everytime after that if I choose to boot to recovery twrp screen comes up first. Confused cause I'm nut sure if this is normal behavior with some phones that have been bumped.
Click to expand...
Click to collapse
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Bxrider117 said:
I accidentally took the update from Verizon and when I went to install it I got the same thing. I would get the lg/android bout screen and then it would go to twrp. I tried to reboot, wipe everything and restore back up and nothing changed.
Then I found this post
http://forums.androidcentral.com/ge...cked-lg-g2-stuck-twrp-no-download-mode-3.html .
This saved me. When in twrp you go to the advanced tab click terminal command, then select. Just follow this directions and you might be golden.
This just worked for me and I didn't have to flash back to stock. I know this says it is for the g2, but it worked. Good luck.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I did the exact same thing early today and stumbled on that same thread. So relieved
jlokos said:
If you boot into recovery from the advanced reboot menu, it goes directly to TWRP. However, when you use the hard key combination, it goes to the stock recovery and when you select factory reset, it is supposed to go to TWRP. It doesn't. I have a new phone on the way.
Click to expand...
Click to collapse
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
ohlin5 said:
So any idea what exactly went wrong here? How did a basic "theme" apparently completely bork your recovery and brick your phone??
Click to expand...
Click to collapse
I have no clue what happened; Verizon sent me a new phone. I don't have a clue whether this was related to the theme, or not. It may have been an unrelated hardware issue.
This started with my trying Online Nandroid Backup from the Play store, which I've used on my previous Android phones. I made a backup with it (I had TWRP v2.8.2.0) while Jasmine 4.0 was up and running, and then I booted to recovery, made a regular backup directly in recovery, then wiped and tried to restore the backup that Online Nandroid created. I saw something in the restore log about uboot partition. It restored the rest of my partitions fine. Then I made a bad choice and I told TWRP to reboot. I thought I should still be able to get into TWRP even if the ROM won't boot, but negative.
The only thing I can get into is the menu to choose Factory Reset, Wipe Cache, Power Off, Continue Boot, and I think there's one other option.
I've tried them all. I've tried leaving the battery out for more than a minute and then trying again. No matter what, after a brief show of the LG logo, the screen goes dark and the notification LED toggles between green and orange repeatedly.
No ROM booting, not even starting, no recovery at all. The computer doesn't see it in this state. I've tried LGMLauncher.exe, LG Flash Tool 2014, and as I expected nothing will see it, which makes sense.
Any ideas? I expect I'm SOL.
Thanks for your time.
looks like you have stock recovery and that's it. Have you tried getting it in to download mode?
BladeRunner said:
looks like you have stock recovery and that's it. Have you tried getting it in to download mode?
Click to expand...
Click to collapse
Hi, thanks for your suggestion.
Maybe you mean something other than "Stock Recovery"? I had TWRP on there previous to restoring the backup, and the backup had TWRP in it too. All options from the menu resulted in the same Green-Orange-Green, etc LED.
I just got home with a replacement. Ugh.
Something like that happened to me.once the whole lg blank screen then the led lights... I just flashed a stock ROM with the flash tools and solved me problem
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Bump...
Ideas/suggestions?
kevinbakon said:
Suddenly and with no recent changes to my watch (unless an OTA was pushed without my knowledge), my watch screen was blank, but still on.
I pressed and held the power button on the back until it restarted.
It starts to boot up, but never finished (left on charger all day).
I've tried several times now and all I get is either a stuck LG logo or a stuck screen with the flying balls of color.
I wouldn't call it a "bootloop" because the booting process does not start over (loop)... It's more like a "bootstuck".
I am able to boot into recovery, clear cache and factory reset. Once I restart though, it immediately gets "bootstuck" again.
I have even let the battery completely drain, placed it on the charger and tried again.
...nothing...?!?!
Any suggestions?
Click to expand...
Click to collapse
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
OfficerJimLahey said:
Something gone wrong in userdata likely, or since you already factory reset, more likely in /system partition.
The last few forced OTA threads in Q&A have a mirror link for a TWRP backup of LCA43. Use fastboot boot (not flash, so you don't keep it permanently) a 2.x.x.x version of TWRP. From there, backup your broken setup, factory reset again, use adb to push my LCA43 backup files to TWRP backups (not to overwrite yours), and then restore.
That should patch you up.
Click to expand...
Click to collapse
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results, but I do see the devise in fastboot, if I am in the bootloader screen
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Otherwise, I guess I could reinstall factory recovery, but I can't figure out how to do that either.
Unfortunately, the LG G Watch Tool doesn't seem to be working for me either. It just says "waiting for device"
Ultimately, all I want to do is get the latest stock OS installed and go from there
Any advice?
kevinbakon said:
Well, I think I may have messed thing up worse now...
I unlocked the bootloader and got TWRP 2.8.7.0 installed. Then I was unable to backup, so I tried wiping the data to see if something was hanging it up...
Now I seem to be stuck in TWRP recovery and each time I reboot it displays a message telling me "No OS installed..."
Also, "adb devices" returns no results
I suspect what I need to do now is obtain an update.zip file from somewhere and flash it in twrp, but I cannot figure out how to access the file directory on the watch.
Any advice?
Click to expand...
Click to collapse
Wait, installed TWRP? If it keeps taking you back into TWRP, then "fastboot flash boot" was used, not "fastboot boot". Read my previous post for difference.
What were the backup errors? Did something not mount? If so, then this (coupled with the original issue), may be hardware related and out of your control.
See if you can get back to the bootloader first. The boot.img can be restored this way, and get you one step closer to booting.
Sent from my ASUS_Z00AD
Helllo yes it seems your partitions are all messed up. Considering that on android wear your "data" on it is almost all on your phone aswell it seems like a waste to try and recover it.
here is a link to the system,recovery and boot images from LCA43 https://www.androidfilehost.com/?fid=24052804347803309 just flash those to each partition correctly ie. fastboot flash boot boot.img etc
and wipe your /cache and /data partition. You will essentially have a completely stock device and if it still thosen't function correctly then it is a hardware fault
Here is a video on how to access bootloader from boot screen: https://www.youtube.com/watch?v=ftSCH7qihRI
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......