I'm running CM 7.2 (android 2.3.7) and I'm facing some problem here. How can I know weather it is a reboot or runtime restart? It starts with lag, then into CM boot animation (skipping HTC logo) and then prompt for PIN. After the boot (or runtime restart), I launched CatLog ASAP to read the logs to find out what's that problem but maybe my phone is running too many processes and cleared those earlier log before I'm able to read those logs. The first line of the log shows starting processes (and many lines after the first too). So if I wanna read those earlier log, I need to wait until the next time the bug appears and read it via adb.
Edit: Up time did not reset. And it's even bugging in my SE Arc running CM 9. CM or what?
Can I know weather it's a reboot or runtime restart without reading logs? (Well I'm a little curious and I think it's a runtime restart, but not very sure.)
Related
About 10 days ago i decided to flash cyanogenmod 7.2 RC1 (my phone was running Andromodus Audacity before). Everything was running perfect, until today.
When I turned my phone on, it boots into cyanogenmod and eventually I can see my homescreen. But after about 20 seconds it reboots itself. It boots into cyanogenmod, and the same things happens again.
So, i rebooted into recovery and flashed cyanogenmod again (and of course wiped data/cache/dalvik).
But even with a fresh rom installed, it still happens again. Dont know why?
So is there any solution to this problem?
Superwipe and flash again?
Sent from my Desire Z running CM7.
steviewevie said:
Superwipe and flash again?
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
With superwipe, you mean format data/cache/system/dalvik?
I already wiped these and flash cyanogenmod again, but didn't solve the problem.
Ok, now I understand what Superwipe means.
So, I tried to flash the normal Superwipe, and reinstall Cyanogenmod, but the same thing occured again. I even tried Superwipe+, but still doesn't solve the problem.
I also tried flashing an different rom (MIUI), but even with an other rom, the reboot still happens
I tried Superwipe again, but still the same. Then i tried Superwipe+ again, and i'm now in Cyanogenmod for more than 5 minutes!
So, i think that this problem is solved!
you can always try fastboot -w, its even cleaner than superwipe but of course you need to be at a computer
Sent from my M723-GDX using xda premium
Might be a bad download... redownload the rom when you have uninterrupted net connection
Possible reasons for phone rebooting after starting system
carks said:
... So is there any solution to this problem?
Click to expand...
Click to collapse
Check all the following points:
No undervolting
Cpu clock lower limit above 200Mhz
Cpu clock upper limit lower than 1.3Ghz
Sim card inserted properly, clean and dry
SD card inserted properly, clean and dry
Battery contacts clean, no dirt in contacts
Furthermore connect you phone to the computer and use adb to get debug information from the phone:
Check if your internal emmc is working properly with the command:
adb shell dmesg | grep mmc0 (on Linux) or
adb shell dmesg (on Windows)
When the result shows the following messages then your internal emmc is likely to fail soon completely:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Use command adb logcat *:V to show everything that goes on on the phone during booting and running. Errors show up then! See adb logcat --help for usage of the command.
Use command adb shell dmesg to see kernel messages.
Check if your phone also reboots when booting into recovery.
(Power off completely, "fast boot" disabled. Push <Volume Down> and <Power> simultaneously for about 3 seconds. Select Recovery with <Volume Down> and boot Recovery by engaging with <Power>.
Best regards,
Catherall
Hi everybody,
I'm experiencing the same problem with my Desire Z and Cyanogen 7.2 RC since this afternoon.
I installed it from a Cyanogen 7.1 stable last three weeks (when the new RC got out) and it was stable since today. For some reasons, I rebooted it (I thought properly), and got stuck with persistent reboot after the HTC logo, the Cyanogen animation and the Pin code screen. After I typed it and pushed OK or if I let it for about 15-30 seconds, the screen goes black and the phone reboots.
The last time it happened, I had to reinstall a 2.2 legacy HTC rom then rooting again and install Cyanogen.
Things I tried :
> Boot without SIM card : same result, I get access to the desktop and reboots
> Boot without SIM and SD card : same result
In Recovery
> Wipe /cache
> Wipe dalvik cache
> Wipe data and going from 0 : same result
> Restore a nandroid backup from the recovery (2 of them, one made after installing Cyanogen 7.2, the second after Cyanogen 7.1) : same result
Things I have to try :
> Wipe all (SD card, phone memory) and restart from 0
> Throw the phone by the window
Attached :
logcat : one of the logcats performed while I'm getting these reboots
dmesg : one of the dmesg logs in the same conditions.
Hope that will help.
Regards
Ok, so far, I've tried the following actions :
> Format the SD card, Wipe and reinstall a fresh cyanogen. That doesn't work
> Try to boot a cyanogen from SD card. Enough time to see that mmc0 wasn't damaged, but ended by autoreboot
> Beginning to belive in miracles when from a standard boot, the system lasted 6 minutes
> Get my old PC10IMG.zip to roll back to an old 2.2 HTC rom. And it is fu- stable !
Another hint from #G2Root : avoid any taskillers when I will get back on Cyanogen ?
Don't miss the next episode from "that damn phone !"
[Q] Desire Z on endless bootloop after wifi enable
Well great. I installed cyanogenmod 7.2.0 stable on my G2 (HTC Desire Z) on saturday ( I had the HTC firmware until then). But until today I hadn't used wifi. Today I enabled wifi and everything was fine except that the Z couldn't find a local network. So I changed the number of channels to 13 and the network was found. The Z couldn't connect to the network, instead said "network is disabled". Then I decided to reboot. And that's when it started. The phone gets to pin code screen and randomly after about 10-30 secs the phone reboots. And then again and again after a while at the pin code screen. It stayed up long enough for me to turn the wifi off at the settings but still no use, the reboot loop continues.
Any ideas? I haven't tried factory reset or re-flashing CM. But I found a couple of issues with wifi and G2. Has this been solved maybe in a newer version of CM?
Edit: Things I tried:
- I have checked that currently the wifi is disabled
- Factory reset in clockworkmod (didn't work)
- Re-flashing the cyanogen 7.2.0 stable (worked for about 30 minutes, then rebooted by itself) without any additional software installed (except google apps, of course)
Okay so,
I feel like this one's on the medium level of emergency here,
The issue is I flashed my cache, dalvick, factory reset, and (not sure) system to install Simple CM9, everything rolled along nicely except......
After booting into my promising new life, I noticed several issues:
KFU no longer recognized it, though the drivers still read "Android ADB Interface" in my computer
Google Apps would not sync my data, but still allows me to download apps from the play store
The sd Card partition no longer is shown by the OS, but still shows up when connected with usb (i'll be downloading a file manager soon, so this may answer itself to whether or not I can still access it)
TWRP will not boot by means of pressing the power button during initial boot
I understand I could solve my GAPPS sync problem by flashing them, and all my other problems wouldn't matter then. but I still have no means to flash'em.
Any and all help is GREATLY appreciated!
-a lowly noob
P.S. Everything about the ROM is fantastic except for those issues, (which are probably my fault) so many thanks on that end
P.P.S. (I do have a nandroid of my stock os before I wiped so If all else fails I can just go back to that if TWRP can be accessed and start over)
I seen a similar issue earlier and the guy fixed it by reinstalling the twrp
but u can always try going to reboot and select recovery and see if that works
gracci
That's a step in the right direction, thank you
no problem glad I could help
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
Hi,
I have followed the official wiki to install Cyanogenmod 12.1 nightly builds (December 25, 2015 nightly build) on my xperia M. It all worked well for the first time.
But suddenly after using it for some days happily, when I rebooted the device, the moment the device boots up, all the apps start crashing, causing the device unusable. I tried to reboot but it's still there. So I tried to repeat the process to get rid of this and tried to flash the December 30, 2015 build but somehow it is not working.
When I sideload the update zip file, it starts and gets stuck at 47% for quite long time and then suddenly finishes with (Total xfer: 1.00x ). The instant it goes 100%, the android icon showing "update" process disappears and screen keeps blinking and stays dark but still "adb devices" shows my device connected but the device screen just keeps blinking and nothing shows. I tried "adb reboot" but it throws this error
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
the "kill-server" command fails as well and thus, the problem persists.
I also installed open gapps after installing CM12.1 on the very first time. But in all those re-flashes, I skipped flashing it altogether and wiping cache partition, media and data & factory reset, these apps (calendar, music and gmail etc) throw the error the devices boots up. I guess the device is not getting formatted properly and its not being flashed with just the newer image. It gets stuck at 47% for way too long (almost 20 mins or more), while if I remember correctly, it didn't do so on first flashing.
Since I can't use any app when the device is ON, I can't open settings to check anything. Please help me getting rid of this, so that I can enjoy using this awesome ROM.
Thanks in advance.
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.