Related
on an advent vega running honeycomb 3.2 v7 (viewcomb based on vega) on reboot crashes to starting fastboot USB download protocol and freezes every time requiring a reinstall.
any suggestions ?
exact thing happened to me. powered on the tablet one day and it has self bricked itself. iv gona back to stock 2.2 firmware since honeycomb is just problems and self bricking is just pointless, it takes too long to install apps again and its just adding to the nand wear.
FIX AVAILABLE!!
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i updated without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Update: Some users contacted ASUS and it seems they are aware of the problem. A fix is supposed to released soon, in the form of another OTA update.
Update2: Very good knews for rooted users. The test13 version of guevor's kernel is able to let the TF deep sleep and not reboot. Link to his thread:
http://forum.xda-developers.com/showthread.php?t=1565519
THANK YOU, GUEVOR!
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Have you tried a factory reset?
Balor said:
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Click to expand...
Click to collapse
Yes, please.
Sent from my Transformer TF101 using XDA Premium HD app
Can´t give you a logcat yet but here's my TF101 info:
FOTA to ICS 2 days ago and started random reboot's... Not Rooted (never has), no service/app/etc.. killer, but i did disable all of ASUS crapware on the Apps manager.
I was able to caught one of the reboots (it's freeze on the ASUS logo) and when i hard reboot it, during boot sequence appear some message saying that was finalizing update (this was after the FOTA and after other 2 random reboots. I did reboot the device after the update at least twice before experiencing the 1st Random Reboot).
info:
S/N: B90KAS146231
WW (Build Number IML74K.WW_epad-9.2.1.11-20120221)
Kernel: 2.6.39.4-00002-g2977a0d » [email protected]#1
as soon i have the Log i will post.
Hope this help somehow
baseballfanz said:
Have you tried a factory reset?
Click to expand...
Click to collapse
Every kind of update method that you can think of was tried. In that case, yes, it was wiped. Several times, in fact.
Please, post just what i asked. I want this info to investigate the issue. Post on another thread if you want to share theories or something else.
Sent from my Transformer TF101 using XDA Premium HD app
Mine was never rooted, 100% stock, took the ICS OTA on Friday moring, ran great all day, I woke up Saturday morning (I had docked it and put the doc on the charger friday night when I went to bed) and it was stuck in a boot loop. Now I'm looking at how to NVFLASH it back to honey comb to recover it, might as well root it now.
Les
still waiting to freeze or reboot ... for now 493K of logcat
Sent from my Transformer TF101 using Tapatalk
This is going to be a problem in the kernel like it has been on previous releases. When kernel source is released then the kernel devs will fix it and then asus will fix it. My SODs are caused by a kernel panic so until we get an updated kernel we need to get asus to release source.
I am mostly a longtime lurker/user of XDA but I thought I should contribute to this thread.
Bone Stock 16g TF101-A1, Refurb purchased last week from online vendor. Still getting used to the tablet format but I also purchased a TF101 Dock.
I noticed yesterday that I had a couple of random re-boots. Didn't know if it was related to an update or why this particular tablet was "refurbished." About 7 hours ago, this morning, I got multiple re-boots. Splash screen then power off and on again. I saw at least 15 re-boots before I started looking around for solutions. I tried the stock rom (downloaded from Asus) and re-boot to recovery w/o any success. Re-booted and wiped (hard reset) multiple times as well.
Still no complete boot but I had two separate and distinct paths that displayed:
1. it would boot with an android bot asking for a password and the keyboard displayed
2. It would cold boot into the "Start" screen like a normal set up.
I did manage to get the recovery started only to reach the bot with the exclamation point and no further progress at recovery.
In either case, typing a password of any kind did nothing, and hitting start and beginning the set up process did nothing but continue the re-boots/splash screen/power up/power down.
Finally connected to my laptop and it succeed in a complete boot and I was able to set up and connect to my wireless. It did not re-boot for several moments and I was able to observe the "About" page from the settings. I was still running
HTK75.US_epad-8.6.5.21-20111216
I also noticed that it was actively downloading a "firmware update" I went through several more re-boots until it finished the download and then I installed the firmware w/o any further trouble. In watching the download, I noticed re-boots at 31%, 32%, 41% "download completion", and one or two more before it fully downloaded. Of course, it did re-boot upon completion of the upgrade.
I am now running Android version: 4.0.3 Build number: IML74K.US_epad-9.2.1.11-20110221
Everything has been stable for an hour or so of moderate use including installation of multiple apps.
FWIW, I think that the reason my problem started is that I had my WiFi set to turn off when screen is off. I believe my incomplete download started the re-boots and my settings "may" have contributed to the incomplete downloads that started the rest of my issues.
Thanks to all of the "regulars" around here that are busy helping us customize our devices. This may not be my first post, but I think I have less than 5 posts right now. Hope this helps in discovering the causes of the re-boots.
ICS OTA on Saturday, 2 reboots already, stock rom, 100% original, Italy. Should i contact Asus?
msaraiva said:
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i update without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
So... if you do the ful update via CWM there are no problems?
Sent from my Transformer TF101 using Tapatalk
Just Once
I have experienced a single random reboot since applying the OTA ICS upgrade to my US B70 TF101.
That was then...
Now the tablet is virtually unuseable. Not only are there random reboots, but lags and freezes ad nauseum. I am NOT a happy camper
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
jparity said:
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
Click to expand...
Click to collapse
My device never gets stuck in the ASUS logo, it always completes the boot process, and the wifi policy is the default one, so i don't think it's related to it. But it's probably something to do with the kernel and deep sleep state. Even with the wifi policy set to never turn off, the device enters DS.
Sent from my GT-I9100 using XDA App
reboot cant have anything to do with the apps (like google earth) as those will simply FC on fault and are not capable of taking system down. this must be a kernel or driver issue.
transformer prime got ota update recently that was supposed to fix reboots and it contained new wifi driver. so possibly this is something to do with wifi.
my wifi sleep policy setting is to be always on when on power and sleep when screen is off on battery.
never had a reboot when plugged in, had a few always on battery power - so it might be related to wifi beign powered on in sleep to do periodical email check. just a guess.
I am running stock unrooted atm. I reverted back from rooted to stock before the ota update.
I generally get one random reboot each day. They happen when my transformer is in sleep mode always. It'll be st next to me asleep and then I notice the screen turn on and it is rebooting. My "Keep Wi-Fi on during sleep" is set to "Always".
I removed root as I wanted to see what stock performance was like. Apart from these reboots I'm totally happy.
2.6.39.4 and WW_9.2.1.11
Not sure how much help that'll be to others, but there you go.
I had these random reboots aswell on my device but since yesterday morning it stopped.
- Removed SetCPU
- Forced 2D rendering to the GPU.
Still testing it but so far no reboots
Stock ICS + Root
Getting the same exact thing, froze during boot up one time.
Running S/N BBO
Tossed a ticket into Asus letting them know, hopefully I get a response back soon.
I had random reboots the first day after updating,
but have set
1. the wifi to be off when the screen is turned off (in wifi settings), and
2. have turned off the location service that uses your wifi to aid positioning (in location settings).
and this seems to have stopped the reboots.
Hope this helps someone.
I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake
steviejake said:
I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake
Click to expand...
Click to collapse
The RR and SoD come standard with asus stock FW for most people, there is a new .27 update you could try that apparently fixes things, but it made things worse for me
The serial number is generally on a sticker next to the charger port of the tablet half, B4O > B60 and some B7O are SBK1, after that are SBK2
If you are SBK1 you can use NVFLASH to clean install the OS
I decided on Stock FW Rooted and CWM with PERI, then Guevors Kernel
So far so good, stable for a couple days now
Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake
steviejake said:
Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake
Click to expand...
Click to collapse
If the flash worked with sbkv1, then more than likely the unit is sbkv1. Otherwise, it shouldn't have worked at all . As the other poster said, RR and SoD is pretty common with the stock Asus firmware for some people -- you might try returning to Revolver now that you've gone back to stock, and start on Revolver again with a clean slate.
I am also running the same setup as the previous poster, stock .27, rooted with guevor's kernel. Been that way for only a day right now, so I can't say much about it yet.
Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake
steviejake said:
Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake
Click to expand...
Click to collapse
If you used NVFLASH to get back to stock, you could have just let the FOTA update you to .27
Then you can root and so on after that
NVFLASH returns the tablet to factory settings, ie. as it was when you unwrapped it on day 1
Not good. My tablet seems to be in an internal storage hell. Every Rom I try to install will crash with moderate use after booting. I have tried NvFlash, EasyFlash, Wolfs Ultimate flash and downgrade, every variation of stock HoneyComb and ICS I can find. I cannot keep this thing stable beyond 5 minutes of use. I have tried multiple factory resets and wipes, run "Superwipe Full" multiple times and nothing seems to work. What can I do to recover this tablet before I just give up and send to ASUS (god help me) for assistance? Any help would be appreciated
Thanks StevieJ
Ouch. Sorry to hear about your troubles. Horror stories like this have prevented me from diving into the root and custom rom scene with my one and only tab. [I am leaning towards a Nexus 7 when it comes out, and will perhaps root etc when I get that. I feel like it's a safer endeavour with a non-locked bootloader]
I'm interested in finding out what may be causing all this, so I'll be subscribing to this thread. Sorry I can't provide anything more than good luck to you.
Sent from my Transformer TF101
Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake
steviejake said:
Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake
Click to expand...
Click to collapse
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.
hairy1 said:
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.
Click to expand...
Click to collapse
Funny you should ask that. I just NvFlashed 9.2.1.24 and was using the tab with no WiFi, no account information and everything worked just fine. I then enabled WiFi to see what would happen and it still worked, but I had not logged in with any account information yet. It still worked fine, as I was able to surf the web with no problems. I then tried to add my account information and started getting crashes using the Play Store, syncing my accounts, etc. It seems to be linked to updating account information and not just WiFi. I will investigate further
Thanks
StevieJake
Adding an account, even a new account, will bring down the tablet. It reboots until it is only a dark screen that requires APX mode (VolUp +Pwr) to rebuild the tablet. I can get into recovery and also factory reset mode (VolDwn + Pwr), but that is it. I'm so confused
I found a CWM backup I had from back in March. It restored fine, but still had problems that resulted in multiple crashes and eventual death again. Oh Bother!!
StevieJake
Fixed it!
Here is what I did. I was always to get the tablet into APX mode (Vol Up + Pwr) so I NvFlashed 9.2.1.24 from this site:
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/. I did this 5 times, never letting the tablet fully reboot after I got the "success" message upon completion. I then did a data wipe (Vol Dwn +Pwr, then select Wipe Data and then Vol Up, Vol Up) 5 times. I then used the same NvFlash 5 more times and let the tablet fully reboot and entered my Google credentials. I had prepared a MicroSD card with the zip file extracted from the ASUS site that contained the latest firmware (.27) and placed in the root directory of the MicroSD card. The tablet recognized it as a system upgrade and installed the firmware grade with no problems. The tablet rebooted fine and showed the installed firmware. I then did a data wipe as described above 5 more times and then let the tablet reboot fully and once again entered my Google credentials. The tablet now runs all programs without faults, has no video artifacts on the live wallpaper I use (Blue Skies) and is running just great. I am able to update all apps with out errors from the Play Store which was also an issue.
I hope this helps someone to get their tablet back, as I used all the resources on this forum to bring this wacky method to restore my tablet. Thanks to all you unnamed posters for your help
StevieJake
I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101
Not so fast!
Although the tablet did last longer (almost 2 days), it ultimately failed again to an unbootable state. Its back to the drawing board again.........
StevieJake
rootblock said:
I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101
Click to expand...
Click to collapse
It may just be giving up, electronics are stupid sometimes and fail for no reason. I had a brand new HDD that worked for two days, I left the computer off for three weeks and when I turned it back on the HDD wouldn't even spin up :-/ Good luck buddy.
Okay, I'm done. Just got my RMA and am sending this puppy in. Thanks for all the help, I will try to post the results later when I get it back. Glad I made the impulse purchase for the Nexus 7, as I will not be totally without a tablet.
Thanks for all the help again
StevieJake
RMA and back from the Dead!
Well I got it back from ASUS after the RMA. It had a short visit in Texas, was returned promptly and appears to function normally. I never received any feedback from ASUS on receiving the tablet, what was wrong with it, what they did to it or when they shipped it. But its fixed. Running .27 latest firmware and seems to handle everything I can throw at it.
They did a bang up job so far and I am more than happy with their service.
StevieJake
All right, so here's my scenario:
I've been running CM10 builds for a while now, and for the last week or so I've been getting more and more freezes, random reboots, and full shut-downs. I finally today was sick of it and decided to give up and go back to stock. I ran into no end of problems getting into recovery mode and couldn't do so consistently or reliably, but managed with the Nexus toolkit to go back to stock rooted. But I started having crashes and reboots even during setup after this. So then I reflashed to stock without rooting and had similar issues, plus some apps wouldn't install with various unspecific errors. I finally took it all back to stock with LOCKED bootloader and I'm still having random crashes, reboots, boot loops, and apps that refuse to install.
Is there anything else I should be trying before I go to ASUS and turn it in under warranty?
TurboFool said:
All right, so here's my scenario:
I've been running CM10 builds for a while now, and for the last week or so I've been getting more and more freezes, random reboots, and full shut-downs. I finally today was sick of it and decided to give up and go back to stock. I ran into no end of problems getting into recovery mode and couldn't do so consistently or reliably, but managed with the Nexus toolkit to go back to stock rooted. But I started having crashes and reboots even during setup after this. So then I reflashed to stock without rooting and had similar issues, plus some apps wouldn't install with various unspecific errors. I finally took it all back to stock with LOCKED bootloader and I'm still having random crashes, reboots, boot loops, and apps that refuse to install.
Is there anything else I should be trying before I go to ASUS and turn it in under warranty?
Click to expand...
Click to collapse
Yes, you should try to return back to stock unrooted.
If the problem persists, then you know it is not a software glitch.
To do so watch: youtube.com/watch?v=-E-EF0QC0Gc
anoperson said:
Yes, you should try to return back to stock unrooted.
If the problem persists, then you know it is not a software glitch.
To do so watch: youtube.com/watch?v=-E-EF0QC0Gc
Click to expand...
Click to collapse
Yes, as I mentioned I already took it back to stock unrooted and then even went so far as to relock the bootloader. I was just trying to confirm that there was nothing further for me to try before assuming that meant I had fully ruled out all software influences or possible self-remedies. So yeah, if that's that, then I guess it's time to contact ASUS.
Hi,
I am reading from time to time here at xda about random reboots issue with ZUK Z1, so here is my short story.
I am the user of ZUK Z1 since last year at the time there was only COS12.1 and CM12.1 available. The phone was working great for the first few months, no single random reboot, even with heavy usage and tons of root tools like xposed framework, greenify (with exp. mode), amplify and other experimental tools etc. Rock solid stability, CM12.1, ZUI, COS12.1, no matter which one.
Some day, somewhere beetween feb/march this year I started to see occasional random reboots, sometimes once a week and sometimes three times a day. After the last one of this random reboots, the phone refused to boot. No recovery mode, no charging screen, no fastboot, even no access to qualcom recovery port for use with QPST and QFIL tools.
Tried to drain the battery and charge again with no success, tried to soft-restart by power button - no success. The thing that helped after phone sitting on desk for next three months, was to dissassembly the phone and reconnect battery. After this, the phone boots up again, bot the random reboot issue is back, no matter CM12.1, CM13 or COS12.1
And now the questions time:
The question is, is this a software issue after some of the updates or hardware issue?
Are there users with the random reboots problem with the newest firmware?
How to debug and catch this random reboot on the logs without ADB connected to see what is going on?
What have i done to fix the issue:
- reflash phone many times with different versions of COS12.1 and CM13
- flash fresh .zip from recovery
- flash directly from fastboot with official COS images the support page
- fsck, partirion check for errors, etc.
- formated phone by QFIL tools
- tried to track the problem from logs, but so far no value information are stored after reboot
What i am going to do:
- install ZUI 1.6 to verify that the issue comes back
- as much as i can, use the device with ADB logcat connected by cable, to catch the occasional reboot
- recompile kernel with enabled options to store crash reason after reboot ( kernel pstore feature or last_kmsg )
I am in the same situation as you, investigating....
Please update your results, very interested to find if software or hardware problems....
Thank you.
Carlos
Are you restoring apps after you flash your phone? If so, try not to. Just install basic apps you need and see if problem persists, since Google restores app with it's data.
Phone rebooted in recovery, so I think it's a hardware problem.
Phone is traveling to China again.
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Fenomen007 said:
After what perio of time your problems started? I have my z1 for 2 weeks and it works perfect. I keep it on heavy usage for a few hours daily.
Click to expand...
Click to collapse
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
errecez1 said:
Phone arrived 25th may, 20 days with no problems, reboots were increasing to the limit that icons on main screen didnt load, rebooted inmediatly. So phone became unusable.
Hope your unit to be the good one!
Click to expand...
Click to collapse
I love everything in that zuk so hope it won't brick. When it happen i will just chargeback money from gearbest
Hello,
I'm in the same situation !
My phone randomly reboots and also freeze (have to do an hard reset).
Have you find any solution ?
I am also having this issue... I will probably send it for the warranty. I have tried a few different roms, even restored back to CyanogenOS and the reboots continued...
I got mine since October, haven't had any reboots so far.
I'm running the latest update from cos without root or custom rom.
Seems like a hardware issue to me, I have tried everything software side.
same issue
I'm also having the same issue,any fixes??
Random reboots just stopped happening on my device a week ago. Before that I was trying different ROMs and flashed different versions of TWRP but the reboots were still happening. Then the reboots just stopped from happening and now everything is working perfect. I think it is a hardware fault. Probably some electronics (cables or what not) on my device are now having contact but were not having it before, I don't know. But if you are experiencing rebooting issues, just send your phone to the repair.
Any fix to this?
Whenever I do dirty flash, my zuk z1 random reboot twice a week. It is highly recommended to do a clean flash if you want to avoid random reboot.
Clean flash = No random reboots. @sebeqone