I'm on Miui. I was having wifi problems, reboot wouldn't fix it (it would just say Error instead of On/Off). So I went into recovery and wiped Dalvik-Cache. Did reboot. After 30 minutes, it was still on the X screen. Hooked it up to computer, did adb reboot recovery. I can get into recovery, but it wont boot into Normal. Any suggestions, besides restoring my 3 month old Nandroid?
Wiping dalvik shouldn't cause any problems, because Android should regenerate any files that are needed.
I would probably start with wiping the /system partition and reinstalling MIUI and gapps.
What he said. Also, you can try adb shelling in and seeing what the output in logcat says. Might be as simple as one app getting corrupted and needing to replace it.
I doubt adb will kick in with the X screen. I don't think it kicks in until partway through the Android bootscreen (no idea what MIUI uses for their bootscreen).
ADB daemon fires when the "X" screen is about to finish.
In any case, my suggestion would be the same - attempt to reflash ROM and fix permissions, and if it doesn't work - then restoring the backup would be the best option.
I tried wiping /cache and Dalvik-cache again. Waited 2 hours on the X screen, nothing happened, the phone would randomly vibrate though. "adb logcat" just produced a never-ending overflow of text. I ended up using "adb reboot recovery" to just restore my backup. Didn't lose too much thanks to TB and MyBackupPro. Thanks anyways!
Do you have sd-ext enabled?
Sent from my Nexus One using Tapatalk
I have had this problem while running the MIUI ROM. I assume you had your dalvik moved to SD using a2sd. That was the problem for me. I was able to consistently repeat this problem while I was using this ROM. It is one of the few reasons I switched back to CM. Unfortunately I never found a way around it besides wiping the entire ROM and installing fresh.
Related
I am using android NAND for a pretty long while now and it always worked great. Untill this 1 night i forgot to charge my phone and all battery is drained. So the next morning i turned my phone on with the charger in and things seemed to be ok and i went for coffee.
When i came back the screen was stuck on the startup, the black screen with "HTC" in the centre. So basically its starts up, MAGDLR does it thing and then this "black HTC" screen shows and gets stuck. Tried removing battery a couple of times and still the same.
What is the best solution for me to do now?
If losing your settings and data isn't a problem (I.e you keep a decent sync routine) then I'd do.....
Enter cwm , full backup, wipe cache and dalvik cache
Reboot,,, fixed?
No..
Into cwm, (you already backed up), wipe data factory reset,
Reboot, fixed?
Yes, see *1
No, start from beginning, full wipe, reinstall rom. Once its working, see *1.
*1 once you have the fresh unset up rom running, (and assuming you are using an ext partition) I'd go to cwm, do another full backup, and then try an advanced restore of just the SD ext partition, (then clear dalvik, since some variants of a2sd move dalvik to SD, and u don't want that restored)
If that's successfull, you will have restored all your installed apps.
If you don't have an ext partition, you could try restoring the data partition, but it'll likely restore the error too.
I did these steps as written but somehow it didnt work. Only on the first boot up it worked. So ive put another android rom on it and its working now.
Thanks for the help
The title says it: My TPT is bootlooping and when I try to wipe the cahce/Dalvik-cache in recovery, it just won't finish.
I'm running ICS (OTA3), but the same thing has happened to me before with Honeycomb.
I don't want to wipe data! Any ideas?
You qualify for a new motherboard if you want it.
But that would not preserve my data
My understanding, and I could be wrong, is that once you start boot looping you need to have made great backups prior to the issue because all you can do is send it in for repair. Hopefully you have such backups if you have root.
Not good news so I hope I'm wrong. Wishing you luck.
I pulled some of the data via adb and then did a factory reset (in recovery). Now it boots again.
I just hope it won't happen again. This was the second time already: Once it started bootlooping in Honeycomb and now ICS. It just came out of nowhere (it booted up fine many times before).
Excellent news. Didn't think you could pull anything with adb while bootlooping. Should have tried that straight away.
I still could enter the recovery mode. Strangely, wiping cahe/dalvik cache alone didn't work (it wouldn't wipe), but wiping everything (which also includes dalvik cache) worked...
I still lost some important data, but at least my tablet works again. I just hope it won't start bootlooping again... but I'll definitely make sure to have an automatic backup solution set up just in case.
Good show. At least you're not bootlooping. Too bad about the data.
My issue is this -- my phone will be running fine for days, even weeks, and will then spontaneously reboot. The phone will then get stuck on the Android "Starting Applications" step and never get any further. I've attempted to wipe cache and Dalvik, and even gone so far as to re-flash the ROM I happen to be running at the time.
This has happened to me at least a half dozen times, and it's starting to frustrate me. I've had this issue with at least 4 different ROMS, including CM 10.1, PA, AOKP, and at least one mixed feature ROM. The only solution I've found at this point is to do a factory reset and system wipe and start from scratch.
Any suggestions on what I might try next time? I'm really at a loss.
dont wipe or clear data after you flash a rom. flash rom and if it installs correctly then clear the cache and thats it. then let it reboot
i used to get stuck in that same screen, but thats because i was clearing data after i had flashed a rom. hopefully that helps
Had this issue. Do a stock flash with the toolkit
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
go to recovery, do a factory data reset.
I recently decided to take the oplunge and un-moto my Defy with a Quarkx CM 10.2 build (cm-10.2-20130801-NIGHTLY dev thread:http://forum.xda-developers.com/showthread.php?t=2385250).
I've been running it for 2 weeks or so without what much trouble until this morning, I forgot to plug it in, so it discharged over night (was working before i went to sleep). I had some trouble powering it up this morning, figured it was discharged, now it does not boot at all, and has not booted yet. It sticks to the CyanogenMod boot icon.
It's currently charging at 100% for a wile longer (as per these instructions http://forum.xda-developers.comhowthread.php?t=1778492), but i don't know what to do next without a re-install.
I have some other specific bugs to report but cannot post to the dev thread ( as i'm a Newb and this is my first post.
- Voice capture/use with BT Headset (known)
- BT on cannot use headset mic (known)
- Focus+Camera problems (Known)
- ~10hr battery life (known)
- Bare GPS without extra google assistance not working with Maps threshold to high? (?)
Backup data from recovery, reinstall cm10.2, don't wipe data, wipe cache. If it doesn't work then wipe data and cache. You should get it to boot, and then restore apps from backup using titanium backup
Look for the GPS thread in General, edit the file as given there. Should help with the GPS locks
Sent from my MB526 using Tapatalk 2
thekguy said:
Backup data from recovery, reinstall cm10.2, don't wipe data, wipe cache. If it doesn't work then wipe data and cache. You should get it to boot, and then restore apps from backup using titanium backup
Look for the GPS thread in General, edit the file as given there. Should help with the GPS locks
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I used TWR to clear the davik cache, and the system booted, then did the davik byte compile ('Android upgrading apps screen) then went to starting apps anf failed there. I will as you say, but before i do, is there any way of tracking down what is happening? I'm mounting the various fileystems from the boot USB mount tools, and would like to know where to look for some logfiles or other.
I have been poking around, (using ls -alrt to see what was last accessed) and not come up with anything, so now i want to watch boot messages with adb logcat (as described here cyanogenmod.org/w/Doc:_debugging_with_logcat) , but i have no idea how to enable them. Its either that or try and figure out how topipe the kernel console over USB.
Which is redonkulous because if the davik is compiling, then its not a kernel problem, its something else later in the boot sequence, long after adb/logcat should be throwing out errors.
Any pointers? I would honestly like to fix this instead of wipe, because I have not got a Titanium backup knocking about of the phone prior to this failure. Or rather i do, but its a week or two old.
It's not a kernel issue. Most likely your data partition is corrupt, and there is really no easy fix for that. You should first take a backup of it, and then you could try to salvage it using titanium backup (if really lucky) or a Linux distro to try and recover some data(it's basically a ext4 partition image)
I don't think it can be fixed from the device end.
For boot logs: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Enable adb in boot menu before that
Also, kernel logs can be obtained via a UART cable. But I'm not sure how they can help you fix this issue
Sent from my MB526 using Tapatalk 2
Something in Data was the problem.
I had to do a complete reinstall and rebuild to get it working.
Is there any way to avoid/diagnose this kind of problem other than daily backups and making sure it never ever runs out of power (the battery reporting is all over the place!)
thekguy said:
It's not a kernel issue. Most likely your data partition is corrupt, and there is really no easy fix for that. You should first take a backup of it, and then you could try to salvage it using titanium backup (if really lucky) or a Linux distro to try and recover some data(it's basically a ext4 partition image)
I don't think it can be fixed from the device end.
For boot logs: http://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging
Enable adb in boot menu before that
Also, kernel logs can be obtained via a UART cable. But I'm not sure how they can help you fix this issue
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I hack embedded linux as a day job, so know something about this already, though I'm a complete cyanogenmod/rom hacking newb.
I tried most of the things you suggested, at least to the point of booting with logcat. Nada.
The problem seemed to be that adb was not coming up. I used the bootloader adb shell to try and force adb to come up (changed an enable from disable in the init.rc) it seemed to make matters worse, so i went for the rebuild.
I performed a TWRP backup of the system and data partition before doing any of this. I know the backup was working because i restored the system partition and blew away the data partition, and it booted.
What i want to do now is restore some of the data from the data partition (call logs and SMS etc, everything else can be re-created). How, where would i look for that?
t1moc said:
I hack embedded linux as a day job, so know something about this already, though I'm a complete cyanogenmod/rom hacking newb.
I tried most of the things you suggested, at least to the point of booting with logcat. Nada.
The problem seemed to be that adb was not coming up. I used the bootloader adb shell to try and force adb to come up (changed an enable from disable in the init.rc) it seemed to make matters worse, so i went for the rebuild.
I performed a TWRP backup of the system and data partition before doing any of this. I know the backup was working because i restored the system partition and blew away the data partition, and it booted.
What i want to do now is restore some of the data from the data partition (call logs and SMS etc, everything else can be re-created). How, where would i look for that?
Click to expand...
Click to collapse
You can restore the call logs and stuff using nandroid manager.
hotdog125 said:
You can restore the call logs and stuff using nandroid manager.
Click to expand...
Click to collapse
Thanks! That worked.
Though before it did i had to do some cleanup of .comp.comp.comp.comp files - failed decompressions i guess.
nandroid is now going on my essential apps list
Well it happened again.
I was having trouble turning off bluetooth. MortPlayer Audiobook player had decided to keep hold of the BT connection after i stopped the player and turned off the headset. So i tried a reboot, and the phone has not come back up again. Which is annoying because it has been working fantastically until now.
The link to get the adb log does not work. adb does still not come up during the boot sequence.
again like last time I started up adb shell to have a poke around on a running system, and again after 10 minutes the system powered off, and would not power on. Even though it was/should be charging over USB. Now i plug it into the power, and the batter charge indicator comes up saying 5% power. So no idea about how to stop that happening. So far though the boot menu and TWRP works like a charm.
I really want to track down whatever this issue is, but so far hitting a wall. Is there some where i can splice in adb coming up? or get the dmesg/syslog/adblog written the the sd card so i can attempt to analyse the problem?
Hi!
I recently updated my ROM to the Paranoid Android 3.98, I did a full wipe, flashed the ROM, latest Gapps (with TWRP) and ever since the tablet has been become really laggy on opening apps or doing anything. I realised something was wrong straight after I booted it up by how long it was taking to connect to the WIFI etc.
Anyway, its hanging a lot on the unlock screen and sometimes I get a "Process System is not Responding" prompt. I've tried going back into recovery and clearing the caches/data again and its still hanging. Ive also tried using CWM recovery to wipe the tablet, flash the ROM/Gapps etc and its still really slow. Lastly, I just tried a factory reset from the settings menu and again, its still the same!
Any ideas on whats up with it and how to sort it out? I was thinking about unrooting it back to stock although I think the problem will still probably happen. I came from the PA 3.95 build and did a clean flash.
Cheers!
Chris
I think I have fixed it by following a post by Chasmodo on how to do a super-clean install.
1) I booted into recovery.
2) Did the three wipes (Data, Cache, Dalvik) several times over.
3) Went to Mount & Storage and formatted both system & cache*.
4) Flashed PA 3.98 & latest PA-Gapps.
5) Wiped both caches again and rebooted.
As soon as connecting WIFI, signing into Google I could tell it was running a lot faster again and now the lag on the unlock screen & opening apps seems to have stopped, also haven't had the "System Process isn't Responding since."
*Chasmodos version of the super-clean install didn't say to format the cache as well although I had tried just formatting the system and it didn't fix the issue. So I thought I'd try the same process with a cache format as well and now all issues seem to have been rectified.
Cheers
Chris