Related
Hi,
I'm starting to have random reboots since the new update 2.3.4. Anyone else having problems ?
- I have the Fido Nexus S (i9020A)
- CWM 3.0.2.5 for i9023 (as specified in the thread to root)
- Rooted
It was ok (some reboots during calls, but not when the phone is just sitting there like it does now) with 2.3.3
Thanks in advance
Mine rebooted 3 times today.
First time I've seen it happen on 2.3.4 and it's aggravating.
It happened on my 2.3.1 and 2.3.2
I'm i9020xxkd1
I have not seen it on mine as of yet, I have just rooted and installed CWR so I will see if it changes and let you know.
What I had done before upgrading was to flash back to complete stock 2.3.3 then perform the upgrade to 2.3.4
No random reboots on mine so far. My phone is stock, unrooted.
Mine has worked great also but it is stock, also unrooted.
Hi
I've had a couple, rooted and with both stock Rom and cyanogen
Sent from my Nexus S using XDA App
I've also experienced this.
Got Stock, rooted.
WarpedMonkeys said:
Hi,
I'm starting to have random reboots since the new update 2.3.4. Anyone else having problems ?
- Rooted
Click to expand...
Click to collapse
I haven't had any reboots with v2.3.3 or now with v2.3.4 using a Rogers Nexus S model 9020a. I'm running stock and not rooted.
Maybe rooting causes this issue as the only posts with issues are all rooted?
I've been running mine rooted for a day, used it pretty heavily with no issues. I did have a reboot loop in 2.3.3 but that was with Beautiful Widgets.
So far no reboots while in call with 2.3.4 (knock on wood), as it was bad with 2.3.3. Manually installed 2.3.4 within a few days after its release, and have had a few disconnected (dropped) calls - but not a full reboot of the phone itself.
One might say this is T-Mobile, but in the 9 years I've been with T-Mobile, I've never had a problem with dropped calls before. So I can't help but wonder if this is a 2.3.4 issue, since it didn't happen before 2.3.4.
While annoying, at least it's not as bad as a full phone reboot.
bfksc said:
I haven't had any reboots with v2.3.3 or now with v2.3.4 using a Rogers Nexus S model 9020a. I'm running stock and not rooted.
Maybe rooting causes this issue as the only posts with issues are all rooted?
Click to expand...
Click to collapse
Yep I'm comming with the same conclusion. It's pretty lame since there's no way I'm going back to unrooted, guess I'll have to deal with it until someone finds what program is causing this.
I'm getting about 2-3 reboots an hour, this is getting serious. Any way to obtain the crash log or something to tell me what's causing this? I've read logcat wasn't really reliable.
moe3754 said:
Mine has worked great also but it is stock, also unrooted.
Click to expand...
Click to collapse
nm. Covered via PM.
I9020A stock 2.3.4 unrooted
Got a random reboot today, updated version yesterday.
Sent from my Nexus S using XDA Premium App
Seems to have something to do with the SETCPU app. I'll try changing some of my profiles. When my phone is full charged, I don't have any problem, but as soon as it gets kinda low, I can have 4-5 reboots an hour or 0... all comes down to luck.
Sent from my Nexus S using XDA Premium App
I am having reboots during calls. happened twice yesterday
I have a 9020a running 2.3.4 updated manually via CWM.
no reboot, fido 9020A in stock, unrooted
Hi all,
Ever since I upgraded to 4.3 I've noticed my phone, when idle, completely shuts off and I have to do a hard reset to get it back up again. It did this when I was Chromecasting netflix, but I've completely removed netflix since then. Anyone else noticing their phone completely shutting off when idled? Any solutions?
FYI. My phone is not rooted. Standard stock 4.3
I'm having the same problem at least once a day and totally random. Not rooted and stock 4.3.
Sent from my Nexus 4 using xda app-developers app
I'm seeing random reboots about once or twice a day too.
I'm running deodexed stock 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=2010887
Did cache/dalvik/system wipes. Upgraded from stock 4.2.2, which was stable as a rock. Might go back to that.. nothing too new in 4.3
Try reflashing everything using the google stock occam image. Mine works fine here.
Hello fellow N10 owners,
Unfortunately, the OTA KitKat update for my N10 is still not available for download.
I have reset the Google Frameworks app, but that did not work.
I am running Android Version 4.3 build JWR66Y stock rooted.
If you guys have any suggestions I would really appreciate it. Also, If you would know
how I could keep root after the update that would be awesome!
Thank you
BosCeltics18 said:
Hello fellow N10 owners,
Unfortunately, the OTA KitKat update for my N10 is still not available for download.
I have reset the Google Frameworks app, but that did not work.
I am running Android Version 4.3 build JWR66Y stock rooted.
If you guys have any suggestions I would really appreciate it. Also, If you would know
how I could keep root after the update that would be awesome!
Thank you
Click to expand...
Click to collapse
Mine is still not showing either......kinda depressing.
oakbowery said:
Mine is still not showing either......kinda depressing.
Click to expand...
Click to collapse
USA?
BosCeltics18 said:
USA?
Click to expand...
Click to collapse
Yes, Mississippi to be exact. I've hit the check now button 1,000 times I think.
oakbowery said:
Yes, Mississippi to be exact. I've hit the check now button 1,000 times I think.
Click to expand...
Click to collapse
hahaha! same
Glad to know I'm not the only one. I was beginning to wonder if my tablet was screwed or something. I have a nexus 7 also and it has yet to get an OTA update either.
I from malaysia and also don't get any update message yet : \
Sent from my Nexus 10 using XDA Premium 4 mobile app
Perhaps Google is waiting for Kitkat to be released on the new Nexus 10 before updatring the original Nexus 10.
There is no new Google 10 and seriously once you get KitKat on your tablet you'll wish you hadn't, the OS is like a giant phone and isn't geared up for tablets.
Sent from my Nexus 10 using Tapatalk 4
BackDaws said:
There is no new Google 10 and seriously once you get KitKat on your tablet you'll wish you hadn't, the OS is like a giant phone and isn't geared up for tablets.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I disagree. With the exception of the PhoneUI settings screen it's exactly the same thing we had before with much improved performance and reliability. I'm so glad to get rid of 4.3.. Nothing but problems.
Maybe it's been pulled.
Sent from my Nexus 10 using xda app-developers app
Use Adb to sideload the ota zip if you do not want to wait
And I think KitKat is great on the n10, especially with the new launcher installed
Sent from my Nexus 5 using Tapatalk
I'm still waiting too. I'm in London, UK.
Sent from my Nexus 10 using Tapatalk 4
The full image is available on the Nexus factory images site. If you can't wait for the OTA, just download and flash that. Just remember to edit the batch file so you don't wipe everything. Here is the link.
https://developers.google.com/android/nexus/images?csw=1#mantarayjwr66y
Taking advantage of the topic, I'm from Brazil and me has not yet come to update my tablet version is also JWR66Y rooted, I need to get the root to update via OTA? Because I remember the last update to 4.3, when restarted I had problem with the boot image and had to use a tool to change the boot image
I waited, and waited, but gave up a couple nights ago. Seems to me, it should be like a voting system. The more manual update checks you do, the sooner you get it versus those that don't manually check. Those that don't realize the update is even or won't miss it for another few days.
Editing the -w out of the batch file was troublesome for me. The flag would complete and the tablet would reboot, but it would then hang on the nexus boot screen. Tried twice, but waiting a half an hour each time, I deemed it failure. Unexpected too since I had done a full wipe, factory fresh 4.3 the week prior.
Running the unedited batch with wipe went without a hitch. No biggie since I had done it recently.
--OctOS Powered VZW GS4 Dev Edition
Bait-Fish said:
I waited, and waited, but gave up a couple nights ago. Seems to me, it should be like a voting system. The more manual update checks you do, the sooner you get it versus those that don't manually check. Those that don't realize the update is even or won't miss it for another few days.
Editing the -w out of the batch file was troublesome for me. The flag would complete and the tablet would reboot, but it would then hang on the nexus boot screen. Tried twice, but waiting a half an hour each time, I deemed it failure. Unexpected too since I had done a full wipe, factory fresh 4.3 the week prior.
Running the unedited batch with wipe went without a hitch. No biggie since I had done it recently.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
Yeah, I updated mine with the factory image several days ago...I decided to go ahead and let it do the full wipe since I was reading that folks were having issues after removing the "-w" flag. Full wipe is probably the way to go anyway if want to avoid bugs.
For anyone interested who hasn't done this before, I found the instructions here to be quite helpful:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
can i keep root with 4.4 OTA
Alright guys looks like I finally got the 4.4 OTA.
Anyone know how I can keep root???
Flash SuperSU from custom recovery. SuperSU v1.69 worked for me. The latest is 1.75.
--OctOS Powered VZW GS4 Dev Edition
Worked thanks bud
Hello,
The 4.4 OTA has been released for a few weeks now. I have yet to receive it on either my 2012 (WiFi only) or my 2013 4G LTE models. Has anybody here had this problem? Neither tablet is rooted or moded in any way, except I downloaded the new GEL Launcher and the new play store, but still on 4.3 ( and 4.3.1 for the LTE model)
Thanks in advance,
Kyle
Sent from my Samsung Galaxy S4
Thanks, man. The only problem is I don't own a computer ( I know, right!)...
Is there a way without root to flash the zip?
Kyle
Sent from my Samsung Galaxy S4
My wife's 2012 WiFi has not received the OTA yet either. It's only rooted with custom recovery installed.
It received all the other OTA's just fine.
It is SO SLOW! I'm really hoping KitKat breathes some life back into it.
I downloaded the factory image and am planning on wiping it clean in the next day or so. That doesn't really help you though without a computer.
Droid-Life had an article a few weeks back about the update with instructions to install using adb sideload. Then they said "flashing the .zip file through recovery often times works"
I'm guessing that won't help you either since you're not rooted or anything.
Anyway, you're not alone in not receiving the update yet. I'm wondering what the issue is.
Here's the DL article:
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
Let me know how that works out. I have been debating doing a factory reset on the device to see if that would push the update to my device. If you have any luck keep me posted.
Thanks.
Kyle
Sent from my Samsung Galaxy S4
Hey! I rebooted my Nexus 7 and received the new Kit Kat 4.4 update lol. Now my 2012 Nexus is running super smooth, better than new. Screen transitions are slick. I'm going to play some games and watch a video.
Also, if anyone knows how to change the click, battery, WiFi, Bluetooth, etc. Back to the Google Holli blue instead of white let me know... I liked the holon blue look.
Sent from my Nexus 7 using xda app-developers app
This morning I went into Google Framework Services and cleared data, cache and force stop. Then went to system updates and the OTA came through. I wasn't expecting it to work and was quite surprised.
Sent from my Nexus 7 using xda app-developers app
KitKat 4.4 Destroyed my Nexus 7
I got the OTA update this morning and did it. Now I get no command...called google didn't buy it from the playstore so they sent me to AUSUS they gave me an RMA since I have LOST EVERYTHING and not able to get in. It did have grouper 4.23 before but the recover doesn't work so they say I have to send it in. Does anybody know if there is a way to get this working?
I see others had good results..I am really upset...
:crying:
It is no longer rooted either since the grouper update...VOO DOO didn't work and of course I didn't find out until AFTER I lost root...my developer who I bought the kit from didn't have a connection to update my kit and now I have a new computer lost my files and kit...grrrrrrrrrrrrrrrrrrrr
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Real1minshen said:
Hi,
My Nexus 6p has 32GB Samsung emmc.
I upgraded it to 7.11 several days ago and used it for 2 days before I knew many Nexus 6p has a boot loop problem(luckily I didn't have it when I was using 7.0). So I flashed back to 6.0.
My question is, since I had tried 7.11, downgraded it, and good with 6.0 since then. Does it prove that I don't have a hardware problem and I can use 7.1.1 safely?
The reason I'm using Nexus 6p is I really want the latest updates.
p.s it's my first thread on XDA.
Thanks for any thoughts and comments.
Click to expand...
Click to collapse
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
jhs39 said:
Nobody knows for sure what causes the boot loop of death, which is what I assume you are concerned about, but multiple people who stayed on Marshmallow and never updated to Nougat reported that they got it anyway. If you want to run Nougat you should do a clean install of the full factory image and see if you still have the problem. As long as your bootloader is unlocked and USB debugging is enabled in developer options you should be relatively safe should you encounter problems again. I have been running 7.11 or roms based on 7.1.1 for as long as I have had this phone and have never encountered any serious issues. The vast majority of 6P owners don't have serious issues with Nougat. I personally wouldn't go back to Marshmallow because I got the 6P to be up to date as well.
Click to expand...
Click to collapse
Thank you~