Develop Bugs

JSS15R Causes Reboots When Uninstalling Any App

As soon as I upgraded my 2013 Nexus 7 (Wi-Fi) to JSS15R I started having a problem where every time I try to uninstall an app the tablet reboots. It's not a full reboot, however - it just jumps to the Nexus "X" logo and boots from there.
When I originally updated I was rooted, but I've since performed two factory resets and I still have the issue. I've searched and found lots of posts talking about random reboots, but this definitely isn't random. It's recreatable every time and only seems to happen when uninstalling an app. Is anyone else having the same problem?
Here's a vid showing what happens:
http://www.youtube.com/watch?v=yD2fDb4kHsY&feature=youtu.be

I seem to have fixed it. I'll leave the post here in case anyone else runs into the same problem.
A factory reset won't do it. You need to do a full Flash Stock and Unroot. I downloaded the factory JSS15R image from Google, then used the "Flash Stock + Unroot" option in WugFresh's Nexus Root Toolkit. Everything appears to be back to normal now.

Thanks for the thread.
I have the same issue mentioned above and can confirm that I have "never" rooted my new Nexus 7, so this is not likely the cause.
Also, the previous poster found that a full factory reset did not sort the issue, so thanks for this and now I won't lose time trying a reset.
Also, the previous poster pulled a full stock image from Google, which fixed his issue. Therefore, this might imply that the JSS15R incremental [I believe all updates so far for this devices were incremental] does not apply properly [in some or all cases]? and/or some bits were left out of the incremental? Or some errors were encountered while applying the incremental? Logs somewhere?
So, any idea when / if a full image will be rolled out from Google for the Nexus 7 (2013)? Never?
I suppose this is only thing good about the ~200 MB "full" CyanogenMod (CM) 10.2 nightly images I put on my SGS III [no incremental issues].
After owning this tablet for 2 months, I as still hoping for stability and have resisted "rooting it" or "ROMming it" in case I need to send to ASUS against the 1 year USA warranty [purchased from Best Buy in USA - April 2013 manufacture date]. Now in London, UK, so no easy way to return it to Best Buy or ASUS USA.
BTW, my first purchase of this problematic tablet was returned to Google (Play Store) in early August 2013. Most of the sensors did NOT work.
A bit off topic, but I wonder how well CM 10.2 would behave on this tablet? since even the core Android 4.3 software from Google [which CM is based on] is "still" struggling with issues 3 months after launch for so many Nexus 7 (2013) users.
If I have to wipe the device and install a full JSS15R ROM, then I am open to putting a different ROM like CM.
GjT

GJT-UK said:
So, any idea when / if a full image will be rolled out from Google for the Nexus 7 (2013)? Never?
Click to expand...
Click to collapse
Just a quick update to say that when I upgraded my tablet [Nexus 7 (2013)] back in December to Droid 4.4.0, this reboot issue went away.

[Q] Nexus 7 2013 wifi 4.4kitkat system update problem

So still no lollipop on my nexus 7 2013 wifi, its not rooted, i did a factory reset to start fresh, i did a backup before that. when it finished factory reset backup restored all and it works ok and again still no lollipop but a new problem started to show. Before i did a factory reset my system update automatically checked for updates 2-3 times a day, but now it doesnt do that at all i can check it manually but it doesnt check it automatically. whats the problem? can i fix it somehow? thanks to all who can help
p.s. i can see that my apps wont automatically update like before even tho my play store is set to update automatically

Why not just flash the factory image at this point? I would never wait for the OTA to prompt me. As soon as the factory image was on the Google website, I would be flashing it.

SwoRNLeaDejZ said:
Why not just flash the factory image at this point? I would never wait for the OTA to prompt me. As soon as the factory image was on the Google website, I would be flashing it.
Click to expand...
Click to collapse
Yes that is a good idea if you know what you are doing, and i'm afraid that i'll mess something so i'll wait for OTA but can you help me with this update problem for now?

[Q] Nexus 7 2013 (wifi) update from 4.4.4 to 5.1.1

Hi,
I've read many articles about problems with OTA update of Nexus 7 2013. I'm on 4.4.4 now.
I received OTA to 5.0.2, but during update process I received an error (after that my Nexus rebooted correctly to 4.4.4, and is working ok).
I'm a second user od this N7, previous user installed TWRP&root, ROM was stock.
Before OTA update I returned to stock recovery, and unrooted my N7. ROM is still stock.
Now a question:
1. Do you know a safe way to update N7 from 4.4.4 to 5.1.1 but without wipe of all data?
2. Maybe someone successfully used Nexus Root Toolkit on N7 migrating from 4.4.4. to 5.1.1 with no wipe option?
I don't want to brick my N7, if it's a risk of brick, I'll stay on 4.4.4, but 5.1.1 is quite good option...
Thanks for answers,
Marek

I'm having a similar issue in that when I click the install button it gets stuck and won't reboot to install the update. It just says rebooting but nothing happens. So wondering if anyone has any ideas to sort this out without doing a hard reset?
Sent from my Z3C

Perhaps you could try this method
http://forum.xda-developers.com/showthread.php?p=60628837

mgdorbit said:
I'm having a similar issue in that when I click the install button it gets stuck and won't reboot to install the update. It just says rebooting but nothing happens. So wondering if anyone has any ideas to sort this out without doing a hard reset?
Sent from my Z3C
Click to expand...
Click to collapse
Sorted mine out by side loading through adb andriod v5, then it's now updating through the normal process [emoji2] [emoji106]
Sent from my Z3C

But now I have 4.4.4 not 5.1 (as in given links).
http://forum.xda-developers.com/nex...e-to-5-1-1-t3103854/post60628837#post60628837
first sentence: "Start: Nexus 2013 with rooted 5.1."
Is this safe method for migration android 4.4.4. -> 5.1.1 with no wipe?
Regards,
Marek

I used this guide and sounds like your the same as me so download the 5.0 zip file first and side load this first. Not checked everything yet but it looks like nothing deleted, so all is good.
http://www.talkandroid.com/guides/b...on-your-nexus-device-download-links-included/
Sent from my Z3C

during sideload I receive: verifying current system... "system/lib/libEGL.so" has unexpected contents error instalation aborted

Not sure with that then as I'm not sure what that means, so can't help you there. Might be best to backup and then install a clean image now. Also you can use app called Helium which will back up app data for Apps which don't do Cloud saves.
That's unless someone else can offer some advice.
Sent from my Z3C

I managed to do the update to 5.x in this way:
Step 1. Nexus Root Toolkit -> Flash Stock+Unroot (I choose my current ROM 4.4.4 and NO WIPE option)
Step 2. As was described above by mgdorbit
After step 1 - I was able to process OTA update (Step 2) without any errors.
Regards,
Marek

Is there a way to avoid N7 hard brick?

Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...

carpamagica said:
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
Click to expand...
Click to collapse
why would it brick via OTA? almost all N7s are updated that way.
the best precaution for not bricking it is if you follow the instructions that are given for manually flashing factory image, although I don't think it is necessary to do it manually. I did it OTA and it works perfectly normal.

Hard Brick
FWIW,
I've used Ubuntu with the adb utility and if I "bricked" my N7 2013, I found when I got to the bootloader "START"
window, I could simply do the sudo ./Install-all.sh command that comes in the package for the "stock" Android
kernel without any prerequisite commands and the ROM would load.
Of course anything that was on there previously was wiped out but at least I had a new system to start from.
I discovered this when I had my "bricked" device at the START window and the "adb devices" command showed that the N7 2013 was recognized at the USB port. Just went ahead and did the Install-all.sh command and away it went.
I tried to get Android 6 installed, rooted and with MultiROM operating but no dice. When I got to the point of installing MultiROM on Marshmallow, the device would perpetually boot into TWRP, never booting Marshmallow. I ditched it and went back to KitKat 4.4.4 and got it settled and then loaded a Cyanogenmod
snapshot. I'm liking CM more and more.
I'm just a script kiddie that's dinked with Linux since '93 and am by no means an expert. The background has helped when slogging away with my N7 2103 Flo. Kurt

reso91 said:
why would it brick via OTA? almost all N7s are updated that way.
Click to expand...
Click to collapse
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)

carpamagica said:
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
Click to expand...
Click to collapse
Sigh. The issue was widely reported as being caused or exacerbated by the OTA update to the initial release of lollipop. The best way to avoid the issue, if there ever truly was one, is to simply use custom ROMs, or stock rooted ROMs, which can be installed via custom recovery as opposed to through installing the factory image...

One of the nice things about Nexus devices is that Google posts factory images on their site. I generally prefer to use those, rather than OTA updates, as it guarantees a fresh install. I use a variety of other methods to backup/restore data and apps, but I've had pretty good luck doing it that way.

There's a really simple way to not hard brick your N7 with an OTA update:
If your present Android version is working okay, is stable, and does what you want it to do...wait for it...LEAVE IT ALONE!
Seriously. Other than for additional stability and MAYBE security enhancements, stick with what you have. Don't fall for all the hype out there.

The bricking caused by lollipop was due to a bug in the update causing a excessive amount of read/writes to the NAND and caused premature failure of the chip, this has long since been fixed and lollipop is safe for use again.
Sent from my Nexus 7 2013 using Tapatalk

Slow Phone and Options?

Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!

Have you tried looking through the various posts within the forum to find your answer? I just scrolled through and found a few without searching. Exerting a bit of effort could yield amazing results, at least that's what I've had happen over my years on here

bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
My Verizon Note 4 is exactly at the same update level as yours and it is working great.
When you did the factory reset did you completely wipe all user data on both the phone and the SD card? If not I would give that a try.
I would also suggest that you not let Android restore any applications when you first start the phone after the factory reset. You could have an errant app causing problems. If it seems to work phone without any user installed apps I would then reinstall apps one by one and make sure the phone continues to work fine. It it starts to run incredibly slow again then the last app you installed is likely the culprit.
If these options don't work I would take the phone to a local Best Buy. Go to the Samsung Experience counter and talk to them. They can do a deep factory reset that will completely reinstall the firmware and thereby restore the phone to a pristine factory image.
If these options do not fix the problem you may be in the early stages of hardware failure. The Note 4 has developed a bad reputation for the motherboard slowly failing and causing progressively worse problems. That is what happened to me and the phone eventually became unusable. I finally had to contact Samsung technical support (1-800-SAMSUNG) and they had me send the phone in. They replaced the motherboard and other printed circuit boards. It did cost me $70 since the phone was out of warranty, but it works like new now.
Good luck. The Note 4 is still a great phone and worth the effort (and possibly cost) to get it fixed.

Can anyone confirm that Foxfi tethering works (not usb) on a non rooted Verizon Note 4 phone (marshmallows 6.0.1) with the following security update installed (mmb29m.n910vvrs2cqe1)

bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
Yeah im thinking the problem is this phone came just packed with bloatware nobody uses a third of the garbage that came preloaded (200+ apps you use 10 of). You can root but you have to downgrade with odin back 5.1.1. bpa1 . you could also try a less invasive approach and just disable the bejeezus out of pretty much anything allowable there is an easy disable option that lets you do it in batches from the apps drawer. I did this to root the phone given the unstable root method.