yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] laserbiz:
I know many people have flashed MM 6.0, but has anyone upgraded via the OTA to MM 6.0? I had origianlly flashed 6.0 but could not install the Netflix update so I reflash Lolipop 5.0 and upgraded via OTA's to 5.1.1 and here I sit waiting for the OTA of 6.0.

On a side note is there any chance of rooting this device. I have read thru this thread many times and not being as adept as many of the experts here, I am finding it difficult to find some clear instructions. any help would be greatly appreciated. BTW I know how read concise instructions, I have a rooted Galaxy Nexus and also a rooted Samsung Note 8. I can root but for some reason this Nexus 7 (2013) has me scratching my head. Thanks for reading and perhaps offering some help.
[Nexus 7 (2013) General] Masteryates:
The USB MTP is a bug. :crying:

You can go into developer options and see that your device is set to MTP but it still doesn't show up in windows explorer. The workaround is to change back to charge only and then back to MTP. :eek:
[Nexus 7 (2013) General] miniblue:
Rooting

If you google "Nexus Root Toolkit" and install it by Wugfresh you can follow simple instructions to rooting. It even steps you through getting and installing the required drivers.

You won't know what it is doing or why but it does get the job done.

There is a manual way step by step using ADB and there is a thread on this forum for that.

Good Luck
[Nexus 7 (2013) General] hellkiller:
Does somebody has problems with WiFi? When turn it on it takes too much time to connect to network. After connecting everything is OK.
[Nexus 7 (2013) General] fqr:
Yes, i have the same problem, when switiching on wifi, the N7 doesn't scan for wifi. so i have to open the dropdown wifi menu, then it starts scanning and connects.
[Nexus 7 (2013) General] hellkiller:
It connects in my case but takes much more time than before.
[Nexus 7 (2013) General] miniblue:
Is this with or without the OTA fix. On lollipop I had large problems with wifi connecting. With MM it is working great. I don't want to take the OTA fix if it will be screwed up again.

Thanks,
[Nexus 7 (2013) General] hellkiller:
[MENTION=2922634]miniblue[/MENTION] Last week there was an OTA update about 2MB. I installed it. But it was the same before it. No problems on Lollipop.
[Nexus 7 (2013) General] th.rahi:
:thumbup:
[Nexus 7 (2013) General] CouldntThinkOfAUsername:
How long will it take to release this an OTA, I really don't want to do a full wipe.
[Nexus 7 (2013) General] fqr:
then just flash system.img and boot.img from the factory image, whipe cache afterwards and youre done without loosing your data
[Nexus 7 (2013) General] Stanzilla:
6.0.0 (MRA58V) for the Nexus 7 @ https://developers.google.com/android/nexus/images?hl=en

Reddit: https://www.reddit.com/r/Android/comments/3r95t2/android_60_november_security_update_images_are_out/

Details at https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
[Nexus 7 (2013) General] mlj11:
What's the best way to update to the latest build without losing data and root?
[Nexus 7 (2013) General] idCyber:
Dunno if this works as have never tried but in theory , using NRT on the PC, you could update with no wipe option.
[Nexus 7 (2013) General] poisike:
I flashed MRA58V factory image on my razorg without wipe, everything worked as expected. Then i tried to root with Nexus Root Toolkit v2.0.5 but after doing this my device does not fully boot, it will stay on the new boot animation forever. Nexus Root Toolkit does not have MRA58V build, so i tried with MRA58K and "Any build" setting, but the result was the same. So i flashed system.img again and everything works again, but no root of course.

Is it possible to root razorg on MRA58V?

I understand i need a modified kernel? Is kernel the same for razor and razorg or are they different (because of mobile radio)?
[Nexus 7 (2013) General] Rempala:
lol maybe oneday i'll get the 6.0 ota.
[Nexus 7 (2013) General] yosmokinman:
^Back up your data, unlock the bootloader and flash the image. It is EASY.

^Chainfire hasn't posted a modded boot.img yet for 58v.

Assuming you're already on 6.0, use these fastboot commands:

Fastboot flash boot boot.img

Fastboot flash system system.img

Fastboot format cache

Fastboot reboot

You have to wait for the modded boot.img to be posted for root or compile it yourself. After it is just flash it like above then flash twrp then the su.zip through twrp.
[Nexus 7 (2013) General] Rempala:
I would love to flash it, but my usb port is completely shot. I have to charge it using a wireless charger.
[Nexus 7 (2013) General] seanvree:
If we are already on 6.0 how do we install the latest security OTA? I get the OTA, choose to install, and it reboots into TWRP, but then I can't tell what goes wrong because script moves too quick, so I boot back into 6.0 and the OTA is still there?

Thanks,
[Nexus 7 (2013) General] hellkiller:
You can't install the OTA if you are not stock - you have another recovery and update will fail.
[Nexus 7 (2013) General] Elcs:
My OTA for Marshmallow has popped up. Having just fixed my Recovery, went Xposed and 5.1.1 is running better than 4.4.2 ever was on this tablet I cannot justify taking the risk of moving to Marshmallow.

Glad to see that early impressions seem to be good :)
[Nexus 7 (2013) General] biggiestuff:
Did the radio change in MRA58V? I've noticed my cellular bar is constantly orange or red now.
[Nexus 7 (2013) General] Ambious:
Nope, same radio - same bootloader
[Nexus 7 (2013) General] DoM!niC:
Nice !!! :) I like real AOSP Roms like this ;)
[Nexus 7 (2013) General] Ambious:
Technically it's not AOSP but Stock.

AOSP means it's compiled from android source code, and usually doesn't have google apps in it natively.

Stock means the rom itself was compiled by google and apps and features were added to it based on the model.
[Nexus 7 (2013) General] struct:
Do we have a Marshmallow img to root 6.0.0 (MRA58V) yet ?
[Nexus 7 (2013) General] netpc02:
trying to find MRA58V modified boot image...
[Nexus 7 (2013) General] yosmokinman:
^ http://xdaforums.com/showpost.php?p=63645248&postcount=2506
[Nexus 7 (2013) General] Emalasto:
So if I've already taken the ota and the october security patch, am I still able to root? I'm just confused on which instructions to follow.
[Nexus 7 (2013) General] juliatan:
To root factory image 'razor-mra58v-factory-45d0421b' next to flashing bootimage 'razor-mra58v-boot.zip', do I need to flash stable SuperSu 2.46 or the beta SuperSu 2.52?

Thanks
[Nexus 7 (2013) General] juliatan:
Big problems here.

1. The file 'razor-mra58v-boot.zip' refuses to flash with TWRP.

2. As substitute used 'ElementalX-N7-5.05' causes bootloop

Anyone a solution for this?
[Nexus 7 (2013) General] pk-sanja:
No need for the modded Boot image.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 7 (2013) General] quickdraw86:
1. The reason the 'razor-mra58v-boot.zip' won't flash in TWRP is because it isn't a flashable .zip... If you look inside the file, there's no updater script or anything. You need to extract the contents of the .zip and install the resulting boot.IMG file to the boot partition of your device, which can be done in TWRP, flashify, or with ADB...

2. Versions of elemental x prior to 5.05 will result in a bootloop if you don't successfully install the modified boot.img and possibly a permissive .zip, and superSU 2.5.2 beta. See #1.
[Nexus 7 (2013) General] juliatan666:
Thanks for reply. But my Flo seems dead. Can boot into recovery, but flashing factory image fails. Some cannot write to storage error. Wish never flashed that damn ElementalX 5.0.5. Will read the unbricking threads tomorrow, but probably going to need new tablet.

Verstuurd vanaf mijn XT1562 met Tapatalk
[Nexus 7 (2013) General] quickdraw86:
Hmm... If you're unlocked and have a custom recovery, indeed, factory image will fail. I doubt you're hard bricked, but may take a few steps, and ADB to get you going again.
[Nexus 7 (2013) General] ksaves2:
I use adb on Ubuntu linux. I had the same problem. I used adb to load Marshmallow.img, got it running. Did the TWRP install, Elemental-X thing and superuser. Got that going. Funny thing is TWRP doesn't offer to root the device right off the bat like it used to. Says it'll keep the first ROM "read only". (I haven't messed with this for a long time mind you.) Hmmmmm, that's weird. So I did all the rooting routines like suggested for

MRA58V and later MRA58K. Is it really rooted? Well, I go to install Multi-Rom so I can add additional ROMS and guess what? I get it loaded and TWRP (2.8.7 ) keeps booting to TWRP no matter what. System was

pseudo bricked. So, I go back to installing 4.4.4, get to installing TWRP 2.8.7 and again no offer to ROOT the danged thing like in the past. Did the MultiROM install and thank heavens that "took" with no trouble.

Went and added a recent 5.1.1 Cyanogenmod Snapshot just fine and I can multiboot OK.

So, my basic 4.4.4 system with gapps runs fine, it appears rooted with SU and stickmount is in. I have Elemental X of both ROMs because I like to run an SDR dongle and it's nice to be plugged in to power cause it

sucks juice. If I need to plug in a memory stick, I just use a Y cable and have an external battery connected or a power supply and all is well. Or is it? When I fire up my Cyanogen Snapshot which is a 5.1.1 kernel,

it sure as heck not Rooted. I can't get it to root.

Is it possible to root the secondary ROM too? I want to download a Dark theme because I've had more luck reading the screen in bright sunlight using that and a small box that is painted flat black on the inside.

The theme will not install unless the device is rooted! So even though the primary 4.4.4 is allegedly rooted, the secondary seems not. Is that a quirk with TWRP or can all the ROM's be rooted?

Oh, to unbrick the N7 2013 using adb here's what I do on my Ubuntu linux box. If you can get it to the bootloader screen with the two finger salute, go to START. Make sure it's plugged in and in a terminal I type

"adb devices". If I (or you) get a response that your device is there, you're just about home. Now from the directory where you have the stock kernel .img unzipped (Make sure you have the permissions set on the files so anyone can read them, rwx, rwx,rwx is safe) there are a couple of bat file commands there. Just do sudo ./install-all.sh and away it will go installing the .img file. When done, reboot and be patient, it will seem like the system is stuck on the opening screen but it will come up and do final installing and you'll have a basic system back.

Oh, use Ubuntu because it's simple as pie to get the Android SDK utilities for ADB in. Simple to google that. I live a lot with Slackware and a rote install was not my cup of tea. Sounds stupid but leftover small hard drives can be nice sitting around because you can install a specialist app on it and drop it in and go.

Best regards, Kurt Savegnago your most humble script kiddie.
[Nexus 7 (2013) General] juliatan:
Stupid me managed to fix bootloop.

Flashing Factory Image still would not work. Trying to boot via fastboot TWRP several boot errors first, but TWRP booted finally after many tries*. (I have stock recovery, always boot not flash TWRP on my Nexus and Moto's). Saw via file manager in TWRP also Xposed files on my storage and remembered that I probably flashed Xposed too. Flashed the uninstaller and Flo boots again. Read that flashing Xposed for MM causes bootloops when not removing first some apps from system, because system partition too full.

*The flash errors and difficulty with keeping USB connection with Windows on my two PC's is probably caused by the Nexus hardware driver issue often terrorizing Nexus users with Windows 8.x & 10. Am going to install Ubuntu as multiboot and see if usb connection is more stable on Gnu/Linux. With loosing usb connection so often in Windows 10, flashing is too dangerous.
[Nexus 7 (2013) General] quickdraw86:
I think the thing that you might be missing is that CM 5.1.1 isn't pre-rooted. The last few official versions of TWRP (i realize you use a multirom recovery, but they share a codebase) will detect that, and offer to install superSU binaries before your initial boot of an unrooted ROM, but the detection and installation of the superSU binary is hit and miss. I don't personally use multirom (it's handy, I've tried it, but too much of a hack for my taste), but, AFAIK, primary and secondary files don't share all partitions, so, if one ROM is rooted, it doesn't necessarily mean the second one is as well. Great point about Ubuntu, it beats windows 8 and 10 hands down as far as driver detection, USB tether, and ADB... By a mile.

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Good deal that you got it. I've avoided windows 10 for that very reason you mentioned. I have old laptops that still run XP and windows 7 to keep me covered anyway.
[Nexus 7 (2013) General] ksaves2:
Is there a different modality from what I'm doing to multi-boot a couple of different ROM's so they can all be rooted? Thanks Kurt
[Nexus 7 (2013) General] quickdraw86:
No, what I'm saying is that between a primary and secondary ROM, if you've selected "don't share kernel" in multirom, the two ROMs share only

/sdcard. As the ROMs don't share

/system, or, more importantly

/system/xbin, where the superuser binary is installed to, you need to flash a superuser binary onto a ROM installation that isn't pre-rooted.

So, to answer your question, no, there isn't a better setup or modus operandi to rooting all ROMs, as the ROMs don't share the /system partition, the partition from which root privileges are installed/executed.
[Nexus 7 (2013) General] ksaves2:
Thanks loads. I found part of my problem for overall use was I used a zipfile

instead of an .img file for CF-Auto-Root-flo-(etc.) Really stupidhead move on my

part. So at least I have the Primary ROM rooted. My secondary is CM so this is workable for me. I originally had KitKat, loaded CM as a secondary, didn't realize the secondary wasn't rooted, finally got rid of KitKat and was able to somehow root CM. I wanted to try things out again so after multiple "bricking" events

I got it to a tolerable state. God bless adb and the "sudo ./flash-all.sh command.

Wipes 'er clean but at least brings it back to life!

Kurt
[Nexus 7 (2013) General] Wake89:
Hello, hopefully someone can help.

I bought my N7 2013 on black friday and let it update all the way to marshmallow OTA. So its completely stock.

I unlocked the bootloader, and im trying to flash the MRA58V boot.img i downloaded, but when I boot back into M and go to 'about tablet', it still shows the stock kernel.

Is there some step Im missing, it seems like my device is blocking the new kernel.

The flash of the modified boot.img appears to complete successfully but apparently it's not.
[Nexus 7 (2013) General] fqr:
6.0.1 factory image (MMB29K) for n7 is available; https://dl.google.com/dl/android/aosp/razor-mmb29k-factory-a39e7047.tgz

and here for the moble version: https://dl.google.com/dl/android/aosp/razorg-mmb29k-factory-44d21f0a.tgz
[Nexus 7 (2013) General] Cye3s:
Looking for boot.img to MMB29K root
[Nexus 7 (2013) General] rodhull:
You don't need one - the newest EXPERIMENTAL SuperSU flashable zip will auto-patch the stock boot image:

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[Nexus 7 (2013) General] r80ies:
I flashed 6.0.1 and now I have no free space in /system. Any thoughts or suggestions would be appreciated.
[Nexus 7 (2013) General] Andrew025:
I'm experiencing the same.
[Nexus 7 (2013) General] m+a+r+k:
Try the Bad Boyz cleaner script. It gets rid of useless system apps that you've updated and which then get stored elsewhere.

http://xdaforums.com/nexus-7-2013/development/rom-bad-boyz-nexus-7-stock-rooted-t3219148
[Nexus 7 (2013) General] nicche:
Hi everyone!

I've a N7 wifi model, yesterday I had try to root with CMW but when I opened the recovery pop out these errors:
[Nexus 7 (2013) General] frans23:
used the script, now my battery show 3,997% :eek:
[Nexus 7 (2013) General] holmgren:
I bought my mom a nexus 7 for Christmas and I just took it out of the box to get everything updated so she didn't have worry about anything and it had a small 10mb update that installed right away, but now it says that device is up to date and is still on 5.1.1. Did google push this out as an OTA or do I have to flash it? I also own an N7 but I have it rooted and have TWRP installed and havent used it for a while so I dont know.
[Nexus 7 (2013) General] $!>:
got an ota update for 6.0.1 guys.

i was on 6.0 fully stock.

i updated and my tablet is stuck in infinite boot loop.

tried clearing cache from recovery.

anyone face this?
[Nexus 7 (2013) General] Ambious:
I flashed factory image and it was fine at first, it only started bootlooping when I tried rooting.

It was resolved once I disabled "SELinux/Enforcing" in the Kernel setup.

Were you rooted/xposed?
[Nexus 7 (2013) General] nicche:
ok guys I resolved my problem with the N7.

I used first twrp, the multiroom mod. , then elementalx and finally supersu beta
[Nexus 7 (2013) General] $!>:
no i wasn't.

i hadn't even unlocked the bootloader.

i fear to do any of the measures cause ill lose my data.

any fix without involving rooting,unlocking bootloader or format/factory data reset???

cause i dont want to lose my data
[Nexus 7 (2013) General] sacto7:
Thanks about letting me know the OTA 6.01 is coming!

Got mine yesterday & it downloaded & installed without any problems.

My nexus 7 2013 is all stock & without any "additives". I did do the taps to get the developers' option tho but didn't do anything with it.
[Nexus 7 (2013) General] r.sorujlall:
i have a issue here. i've checked online but couldn't find anything to help me. i flashed the stock 6.0.1 MMB29K image and it boot. i want to root for i down twrp 2.8.7.0 (latest) and i unlock my bootloader without issue. i then flash twrp through fastboot and boot into twrp but my entire device seems to be wiped. the supersu zip and everything is gone from the device storage and when i try to reboot i get the "NO OS INSTALLED" message. it seems that flashing twrp wipe my entire device. is there a special way or version of twrp i have to flash. i tried it twice to be sure and redownload all the file to rule out corrupt download
[Nexus 7 (2013) General] nicche:
mhhh....when you unlock the bootloader, basically you do a big wipe in fact the message say this

and then when you flash the factory image if you use the script " flash-all.bat " automatically It does a facroty reset. So you should flash again the factory image with fastboot in bootloader mode, then try to flash this version of twrp http://d-h.st/Uz5u it works for me and finally flash the right version of supersu with twrp obviously!

I hope that you understand my knowledge of english isn't high!
[Nexus 7 (2013) General] r.sorujlall:
I will give that version of twrp a try.

I do understand that unlocking bootloader wipes the system. That's not the issue. After unlocking bootloader I can reboot to the os just fine and setup back again. But when I flash twrp latest two versions (2.8 & 2.7) it formats the device also not wipe. There is no os, user data, nothing
[Nexus 7 (2013) General] nicche:
It's so strange! anyway I had try also many versions of recovery but they had a issues like as doesn't works the mount storage or not works flash supersu.

In the end I used the version multirom twrp with elementalX ( very good kernel) and finally SuperSU-v2.62-3
[Nexus 7 (2013) General] r.sorujlall:
Thanks for the tip. I'll totally give it a try tonight when I have some free time and post back the result

Update: so multitom twrp work. thanks man. got root and rocking the kernel you suggested
[Nexus 7 (2013) General] juliatan666:
Flashed 3 times 2 different 6.0 images. Now flashed 6.0.1 image. In total minimal 6 factory resets. Still huge battery drain. With wifi off 1-2% an hour. With wifi on 2-3% an hour. Google syncs off, most Google apps disabled. Not installed apps yet now.

Before MM idle drain was 2-4% after 24 hours.

In wifi advanced set to never keep wifi on when screen off not working. Must disable wifi manually.

About to give up on MM. Very disapointed in Google's sloppy firmware again after 5.0.x debacle. Read many simular bad battery life reviews. And good ones like battery life is a lottery on MM. Does Google even test their own firmware? Downgrade to LP or KK, or perhaps after years try a custom rom is next. And will not upgrade other devices to MM yet.

OMG. Am I gonna miss RRO Layers in MM if going back to stock 5.1.1. Was lIke a dream come true.

Verstuurd vanaf mijn XT1562 met Tapatalk
[Nexus 7 (2013) General] noahvt:
Why does every .0.1 release always f*ck up my device and make it almost unusable??!!

5.0 & 5.1 & 6.0: Everything super stable.

5.0.1 & 6.0.1:

Touchscreen bareley works,

Cannot watch a youtube video without crashes,

Tablet reboots a lot,

Extreme battery drain,

Extreme heat,

App fc's, App fc's everywhere,

Memory issues,

....

This keeps frustrating me, every .0 or .1.1 release works flawlessly and then the .0.1 releases come and f*ck everything up :/
[Nexus 7 (2013) General] SurferLTU:
Is that battery drain aknowledged by google as a bug officially?
[Nexus 7 (2013) General] kalda01:
Is there a USB connectivity issue ? my PC shows empty folder under NEXUS 7 2013 device.
[Nexus 7 (2013) General] miniblue:
Don't forget to change USB mode on tablet to file transfer. It defaults to charging only
[Nexus 7 (2013) General] kalda01:
Thanks. That was it.
[Nexus 7 (2013) General] mydian:
How strange. My tablet got the 6.0.1 OTA (it's not rooted at this time) and doesn't have any of the issues you're describing. 6.0 had the occasional reboot but so far 6.0.1 has been rock solid. Excellent battery life as well. Much better than lollipop. I have the opposite luck it's usually the x.0 releases that give me problems.
[Nexus 7 (2013) General] RBEmerson:
I'm currently using a rooted 5.1.1. Of course this means the OTA won't work. What are my choices so I can bump up to 6.0 and be rooted (mainly for TI)?

ADDED: I don't like FDR's but I won't resist it for this device.
[Nexus 7 (2013) General] jshamlet:
Get the factory image from Google. Modify the flash-all.bat by taking the -w out of the fastboot command. Run flash-all.bat. Keep in mind, this is the equivalent of a "dirty flash", but it worked fine for me going from 5.0.1 to 6.0.

As for root, Chainfire has a .zip of the beta systemless SU that you can install from TWRP which will modify the boot image for you. He has one specifically for several models of Nexus devices, so pick the right one. I ran it on my N7, and it worked just fine - as did the systemless adaway .zip. Just keep in mind that you need to tell TWRP to leave your /system partition read-only and for the love of all that is holy, DON'T install supersu when you reboot (ever)
[Nexus 7 (2013) General] RBEmerson:
Er, what am I missing about SuperSU? AFAIK, without it, there's no way to grant su to TI, CM, FX, etc.
[Nexus 7 (2013) General] jshamlet:
The systemless root .zip you installed from TWRP will put a copy of SU free on your device as part of its installation.
[Nexus 7 (2013) General] RBEmerson:
For reasons I don't understand, almost any rooting I've done (4 different devices/mfgs to date) refuses to install SU or BusyBox for me. OTOH, if I install them by hand from Play Store, life is good. What's the risk here?
[Nexus 7 (2013) General] jshamlet:
If you are using systemless root, and thus left your system partition read-only, there are special instructions for Busybox - which, unfortunately, require the paid version. When you go to install, change the install path to /su/bin. It should work fine after that - I have BB on my One M8 and N7.
[Nexus 7 (2013) General] RBEmerson:
The new BB update specifically includes systemless rooting as a updating point. I also "own" SuperSU Pro as well as BB Pro. How much does that change things?
[Nexus 7 (2013) General] jshamlet:
Nope - I just did it before the update.
[Nexus 7 (2013) General] RBEmerson:
Gotit - more next week, when I return to the States from Germany (and a miserable DSL connection).