yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] lollyjay:
Best wishes for a successful operation and good recovery!
[Nexus 7 (2013) Android Development] Mac of York:
[MENTION=426561]scrosler[/MENTION]

Get well soon! Your ROMs are always the best but that's never as important as your health.
[Nexus 7 (2013) Android Development] Scott:
What the zip does is kills the "otacerts.zip"

Its best to run it before the notification... I always forget to take the certs out...

Here is the script

ui_print("------------------");
ui_print("www.scottsroms.com");
ui_print("------------------");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
delete("/system/etc/security/otacerts.zip");
unmount("/system");
ui_print("Done!");

After you delete the certs, I think you can clear cache to get it to go away from the notifications. If not you can hide the notification by long pressing it.

On the other three N7's run this before the update pops up.

I have two days left before surgery (Monday 5:30am) and I might try to do a stock rooted tonight... But the key word is "might".
[Nexus 7 (2013) Android Development] Scott:
Well....

Today was my last day at work... And my last ROM will be made today as well... That is before my surgery...

IM uploading Stock-Root-5.1.0-LMY47O :p

I'll post a thread when its up :highfive:
[Nexus 7 (2013) Android Development] Scott:
Check it out yall....

[ROM][Flo][4/17/15] - Factory Stock Rooted ROM - LMY47O - Android 5.1! Lollipop!
[Nexus 7 (2013) Android Development] Naudiz:
Since today, my Nexus 7 on CleanROM doesn't go into Deep Sleep anymore, as long as WiFi is enabled.... Anyone else ever had this problem?

BBS shows Kernel Wakelock "suspend_backoff" and the Device is always awake, unless I turn off WiFi completely...

I'm quite desperate atm... Until now I was very happy with this ROM.
[Nexus 7 (2013) Android Development] dark2099:
Have you tried rebooting, could be something goofy that will reset with a reboot. Also if you're like me and have flashed lots of kernels, might be time to do a clean install with only the kernel you are currently using. Cleans out any misc crap that could be lingering.
[Nexus 7 (2013) Android Development] Naudiz:
Nope, nothing like that. Just a clean install of CleanROM, and yes I rebooted several times now.

I didn't do any changes to the system either lately.... I wonder if this has something to do with the OTA notification that came up a few days ago... :-/
[Nexus 7 (2013) Android Development] dark2099:
Not sure if that could be causing it. Might try either the zip that Scott posted, should be a link a few posts back, to delete the cert, or long press the notification to make it go away. The only other possibility I can think of is if the play service update that came with 5.1 has trickled out to 5.0.x and is causing the issue. Info on that here. http://www.xda-developers.com/psa-google-play-services-wakelock-affects-many-5-x-roms/
[Nexus 7 (2013) Android Development] Naudiz:
Hm, I have now deleted otacerts.zip in recovery and wiped cache & dalvik. Hopefully that will change something, but it's a long shot... Thanks for the excellent article. Lollipop sure is a mess! :-/
[Nexus 7 (2013) Android Development] Naudiz:
It didn't help :( Nexus still won't go into Deep Sleep. It even still shows OTA notification, even though otacerts are removed...

I followed this guide (section about suspend_backoff), but strangely enough the dmesg output didn't list any suspicious event*-**** entries.... This is all very strange... I think I smell a full wipe ahead *sigh*
[Nexus 7 (2013) Android Development] Scott:
Try the new play services first: http://www.apkmirror.com/apk/google...ices-7-3-27-1857062-438-android-apk-download/
[Nexus 7 (2013) Android Development] Naudiz:
Thanks scrosler! However, the N7 needs Google Play services 7.3.28 (1863718-436), which seems to be missing right now on APKmirror, so I used Google Play services 7.3.27 (1857062-436) instead, which didn't solve the problem :(

EDIT: Google Play services 7.3.28 (1863718-436) was uploaded just a tiny bit later on APKmirror and it fixed the problem for me, alongside with some small adjustments which I made to my WiFi-setup (tbh, I don't know which of both actually fixed the problem). In any case, thanks for your excellent help, guys! :)

And [MENTION=426561]scrosler[/MENTION]: All the best for your surgery!!!
[Nexus 7 (2013) Android Development] Scott:
Farewell for now...

I'm locking this thread down. Development has been halted until a later time.

Most of you know I am going into surgery and will not be on XDA for a while.

-Scott

Edit: I decided not to lock the thread at this time. But I got people watching over you ;) Hopefully I will be able to move out of bed in the next 7 days.
[Nexus 7 (2013) Android Development] FrontRowJoe:
Best of luck with your surgery. Lots of folks here will be pulling for you.
[Nexus 7 (2013) Android Development] afonsov:
All the best with your surgery!
[Nexus 7 (2013) Android Development] NikoZBK:
Hope you have a speedy recovery :)
[Nexus 7 (2013) Android Development] snake218:
See you later, best of luck with your surgery (been there) :D
[Nexus 7 (2013) Android Development] EvolJester1982:
Question

I've gotta question. If I'm comin from cleanROM 4.4.4 to 5.0.2. What do I wipe?? (twrp) its been awhile since I did it and can't remember witch things I wipe in the advanced wipe??

I love cleanROM KK and I no LP will be just as fast and smooth if not better ?

Thanks for the help ;)

EDIT: One more question.. I've got elementalX kernel installed on this rom and can't remember witch I used.. So if I flash CleanROM 5.0.2 LP with EX kernel do I use?

Thanks again for the help ?
[Nexus 7 (2013) Android Development] Woody:
See my edits above.
[Nexus 7 (2013) Android Development] EvolJester1982:
if I done a factory reset or everything that you said in the advance wipe. Wouldnt it get rid of my twrp or my root?
[Nexus 7 (2013) Android Development] dark2099:
Recovery won't be affected, so no worries on TWRP. As for root, so long as after you do a factory reset, or the advance wipe you are flashing a new version of CleanROM, that is prerooted, so you won't really lose that. Just make sure before you do either style of wipe, you back up important stuff just for good measure.
[Nexus 7 (2013) Android Development] Doomstang:
I hope the surgery went well. Best of luck on a quick/full recovery! :good:
[Nexus 7 (2013) Android Development] AarSyl:
Here's an interesting observation. My USB port is partially broken, and I barely have access to the PC after twisting and turning the unit. While recognized by the PC, I have access to ADB, but not fastboot (which is strange enough in itself). Because of this, I cannot flash the stock firmware for 5.1.

In another post, I read about someone getting random reboots from all 5.1 roms due to the lack of the latest firmware. I do confirm that this does happen on old firmware.

The interesting part is that the ElementalX 3.5 kernel works on this rom, and also prevents reboots while using the old firmware. This is good for me, since I cannot upgrade to the new firmware at all. There might be a way for me to return to stock, but I don't want to be stuck there, either.
[Nexus 7 (2013) Android Development] madbat99:
Just flash the new bootloader zip then flash the stock rooted 5.1 zip. Easy peasy.

The reboots happened on 5.1 Roms with the 5.0.2 binaries. Most have been updated anyways. Just flash the new bootloader and any 5.1 ROM that has updated binaries.
[Nexus 7 (2013) Android Development] AarSyl:
Not entirely accurate. I HAVE the new bootloader, actually. And I flashed the stock 5.1 rom posted by scrosler. First reboot within 10 seconds of loading the rom.
[Nexus 7 (2013) Android Development] madbat99:
You shouldn't have reboots on stock rooted. Its not a common issue. Flashing the bootloader and ROM is (with a data format of course) is as close as you can get to flashing a factory image and then rooting as you can get without a PC. You have installed all the firmware. This is a nexus not a Samsung, lol.

Seriously though random reboots are not a "known issue" of 5.1 Roms now that the proper binaries are out.
[Nexus 7 (2013) Android Development] Slickademo:
Good luck with surgery brother!
[Nexus 7 (2013) Android Development] Bierto:
Simple question

Hi!

I'm a new user and a little bit noob.

I have only simple question.

Now I have N7 2013 rooted with Clean Rom 5.0.0. with android 5.0.2. (I have not change kernel)

I saw the notification on android 5.1 of the OTA update.

Could I start the OTA update? Or Must I flash the new version?

Now I do not have the need to change the version for which you wonder if it's worth it.

If the OTA update does not work and if the update to Android 5.1 should not be very useful then tell me so that I do not complicate life to update it and I keep my 5.0.2.

I await your advice and thank you!
[Nexus 7 (2013) Android Development] Woody:
See my post here about the same thing. Now my tablet got the notification last night. So that makes 2 with and 2 without in my house. Crazy Google.

I flashed the zip on my son's tablet that got the notification and within a day it was back.

I deleted the actual file manually in /system/etc/security/otacerts.zip on my other son's tablet and he has not gotten it yet (we don't allow "screen time" during the week since they are still in school, so he may not have triggered it yet).

I flashed the zip on my tablet before I got the notification and as I said above, I got it overnight last night

My wife's is unaltered and is on the latest Clean and she doesn't have it at all.

In both the tablets that got the notification, I just long-pressed the notification and once it "changed" there is a ! with a circle around it. Tap that and Block Notifications and it goes away. Simple little thing to stave us off until Scott updates after his healing is done from surgery.
[Nexus 7 (2013) Android Development] Slickademo:
OTG with USB storage working yet?
[Nexus 7 (2013) Android Development] L.F.B.:
Any news about scott surgery? Hes ok?

I hope so... Scott is a great person.

Edit. Just Posted on his forum:

57 Minutes Ago 04:50 PM] Scott : The "good ones"

[58 Minutes Ago 04:50 PM] Scott : On massive pain killers

[58 Minutes Ago 04:50 PM] Scott : Home now

Hes OK. Get better fast Scott :)
[Nexus 7 (2013) Android Development] dang69:
I didn't know it was ever broken? Working fine for me. Reads an SD holder and hooks up to drone flight controllers and gimbal software just fine. That covers Stickmount, EVVGC and Droidplanner.
[Nexus 7 (2013) Android Development] JohnDovas:
got error when installing 5.1

my tablet downloaded the 5.1 version of the rom but when i reboot for it to install it won't let me. it gives me an error and nothing happens, any help?
[Nexus 7 (2013) Android Development] fly4awhtgye:
May need to Reboot Recovery after all your wipes and before flashing ROM in TWRP...or maybe a bad ROM download. Does MD5 match?
[Nexus 7 (2013) Android Development] JohnDovas:
i thought i didn't have to wipe my settings.. you know, since the update is from the android update checker it self. and i don't know what md5 is... or how to see if they match, sorry i'm pretty new to this
[Nexus 7 (2013) Android Development] dang69:
If you were on custom recovery running the earlier rooted version of stock you must go to the first post and download the ROM Scott provided (update bootloader as well). The over the air (OTA) rom will not work once you have taken control of your tablet with a custom recovery. The update checker assumes you are stock. Either stop using it or go back to stock un-rooted.

---------- Post added at 06:44 AM ---------- Previous post was at 06:42 AM ----------

Oops! I got thread confused. What I said still holds but I thought I was in the "stock rooted" thread. If you want the latest that's your only option until Scott gets back on his feet.
[Nexus 7 (2013) Android Development] Woody:
Look at my post a few up from here. What you are getting is the System OS update from Google itself and not Scott/CleanROM.

Since you are new to this, I'll explain what is happening.

Google is sending out the OTA in waves. As I said above, I have 4 tablets in my house and only 2 have gotten the notification so far. But....Since you are on a Custom ROM, the OTA will inherently fail. There are a few reasons for this which I will explain below. Being that CleanROM is based off stock and that Scott didn't delete the OTACerts.zip mentioned above, Google's servers think that this is a stock setup and is sending the OTA to you. They have no idea that you have modified anything at this point.

Here is why it is failing and when Google realizes that the device is modded:

The OTA comes in and you download it. Once you flash it, the package looks to make sure that the device's integrity has not been compromised. If you have modified the /system/build.prop, it will fail. If you have flashed a different kernel or a recovery, the package checks for this and if it comes back as altered, the flash will fail. Sometimes it even looks at the apps in /system/app and /system/priv-app and if those are altered (including deleting and inserting of apks), then the flash will fail.

Long story short, unless the device is in virginal state, the OTA flash will fail. If you want to take the OTA, you're going to have to flash the factory.imgs through fastboot and then take the OTA that way. But realistically if you are going to fastboot a factory.img, you might as well flash the newest one and skip the OTA altogether (flashing imgs is always safer than taking OTAs). I just simply long-pressed the notification and blocked it, didn't download the OTA and will patiently wait for Scott to put out a new CleanROM when he is ready. You can delete the downloaded OTA if you decide either of the two options above, but I can't remember right now where it downloads to (maybe /root/cache I think).

Hope this helps and welcome to Android.
[Nexus 7 (2013) Android Development] dang69:
good explanation!
[Nexus 7 (2013) Android Development] Scott:
Just stopping in to say Hi. Things are going well. I should be at 100% capacity in another 3 weeks!
[Nexus 7 (2013) Android Development] L.F.B.:
Great to see you back, Scott.

Pain killers making a good effect :)
[Nexus 7 (2013) Android Development] snake218:
Glad to see everything its going ok, get well soon :)
[Nexus 7 (2013) Android Development] AarSyl:
Great. At this rate, we will have Android 5.2 by then.
[Nexus 7 (2013) Android Development] hallucinate:
Hilariously callus. Not to say I don't share the enthusiasm for a 5.1 based clean ROM...
[Nexus 7 (2013) Android Development] Scott:
You all wont believe this. I went to turn on my Nexus 7 today and I just get the 5 blinking lights of death. I tried charging it for hours, holding all sorts of key combo's etc. But I cant get it to come up.

Gonna try letting it sit over night on the charger.
[Nexus 7 (2013) Android Development] gnarlycs:
never heard of this, have you overclocked it a lot? has it stayed hot for long periods of time before? does this mark the end of cleanrom development for this device?
[Nexus 7 (2013) Android Development] andyman_187:
this happened to me twice, just leave it on the charger for a few hours and it should come back to life
[Nexus 7 (2013) Android Development] Scott:
Never, never, dont know. Looking for ideas to get this thing going again.

Yeah, its been on overnight. Still nothing. I dont thing its charging.
[Nexus 7 (2013) Android Development] dang69:
Original charger? That makes a difference sometimes.

Most common fix is hold the power down for a good long time, like longer than 30 seconds.

Some people report success holding vol button at the same time kind of like the manual way to get to the bootloader.

You need to try all of the above 3 different ways, no cable,with original cable and charger hooked up and with known good cable hooked to computer.

The last resort is open the case with a plastic spudge, disconnect battery, reconnect.

Everyone I know that got past this did so with button pressing but weren't sure what combo was the golden bullet. Just keep trying with periods of rest on the original charger.

Dan
[Nexus 7 (2013) Android Development] Scott:
You and I think the same Dan! After trying every known possible key combo, I resorted to watching a youtube teardown video, popped the back off (without cracking or scratching anything might I add) and disconnected the battery for about a minute.

Reconnected the battery, plugged in power and left it for 10 minutes.

Went back to it, turned it on, and it booted up with 2 percent!

Got it charging now!
[Nexus 7 (2013) Android Development] dang69:
Sweet like pie. They really aren't that hard to open eh?
[Nexus 7 (2013) Android Development] Scott:
A lot easier than I thought!
[Nexus 7 (2013) Android Development] lollyjay:
Glad you're back up and running (pun intended). :D
[Nexus 7 (2013) Android Development] SwoRNLeaDejZ:
This happened to me too, and I did exactly what you did Scott :)

Glad you got the little bugger back to life.
[Nexus 7 (2013) Android Development] Scott:
I didn't get a chance to do much testing but she seems like the CleanROM we know and love :highfive:

Here is an interesting statistic: CleanROM 5.1 was downloaded over 9,000 times. If each person that downloaded CleanROM 5.1 donated $2.00 I would have 1/2 the cost of my surgery paid for! Think about it :D

-Scott
[Nexus 7 (2013) Android Development] Picao:
Thanks for all your hard work Scott, hope you get better soon. Confirmation number: 2MJ53804DV6902353., hope this helps. Have enjoyed your stuff since my Droid Incredible days.
[Nexus 7 (2013) Android Development] Scott:
Oh yeah, that helps! :good:
[Nexus 7 (2013) Android Development] davil124:
scrosler thank you for releasing an updated version of CleanROM for my N7. cheers!
[Nexus 7 (2013) Android Development] hedgefund:
Thanks Scrosler. Take care. Nice ROM. Make a little donation just already. Wish you every best and recover very soon.
[Nexus 7 (2013) Android Development] andyman_187:
anyone else not getting past the google splash screen? full wipe
[Nexus 7 (2013) Android Development] Guichinga:
Here you go: 7J194045TW358102B

Thanks for your awesome rom and your excellent support you do! :good:

Get well soon!
[Nexus 7 (2013) Android Development] Scott:
No. Could be bad flash or bad download. Did you check md5?
[Nexus 7 (2013) Android Development] dxboyz6146:
i've been waiting for this update after so long, and again thnx for the update

btw here's some tip for your hardwork ;)

2X619196K12350222 :cowboy:
[Nexus 7 (2013) Android Development] imgrealy:
Xposed works?
[Nexus 7 (2013) Android Development] andyman_187:
Nope, but I tried flashing your stock rooted 5.1 and it gets into the boot animation but ends in a black screen. I can turn it off with the power button though (power menu shows with only power off as option). Will fastboot flash stock image then I will try reflashing CR once again.
[Nexus 7 (2013) Android Development] Scott:
Yes it does!

Not sure if it works with Android 5.1 though. May want to take the time to research the Xposed forum ;)

Yeah, or just fastboot format userdata. Eitherway its the same thing.
[Nexus 7 (2013) Android Development] imgrealy:
I have a problem. When i connect headphones hear the sound through the speaker.
[Nexus 7 (2013) Android Development] Scott:
What app(s)?

Can someone test this for me? My tablet is too far out of reach.
[Nexus 7 (2013) Android Development] imgrealy:
Everywhere
[Nexus 7 (2013) Android Development] peter121484:
Me too, when i connected the earphone, the sound still coming from the speaker. All the apps i used have this issue too. I did a full wipe and factory reset, it still like that.
[Nexus 7 (2013) Android Development] Scott:
Ok, I think I know what it is...
[Nexus 7 (2013) Android Development] Scott:
This is going to be an issue. I may have to re-upload the ROM to fix it.

Its the power menu being ported from the Nexus 6 causing the problem.
[Nexus 7 (2013) Android Development] Yuccaman:
Here's something from me as well...

2JK17551NN550730H

Nice to see you back around following the Op.....
[Nexus 7 (2013) Android Development] Scott:
I got CleanROM 5.5.1 uploading. This fixes the headphone issue however it takes out the native power button until I can get more time to trouble shoot it.

I tried to make a patch but that didint work so it requires a new ROM download.
[Nexus 7 (2013) Android Development] Scott:
I had to remove the power menu (for now) as it was causing the headphone bug :o

Enjoy!
[Nexus 7 (2013) Android Development] vali_ics:
[MENTION=426561]scrosler[/MENTION] - Thanks for all your great work but i'll stick with 5.1.0 CleanRom because i really want to use xposed + greenify and some other modules...

If i'm not wrong amplify and greenify + xposed = bootloop on Android 5.1.

Thanks again!
[Nexus 7 (2013) Android Development] ganggreen30:
They have xposed alpha for 5.1 unofficial check it out
[Nexus 7 (2013) Android Development] madbat99:
Barely any modules work on 5.1 though. Gravity box doesn't for sure.
[Nexus 7 (2013) Android Development] ganggreen30:
This rom will not boot up I wiped stock rooted os I wiped data system dalvik cache and installed 5.5.1 went thru all the steps as directed and it says success then I reboot to system it shows Google boot logo then goes black and pops up Google and sends me back to TWRP.
[Nexus 7 (2013) Android Development] Tanogeek:
I have the exact same problem with the last upload
[Nexus 7 (2013) Android Development] ganggreen30:
It also says some symlinks failed
[Nexus 7 (2013) Android Development] Summit1:
No problems with installation after bootloader update and factory reset. Coming from Grogg's Way AOSP. I do immediately miss the clear all recent apps! Any way to add that functionality? Thanks for your hard work!
[Nexus 7 (2013) Android Development] Scott:
This means something is wrong with your internal storage. You may need to fastboot erase it. Or wipe data then reboot to recovery then copy ROM over and install.

EDIT: Another way to fix this issue is to flash the Google Factory image. Might be easier for some to just do that.

There is an app by [MENTION=631273]Chainfire[/MENTION] that adds it in the play store: https://play.google.com/store/apps/details?id=eu.chainfire.recently

Lets you configure it too
[Nexus 7 (2013) Android Development] Summit1:
Thanks . . . that works great and resulted in a donation, which was long overdue - shame on me! I've been using your CleanRom's for quite a while - since the Flo came out pretty much.
[Nexus 7 (2013) Android Development] Tanogeek:
After hours spent trying to flash 5.5.1 with the symlinks error, lot of full wipe (data, cache, system, internal), and files sideloaded, all went good when I unchecked "PlusOne and Photos" app in Aroma...

Don't know why it fails when it's checked.
[Nexus 7 (2013) Android Development] afonsov:
5.1.1 (LMY47V) factory image is out :)
[Nexus 7 (2013) Android Development] FooFighter312:
Happened to me just now and luckily I saw your post. Unchecking PlusOne and Photos fixes the issue for me as well.
[Nexus 7 (2013) Android Development] SwoRNLeaDejZ:
Yeah it is, and my Nexus 9 is still only at 5.0.1 as far as Google images are concerned. Very annoying. At least my Flo is getting some love.
[Nexus 7 (2013) Android Development] Scott:
Thats a work around but not a proper fix. If you look at the symlink errors its telling you its having an issue making the symlink due to no storage space. Trust me when I tell you that you should wipe data. But that is your choice.

DAMN!
[Nexus 7 (2013) Android Development] vietnguyen271:
Is this ROM used for Nexus 7 Wifi only? Can I use it for my Nesus 7 2013 LTE?
[Nexus 7 (2013) Android Development] DarrelK:
THANK YOU! I was getting the same error and it was driving me insane.
[Nexus 7 (2013) Android Development] Scott:
No
[Nexus 7 (2013) Android Development] Tanogeek:
I wiped everything following your post, my tablet was clean (system, internal storage, data etc) and I was still getting the error with Plus one and photos in aroma
[Nexus 7 (2013) Android Development] ianjojo:
samesies. did a full factory restore, and still got symlinks failed, and bootloop. worked fine when i unchecked "plus one".