it is called by init.rc, which can be killed at any time after boot, although it restarts immediately. nothing wrong if i killed it repeatedly, so i replaced it with a script and no problems occured. however, after i rebooted the phone, it wont boot properly right after the bootup sound is triggered and i had to restore /system by rom manager
by assuming it's actually for tv out function, i really want to prevent this from running/or to remove it completely
any idea pls?
thx
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
Good morning guys,
I'm not sure how to explain the problem.
It started when I downloaded Telegram (Whatsapp + encryption = <3)
The phone crashed and the problems began. Everytime it started, its trying to download Telegram again and sais, that there is an error.
Also it randomly crashes.
And somehow my phone is loading a "image" each time its starting.
That means, i can flash, change, root, whatever I want to do, but as soon as I restart the phone, its booting into the same.
Hard to explain. Whatever I changed, send or recieved - dissappeared.
TWRP somehow also doesnt work, its not even booting in it.
Also, I cant get into the Bootloader, as soon as I do the Vol+ Power combination the Samsung logo appears and nothing happens, i have to pull the battery our to restart it. Well, the phone vibrates once, but thats all.
In the download-mode Im able to flash with Odin, but that doesnt changes anything after the restart.
Im not sure, maybe I clicked RE-Partition while trying to fix it or my flash wasnt clean or sthing like that, but atm the phone is unusable.
Hope you got some ideas
-maverick_skaw
Hi,
I have the same problem.
Somebody, any idea?
MaverickSkaw said:
Good morning guys,
I'm not sure how to explain the problem.
It started when I downloaded Telegram (Whatsapp + encryption = <3)
The phone crashed and the problems began. Everytime it started, its trying to download Telegram again and sais, that there is an error.
Also it randomly crashes.
And somehow my phone is loading a "image" each time its starting.
That means, i can flash, change, root, whatever I want to do, but as soon as I restart the phone, its booting into the same.
Hard to explain. Whatever I changed, send or recieved - dissappeared.
TWRP somehow also doesnt work, its not even booting in it.
Also, I cant get into the Bootloader, as soon as I do the Vol+ Power combination the Samsung logo appears and nothing happens, i have to pull the battery our to restart it. Well, the phone vibrates once, but thats all.
In the download-mode Im able to flash with Odin, but that doesnt changes anything after the restart.
Im not sure, maybe I clicked RE-Partition while trying to fix it or my flash wasnt clean or sthing like that, but atm the phone is unusable.
Hope you got some ideas
-maverick_skaw
Click to expand...
Click to collapse
R. T. F. the guides on general and Q&A section
Hi, this is my first post. I have tried to search and look through the question threads, but nothing seems to be close to the problem I have here, hoping someone can help me.
I have this Xperia TX, recently given by my friend, it can boot up ->sony->ribbon-> entering system->shutting down, it's not like a sudden blackout but more like a command sent telling the phone to shut down, it has the window saying shutting down and vibration at the end, but the shutting down is instant, can't operate yet. I made several approaches trying to fix it, these are what I have been done with it.
-Flashing different stock ROMs using flashtool, the flashing went perfectly without errors, and phone will boot and install new system until the setup wizard (languages, time etc) comes out on screen, and it shuts down right away.
-I used flashtool to unlock BL, succeeded.
-I flashed TWRP, it can boot into TWRP without any problems and working fine.
-I formatted the phone partitions using TWRP, working fine.
-I flashed cm-12.1-20151010, and same thing happened as soon as the system launcher comes out.
-And I flashed stock ROM again, the problem remains.
The phone won't charge the battery, so I tried using a separate charger avoiding 0 battery situation (I do see the battery icon showing 50%+ when it shutting down), and I also tried another lt18i battery (don't want to buy a new one yet in case the phone is dying), and there is no different.
I don't understand the problem, all the operations work fine but can't boot in system, doesn't seem like a hardware thing but what else can it be? I am not hoping to fix it any more at this point, but can anyone tell me what could possibly cause this? Can I read a boot up log somewhere so that I know what happens during booting?
I hope I didn't break any routine or do anything wrong here, if I did, apologies in advance, thank you.
Hi all.
So this is quite strange (i think).
I managed to root my s20 fe 4g using magisk with the help of some people from here and a guide.
I have played around with it, installed some stuff, uninstalled some apps (using titanium backup) and was all well.
When I went to restart the phone to give it a clean break, it now wont load up again. Just gets stuck on the 'Phone is starting...' screen. Now this isn't a huge problem, i thought I couldjust flashthe stock firmware again and root the same way and perhaps it will be well. The problem is it wont boot into download or recoery because it is stuck in a cycle of trying to start itself. I can force it to restart by holding the vol- and power button, but that is the only combination that will make it restart, it instantly restarts before i can change the keys held to try and get it into download mode.
Does anyone know what I can do to try and remedy this so it will start again?
UPDATE:
I think i stupidly must have deleted the one ui launcher by mistake... Now I am trying to get an APK to the phone, but ADBdoesn't recognise it at the 'phone is starting' screen. My phon is at dead stage, so i can get it to boot into download now, but it doesnt seem to want to go into recovery, and i think its stock recovery, so not sure if ADB will work?
Any other suggestions to get the launcher apk pushed and installed?
if you can get download mode flash the rom again, hopefully you still have it from rooting.
don't use titanium backup to uninstall system apps. even using it to freeze apps can be a problem if it's not gonna boot up.
get a copy of a safe debloat list and stick only those listed packages that others have found to safe to deactivate.
I didn't do anything unusual, but I found my device can't boot even in safe mode
I tried using the original boot.img and it booted fine, but then I can't get enough permissions to remove the module might causing the problem
Is there a way to resolve it?