I tried editing the floating-feature.xml to enable clock animations, but after restarting and entering my SIM card's PIN code, There was only a black screen with my battery percentage and the time displayed on the top. After 30 seconds, it restarted and enters into recovery mode. I'm not sure how to resolve this issue. I managed to get the device into systemui safe mode, and tried editing the floating-feature.xml file again. But, even after fixing what I changed, the issue
is still there. I don't know how I got the device into systemui safe mode, and I don't want to reflash the ROM and lose all my data. I haven't backed up my images and files in a while.
nvm i fixed it by reflashing the same rom but using the home_csc insted of csc
Related
Starting this morning, my Nexus S is stuck in landscape mode.
When I fist boot up the phone, it seems to launch directly to the desk cradle mode, but it has never been connected to one.
Everything is landscape even the launcher. I can't use the phone because I can't reach the OK button for the SIM card PIN enter screen.
Factory reset didn't help. The inital setup is portrait, but after that it reverts to landscape.
Any ideas? Might this be a hardware problem?
EDIT: Android 4.0.3
EDIT2: I applied the VQ8PQk_V.zip OTA update manually to my stock 2.3.6 version. After a factory reset, the phone works as normal until the first reboot. The accelerometer is still working, i tested it after a factory reset before rebooting the phone.
Up
Sorry me for waking up this thread from his graveyard after 3 month.
I have an i9023 with the same issue of Tocharius:
my device is stucked in landscape mode and when i try to turn on it I cannot enter PIN code because OK button is outside the screen. The only way I have to make it works is to wipe data partition and everything works fine until first reboot.
In addition to this problem fastboot has stopped recognizing my phone, while ADB still recognise it.
When the issue firstly appears I was under CyanogenMod 9 v6.0 (Kalimocho).
I tried to flash other ROMs, but nothing has changed.
I tried to revert to stock, but nothing has changed.
I tried to open the phone, clean every connector i found, but nothing has changed.
Someone can help me?
I got this problem too. Lately I installed CodeNameAndroid 2.0 http://forum.xda-developers.com/showthread.php?p=25941996#post25941996 and after reboot my phone got stuck in landscape mode. I tried to reflash the rom and everything was fine until a reboot. Wiping data and resetting factory helps until reboot. I flashed another rom http://forum.xda-developers.com/showthread.php?t=1588799 and again the phone was stuck in landscape after reboot. I tried all rotation settings but nothing changes.
I was browsing settings searching for something that could fix it and turned adb debugging off and on and now it is stuck in portrait mode.
Yesterday was watching a youtube video on chrome and just lost systemui, was able to finish the video, and after that phone did nothing else, had to restart...
it plays boot animation and after that there there's just a black screen (backlight on) and nothing else, (phone does not ring if a call, volume keys make no sound)
PS: Since I'm on 4.4.2 with ART, usually it tries to update/optimize one app and after that, there comes the lockscreen
but now, not even try to update app...finish boot animation and there's nothing else....
I know that a dirty install is not good, but since I just need to recover some files (then do I make a clean install)
I guess dirty install is my best option to recover files
my phone is a XT1033 retail_br, with bootloader locked, so i'll need a stock rom*
*= guess a 4.4.2 or 4.4.4 would be the best match, but i'm not sure
can someone help me finding the right files and also explain how to flash a new room and keep user data?
Thanks in advance for anyhelp
Stock ROMs are available from here. Get the correct file for your exact model. You could try flashing these ZIPs through TWRP and seeing if it boots.
If that doesn't work, you could boot into TWRP and use the 'cp' command in Terminal to manually copy files from the /data/ partition to /sdcard/.
Hello all, so after reading a post on how to change your boot animation on the Samsung Galaxy S6 (G920-F But applies to other variants)
I gave it a try, and I decided to use the method where you transfer three files to system\media. So I did, and upon restarting the phone, it wouldn't restart, but instead black out for a few seconds then go back to the lock screen. After this, I panicked (Thinking that I broke it) and reverted the old files to where they were (From a backup I made previous to changing it) and it still does not work. Is there something I can do without reinstalling the ROM (Which in question is the stock ROM) or a method without posing my data? If not, they'd be the last resort. I do have root access (Rooted with CF-AUTOROOT)
Side note: The exact same thing happens when you try shut it down as well, and the only way to shut it down is to use an app that executed a script to shut it down, or booting to the recovery and shutting it down from there. I'm using TWRP recovery. version 3.0.2-0-zerolte (That is the name of the TAR I used to flash)
I was thinking about this for a while and I have this question; Is there a way to log everything the phone does before running into errors, causing it to go back to the lock screen after restarting/shutting down?
If there is any other way to restore it or troubleshoot it, please tell me. I'm reinstalling the ROM as a last resort if anything else lets me down
Other than the boot animation errors I've been having, the phone has been working just fine. Just it boots up way faster then it is meant to do when powering on (No one's complaining about that)
I switched off my phone (Motorola Z2 force, XT1789-06) during ringing. I am not sure if this caused the problem, but since then I can't switch it on. During booting, when it starts to show the animated "Moto" logo, it restarts booting, so I can't get to the normal graphical user interface. If I don't touch it, it repeats rebooting until its battery gets empty. It is not rooted, has latest official Android (version 9, I think, nash_retail) on it.
Until now the only thing I could do is to boot into fastboot mode. There I can log in into recovery mode or do some diagnostics, check some logs etc. As far as I can tell they show no problems at all. Except maybe "failed to read fstab from dt" in /tmp/recovery.log -- is it normal in recovery mode?
I tried some manual reboots from fastboot/recovery menu (on the phone), with and without SIM card inserted, with and without being connected to the charger, but they changed nothing: the phone keeps rebooting at the same stage of booting.
I hoped to be able to adb connect to the phone and pull the files from it, hoping I could use these data after a reinstall. But adb devices show no connected devices. I guess adb is not available in this stage of Android loading. Or is it available somehow?
fastboot devices show the phone, but I am not sure what can I do without triggering a factory reset. E.g. what if I would 'fastboot flash boot boot.img' from the stock ROM? I guess something went wrong on the boot partition, so rewriting it could solve the issue. But I afraid rewriting the boot partition would result in a complete factory reset.
My questions:
* what to try to make the phone booting normally?
* can I change boot config to skip logo animation?
* if booting normally is not possible: can I somehow copy my files from the phone to my laptop (linux)? If I can copy them: is it realistic to be able to use those files to restore the apps' states after a reinstall (after a factory reset)? I would like to keep e.g. my phonebook, SMS, Whatsapp and Signal chat history, OsmAnd favorites, Colornote notes, AndOTP credentials, etc. (I have a backup of some of my files, like photos or gps tracks, synced to my laptop with SnycThing automatically, but many others are not backed up recently.)
* if backing up my data is not possible: can I try to fix the booting issue by e.g. flashing a new boot.img without risking a factory reset? What exactly should/could I flash?
* if none of the alternatives above work: are there any other thing I could try or shall I simply accept the data loss and do a factory reset from fastboot menu?
Thanks a lot for your help and ideas in advance,
Peter
Hello everyone,
So I have a rare issue. I have a OnePlus 6. Today, it started to act really weird. It became so slow that even swiping on home screen with no apps opened takes like a minute to register. I forced power off the device. When powering on again, it seemed like it take around 10 minutes or so to boot. Again, extremely slow. I tried everything from restarting and clearing app cache while in the system itself but no luck.
So, next thing I booted to recovery mode, typed my pin, and cleared system cache and settings. It started to progress until just a tiny bit left before the end of the progress bar, and it got stuck again. Kept like this for a long time. I had to force power off the device again. Now, when I try to power on the device, it launches into Recovery Mode. I tried my pin but it wouldn't decrypt and looks like the device is no longer recognizing it. I tried a couple of "default passwords" but it wouldn't work either. It only gives the option to "Forget Password?" Which should wipe everything off the phone. The only other mode it launches into is Fastboot Mode. I'm using Stock everything and Device State is Locked. I'm not sure where to go from here.
Now my question is, is there any way I can open my device again without losing data? Maybe some way I can pull files using adb in that state then factory reset? Or maybe someway I can bypass Recovery Mode and boot again? I have important data that I can no longer access if the only way to fix this is by wiping everything!
Can anyone help? Much appreciated in advance.
When a phone permanently boots into Recovery mode then either Android OS is corrupted - for whatever reason - or phone's bootloader is misconfigured.
If phone is accessible by either ADB or Fastboot you can try to exit Recovery mode by forcing phone to boot into Android OS ( Normal mode AKA System ) by applying the related ADB and/or Fastboot command.