<Mod edit: THREAD CLOSED on request of OP>
Sorry... I didn't realize there was a power button plus up volume key combination. That rebooted my phone. There is no crisis. Moderator can delete this
I am little spooked. .I think I have tried everything but my phone seems dead.
First, I have a TMOUS OP7 Pro which I converted to international and was running 9.5.13.GM21AA. I have been using the phone without problems for several days.
The phone is rooted with Magisk and I had a few modules installed including Rira-Core and Rira-EdXposed (SandHook). However, I had not installed the Xposed Installer apk.
The last thing I did before I rebooted was install the Xposed Manager apk. I read that this app was a better option than the Xposed Installer apk. I did not think I was risking anything because I had installed this same app before. without problems (but if memory serves I had first installed the Xposed Installer apk, downloaded some xposed modules, then uninstalled the installer apk and installed the Xposed Manager apk). This time I just installed the Xposed Manager apk.
I previously messed something up about 4 days ago. I am not sure what I did at that time, when I tried rebooting it strangely hung at the "Unlocked Bootloader" screen. However, I was able to get to the booloader screen. Since I had a backup, I just did a flashboot boot twrp.img using the SDK tools and restored it. The difference though was that I was able to get to the bootloader screen. Now I cannot seem to get anything. Screen is just black. I simply rebooted it and it went black. No unlocked bootloader screen, just black.
I have tried holding the power button and down volume button simultaneously, but nothing happens.
As said, I am very spooked and worried. Does anyone have any suggestions.?
THank you in advance.
Paul
Related
Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out
ForceClosed said:
Hey all,
I've been running Pac-ROM 4.4.4 for quite a while with hardly any issues, but I recently noticed some touch errors such as the home button and task button activate simultaneously when I only press one button. It sometimes takes a few taps before only the home button is registered. Also on the right side of the screen I can't pull down the notifications bar; that only works in the middle-left of the screen. Because of this, I decided to upgrade my ROM to the newest beta version of Pac-ROM lollipop.
Now my issue: the new ROM had issues with google store and services. Instantly upon booting up, youtube kept spamming my screen saying it couldn't run. I also had notifications for google play store, so I uninstalled both youtube and the play store (after clearing cache for a simpler fix). That got rid of the pop-ups, but I still couldn't access my google account. I browsed some threads and they suggested to remove my google account and clear cache for google services. This didn't fix the problem so I decided to flash back to the stable 4.4.4 and reinstall the apps I removed.
Here is where I foolishly realized I never updated my gapps to 5.x.x. Being too late, I thought I'd just flash the gapps and lollipop rom after getting things back to normal in 4.4.4. Unfortunately, I was never able to boot after flashing 4.4.4.
Now I am stuck in a boot loop, do not have debugging enabled thanks to the update (so I can't use adb), my recovery won't boot using power + vol down, and my computer doesn't even recognize my phone when using LG mobile support tool.
Other things that may help:
LG G2 ls980zve
TWRP 2.8.x.x
cannot access adb or fastboot
cannot access recovery
cannot turn on phone
updated lg drivers as of today, but computer doesn't recognize my device in device manager
followed these threads but couldn't resolve the issue:
http://www.rwilco12.com/forum/showthread.php?tid=96
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2471370
Ask if I forgot to mention anything crucial.
Good luck figuring this out
Click to expand...
Click to collapse
Here's a guide that can help you.
i am sure that there's guides here on xda too.
That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!
ForceClosed said:
That guide was essentially the same as the two links I referred to except one thing... It reminded me to reboot the computer after installing drivers! HAHA. Now it worked smoothly.
Such a simple fix, thanks!
Click to expand...
Click to collapse
Hahaha!! Happy that I helped someone!
I have a Samsung Galaxy S5 mini on stock rom, rooted. I was looking through Xposed for new possibly interesting modules. I installed one which said you can set volumes to have more than 15 points. So I installed it but I did not reboot yet figuring that I would do that later. I made all new backups of my apps and data using Titanium backup and then tried to reboot my phone but the reboot menu button would not work and the screenshot button at the top was blank yet functional. So I loaded up, or attempted to load up Wanam Xposed to check what was going on since that is what configures my rom and it said the app was not installed when I pressed on the shortcut.
So I rebooted the phone, entered the encryption password, it came up to the lock screen and from that point it would say my password did not match. I tried every password I have ever used, varying case and everything. No password worked. I had not manually changed it either. I had no choice but to factory reset the phone and format the SD card. Also I should mention that when I found out that wanam xposed was not seemingly installed any more, I attempted to install it and it would just say "App was not installed" or something. Then I installed Wanam Toolbox or something, I forget exactly now, but that installed and I rebooted and that's when I noticed my lock screen password was not working.
Any ideas on what the cause may have been and what things I could attempt to do if it ever happens again? I thought there was a thing where you can use your google account to unlock the phone but I could not get that thing to come up.
Hi. My S6 has been running great for a while. It's running CleanROM. I got a notification that there is an update to SuperSU. I chose to update it normally because there's no recovery since the bootloader is locked. During the upgrade, I got a message saying that Knox was detected and if I wanted to disable it (temporarily?). I chose Never not thinking about the implications. The phone rebooted as part of the upgrade but now it is stuck in a bootloop. It does boot up for a very short time. Enough time for me to draw my security pattern and for some apps to load, but then the phone reboots. Any idea what's going on? Any suggestions on recovering from this? Thanks.
UPDATE: Somehow I recovered. I was able to power down the S6 because I had that small window to do so. I booted to Safe Mode and disabled SuperSU. I rebooted normally and everything was ok except SuperSU was disabled. I uninstalled SuperSU Pro and then uninstalled all updates for SuperSU. Play Store wouldn't let me totally uninstall it. I updated SuperSU. This is where it gets a little foggy. I think I re-enabled SuperSU and then it said that Knox was detected and whether to try to disable it or never disable it. This time I chose to disable Knox. SuperSU tried to disable Knox but got stuck with the spinning arrow. It was strange because I was able to go to Settings, but when I went to Apps or Logs, I got a continuous spinning arrow. It seemed to do what was needed though because my root checker verified I was rooted again. I rebooted again and ran SuperSU again. It gave me the Knox detected message again. This time I said Never disable. Rebooted one more time, ran SuperSU and no more message. Last step was to reinstall SuperSU Pro. I am not sure exactly if I had to do all these steps and what exactly was going on, but I think I am back to normal running SuperSU Pro v2.79.
I installed GLtools and after completing, the screen stuck and it is always on (never sleeps or dims display). None of the buttons work. I waited till it used up all battery and then charged to 5% to turn on again. When I turn on, I see my launcher still the same (and the phone launcher desktopsetup pretty intact), but after a few seconds, screen stuck again, buttons not working again.
Is there a way to remove/uninstall GLtools through PC or whatever means to fix this?
Please help.
Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!
Lum_UK said:
Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!
Click to expand...
Click to collapse
I did not flash anything. It was in stock rom. Is there still a way to fix this (remove GLtools)? Is the GLtools running in background that's why I was still able to unlock my phone and use my phone for a few secs before screen hang again?
EDIT:
I got it to work long enough to uninstall GLtools but there is this loading bar that appears even after I had removed GLtools,
http://i.imgur.com/dN4HaZW.jpg
Is this from the phone? or from my root app?
My phone screen still hungs now. I think it's not GLtools issue.
That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?
Lum_UK said:
That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?
Click to expand...
Click to collapse
So I learned how to force close the phone from you (hold power button for 10 secs), then I turned it on normally, it worked fine as normal. I tried rooting with KingRoot and it rooted, tried to install Xposed Framework thru a method found in youtube because I don't have TWRP (method uses BusyBox Pro, Terminal Emulator to flash the zip). But Xposed modules download button don't download (button goes back to idle when I tap "download").
I also tried Lucky Patcher and other similar apps to convert or move user app to system app, after reboot, the converted app is gone (deleted). This bar also keeps appearing after I did this.
That bar keeps appearing and freezes the screen (whatever the screen is currently showing) both during and after the progress bar finishes. Tried to force close and turn it on again. Stuck on Oppo screen for 8+ hours (left it as is, I went to sleep). Decided to flash the stock rom (power + vol down) without wiping data. Worked and returned to normal desktop launcher setup but phone goes back to unrooted. Xposed Framework is gone too.
Is this bar meant to check if I am doing changes to the system like root, Xposed, converting user app to system app and prevent me from doing those? I really need those things on my phone! :crying:
the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.
Lum_UK said:
the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.
Click to expand...
Click to collapse
why did the download button of Xposed not work when I tap on it? it does nothing for me.
Which Xposed should I get? I saw 2 APKs, a 3.0 and 3.1.1 alpha 4.
I was actually rebooting after I checked XMultiWindow module in Xposed when it got into bootloop
Get 3.11a4
All was well until this morning I got a notification that SuperSU needed updating. I said yes, and it gave me two options: 'Normal' and TWRP, or something similar. I went for normal. After a few moments a message appeared saying that the update was successful and that I should reboot my phone. I clicked reboot and now the device gets to the animated CyanogenMod logo and stays there forever.
I booted into recovery (by holding the volume down button at the same time as the power button), and from the main TWRP screen have backed up the phone (and copied the contents to an external device) and tried clearing the cache. This has not helped.
Can anyone advise what I could try next please?
UPDATE: Fixed it . I found a copy of UPDATE-SuperSU-v2.65-20151226141550.zip in the Download folder of the phone's internal storage, installed that using TWRP and rebooted the device. It has started fine, with the only strange thing being that SuperSU no longer appears in the Android Apps Drawer. Any idea why this might be? Is this likely to be a problem? I'm not sure I fully understand what SuperSU really does.