yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] v12xke:
Trying to upgrade my LTE N9 to LMY48I. Capability is there in "flash stock" to d/l the new Google image and to check the file hash, but there is no patched boot.img for no force encryption available yet and I am unencrypted. Can I use the previous patched boot image? Either that or I need a flashable OTA file from LMY47X=>LMY48I. Thanks.
[Nexus 9 Android Development] prdog1:
If security fixes weren't in the kernel can use the old one. :cool:
[Nexus 9 Android Development] lept_2014:
If you want a 'boot.img' modified for N9 LTE (LMY48I), I made it.
[Nexus 9 Android Development] v12xke:
Thanks... much appreciated.
[Nexus 9 Android Development] v12xke:
FYI..... Wug is working in the background. Toolkit was updated for LMY48I with image and no_force_encrypt kernel. Woot!
[Nexus 9 Android Development] undertaker2k14:
I used this tool to update my rooted, unlocked N9 from LMY47X TO LMY48I yesterday and the device kept on rebooting straight to recovery despite me trying to flash stock + unroot multiple times with both no wipe (initially) and later with wipe data and soft brick selected. Even tried to flash LMY47X back but no dice (booted but gave a 'no command' error screen), and during my last attempt to flash LMY48I again to do a factory reset one of the extractions failed and the device is permanently bricked. Been using this toolkit and nexus devices for 4 years, first time this happened. When my replacement comes, I am just unlocking the bootloader and going with stock OTA updates, with monthly updates rolling out for nexus, doing this manual flash everytime is going to be one big PITA.
[Nexus 9 Android Development] madbat99:
Should have used the force flash option.

BTW, Android on his back and "no command" on screen is not an error. It's stock recovery.
[Nexus 9 Android Development] undertaker2k14:
I did use the force flash option every time , just like when I used the tool to update from 5.0.2 to 5.1.1 (which only took one try).

As much as I love tinkering with stuff in my spare time, doing a manual flash every month may just deter me from rooting the N9 again.

Not an android expert by any means (only delve into it when needed) but have been rooting/flashing stuff since 2011 with my Infuse 4G, never ended up with a hard brick before. Being a nexus and my stellar experience so far with Wug's tool, this was least expected.

Come to think of it something about the N9 is just unfriendly, I recall when google botched the 5.0 to 5.0.1 update and I had to manually flash the stock images to get it back up (early days of the N9, do not think wug's tool was updated to support N9 at that point). On my previous, N5 and N7s never had a botched update.
[Nexus 9 Android Development] undertaker2k14:
Has anyone else done a flash to stock + unroot using the toolkit from LMY47X yet? Wondering if it was just sheer dumb luck or if there is an issue with doing the upgrade this way? I did try to use force flash + wipe when I tried to restore the LMY47X and it still rebooted back to recovery /no command (this is right before the final, fatal attempt). My biggest failure was not taking a full adb backup prior to the install, that would have likely saved the day.
[Nexus 9 Android Development] undertaker2k14:
Really wish someone can validate/invalidate my scenario by doing the LMY47X to 48I upgraded on a rooted, stock N9 and see if they are successful. I was using windows 10 though that shouldn't have been an issue since I reinstalled nrt and ADB recognized the N9 until the last fatal attempt (only thing different about this last attempt was I selected factory reset post flash to stock option). And 47x TO 48i should just work without wiping data unless I am missing something,
[Nexus 9 Android Development] prdog1:
Easier, quicker and safer to just fastboot the factory image. :cool:
[Nexus 9 Android Development] undertaker2k14:
Isn't that what the flash stock + unroot does anyways in NRT albeit via the GUI? If not, that's what I will do moving forward...
[Nexus 9 Android Development] prdog1:
Pretty much but uses other scripts also. With manual fastboot we haven't seen any of these bricks. And never set it to lock without a first boot. If unlocked should be able to fix it even if something goes wrong. Not sure what your brick was but most can be fixed with a manual format and reflash. I been lucky. Have had bad flashes both manually and with toolkit but have always been able to get out of it with manual fastboot. :cool:
[Nexus 9 Android Development] madbat99:
I updated with the flash stock option and it went fine. if you selected factory reset after flash, thats why you were on the no command page. You probably could have just finished going into recovery ( by holding power and tapping volume up) then selected factory reset in stock recovery. Thats what I do anyways. But if you didnt select factory reset after flash stock, you might have just needed to wait longer. sometimes the scripts take longer on n9.
[Nexus 9 Android Development] undertaker2k14:
Got my replacement yesterday and so far so good, it auto updated to LMY48I without issues. QQ: After reading different posts, it seems that folks are having trouble unlocking the bootloader if not done prior to 5.1, but couldn't find anything definitive.

I do plan to unlock the bootloader eventually (though avoid root this time for the convenience of monthly OTAs), any known issues with unlocking the bootloader on a device that is already on LMY48I stock?
[Nexus 9 Android Development] madbat99:
No issues. But unlocking wipes all your data so you should do it before you set up.
[Nexus 9 Android Development] JMooney5115:
So much easier than rooting my HTC Incredible back in 2010.
[Nexus 9 Android Development] tommy24:
Delete
[Nexus 9 Android Development] johna2u:
I just update my nexus 9 lte to LMY48T from LMY48M using the Sideload ota feature. That worked perfectly. Someone had suggested this would trigger the 6.0 update to kick in if I was on the latest build. Well, no luck so I decided to just go the next step and Sideload 6.0 the same way. I am getting errors that the needed support files are not available. LMY48T isnot available in the dropdown menu so I chose "Any". Any ideas?

I am pure unrooted stock with original factory recovery.
[Nexus 9 Android Development] madbat99:
You can pick 6.0 as your build and choose flash stock+unroot with " no wipe" enabled. Or even download the ota yourself and sideload with wugs.

Sent from my Nexus 9
[Nexus 9 Android Development] johna2u:
I did download the 6.0 ota update but tried the Sideload ota update option in wugs. It want to download stock recovery and I guess can't find it so it errors out. I will give your method a shot.
[Nexus 9 Android Development] madbat99:
Stock recovery is in the factory image. Just extract it. Then use fastboot flash option in wugs. If you want stock recovery.

Sent from my Nexus 9
[Nexus 9 Android Development] lilliput222:
these md5 errors are driving me crazy . I have downloaded stock rom from volantis from Google as well as Toolkit itself many times everytime md5 mismatch on evry downloads wheather rom or no_encryptkernel
[Nexus 9 Android Development] johna2u:
Ok Problem solved. I am now successfully on 6.0 This is what I did.

My previous build was LMY48M

I updated through Wug's Nexus Root Toolbox using the Sideload OTA update feature to LMY48T

After the update I received a pop up through wugs asking if I wanted to update my Build number. I don't recall what I did at that point but I think that is what caused my issues updating to 6.0

No OTA marshmallow update notification ever came through.

I tried to manually flash the update the same way I Updated to LMY48T.

No go. I kept getting a message that there were no files available from google for my build number (LMY48T was not available through the dropdown menu in Wug's so I had selected "Any"

Finally I ran the sideload function again. This time choosing LMY48M as my build. I received a warning the the build did not match but I went ahead and proceeded anyway.

Finally the update proceeded without a hitch and I am ready to Explore Marshmallow 6.0

I am posting this just in case someone else is having the same issue.
[Nexus 9 Android Development] macrossmerrell:
When that happens to me, I have to pull the power on my router. Usually to many discards have been captured and the memory is full.
[Nexus 9 Android Development] lilliput222:
Uninstall and Re-Install toolkit resolved the problem :fingers-crossed::laugh:
[Nexus 9 Android Development] avinashdelhi900:
Any luck rooting Android 6.0 with this toolkit??
[Nexus 9 Android Development] liang512:
Yes, I had.
[Nexus 9 Android Development] ricco333:
Ok, I need your help, I'm on 6.0 unlocked bootloader, twrp installed decrypted but I can't seem to be able to root this thing, it doesn't matter what I flash it always hangs at the Marshmallow boot animation, tried to flash SuperSU 2.52 with the boot image combo and same results, believe me I've tried. First time using a toolkit, so what do I do to root this N9 in 6.0 with Wufresh toolkit?

Any help will be greatly appreciated.

Thanks

Erik
[Nexus 9 Android Development] liang512:
I am sure you read the instructions here, https://plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp

You can try TWRP, wipe>factory reset, and see if it will boot. If it still does not work, you can flash stock + unroot, and root it again.
[Nexus 9 Android Development] v12xke:
Make sure to install a kernel first (or Chainfire's boot.img) before flashing SU. From TWRP transfer the files from your PC to the root of N9, and then flash them with in order withTWRP. Why not try a custom kernel like ElementalX? Flash the kernel first and then SU. If you cannot get root this way, you probably will need to do a factory reset.
[Nexus 9 Android Development] placebo_domingo:
I seem to have run into a problem when flashing 5.1 LMY48M image, (I'm not ready for 6.0 yet) All goes fine via fastboot, and it finishes but device just stays at the Google boot screen. I've waited well over 10 minutes. The only error I see in the Windows terminal screen is at the very end. FAILED (command write failed (Unknown error)) And it finishes right after that. I can still get back to fastboot and it still shows up under fastboot devices. I also tried the newer LMY48T image - same deal. Should I try 6.0 instead or would I just be digging a deeper hole? Never had a problem with the NRT before. :(
[Nexus 9 Android Development] madbat99:
Are you sure that your bootloader is unlocked?
[Nexus 9 Android Development] placebo_domingo:
It says ***Device State - UNLOCKED *** at the top.

FLOUNDER PVT SHIP

HBOOT-3.44.1.0123

OS-n/a

eMMC-boot 2048MB
[Nexus 9 Android Development] placebo_domingo:
Just did a manual flash. All good now! :)
[Nexus 9 Android Development] manxexile:
Have you tried using the ElementalX kernel @ http://elementalx.org/ ? Worked fine on both Nexus 7 Wifi & the 9 before Wug developed his own rooting procedure!
[Nexus 9 Android Development] ritchea:
[MENTION=3110798]WugFresh[/MENTION],

Haven't run 2.07 with my N5 yet, but N9 system update and reroot went smoothly. [I didn't even try with 2.06 :( ] FWIW, this is the first time (of maybe 6-8x) using the toolkit with N9 that the tablet automatically rebooted from the fastboot screen at the end of the system et al flash. I always had to manually reboot. Xposed and Gravity box working as on K version.

As always, thanks for getting on top of the issues.
[Nexus 9 Android Development] WugFresh:
Hey guys/girls - I know I have been a bit MIA on XDA, but I am still around

If I missed any of your posts - my bad. I will try to back track through this thread.

NRT v2.0.7 is out now with support for all the new marshmallow builds, and a whole big script on my end to keep supporting new ones as they come out. NRT v2.0.6 had some bugs - so I am sorry if any of you were having complications with that release.

Make sure you update the kit to the latest masterlists via the update button, or letting it auto update on start (as of this post the latest are 3092). Cheers! Enjoy!

{{ WugFresh }}
[Nexus 9 Android Development] aaronsomek:
Thank you man, you saved my Nexus! Great app!
[Nexus 9 Android Development] osnapitsjoey:
If I root using this method, and unroot when a Ota update comes around, will I be able to download the Ota?
[Nexus 9 Android Development] madbat99:
Yes. Or just flash the new factory image with no wipe option. That unroots and updates in one step.
[Nexus 9 Android Development] osnapitsjoey:
Thanks man.
[Nexus 9 Android Development] AlexanderDG83:
Used Wug's toolkit to unlock and root my new nexus 9 and now all works very good. Thanks!
[Nexus 9 Android Development] nightshot72:
I love this toolkit, saved me many hours work, thanks wugfresh
[Nexus 9 Android Development] simonintx:
I've been working on this for two days and not making much progress. Can someone help?

I'm trying to root 6.0.1 I flashed the factory image. The factory image worked fine. Then I tried to root using the Toolkit. It would get stuck on the bootscreen and never boot. I saw this post and tried to flash the Elemental kernel first. It said it flashed fine but it won't boot. It gets stuck on the bot screen with the red exclamation mark. I must be missing a step. The other thing I noticed is I can't get into TWRP recovery using power and volume down. The only way I can get to it is to use the Toolkit and it will "temporarily" let me use TWRP.
[Nexus 9 Android Development] v12xke:
Things have changed since my last post. Systemless now. Make sure the latest EX and SU systemless are in the root. You can use MTP even in temp TWRP to move those. Flash those and try to boot. If no joy, factory reset. Boot to the dead Android and use keypress to access the factory recovery. The toolkit flashed over your recovery, so you'll have to reflash it back later on. Best I can do ATM...on the road. Will check back later.
[Nexus 9 Android Development] simonintx:
Worked perfectly! Thank you! I have Super SU and busybox installed from my old system. Should I delete them?
[Nexus 9 Android Development] v12xke:
Maybe you mean the apps? You may have residual Busybox installer app, but Super SU should have been updated.

1. Flashing Chainfires' SU installs the correct new app in your drawer, and you can check the version number to be sure. Should be 2.62 or 2.64.

2. Busybox installer app should be run as several root apps require it. I use BusyBox Free.

I would encourage you to install a minimal ADB/Fastboot on your system and just do this yourself from now on. There are many tutorials on how to fastboot flash images your phone. Not to take anything away from Wug's NRT, but you can do the whole upgrade from the Google factory image files as soon as they are released by Google.

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

Not a tutorial, but here is the sequence I use on my N6, N7 & N9.

1. Drop the very latest systemless Super SU.zip and EX kernel.zip into the root of your storage/SD.

2. Fastboot flash the bootloader, radio, system, boot and vendor(N9) .img files. Do not flash recovery or userdata.

3. Reboot to recovery (since you don't flash recovery, TWRP is still there)

4. Flash Super SU and EX Kernel (or any custom kernel that supports systemless)

5. Reboot and *do not* let TWRP "root" or otherwise write your system. It hasn't been updated yet to understand systemless root.

Good luck!
[Nexus 9 Android Development] glockman4519:
Just wanted to thank you once again. I got the donation version of this outstanding program when I got my Nexus 6. I have since used it for my Nexus 10 and just today, not 30 minutes after first bootup of my new Nexus 9. I have used quite a few tools like this that do what this one does but in my humble opinion, this one is the best hands down.

"Chance Favors the Prepared"
[Nexus 9 Android Development] glockman4519:
I tried using the advanced utilities to get rid of the forced encryption on this device and I got several errors in TWRP, most of which were unable to mount storage and then put my device into a recovery boot loop. This tool is great though because I used it to revert back to stock and re-set my device back up. Still wondering why it did that though. I will do some more research on disabling the forced encryption before I proceed though. I will just have to be careful what I flash now.

Edit;

I got it. After going back to stock with this great tool, I just formatted my data and that got rid of the forced encryption.

Thank you again for such a great tool.
[Nexus 9 Android Development] seegs11:
I've unlocked and rooted my nexus 9 running 6.0.1. Is there anyway I can downgrade to lollipop 5.x.x? If so can someone please provide guidance how to?
[Nexus 9 Android Development] madbat99:
Just pick that as your build in the toolkit and do a flash stock+unroot. Easy peasy.
[Nexus 9 Android Development] WugFresh:
Need a tester for Nexus 9 who is running stock android N preview with an unlocked bootloader. Please message me on google hangouts, wugfresh at gmail. Cheers,

{{ WugFresh }}
[Nexus 9 Android Development] Migamix:
https://www.androidfilehost.com/?fid=123

for noforce_encrypt_volantis_npc91k.img

FAILS, 404, DNE

last thing i want is an encrypted N9, its slow enough already, and i see the N9 not in the list on the main web site as and official thread, i guess this is another orphaned device noone wanted, but i own one thats getting little support.
[Nexus 9 Android Development] Wi1son:
On the latest Pure Nexus ROM - Not sure what I should choose for my Android version, since About Tablet lists the build number as MTC19T? Should be AOSP 6.0.1_r25. Thanks.
[Nexus 9 Android Development] corkiejp:
Did you find a tester yet?
[Nexus 9 Android Development] jerryatherton:
I can test.
[Nexus 9 Android Development] WugFresh:
I still need a Nexus 9 tester who is running stock android N with an unlocked bootloader.
[Nexus 9 Android Development] corkiejp:
Test Done. Your Welcome.
[Nexus 9 Android Development] fkinell:
Beta N - Nexus 9 – Formatting is not supported for filesystem with type 'f2fs'

Hi, In removing Beta N from my Nexus 9 using NRT (which has worked flawlessly everything b4) I am unable to Flash Stock + Unroot.

The process goes through un-hindered until I get ..

Formatting is not supported for filesystem with type ‘f2fs’

On Reboot I am stuck at the Google Screen and nothing happens!

Either I or the solution to this is “Simple” I am sure.

I appear to have full control over the N9, I can access TWRP I can wipe and format partitions …etc.

Just can’t get the N9 to accept a stock ROM after the Beta N trial (which was becoming unusable anyway)

Please help..
[Google Chromecast] mimepp:
It's free. Have fun!

speed4cast - Speed for chromecast

speed4cast: test the network speed for chromecast

Download:

You could search/download speed4cast from google play store.

User guide:

http://goo.gl/0m0Hoz

Features:

measure download speed

upload speed

latency

jitter

Usage:

speed4cast allows you to measure download speed, upload speed, latency and jitter of chromecast
[Google Chromecast] mimepp:
User email group:

https://groups.google.com/group/speed4cast

Demo video:

youtube:

https://www.youtube.com/watch?v=yZ2Kr__DBhc

youku:

http://v.youku.com/v_show/id_XODI5OTYyODYw.html
[Google Chromecast] mimepp:
screen shot:
[Google Chromecast] woody1:
I tried it, and it went to Pass 3 and got sick at 94%...

---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------

Then I got "Error:2001 test error"
[Google Chromecast] theronkinator:
Worked great for me, really useful, confirmed my thoughts about the Chromecast wifi been rubbish which is ashame, only getting 7.48Mbps down, when my phone next to it is getting ~30Mbps.

Using the App I've played around with my chromecast location, if I connect it to a 2m HDMI cable and move away I can get the chromecast to 24.83Mbps which is obviously a massive difference, chromecast is always doing HD now instead of flicking between HD and VHS.

Thanks.
[Google Chromecast] ROADKING17:
Download 14.04 mbps over here upload 0.8 mbps
[Google Chromecast] crypt0kiddie:
Yeah I can confirm that this app allowed me to figure out that I get a consistent increase of 5~6.0Mbps more speed when using the HDMI extender.

Left this a 5 star rating!
[Google Chromecast] mimepp:
That's great.

Enjoy.
[Google Chromecast] mimepp:
http://www.pocketables.com/2014/11/test-chromecast-speed-speed4cast.html

Test your Chromecast speed with Speed4cast

Paul E King, November 20, 2014

Thanks.
[Google Chromecast] mimepp:
Does anyone need function to test the speed of local network?
[Google Chromecast] Leavard:
I think it would be useful so you can figure out if the poor performance is due to your WI-FI or the actual internet connection.
[Google Chromecast] ThisWasATriumph:
Yes. My internet speed is only 5 MB/s-down 0.6 MB/s-up so that doesn't test how my wifi is functioning. Streaming off my local network sometimes requires 30-50 MB/s.
[Google Chromecast] mimepp:
LAN speed test may need an internal server.
[Google Chromecast] Leavard:
You could probably get away without the server so long as there is a SAMBA shared directory on the network.

BTW, is there a change log for the Play Store update that just showed up?
[Google Chromecast] MattDN93:
Thanks OP for this useful app, also helped determine the HDMI extender really does improve WiFi throughput from my router, at least, the connection speed to the server improved a lot and on a 2mbps down / 384k up line here in South Africa, that's already a big deal ;)
[Google Chromecast] mimepp:
:) Enojoy it.
[Google Chromecast] c6z06vette:
Great little app!!!!! :D

I got following:

Download: 21.92 mbps

Upload: 4.97 mbps

Latency: 17 ms

Jitter: 700 ms

Running an Asus RT-AC56U router with latest Merlin firmware and set Chromecast MAC address to "highest" under QoS under 2.4 GHz wireless. I will run some test moving it around by extending the Chromecast stick in a best position to see if I can improve upon this and report back. ISP is Comcast with typical down/up on a desktop with OOKLA at 60mbps/5mbps.

Based on others experience are these numbers good?

Much thanks for the app!
[Google Chromecast] atomomega:
Great app!! :) thank you very much dev.

Can someone please explain to me what difference does the HDMI extender make? I see some people say it helps them get faster speeds but how?
[Google Chromecast] mimepp:
By default, chromecast will be pluged to TV at rear, wifi signal may be affected by TV.

HDMI extender could help to put chromecast to a right position.
[Google Chromecast] benji14410:
Really good app to test network ! Thank you so much !
[Google Chromecast] atomomega:
Aaah I see! Good point, will try it and see if there's a noticeable gain in terms of speed.
[Google Chromecast] mimepp:
Enjoy speed4cast in 2014.
[Google Chromecast] mimepp:
review for speed4cast:

http://yiwei911.blogspot.com/2014/12/google-chromecast.html
[Google Chromecast] Bobacco:
Hey! I know it's been a while, but I didn't have any luck with getting it to work on a chromecast 2. Is there a way to achieve this?
[Google Chromecast] fgoyti:
Getting a 1001 error, invalid account. Is this working for anyone?
[Google Chromecast] vijaykirann:
Same error here too
[Google Chromecast] mimepp:
it works now, enjoy it.