Hi,
I still have an old v10.0 cyanogenmod on my i9300, a nightly build from August 2012, because there never has been a stable release.
Recently i have found my mobile (having only 2% power less) try to switch off, but it seems that it wasnt impossible for the OS to switch off and so it restarted without having power. Because it was in the night, I just found my mobile in the morning with a bootloop and no power. Even after pluggin the mobile to power and first charging to 100%, I still cannot switch it off. After switching off, it instantly reboots.
The worst problem is, that it is not able to boot. I only see the cyanogenmod boot logo rotating.
With the recovery mode I can access to both sd card and onboard storage. I have downloaded the aroma filemanager and have done an e2fsck with the onboard shell: no problems, everything is fine!
Have cleaned dalvik cache and cache partition: No changes in the behaviour.
Then I have updated the cyanogenmod OS to the latest 10.0 version: cm-10-20121214-NIGHTLY-i9300, but: no changes in the behaviour.
Then I have done an "adb logcat" bootlog, there is a loop caused by a fatal errror in the ActivitiyManager, after each fatal error there is a loop and the mobile tries another time to boot and the log nearly repeats. I have attached the part of that logfile, which repeats every time, means: after the last line of that log you can place the first line of that logfile, endless.
I don't want to upgrade to 10.1, 10.2 or 11, because I still have some important data like wechat and whatsapp msgs, game saves, and so on, which I dont want to lose.
Does someone has an idea, what I can try to do?
Big Thanks!
Related
Hello everybody.
I have a huge problem and basicly it is my fault. Yesterday i repartitioned my microSD card and created swap partition. Just to see if it works. I used swapper 2 to activate this. After this operation phone was working as usual (it was official nightly build of CM 10.2 from 19.09.2013). But...when i rebooted, the phone was stuck on Samsung logo (So yes, even CM bootloader didn't start working). It was 1 A.M. so i was nearly sick with this, but fortunatelly CWM and Odin mode were working. So did battery recharge. Odin and battery still works.
I have tried cache wipe, full wipe, installing another CM version (10.1.3 - via CWM), installing official samsung firmware ( I9300XXEMG4 - i checked in odin only Auto Reboot and F. Reset Time) - whcich resulted in removal of CWM. But it is always stuck on samsung logo, so system itself is not booting. Filesystem is more or less OK, because i launched astro file manager from CWM and was able to copy most of my data.
I tried to do adb logcat when it is trying to boot. Windows recognizes device as "Samsung Mobile MTP Device" after ~20 seconds from turning on, but it can't load drivers for it.
Please help. I am really grateful for any answer.
------------------------------------------------------------------------------
Solved. It turned out that /efs was somehow wiped.
hello there guys
i have nt 16gb
i installed cwm 6.0.2.5 emmc version
and then i installed cm-10.2.1-acclaim.zip
all went well and the device booted fast
but whenever i restart or turn off the device
it wont boot any more
it pass the cyanboot screen to a black screen and stays there
wiping does solve the issue until next reboot
plz help
do i have to change the cm to an earlier version
does the gapps has anything to do with this , i didn't install it
This "boot into black screen" or "boot crash" is, unfortunately, a known and unresolved problem with 10.1.3, 10.2.x and also some 11 builds -- see http://forum.xda-developers.com/showthread.php?p=48305694#post48305694, http://forum.xda-developers.com/showthread.php?p=49046310#post49046310, http://forum.xda-developers.com/showthread.php?p=48301259#post48301259 and http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94.
You might want to give the CM11 Snapshot M4 build a try (see http://forum.xda-developers.com/showthread.php?t=2670589 for how to upgrade to CM11), as I have not run into the issue with this build.
what about 10.1.2
i tried 10.1.2 and it worked
but it has some issues
there are some apps that doesn't work like candy crush and sumle apps
and nt shuts down when it has 25 percent
it shut down and stuck in a restart loop till i plug the charger
any idead?
The phone is rooted and has a few Xposed modules installed; stock ROM.
I shut the phone down every night. When I wake up and turn it on, every now and again it gets into an infinite boot - not a bootloop (at least not in my understanding). It either stays on the LG logo or the Tmobile logo. Sometimes it boots just fine and quick, sometimes takes a minute longer. Other times I have to hold the Power + Volume Down for a few seconds to reboot it, and it boots fine after that. Yet other times, I have to get into the Factory Reset mode and rebuild the Dalvik cache form within TWRP, after which it boots fine.
The weird thing is that when nothing is changed from the moment it loops to the moment it boots fine; it may only be a reboot away. Granted, I do have (quite) a few things frozen and/or removed in Titanium Backup, but should it affect the boot?
Has anyone experienced anything like that?
Attached are the warnings and errors captured while LiveBoot was running. The lines go really fast, and Nexus 5 shutter isn't capable of going that quick (that's why you can see double lines in certain places). The phone booted after I switched to my swap battery.
Just an update, I restored the earliest Nandroid backup and instead of uninstalling these apps, I froze them in TB. No boot issues so far.
Another update. This morning the problem seems to be back, it was stuck on the T-Mobile logo. Although I can rebuild the cache, it's worse now, because I haven't disabled any LG or system apps since the last restore.
Update to this update: after the T-Mobile logo reboot, it now stuck again on the LG logo and took two 5-minute waits before reboots; it booted fine on the third (essentially, the fourth) reboot upon swapping the battery.
Does anyone else experience this?
Hello Everyone,
I own a Motorola quark XT1225 64GB indian version. I had earlier rooted it and installed Lineage OS 14.1 (Unofficial) in it. The installation was without any issues and worked for few months then one day i pressed the power button to turn on the phone and it went into a boot loop and nothing would work. i gave it to a repair shop and he installed android 6.0.1 in it and gave me back. But my phone wont connect to WIFI and later i found out that there was no IMEI or any network related information left in it. only the OS booted and nothing else was working. Even the Developer options were not available as for some reason tapping the build number was not giving any result. he refused to fix it. I tried a factory reset from the settings menu with no result. even the recovery was not available any more in the phone. I tried installing new android stock images both for android 5 and 6 first from RSD lite and fast boot mode which kept failing and then i tried it using the command promt. After installation was complete the phone rebooted and android appeared with erasing written under it but then it went into boot loop and would keep restarting every time android appeared. I tried installing TWRP recovery from the command promt the initial image of the recovery appears but then next second it says unable to mount data and keeps rebooting again and again. Kindly suggest ways to fix my OS as well as have my IMEI restored.
Really need help.
Thanks a lot.
So mom dropped off her old Xperia Tablet Z SGP311 as a "gift". It did not work for her anymore, so if I wanted it and could fix it then I would have another tablet in the pile.
Her description of what did not work was what you would expect from a non-techie aka "some error turned up but I cannot remember what the screen said, so can you fix it?".
In the beginning I thought the problem was the common USB/charging problem, however I feel anything about this tablet seems different than other Android tablets, so after finally managing how volume buttons along with power buttons work, I could rule out it was a charging issue.
Getting the Tablet to boot it seemed that it had been updated and was booting into OS doing the "optimising applications 1 out of 258". However going to the step "starting applications", then tablet would just reboot a few times and then start over with optimising applications, starting applications, reboot and repeat all over. So some sort of bootloop.
I then used Sony's Xperia Companion to repair the tablet from fastboot (volume up + power) which succeded until it should reboot the tablet, then I was stuck in the same loop as above.
After a few tries I then managed to unlock bootloader and get TWRP 3.2.2 booted onto the tablet (booted NOT installed since I have no root).
With TWRP I tried deleting Dalvik cache etc., which did not help the situation, same bootloop.
With TWRP I then gave LineageOS a shot, but LineageOS experience kinda the same bootloop (both LineageOS 14.1 and 15.1).
LineageOS boots fine and proceeds with the fresh install questions (region, timezone, Internet access) but as soon as I hit next on the "Location Services" page the tablet will reboot.
Since this tablet has no value to me, I have tried deleting all data on all partitions from TWRP, I have checked the filesystem with e2fsck on the tablet which shows no errors, but in any attempts it simply reboots at the same stage every time.
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
bjoeg said:
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
Click to expand...
Click to collapse
probably memory problem either RAM or ROM.