Hi,
since 2 days I have a very annoying problem: my GT 7510 reboots every 2 min.
this is not a bootloop! I can successfully boot and work - but only for about 2 mins.
then the device reboots.
What I had done:
due to low disk space, I deleted my old nandroid backups (pre 10.1) using 'file explorer'.
then I turned on the setting "root explorer" in 'file explorer' to access the newer nandroid backups.
I wanted to copy them to a usbstick. this failed.
So I decided to delete these backups as well (using 'file explorere').
this task somehow failed and the device rebooted unexpectedly.
since then, the device keeps rebooting after about 2 min.
what I had tried:
- install previous rom zip ( cm-10.1-20130116-UNOFFICIAL-pd4wifi.zip) --> no success, still rebooting
- reinstall latest rom zip on device (cm-10.1-20130208-NIGHTLY-p4wifi.zip) --> no success, still rebooting
- wipe cache --> still rebooting
- wipe cache + dalvic -> still rebooting
- factory reset -> still rebooting.
I am now back on cm-10.1-20130116-UNOFFICIAL-pd4wifi.zip (flashed over cm-10.1-20130208-NIGHTLY-p4wifi.zip)
I also noticed that I cannot do successful backups anymore.
in recovery > backup, it reboots while data is being backup up.
problem now is:
a) I don't have any backups anymore on the sdcard which I could restore
b) when trying to copy backups to /data/media/clockworkmod/ , the device reboots after 2 min (2mins not enough time to copy 4 GB dump
luckily, the 2min were enough to install 'remotelogcat'.
I run it on my notebook. the logcat is attached.
(the logcat output is an .html file which I zipped)
Hope someone can have a look and find out what is happening and why.
edit: attachment removed because I was able to solve this myself
Any help is appriciated.
tnx a lot
thg-droider
Update:
I did some test using adb (on Windows 7).
Findings:
- copying a handfull of files from tablet to pc works
- copying a handfull of files from pc to tablet works
BUT: when I try to copy an old nandroid backup from pc to tablet, the tablet reboots...
Question: is it possible that the internal sdcard of the tablet is somehow 'broken' ?
if this was the case: would the cmd in CWM 6.0.2.7 recovery potentially help?: "mounts and storage" > "format /data and /data/media (sdcard)"
anyone with a better idea?
tnx
Update 2:
I ended up formatting /data in recovery using "mounts and storage" > "format /data and /data/media (sdcard)"
Doing so, I obviously lost all my stuff.
But luckily, I had a (not to old) backup of TitaniumBackup, which I was able to copy from pc to tablet after the setup.
With this, I was able to restore most of my stuff. :good:
My persoanl lesson learned:
1. do backups on a regualar schedule!
2. save the backups to pc (or another media, e.g. usb stick)
3. don't delete 'old' backup files using a 'file manager', but use the 'delete' option in CWM > "backup and restore"
Related
As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).
Hello everyone,
I need your help. Sorry for the long post.
I have a OnePlus One. It was running on CM 13.0 (Android 6.0.1). I had TWRP and MultiROM installed.
I have had an issue where whenever I flash a zip file in TWRP, the phone will show an error after installing the zip: "Unable to mount storage". This appeared in red color on the screen right after showing the progress of the zip installation. The phone worked fine and all the flashed zips worked great as well. However, the error that appeared every single time when I flash a zip file bothered me. So I tried to fix it. (I know, if it's not broken don't fix it, but sadly I tired).
I followed this video to get rid of the error => (https://www.youtube.com/watch?v=X7yDPszoQ5s). However, instead of getting rid of the error, I ended up with a huge problem. My phone couldn't recognize the data in the internal storage. It showed that the internal storage was empty. When I tired to reboot in TWRP, It said: "No OS installed are you sure you wish to reboot". I realized that the video I followed was for a different problem and that I ended up with the same issue the video was trying to fix! I tried every single option the video suggested to fix the problem and nothing helped.
I connected my phone to my laptop and downloaded the latest CyanogenMod zip for my phone and I flashed it. when I rebooted my phone I got a screen that asked for my password. I typed a random password (I discovered later that the phone will accept any password and say it's correct). I got the following error: "Decryption Unsuccessful... The password you entered is correct, but unfortunately your data is corrupt... To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account...Then the only thing I can select is "reset phone." ". I pressed the reset button on the screen, the phone rebooted and showed the same error. Then I tired flashing PAC ROM and I got the same error again. Then I flashed OmniROM and the phone worked! It didn't show the error.
I have a Titanium backup for all my apps and I also have a nandroid backup for my previous ROM (in my memory stick using an OTG cable). However, I don't have any backups for my internal storage (photos, videos, documents... etc). I am guessing that these files are still in my internal storage. I didn't copy any new files to my phone because I think if I do, then the phone will keep replacing my old files (that I can't see) with the new ones.
My question is: Is there a way to get back these old photos and videos from the internal storage? Note that I didn't delete these files, but the phone can't read them. Also, I checked the nandroid backup that I have and the file system type of the previous ROM was EXT4. My current file system type is the same, EXT4.
Thank you for the help!
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
ic2e said:
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
Click to expand...
Click to collapse
use miflash to start fresh with miui, use miflashunlock to check if bootloader is unlocked properly, flash twrp, redownload the rom and gapps, start flashing through twrp
If you're flashing ROM, do not restore data.
Wipe system+data+cache+dalvik ,then flash ROM+gapps then reboot.
Don't restore anything from other backup
My galaxy S2 (gt-i9100) was running cm13 for about half a year. Some days ago I let google play update my apps. The result is a bootloop.
I've used the voice recorder to record a lot of notes I need to remember. Is there any way to get those files out from the phones internal storage?
The CWM recovery installed lacks the option to wipe cache / dalvik, which I would hope could get the device out of the bootloop.
When booted into recovery, I've tried adb, but the device is unauthorized.
I think usb debuging was disabled, however, I'm not sure about that.
The ideas I have to solve this are:
1) flash some other recovery that will give an option to wipe cache/dalvik and be able to boot cm13
2) flash some other recovery that will make adb able to pull the files while in recovery mode
3) flash some recovery that is able to copy files from internal storage to sd card
4) factory reset, and hope the files don't get deleted (this is the very last resort)
The thing is that it seems like I'll need to do all installations from SD card via the current CWM recovery. Does anyone know of a suitabel download / howto that can help me get my files off the phone?
If reason for boot loop is Xplore file explorer latest update , uninstall it with developer advices:
http://www.lonelycatgames.com/wiki/xplore/crash_on_cm
I did factory reset twice because of app.
Thank you, Kepsilla. Unless that is an app that is installed with cm13 or gapps, I don't have it installed. But your link gave me hope:
If you have custom recovery on your device (such as TWRP), enter recovery mode, open file manager and delete folder /data/app/com.lonelycatgames.Xplore-1
Click to expand...
Click to collapse
That means that if I can install TWRP recovery from CWM recovery, I should be able to access the filesystem. That should open up to two possible solutions:
a) Copy my files from internal storage to SD
b) Delete / modify some files to take all apps I've installed from play store will not start automatically.
Does anyone know of a TWRP that would give any of these possibilities and install on a i9100 using CWM?
(I can't really experiment iwht this - I feel the risk of loosing the files is too high. I have to know I'm going the right direction when I do something.)
Solution was very simple: By holding volume down pressed during boot, the device boots into safe mode - no apps started. Then I could just uninstall the apps that were set to autostart. Reboot and problem was solved.
I came across this way to enter safe mode when googling a error message that started to pop up frequently on my S5 mini. S2 with cm13 appears to have the same way to enter safe mode as S5 mini with factory rom.
Device: SM-G532G Galaxy J2 Prime
OS: 6.0
What Happened:
I tried to root using a CF-AUTO-ROOT image and Odin and got stuck in a boot loop. Then i tried few other stock Roms (<20MB in size each of them) got it working/boot somehow. But all my user data is missing now.
Problem:
Device used to have 8GB Rom with around 2.5-3.0GB free space before this. But now it shows only 1.44GB when i check storage on PC. and shows 7.84GB as system/user data in system storage menu.
Desired Solution:
I need to access my previous user data (specially SMS). That's all.
(So factory reset and wiping which are the common fixes for this are out. )
What I have tried so far
1. TWRP - installed TWRP and tried rooting. (cannot view the zip file as it shows cannot mount /data error in log)
2. Trying with ADB to view (at least) the user data but had no luck. (may be i might be missing some step and ROOT of course)
is this something like i have manged install 2 OSs on the phone somehow (like dual boot without the correct bootloader) or some thing else?
Any help/guide is much appreciated. Thanks.