After installing Xposed Framework, I also installed many modules as one might assume. After enabling all modules, I restarted my device. The device booted up all the way to the AT&T animation and then froze. The LED is also flashing blue. I have tried booting into safe mode, taking out and leaving out the battery and still no luck. Would greatly appreciate a solution without resetting my phone.
When you say you tried booting into safe mode, do you mean Xposed's safe mode?
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Related
I am asking this mainly because I hope I'm wrong about my own assumption.
My phone recently started randomly rebooting itself. At a certain point I woke up and the battery was dead. So recharged it and found it not getting passed the Samsung logo. Thought it was a xposed module since it had been acting up since I activated that again. So decided to disable xposed completely without any luck.
At that point I have tried to put a new rom on it. First time it rebooted during the installation throuwh TWRP. Second time it actually completed the installation and I managed to get into the OS.
But when I tried to install an application through the Google Play Store, in this case Chrome, it rebooted again and get stuck in the boot loop again for a while until booting up again but as soon as I tried to install the app again it crashed again and this kept going.
Have now also tried to install a different rom but the phone either crashes during the installation in TWRP or afterwards while it's trying to boot at the flashing samsung logo.
My assumption is that the problem is hardware related since it happens with multiple roms and even during the installation of said roms. But I really hope I'm wrong about this.
It's a SM-925F if that is important to know somehow.
So, i recently tried install the Xposed framework and got stuck booting up, so i thought ok, this easy, go into download mode and flash, but when it came to booting into download, it didnt work, then i tried recovery and got the same result. Ive tried rebooting into these modes with ADB but get $ADB_VENDOR_KEYS not set, even though i am COMPLETELY positive that i enabled allow USB debugging, as i was testing builds of some apps that i made on this device.
The device will show that it is charging when plugged in and will get stuck on boot forever.
tried all the boot combinations and nothing.
tried ADB on mac and pc and same $ADB_VENDOR_KEYS not set error
downloaded and updated every driver imaginable
used different cables
any support would be greatly appreciated
http://forum.xda-developers.com/verizon-lg-g3/help/unable-to-access-adb-t2830087
Hi all!
My S7 is unrooted, completely stock, running latest 6.0.1 official update
Few days back I updated some apps from the play store and after that, my phone suddenly restarted on its own
This sudden restarting kept on increasing and currently the device boots up for a few seconds, and then freezes and restarts again
I know there's some faulty app that's causing the restarts, because once i managed to turn the UPSM on before the device restarted and it worked fine, with all the apps disabled
I have tried to get a logcat to look for the issue but I can't do that properly as I haven't taken any logcats before and i'm not familiar with the process
I have already tried to flash the stock firmware but that didn't help either
Is there any way or solution to get this fixed? Or can anyone here help me on how to get a logcat so that I can look for the error causing app?
There's a lot of stuff on my phone and I can't risk losing it by factory resetting it
I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.
munchy_cool said:
I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.
Click to expand...
Click to collapse
I've booted into safe mode as well, but that isn't helping either
The same keeps happening in same mode as well. The device boots up, and after some 30 seconds it freezes and restarts and gets stuck in a loop
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
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed