I've recently had the problem, that the phone, booted up with WiFi on, stuck at 1GHz with full load by the system_server process. After examining logcat, I've discovered an message regarding keystore & bad file number. Also, I couldn't get into settings->security anymore, process FC. After some research, I've flashed the system ROM again (e.g. CM10.1) and since that, the error was gone. No more stuck at full speed & full load when booted up with WiFi on.
So what would be the solution, Flashing the rom again?
Related
Hello guys,
Still unsolved
Suspects: uwlopservice (in logcat log), dalvik-vm, link2sd
I have a bootloop problem after installing numerous apps and then using link2sd to move them to sd-ext. I've noticed that whenever I use link2sd it sometimes reboots the system whilst processing numerous apps to link, I'm not sure if this is related to the bootloop problem.
Anyway, this was the last thing I was doing before the device entered a bootloop. The bootloop reboots after the main screen is shown (however there is never enough time to enter the apps menu before it reboots), the reboot sometimes happens immediately after the main screen is loaded or up to about 30 secs after.
I initially thought this was due to the lack of space on /data but i moved the dalvik-cache to sd-ext, but the device still continued to bootloop. The other thing is that I have installed 256 apps (a nice power of 2), perhaps the x8 is limited.
I've attached the logcat log (as bootlop) and the /data/anr/traces.txt (as traces-bootlop).
I hope someone can help.
Cheers
j.
Still unsolved (see next post)
OK. The problem no longer manifests itself on my device. I am unsure of the cause and what I may have done to correct it. However, the main changes I made are as follows:
* Restored original non-bootlooping ROM backup (CM mod backup and restore feature)
* Restored bootlooping ROM backup.
* Moved the dalvik-cache from /data (which was 99.9% full to sd-ext). I tried booting after this, but the OS still bootlooped.
* Created a backup of this ROM.
* Restored the previous step's ROM after restoring any other ROM.
* Calibrated the battery using BatteryCalibrate(tor) on the market.
I do not know whether these steps actually solved the issue, but the problem no longer manifests itself. Perhaps this will be useful to someone else.
Contrary to the previous post, my x8 is still experiencing a bootloop. However, I have discovered that the loop occurs only whilst having the USB/charger cable plugged in through the entire boot process. If the cable is plugged in after boot, the device does not crash (i.e. reboot entering a bootloop). I wonder whether any other users have experience this.
(edit) now this problem seems completely intermittent. sometimes it boots successfully sometimes not, i'm guessing that there is a rogue app somewhere causing this. Just a suspicion so far.
*bump******
decrease789 said:
Contrary to the previous post, my x8 is still experiencing a bootloop. However, I have discovered that the loop occurs only whilst having the USB/charger cable plugged in through the entire boot process. If the cable is plugged in after boot, the device does not crash (i.e. reboot entering a bootloop). I wonder whether any other users have experience this.
(edit) now this problem seems completely intermittent. sometimes it boots successfully sometimes not, i'm guessing that there is a rogue app somewhere causing this. Just a suspicion so far.
Click to expand...
Click to collapse
yes in 2.1 stock to solve this i replaced stock with a custom rom where i could use app2sd ie: 2.2 or 2.3
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Hi,
I've got XT1068, updated to 6.0 Marshmallow. In the past, I got it FDE (full disk encrypted).
Few days ago I unlocked my bootloader to gain root access on my phone using http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
everything went as expected, but by unlocking it wiped all userdata, so I wanted to re-encrypt the phone (and the external SD especially). But now, encryption fails, telling me "encryption fails, you have to reset your phone" each time I start the encryption, ending in a userdata-wipe.
So I thought about going back to stock fw.
After locking the bootloader and applying stock 6.0 FW, I tried again to encrypt the phone, but I am still unable to do so.
Can someone help me giving some suggestions, how I can fix that behavior and (mainly) how to get some errors/debug shown?
When selecting "encrypt now", the green android symbol with black background is shown for 5seconds, then the phone reboots, shows the bootscreen with the M, then it restarts again (after ~30minute) and shows after another 20seconds the message that something went wrong encrypting.
Ok it seems that I found out the problem in my case by myself.
Instead of using mfastboot.exe -w to delete the data and cache partition, I used recovery mode to delete userdata. I did it twice, since the first run, returns some errors.
After reset, I started the phone and got the fresh-install screen. I skipped mobile and wifi networking and did not entered google account details. Then I restarted the phone and waited for ~5minutes and tried to encrypt - everything works. Everytime I started encryption without waiting for some time it failed.
I hope I can save someone else some time, since factory reset takes ~15minutes each time you do it.
Help
I had my phone rooted however recently it started rebooting every hour or so with sometimes rebooting back to home screen and sometimes giving this error
It also starts to get pretty hot
secure fail modem
Security Error: This phone has been flashed with an unauthorized software
I tried flashing the latest firmware and factory reseting
and even then the same symptoms however surprisingly when its setting up on optimizing app screen it doesnt reboot
or when its twrp boot screen it doesnt restart
I am not sure what to
Can someone please help me
latest update
so it turns out if i use a s7 ported rom where I need to flash a data fix and I dont flash the data fix my phone works fine
I obviously dont get any signals but it works fine and no reboots so if anyone has any clue of what the issue is
Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..