Hello, I just started getting random reboots from my generic kitkat tablet and I know it's from the ads that's build in the tablet and nothing else because when I turn off Wi-Fi the tablet is fine no reboots what so ever. Now I did download and install an ad blocker it stops the Ad from loading up completely but a loading screen still comes up and that's when it reboots the tablet. As the title states this is a constant thing and it's really annoying, I wish I could install a custom rom or even CWM recovery but since the tablet came out not long ago there aren't any available at the moment.... So if anybody experienced the same issue my question is are there any other way to get the ads to completely in order to stop the reboots? Thanks in advance
i've narrow it down to it being an issue with the Wi-Fi (i've tried factory reset and that didn't work either) and I see that some are having issue with this as well :crying:
If you are familar with ADB I can try to help you if you can get a logcat so we can see what is happening right before the reboot.
timmytim said:
If you are familar with ADB I can try to help you if you can get a logcat so we can see what is happening right before the reboot.
Click to expand...
Click to collapse
THANKS!! but it's been a couple of years since I really dealt with ADB that i think I would need a refresher on how to set it up (which im trying to look up now) and since my tablet came out early during the summer and there's no custom recovery for it im actually curious to create my own for it
Logcat
here's the logcat of my tablet for anyone that may be interested in helping me, thanks in advance
sketch2k278 said:
here's the logcat of my tablet for anyone that may be interested in helping me, thanks in advance
Click to expand...
Click to collapse
You neglected to tell us that you are running Xposed Framework on your tablet :silly:
First, disable all your Xposed Modules and reboot then see if you can duplicate the random reboot problem.
- If yes, uninstall the Xposed Framework and reboot then try again.
- If no, Reenable your Modules one at a time while trying to duplicate until you find the moduile that is causing the reboot.
Can you list the modules that you are running?
If you want to get rid of the advertisements just add the ips to the hosts file in system/etc
timmytim said:
You neglected to tell us that you are running Xposed Framework on your tablet :silly:
First, disable all your Xposed Modules and reboot then see if you can duplicate the random reboot problem.
- If yes, uninstall the Xposed Framework and reboot then try again.
- If no, Reenable your Modules one at a time while trying to duplicate until you find the moduile that is causing the reboot.
Can you list the modules that you are running?
Click to expand...
Click to collapse
Xposed didn't cause it because it was rebooting on wifi once I did a factory reset I attached another logcat this time factory reset settings
I did notice something though... if I disable the wifi then reset the tablet, let it sit for a minute then turn the wifi back on it don't seem to reboot itself like 5-10 seconds it takes a few mins to reboot (unlike if i was to leave the wifi running while resetting)
CLINTZ9 said:
If you want to get rid of the advertisements just add the ips to the hosts file in system/etc
Click to expand...
Click to collapse
how do I do that?
thanks for the help
http://pgl.yoyo.org/as/serverlist.php?showintro=0;hostformat=hosts
add these lines to your hosts file in system/etc/hosts
Related
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
please delete
showerhead88 said:
I tried searching for anybody who's had the same issue but no luck.
I just factory reset my phone and proceeded to install xposed and a few modules but now I keep getting notifications of every action I take, it shows with the green android system icon. Like for example, in this screenshot, as soon as I went into settings, it gave me a notification. And then I hit home to get back to the stock launcher, and I get another notification.
If somebody could tell me how to turn this off, I would appreciate it a bunch.
Click to expand...
Click to collapse
It's more then likely one of those modules you installed, if you don't know which one it is try disabling one and reboot and repeat until you find the one.
I rooted and installed custom recovery on my HDX7 using the HDX Toolkit according the the given instructions. After a few days I decided to uninstall recovery and moved the TWRP backup to external storage. I hadn't installed any custom roms or created any rom slots. I had no problems for days until these changes I made last night.
I uninstalled towelroot, reading that it was safe to do so. I installed a flashlight app. I installed Greenify and auto-hibernated some some third-party apps - including ES FileManager and Safestrap, which I considered safe since I had already uninstalled recovery. I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well. I also turned WIFI off before shutting down.
The device is now stuck at the second splash screen with the animated white and gold Kindle Fire logo. The screen is also slightly dimming and brightening repeatedly. I can't get into safe-mode/ recovery mode. I looked up what I was disabling but think I goofed using NoBloat and Greenify and screwed myself by uninstalling recovery.
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Segue2 said:
...
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Click to expand...
Click to collapse
Did you try hard reset? Press power button for more than 20 sec. Your kindle should then restart itself hopefully without bootloop. I was once messing with rooted stock fire OS trying to add one app to system apps (live wallpaper support I think), after restart I get neverending bootloop, but I was able to get out of this by doing hard reset, then Safestrap showed again and I was saved.
If you can manage reverse all your changes on system through adb, good for you, but without installed Safestrap ... well, maybe someone with better skills can manage you through this ...
I have tried but hard resets aren't working.
Can you still access it through ADB?
EncryptedCurse said:
Can you still access it through ADB?
Click to expand...
Click to collapse
No, looks like I am having trouble getting adb access. Command adb devices is returning nothing. Windows is recognizing the Kindle, however, but only as a portable device. Definitely had adb access before (established to use the HDX Toolkit). Now, I am wondering whether I disabled adb support on the kindle at some point beforehand.
On a sidenote, I just unplugged and reconnected the usb cable a few times and was able to hit the lockscreen for a few seconds before falling back into the bootloop. I have been able to repeat this.
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Segue2 said:
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Click to expand...
Click to collapse
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
EncryptedCurse said:
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
Click to expand...
Click to collapse
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
jimyv said:
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
Click to expand...
Click to collapse
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Segue2 said:
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Click to expand...
Click to collapse
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
jimyv said:
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread and that you till the thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
Click to expand...
Click to collapse
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
lol
Segue2 said:
I will try fresh installs on Windows again, then. I did read and interested tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Click to expand...
Click to collapse
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
Segue2 said:
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
Click to expand...
Click to collapse
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
jimyv said:
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
Click to expand...
Click to collapse
Ok, good to know about the power.
Yes, I have used the Minimal Adb and Fastboot utility before and couldn't get access.
I can get into stock recovery for a factory reset.
I can not get into SafeMode. It ends up booting to the lockscreen for a second or two before falling back into bootloop - sometimes flashing the lockscreen again.
okay well I do believe you have run out of options..in a nutshell you are looking at a replacement device anyway so you should be on the go for a factory reset
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
by
Segue2 said:
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
Click to expand...
Click to collapse
nope you are out of options before you got to the factory reset.apparently something was done to the system that nobody knew about. Or there is a hardware problem anyway.you can try to hold the power for over 20 seconds or another factory reset but sounds like you need to give Amazon a call anyway you might have had a bad unit. Because nothing you described in above paragraphs should have gotten you to this point.
Segue2 said:
... I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well.
Click to expand...
Click to collapse
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
jeryll said:
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
Click to expand...
Click to collapse
the loop he was in would not allow him ADB either ,something was done here other than what has been stated whether it was known or not.
correction I also use greenify it on all my devices. And to be able to do anything to system you must have had exposed framework installed....in which case I would have never have recommended a factory wipe. as stated several times already. simply hibernating a few apps even hibernating a few apps ( which is about all you can do without framework) would have not gotten him here. he had to have permanently removed something from system or permanently disabled iteither way without knowing exactlywhat service he appy that too it would be a guessing game even with adb.in short like you said lesson learned for another person that bothers to read this thread not to tamper with your stock system without safestrap at bare minimum and a backup
I wonder if he has had any luck with ADB now that he is no longer in a perpetual boot loop. May be able to come up with a reenable command for system apps? Su should still be in systemat least the binaries will be in case the app wasn't. And I think in this case it would be better if the app was not in system but the binaries remained since he cannot get into the OS he will not be able to grant permission..but without. su command should work still
Thanks for the input. Wiithout a doubt, lessons learned here. At the very least, I never should have uninstalled Safestrap even if I wasn't planning on doing anything else to the system. I have the TWRP backup of my rooted stock, but with no way to use it now - useless.
I must have disabled some critical app or combination of apps that lead to the conflict, despite the care I thought I was taking. As far as Xposed framework goes, I never installed it manually. Maybe it is packaged in with one of those apps? The other thing I wondered about was whether disabling wireless could have led to a conflict. Using the Toolkit has been reported to lead to a bug where the system can crash when trying to enable wifi without first enabling bluetooth.
Either way, all I had to do was leave safestrap alone, just in case. F.
All of your help and feedback has been appreciated!
Wow. Well, I have adb access. After mutliple unsuccessful attempts on Windows and Linux, I was able to fire up an old MacBook and established an adb connection in 10 minutes. Unbelievable! The list of installed packages doesn't show any third party packages. Can I push and install Safestrap through adb to get my backups up and running? Whar is the correct syntax for those commands? I have already got a replacement on the way, but I would like to try to bring this one back and unroot. On second thought, maybe I should just leave it?
I installed greenify yesterday, and it has caused my phone crash two times. First time was when I clicked experimental features, second time was when I tried to hibernate a weather app. Both time my phone got stuck, and I can't even turn off the screen. What's the problem?
zhjn921224 said:
I installed greenify yesterday, and it has caused my phone crash two times. First time was when I clicked experimental features, second time was when I tried to hibernate a weather app. Both time my phone got stuck, and I can't even turn off the screen. What's the problem?
Click to expand...
Click to collapse
What is your device and what ROM do you have?
Have you installed the correct version of Xposed installer and APK and is it working?
Is any other Xposed module working on your phone?
If so, please post logs of the crash.
tnsmani said:
What is your device and what ROM do you have?
Have you installed the correct version of Xposed installer and APK and is it working?
Is any other Xposed module working on your phone?
If so, please post logs of the crash.
Click to expand...
Click to collapse
Samsung s6 edge SM-G9250, stock rom. My phone doesn't support Xposed. BTW, where can I find crash logs?
zhjn921224 said:
Samsung s6 edge SM-G9250, stock rom. My phone doesn't support Xposed. BTW, where can I find crash logs?
Click to expand...
Click to collapse
So are you running it on "Unrooted" mode? Have you enabled it in Accessibility and Device Administrator?
Some functions of Experimental Features will not work without Xposed.
For crash logs, you can use ADB if you know how, or Logcat from Play Store.
tnsmani said:
So are you running it on "Unrooted" mode? Have you enabled it in Accessibility and Device Administrator?
Some functions of Experimental Features will not work without Xposed.
For crash logs, you can use ADB if you know how, or Logcat from Play Store.
Click to expand...
Click to collapse
Oh I'm sorry, I rooted my phone and I'm running Greenify on "root" mode. Since my phone freezed and rebooted right after, can apps like Logcat record the crash log? I haven't crashed since I installed "aLogcat" though.
I'm afraid no tool apps on device could log the reboot. You need a connected computer running "adb logcat -v time" to capture logcat around the reboot.
Hi all
Since a few days I get a error " System UI stopped "
Searching on Google only gave me that most common error but not this one. It prompt 1 time a day / 2 days and I don't know how to solve it. It tried clearing the system case but this didn't work.
The error mostly appears when waking up my phone and never when working on it.
I don't use custom lockscreen or launchers and running DarkLord N5 rom since months now but this happens since the last week or so.
I attached a screen of the notification.
Hopefully someone knows the solution
THX in advance
iDreamliner said:
Hi all
Since a few days I get a error " System UI stopped "
Searching on Google only gave me that most common error but not this one. It prompt 1 time a day / 2 days and I don't know how to solve it. It tried clearing the system case but this didn't work.
The error mostly appears when waking up my phone and never when working on it.
I don't use custom lockscreen or launchers and running DarkLord N5 rom since months now but this happens since the last week or so.
I attached a screen of the notification.
Hopefully someone knows the solution
THX in advance
Click to expand...
Click to collapse
Boot into recovery, wipe davlik/cache, reboot to system, checck to see if problem is solved.
Without the proper logs and troubleshooting you are gonna be out of luck.
zelendel said:
Without the proper logs and troubleshooting you are gonna be out of luck.
Click to expand...
Click to collapse
Is there some way to log it for when it happen you could see what causes it?
iDreamliner said:
Is there some way to log it for when it happen you could see what causes it?
Click to expand...
Click to collapse
Yes. It's troubleshooting/android 101. It's called a logcat. You might want to spend a few days doing research.