yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] hohoeyo:
First of all, thank you for the help and guidance.

I spent a whole lot of time yesterday trying to research and figure out how to resolve this issue. Things I tried

1. Toolkit: Tried the Flash to stock with soft bricked status. Did not work

Here's the log of what happened when I tried this option ...

======

Flash Stock + Unroot...

------------------------------------------------------------------

sending 'bootloader' (3911 KB)...

OKAY [ 0.131s]

writing 'bootloader'...

FAILED (remote: flash write failure)

finished. total time: 90.699s

rebooting into bootloader...

OKAY [ 0.007s]

finished. total time: 0.009s

sending 'boot' (7204 KB)...

OKAY [ 0.233s]

writing 'boot'...

FAILED (remote: flash write failure)

finished. total time: 201.769s

rebooting into bootloader...

OKAY [ 0.007s]

finished. total time: 0.008s

erasing 'cache'...

=======

At this point, it essentially froze with no updates.

Then I tried the fastboot method.

2. Fastboot: Tried to flash latest stock image using fastboot. Tablet is in fastboot mode with Start, Restart bootloader, Recovery, Power off as the 4 options. I tried the following commands

* flash devices: works and shows the serial number of the device

* flash oem unlock: Says device already unlocked

* flash erase boot, cache, system, recovery: all either fail or just hang

All the while, the tablet does nothing but stay on the fastboot screen with the green android image.

I researched around and came across this thread that has a lot of similar issues

http://xdaforums.com/showthread.php?t=2471341

I'm concerned that my N7 is bricked as well and needs a new motherboard.

At this point, it looks like my only options are

1. Contact ASUS for options though highly unlikely anything will come off that since I bought this tablet the first month after launch in 2013. Any strategies or ways to get them to service it?

2. Order a new motherboard and test my noob skills at replacing it to see if that works.

3. Accept the worst and get a new tablet but the thing is there is nothing in the tablet world that comes close this tablet. I really love this tablet and find the size, weight and performance to be perfect.

Any other advise or suggestions?

And p.s., btw special thanks to mindmajick for the nudge to try things on my own ... learned about fastboot cmd line options and able to see that nothing really worked flashing boot, cache, system, etc. That led me to research a couple new error codes which led me to the thread talking about failed motherboards.

UPDATE: Looks like a whole bunch of folks having similar issues in the last few days

https://twitter.com/hashtag/NEXUS7BRICKED
[Nexus 7 (2013) Android Development] s9amme:
I had some GPS problems locking my location with other custom ROMs, worked fine on stock. Flashed the 5/04 nightly and GPS is working for me now (both device only and using WIFI networks). Everything else seems to be running fine too, no major issues i've run into yet :good:
[Nexus 7 (2013) Android Development] khaytsus:
Thanks for that confirmation... GPS was appearing to work for a week or so, but never actually got a fix... Hopefully it works completely now.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Is a official CM-Maintainer in this thread, or is it community based? :)
[Nexus 7 (2013) Android Development] idCyber:
Nexus 7 2013 CM maintainer? We don't have that, sadly, never did as I recall. Community shares their experiences here, no one is listening without proper bug report to CM if a problem occurs. Other Devs that build CM based ROMs , search and fix the problems themselves and if they propose to CM a patch, and it gets approved, then we get the fix our device needs, or when someone files a bug report and CM team looks into it. So either use CM with/without a different kernel and live with whatever else is broken (if broken) or go for other CM based ROMs that people that actually have the device and can maintain their build or AOSP ROMs.

Edit: I know I will be attacked again with PMs from CM fanboys (totally different thing from CM user) , please do not hate me but a ROM with no direct maintainer is what it is, as you have experienced with GPS for weeks or months and other stuff, that could only been fixed by a proper kernel from CM end or by flashing ElementalX or Glitch. CM nightly builds provided at mercy's will and fixes that come so late are not something to defend, sorry.

CM sources and the team efforts make a valuable addition to Android community and birth of multiple ROMs by different devs for all devices , and could even be a great ROM for our device but it isn't without a maintainer. For example: a device that has a specific ROM maintainer , bugs get fixed in a matter of days and a device without a specific ROM maintainer gets fixed in weeks or months.

P.S. : In my opinion, a flower with no one to care about her, that is next to another hundred of it's kind but those have people watering them and care about them, can't grow and be as beautiful as the others only with the water that spills from the other flowers.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Im your mind...

Flo is a popular device and CM doesnt care... Ok the most things are working, but there are no optimaisations or something like that :/

Its to say that Flo is a nexus and gets good updates from Google, but a bit sadly that there is NOBODY from CM who makes something :confused: :(

---------- Post added at 00:13 ---------- Previous post was at 00:09 ----------

BTW OP? Could you update the thread title to 5.1? Or is there a updated thread?
[Nexus 7 (2013) Android Development] Lawlrus:
Cm is ran off maintainers, they don't sit down at a table and divvy up money to buy devices, they rely on people stepping up to the plate to do the job.

If there is no maintainer, that means no one wants to take up the task of doing it.

Even though they want to sound like a company, they are not. They require people to out in free time to make sure the builds are running properly. 90% of the people that work with cyngyn, do it for free.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Sounds legal, but could you provide us sources? :confused:
[Nexus 7 (2013) Android Development] Lawlrus:
Source to my statement? That cm is a community driven thing?
[Nexus 7 (2013) Android Development] TheAvngrZ:
To the 90% and so on... but yea I beleive you
[Nexus 7 (2013) Android Development] Lawlrus:
http://wiki.cyanogenmod.org/w/Devs

Most of the people on that list deal with device vendors. The hardware trees and such.
[Nexus 7 (2013) Android Development] khaytsus:
I believe you're mixing things up a bit here.....

CyanogenMod is a community driven Android project.

Cyanogen, INC, is a company.

They each have different priorities. Some may overlap; others may not.
[Nexus 7 (2013) Android Development] TheAvngrZ:
But up to wich point is CyanogenMod community driven? CM is developed by Cyanogen Inc. and they are building the official builds... So where its community driven? Build + Develop = Nearly all? The only thing wich is community are Logs and Flashing, or not?
[Nexus 7 (2013) Android Development] idCyber:
The Android community is divided in 2 :

1. All devs that bring contribution with fixes and improvements to the Android code and build ROMs.

2. The users that flash ROMs and report back bugs and logcats.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Thats the way of unofficial builds and builds before nightlies... With our flo its none of that! :rolleyes:
[Nexus 7 (2013) Android Development] idCyber:
With our flo because we do not have an official CM maintainer, only other CM based ROMs that devs build, if they fix something, they send their code to be reviewed by CM team. Users can post bugs and logcats here but are never gonna be seen by CM team ever.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Yea, but what happend the last 100, 200 days? NOTHING!!
[Nexus 7 (2013) Android Development] idCyber:
My advice: Use other ROMs because official CM is not worth without a developer.
[Nexus 7 (2013) Android Development] Cryptecks:
This is where you're wrong and I'm surprised nobody else said it.

CyanogenMod is developed by some of the Cyanogen Inc people plus thousands of contributors through Gerrit. It is open source and not going anywhere.

Cyanogen OS is developed as a proprietary ROM wholly by Cyanogen Inc and they cherry pick Open Source parts as well.

I still agree with the overall sentiment though. Without an official maintainer, I wouldn't use CM for Flo.
[Nexus 7 (2013) Android Development] boxcar8028:
just flashed n5.13 and got lots of UI FCs. had to flash back to n5.12
[Nexus 7 (2013) Android Development] secaplus:
Same here.

Secaplus
[Nexus 7 (2013) Android Development] frenkowski:
same here...

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Nexus 7 (2013) Android Development] TheAvngrZ:
+1

flashed back too...
[Nexus 7 (2013) Android Development] xttapolatakettle:
Seems like a device-independent problem. 5/13 is crashing on other devices as well
[Nexus 7 (2013) Android Development] secaplus:
Hi

Issue solved on N0514.

I've noticed some visual change on group on homescreen.

Secaplus
[Nexus 7 (2013) Android Development] TheAvngrZ:
I notice in the last days a bit, that my device gets warmer than usal... anybody can confirm?
[Nexus 7 (2013) Android Development] xbs:
Here

https://download.cyanogenmod.org/?device=flo&type=nightly
[Nexus 7 (2013) Android Development] marsaltito:
05.01 dont work , wrong size too ??? 341.0B ?? 04 is ok . im looking for 05 too !? ;)
[Nexus 7 (2013) Android Development] maj_o:
GPS not working. Symbol is in status bar but no position.
[Nexus 7 (2013) Android Development] AnkeshReborn:
For miscallenous

Here's a link being shared, and its not a bug

http://pastebin.com/htnd4hhq
[Nexus 7 (2013) Android Development] atifsh:
Netflix doesn't work, can anyone confirm?
[Nexus 7 (2013) Android Development] Jhall8:
Netflix is working for me.
[Nexus 7 (2013) Android Development] atifsh:
Full wipe flash fixes the issue, seems dirty flash over cm11 wasn't good as what CyanogenMod stated.

strange seems its some problem with gapps, been using pa gapps mini modular as stock cant flash because of storage error.

now i flashed just the rom and installed netflix and it works.

i flashed gapps and netflix stoped working.
[Nexus 7 (2013) Android Development] k3lcior:
Working great for me so far, i'm on latest nightly. I dont like the built in Root though, SuperSU is just much better so i recommend flashing it right away.

Btw. does the CM OTA updates work for anyone?
[Nexus 7 (2013) Android Development] immiMIK:
Updater does not work. Currently I am using Cyandelta to update.
[Nexus 7 (2013) Android Development] marsaltito:
Il like CM12 , just not all apps are ready for 5.0 . :( i will wait some weeks before i try again .
[Nexus 7 (2013) Android Development] atifsh:
without gapps it works, with pa gapps mini modular it doesnt.

also cant flash the full stock version of gapps it says storage space not enough...
[Nexus 7 (2013) Android Development] mindmajick:
I use the following gapps with no issues. Lots of updates needed but no issues: https://s.basketbuild.com/gapps
[Nexus 7 (2013) Android Development] didicola:
same here gps navigation not working:(
[Nexus 7 (2013) Android Development] Naoras66:
i am coming from the last built of CM11 , how should i install Cm 12 ?
[Nexus 7 (2013) Android Development] Badger51:
Mark me confused...

Flashed CM 12 on my Nexus 5 and my calendar entries are not showing.. Only blank entries..

However my calendar is synching on my Nexus 7.
[Nexus 7 (2013) Android Development] Mucky2:
Is there ans custom kernel which supports double touch to wake?
[Nexus 7 (2013) Android Development] h0tkey:
Yes, this one.

With it, DT2W can be enabled in /system/etc/touchcontrols.sh.
[Nexus 7 (2013) Android Development] Mucky2:
Thanks bro! And how can I do this?
[Nexus 7 (2013) Android Development] h0tkey:
Find it with any root file explorer, edit it as a text file and change this line:

# Toggle DT2W (1 to enable, 0 to disable)
echo "[COLOR="Red"]1[/COLOR]" > sys/android_touch/doubletap2wake

Of course, do it after flashing the kernel and make sure to save the file and reboot after.
[Nexus 7 (2013) Android Development] AnkeshReborn:
How much MB does CyanDelta downloads for a nightly update (1 day)
[Nexus 7 (2013) Android Development] aggrophobik:
I haven't noticed mine running any warmer.
[Nexus 7 (2013) Android Development] klaust58:
Warmer? No.

My N7 seems a little bit more severe ?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] TheAvngrZ:
probaby I feel it only because its so hot outside, sorry guys
[Nexus 7 (2013) Android Development] secaplus:
Hello

Is it possible to edit the title of this tread, we are now on Android 5.1.1, Cyanogenmod 12.1.

Thanks, Secaplus
[Nexus 7 (2013) Android Development] mindmajick:
I really wish I knew more than how to build from source. I can't believe a device with this many users doesnt have a maintainer
[Nexus 7 (2013) Android Development] ShreckBull:
I use 0417 build and I can't lock screen rotation to landscape.

Am I alone ?
[Nexus 7 (2013) Android Development] ThehypnooToad:
Is it me or is cm12.1 running slow and buggy
[Nexus 7 (2013) Android Development] aggrophobik:
No issues to report here, running latest.
[Nexus 7 (2013) Android Development] idCyber:
No real developer (that understands how Android works and how to fix things) that has a Flo , ever stepped in to fill in the spot as CM device maintainer for Flo. No interest from devs for the device = vacant CM Flo Maintainer :)
[Nexus 7 (2013) Android Development] TunedFish:
Updated from 5/10 to 5/18 and everything still running well.
[Nexus 7 (2013) Android Development] TheAvngrZ:
No, runs fine, but some bugs didnt get a fix for months :/
[Nexus 7 (2013) Android Development] TheAvngrZ:
[MENTION=4650021]Cm9aphla[/MENTION] could you please update the thread to latest information?
[Nexus 7 (2013) Android Development] Cm9aphla:
Just did it. Thanks for reminding me.
[Nexus 7 (2013) Android Development] boxcar8028:
just flashed n5.23. smooth and stable.
[Nexus 7 (2013) Android Development] TheAvngrZ:
I'll do download and flash it now too... :cowboy:
[Nexus 7 (2013) Android Development] bokagavrilov:
Yea finally after months LiveDisplay got fixed too no more lags!
[Nexus 7 (2013) Android Development] blueyes:
12.1 runs great on deb, I'm just wondering why it pushes old radio image. It persists on installing 5.0.2 radio when I have 5.1.1 installed.. I have to extract it from zip and delete that section of update script. Every time I update.. Is it an over site or intentional? Because I get great reception with 12.1 and new radio. Most of the time better than my phone.
[Nexus 7 (2013) Android Development] blueyes:
OK
[Nexus 7 (2013) Android Development] khaytsus:
I hadn't updated in a few weeks so this might be fixed, but had anyone seen "all" of the sensors stop working? Rotation, light sensor, gryoscope are the ones I immediately notice, perhaps others stop working as well.

Most often I immediately notice the screen won't rotate or the backlight is stuck... if I reboot, it's back to normal. Although I wish I could adjust the backlight speed, it's sooooo slow to change. Yes, I could use Lux, but I hate running apps to do things the base OS does.
[Nexus 7 (2013) Android Development] marsaltito:
I have that issue too on cm-12.1-20150523 !

All sensors stop working ,i installed app from market to check it and all sensors was "red" not working !?!? And sometimes reboot dont fix it i need to shout down Nexus 7 (flo)
[Nexus 7 (2013) Android Development] bokagavrilov:
I was experiencing something similar too but it wasn't a software issue i had it on stock too (tested with multirom ) its a known problem for nexus 7 2013...the only fix i have managed to find its to press on the nexus logo pretty hard and boot it at the same time ..and its temporally..people have been saying that magnetic covers might mess up with it but its not really confirmed..

Here is the link i found about it on android authority http://www.androidauthority.com/nexus-7-2013-problems-524510/
[Nexus 7 (2013) Android Development] khaytsus:
..................press the Nexus logo?? erm..

Anyway, no, this never once happened on stock. Ever. I had stock for about 4 months then went to CM. Unless this is new to 5.1 or such... And the problem is always fixed after a restart, then randomly stops working again..
[Nexus 7 (2013) Android Development] bokagavrilov:
Reboots didn't fixed it on my end , have you tried a different kernel (personally I prefer elementalx)
[Nexus 7 (2013) Android Development] khaytsus:
I have not, but I've pondered it.. I typically will keep with a ROM for a while and see how it's set up, then start changing it... But given the Flo has no active maintainer, there's nobody tweaking specifically for it..... And besides, if it goes badly etc, simple to fix. I've actually downloaded the kernel a few times but never flashed it yet. Perhaps I'll do that and see if it helps.

I haven't attempted to debug the sensor issue... It's very likely kernel, unless there's an Android subsystem that handles all sensors like that, as they "all" seem to go out at once. GPS seems fine, but I'd have to verify that.
[Nexus 7 (2013) Android Development] andyman_187:
The sensor issue has bugged me ever since Kit Kat, and this seems to be a hardware issue. Check out this video for a potential fix:

https://www.youtube.com/watch?v=cOn...LCAeBe2hVU&annotation_id=annotation_572260273

I've tried this personally (except for the tape on the other parts which I think is a little overkill, instead I used some thin foam and taped them onto the ribbon connectors for a snug fit), and I have not had a problem with sensors freezing.

If you're brave enough to pull of the back cover and attempt this, it will most likely solve your sensor problems for good
[Nexus 7 (2013) Android Development] marsaltito:
I get something strange with latest CM12.1 !

I format (internal storage) my Nexus 7(flo) ,downloaded CM12.1(cm-12.1-20150526-NIGHTLY-flo.zip), gapps 5.1 (from CM wiki) to my PC , moved it to Nexus internal storage and installed them.

After install no option to make or connect to gmail account there is only google market that dont start at all !?

Anyone with some ideas what to do ?

*EDIT*:

I just found there is some bugs in official CM gaps i just got one from here on xda and worked fine ! Nice !
[Nexus 7 (2013) Android Development] W@r10ck:
Sup guys, I just had my Nexus 7 2013 LTE edition. I have ver 5.1.1 Build number LMY47V. I have a few questions. Does this means my bootloader is already unlocked? Is this compatible with this version? lastly, one reason I wanted to root my nexus so that I can enable tap to wake(if anyone is kind to share how you guys enables it)does this rom has that feature?. The power button placement really sux. Thanks.
[Nexus 7 (2013) Android Development] TheAvngrZ:
I you boughty your device and you did nothing on software its not unlocked.

You have a deb, so you need to flash a deb ROM over CyanogenMods Website.

Just root doesnt is enough for tab on wake for that you need a custom kernel for yor deb.

http://xdaforums.com/nexus-7-2013/development-lte is the section of your tablet stuff... you really must be careful, that all stuff is compatible with deb...
[Nexus 7 (2013) Android Development] W@r10ck:
Thanks for the info :)
[Nexus 7 (2013) Android Development] PowurPlayr:
Where to find Gapps for latest build? thank you...(didn't see link in dl section)

Found this:

I use the following gapps with no issues. Lots of updates needed but no issues: https://s.basketbuild.com/gapps

Thanks MindMajick!
[Nexus 7 (2013) Android Development] mindmajick:
You're welcome [emoji6]
[Nexus 7 (2013) Android Development] khaytsus:
By the way, the sensors all going stupid after a while seems to not happen when using the ElementalX kernel. So worth a try for anyone else annoyed by that issue.
[Nexus 7 (2013) Android Development] playitlouder:
Could anyone please test Soundcloud on CM12.1 offical?

I crashes on my Nexus with Glitch Kernel and f2fs when trying to play a song.

Not shure, if if is because I restored with Helium backup (although I completely uninstalled and reinstalled the app), or if it is rom related.
[Nexus 7 (2013) Android Development] klaust58:
Bootloop with current nightly 0623. Anyone else? :cowboy:

Log:

06-23 08:49:54.879: I/SystemServer(10669): Making services ready
06-23 08:49:54.880: I/SystemServiceManager(10669): Starting phase 550
06-23 08:49:54.895: E/AndroidRuntime(10669): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.fg
06-23 08:49:54.895: E/AndroidRuntime(10669): java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String[] java.lang.String.split(java.lang.String)' on a null object reference
06-23 08:49:54.895: E/AndroidRuntime(10669):	at com.android.internal.util.cm.QSUtils.isQSTileEnabledForUser(QSUtils.java:212)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at com.android.server.usb.UsbDeviceManager$UsbHandler.publishAdbCustomTile(UsbDeviceManager.java:913)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at com.android.server.usb.UsbDeviceManager$UsbHandler.updateAdbNotification(UsbDeviceManager.java:874)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at com.android.server.usb.UsbDeviceManager$UsbHandler.handleMessage(UsbDeviceManager.java:689)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at android.os.Handler.dispatchMessage(Handler.java:102)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at android.os.Looper.loop(Looper.java:135)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at android.os.HandlerThread.run(HandlerThread.java:61)
06-23 08:49:54.895: E/AndroidRuntime(10669):	at com.android.server.ServiceThread.run(ServiceThread.java:46)
06-23 08:49:54.897: I/SystemServer(10669): WebViewFactory preparation
06-23 08:49:54.907: I/Zygote(10669): Process: zygote socket opened, supported ABIS: armeabi-v7a,armeabi
06-23 08:49:54.947: I/ActivityManager(10669): Start proc 10784:WebViewLoader-armeabi-v7a/1037 [android.webkit.WebViewFactory$RelroFileCreator] for
06-23 08:49:54.947: I/Process(10669): Sending signal. PID: 10669 SIG: 9
[Nexus 7 (2013) Android Development] MaddMaxx636:
After i flashed the 6/25 nightly it keeps crashing to black screen and never comes out of the black screen state. It also never crashes and it also never lets me turn the screen down.
[Nexus 7 (2013) Android Development] akipapa:
Could you teach me how to get the log file?

Thanks in advance.
[Nexus 7 (2013) Android Development] TheAvngrZ:
download the ap syslog from playstore ;) this app makes all for you :)
[Nexus 7 (2013) Android Development] playitlouder:
Does rotation lock work for others on this rom? (in every orientation)
[Nexus 7 (2013) Android Development] khaytsus:
Okay, not completely.. After about 10 days or so of using the kernel, the sensors 'died' again. But it happens much less frequently I guess.
[Nexus 7 (2013) Android Development] playitlouder:
That happens on stock, too.

Just from time to time, but it is annoying nevertheless.

Does rotation lock work for you?
[Nexus 7 (2013) Android Development] khaytsus:
I used stock on my Flo about three months and at least a month on Lollipop, I never once had this happen, ever. But perhaps I just "got lucky".

Rotation lock? Sure, let the device go to sleep. Locks until you reboot it. :crying:
[Nexus 7 (2013) Android Development] playitlouder:
Had the sensor hickups from 5.0 to 5.1.

Sensor apps cannot read any sensors any more. Exept magnetism I think (CPUZ).

It is probably best to post a logcat, if it happens again.

My problem is, that if I tap the rotation lock button the tablet switches to Horizontal (the way the Bootloader is). It is not locked in the orientation I have been in (especially annoing in Youtube).