yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] ftd0411:
Is there a way to flash this so that it does erase all personal data? I'm in a real bind. I have a U.S. unit that the screen went dead and debugging is not enabled. I was logged into my Google account and email and pics are on there. I have no way of controlling the unit, although the bottom buttons light up and I hear sounds when I touch the screen or push the power and volume buttons. I tried hooking it up to my TV through the mini USB-HDMI, but no signal comes out, so the entire video must be shot. If I can flash something through odin that will replace everything back to stock, including erasing any personal info., I would be more comfortable with returning the unit. But the above post seems to say apps and personal data are not erased with the firmware here. Any help would be appreciated.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Back then, firmwares erased everything. I think now they keep personal data. Flashing stock should still flash even if USB debugging is off.

Can you still enter Odin mode and recovery.? If so just flash the stock image then factory reset in recovery.
[Galaxy Tab S Android Development] ftd0411:
The problem is I don't know where I am on the unit. Without being able to see anything on the screen, especially the pop up menus, I don't know if I am in recovery or ever powered off so that I can try and enter download mode and flash.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Hold power, vol up and down, and home button all at the same time untill it reboots. Try that
[8125, K-JAM, P4300, MDA Vario Software Upgrading] aperley:
OK guys,

here is the final solution for the issue. By default, Voice Commander 1.6 built-in WM6 ROMs is unable to be activated from Bluetooth headset. The most common workaround here was reinstalling VC over the default one. That costs you couple megs of storage wasted, older/uglier icon in Settings, and slower device overall. No need to do it anymore! Here is a simple registry hack that enables bluetooth activation of VC.

Don't forget to soft-reset after installing.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] BA_Flash_GOD:
!! Yoz !!

Brilliant !!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] vippie:
Great job! I will try it the next time I flash my rom again! :)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cyberdrakula:
Great Find
[8125, K-JAM, P4300, MDA Vario Software Upgrading] jwzg:
Thank you! Works like a charm...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] baarod:
just out of curiosity, did you figure this out yourself or find it. if the former then how and if the latter where?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] doctajay:
I have WM6 on the 8125, with the 2.19 radio, and this isn't working for me. It keeps saying that there was an error with voice command and that I should restart it. I reset my phone a couple times to make sure that it worked, but it isn't. How do you uninstall the cab? Or will reinstalling vc 1.6 take care of it?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] aperley:
Found this out by myself by exploring the VC 1.6 CAB with WinCE CAB Manager and comparing the registry values it adds to the system after installation with the existing ones. I figured out before that simple replacement of all built-in VC's files with the files of retail VC doesnt show any result. So, I found the difference here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]

"BTAGExtModule"="vcbthag.dll"

- that's the key from installation CAB. The default value of the BTAGExtModule key is different. I tried to change it appropriately, soft-reseted - and voila!

The CAB posted here just changes the registry key mentioned above. You can get the same result by editing your registry manually.

So far I did not notice any side effects of this reg hack. If you can not install this CAB, there is probably something to do with allowing installation of the unsigned CABs on your device. Anyway, you can edit your registry by hand.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] robdahood:
You are my new best friend. I was sure this was possible but thought I was going to have to spend a whole day working it out. Downloaded your cab and 2 minutes later my Plantronics 590a headphones work flawlessly.

Thanks again for saving me a lot of time and a few grey hairs!

-rob
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dwny:
Great job........it worked for me with no mishaps........Thanks!! :)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] monkey594:
thx

confirm working on Parrot bluetooth carkit too.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Dr Puttingham:
@aperley - Respect, my friend.

Thanks much!
[Nexus 9 Q&A, Help & Troubleshooting] QA Bot:
Q&A for Root

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Nexus 9 Q&A, Help & Troubleshooting] fastbyte27:
Nexus 9 root

I'm a newbie so can't post in Chainfire's root thread; but thought I'd post an issue with rooting my N9 in case it helps anyone.

When trying to boot inject.img, it returned "FAILED (data transfer failure (Unkown error))". Tried multiple times, rebooted, etc. Confirmed connection by fastboot devices command.

Not sure exactly what caused it to work, but I rebooted my PC, tried it, it failed, so I unplugged USB connector, plugged it back in to a different port on PC, and SUCCESS! (Maybe just bad USB connection??)

Hopefully this helps someone out there.

Cheers,
[Nexus 9 Q&A, Help & Troubleshooting] thebrainkafka:
Is autoroot working in 25L, the New update?
[Nexus 9 Q&A, Help & Troubleshooting] mrshades812:
The new update is Q. Some have gotten auto root to work, others have not. You can do the manual root method and flash the elemental x kernel. That was updated with the latest commits.
[Nexus 9 Q&A, Help & Troubleshooting] Agazoth:
Flash LRX21Q manually. You will need to unzip the package and fastboot flash all img files manually (see this thread: http://xdaforums.com/nexus-9/help/factory-image-flash-t2929019). After that Auto CF will work.
[Nexus 9 Q&A, Help & Troubleshooting] Chelsea Elvira:
I have learnt so many things from your artic,thank you.

---------------------------------------------------------------------------------
[Nexus 9 Q&A, Help & Troubleshooting] MikeRL100:
I don't know how you guys got it working. I'm on the latest factory image. I ran CF auto root just fine, but then I rebooted and went to flash the SuperSu update to 2.25 via TWRP, and apps just freeze when I try to grant them root now. SuperSu itself will open and I can configure it, but it never comes up when I should be getting an access prompt from using an app requesting root. The app and SuperSu just seem to freeze.

I'm on the latest TWRP as well. I had some issues and went into fastboot and rewrote the system image from the factory image and my device booted again, but updating SuperSu via TWRP says it works but I still get freezing on every app I attempt to grant root. So basically I cannot use root at all.

Moved the above here from Chainfire's root thread. I don't have a clue what's causing the freezing.

EDIT: It gets odder. It's as if the prompts are the problem. I changed SuperSu to grant by default and an app worked. But if I set it to prompt, nothing comes up. Logs only appear when I set it to allow by default.
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
I lost root somehow. Probably kernel. I just reflashed stock recovery and R boot image, ran CFAR again, flashed TWRP and then 2.25. All good now. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] MikeRL100:
Maybe I need to do a complete wipe. Or perhaps I could wait - if anybody knows what I should do. I would log it, but how do I get logs without root? Chainfire may be interested.
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
I just wiped recovery, boot and reflashed those stock images. Ran CFAR. Flashed TWRP. Flashed 2.25 in TWRP. All good now. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] di11igaf:
There's a few lines in init.rc that need to be changed to get root working if flashing a factory google boot.img. Kernel itself doesn't just the kernel zimage won't break root, but flashing a boot.IMG will unless you make a small edit to the ramdisk.
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
For those having problems after flashing 2.25 go into SU settings aand uncheck and recheck the Enable SU checkbox. Worked for me. Working as should now. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] MikeRL100:
Yes I mentioned that in a thread earlier. Must have not been the only one with the problem.
[Nexus 9 Q&A, Help & Troubleshooting] thebrainkafka:
Latest beta 2.27
[Nexus 9 Q&A, Help & Troubleshooting] Diesel779:
I'd wait before rooting, seems Chainfire may be able to root without the kernel patches soon: https://plus.google.com/u/0/+Chainfire/posts/K7n4e1q5SMD
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Seems to be working. Reports are good. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Nexus 9 Q&A, Help & Troubleshooting] Diesel779:
Things are moving along quickly :) I'm going to hold off from rooting for a few days maybe longer. Give Flar2 time to do some more work on his kernel too.
[Nexus 9 Q&A, Help & Troubleshooting] fhem:
SU 2.27

I was on R unlocked and rooted w/CFAR using su 2.25 and TWRP 2.8.2.1. Here is what i did - uninstalled/deleted SU, fastboot erased recovery and boot, fastboot flashed stock R boot and recovery. Rebooted all was ok NO ROOT. Then -> fastboot erase recovery -> fastboot flash TWRP -> flashed SU 2.27 w/TWRP -> wipe dalvik/cache -> reboot -> BAAAM ROOT. Thank you Chainfilre!!!!!!
[Nexus 9 Q&A, Help & Troubleshooting] Algruista:
After root dont get updates

After root my tablet nexus 9, I don't get updates. The device detect that there is a update, download it, try to install and then say error!!!

I have did the CF-auto root flasheable. Do you have any solution for that???
[Nexus 9 Q&A, Help & Troubleshooting] fhem:
Read this forum http://xdaforums.com/nexus-9/orig-development/root-t2929118

or try this one http://xdaforums.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Can only OTA update pure stock. Root or any modded files update will fail. There was also a recovery or bootloader mismatch that broke updates that has been fixed. If rooted or modded must manually flash update as per the above post.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Nexus 9 Q&A, Help & Troubleshooting] Algruista:
Allright

Allright, then if I use the nexus root tool Kit for root my Nexus 9, you think that i can get the OTA Updates from the tablet?
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
If you root, change recovery or mod any file in any way you cannot get the OTAs. If want root you are going to have to manually update from each full stock Factory image.( Hopefully they rewrite the script so the full images flash correctly.) Then re-root and reinstall TWRP. Root and TWRP can be done from the toolkit after you have a full stock image on phone. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] Algruista:
Ok thanks you very much. I was asking you becouse with the nexus 5 I did. Another question is, today I receive in my nexus 5 a lolipop update i get the same trouble with that?? If i try to root the nexus 5 with lolipop I won't get the OTA updates?
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
They changed the way they update. They no longer update line by line. They throw blobs at it with a verification check. Just think Verizon looking for missing files and bloatware. They are pretty much doing the same way with Lollipop. My guess is they do the same way for all the Nexus devices. May be able to flash the full stock image auto on N5 instead of each partition separately. Then could do all with Toolkit. Have't heard yet.:cool:
[Nexus 9 Q&A, Help & Troubleshooting] Algruista:
OMG, I needed root on my phone! So I will install the OTA update manually if there isn't any way.

Thanks you prdog1 4 all

Have a good night
[Nexus 9 Q&A, Help & Troubleshooting] Joe_6pak:
Is there a 4-way reboot app that works with a rooted nexus 9?
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
This was only one I found to work altho TWRP Manager is supposed to be fixed also. Haven't tried it yet. :cool:

https://play.google.com/store/apps/details?id=phongit.quickreboot
[Nexus 9 Q&A, Help & Troubleshooting] Joe_6pak:
Worked like a charm - mucho thanks :o !
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
No problemo. :p:cool:
[Nexus 9 Q&A, Help & Troubleshooting] mtbowen:
Issue using CF-Autoroot on Nexus 9 running commands as root

I rooted a Nexus 9 using CF Autoroot and it works great for the most part. However, I have a strange issue where some commands are not executing as root, but do as shell. I first noticed this with an app that I use (VMLite VNC), but it also happens with built in commands like:

screencap -p /data/local/tmp/test.png

Executing the above as root gets this in the log:

E/ServiceManager( 148): SELinux: getpidcon(pid=3427) failed to retrieve pid context.

E/ServiceManager( 148): find_service('SurfaceFlinger') uid=0 - PERMISSION DENIED

I/ServiceManager( 3427): Waiting for service SurfaceFlinger...

W/servicemanager( 148): type=1400 audit(0.0:90): avc: denied { search } for name="3427" dev="proc" ino=25237 scontext=u:r:servicemanager:s0 tcontext=u:r:init:s0 tclass=dir permissive=0

E/ServiceManager( 148): SELinux: getpidcon(pid=3427) failed to retrieve pid context.

E/ServiceManager( 148): find_service('SurfaceFlinger') uid=0 - PERMISSION DENIED

I/ServiceManager( 3427): Waiting for service SurfaceFlinger...

W/servicemanager( 148): type=1400 audit(0.0:91): avc: denied { search } for name="3427" dev="proc" ino=25237 scontext=u:r:servicemanager:s0 tcontext=u:r:init:s0 tclass=dir permissive=0

E/ServiceManager( 148): SELinux: getpidcon(pid=3427) failed to retrieve pid context.

E/ServiceManager( 148): find_service('SurfaceFlinger') uid=0 - PERMISSION DENIED

I/ServiceManager( 3427): Waiting for service SurfaceFlinger...

W/servicemanager( 148): type=1400 audit(0.0:92): avc: denied { search } for name="3427" dev="proc" ino=25237 scontext=u:r:servicemanager:s0 tcontext=u:r:init:s0 tclass=dir permissive=0

E/ServiceManager( 148): SELinux: getpidcon(pid=3427) failed to retrieve pid context.

E/ServiceManager( 148): find_service('SurfaceFlinger') uid=0 - PERMISSION DENIED

I/ServiceManager( 3427): Waiting for service SurfaceFlinger...

Any ideas?

Mike
[Nexus 9 Q&A, Help & Troubleshooting] fhem:
I would start fresh in fastboot and erase all and reflash the latest LRX22C stock images including recovery. Then reflash twrp and then supersu v2.37 with twrp-cfautoroot not required anymore. I would not erase data but if have tibu or other backup may wnat to do that also. Good luck. Hope this works for you.
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Do you have latest busybox. Actually I needed SuperSU pro version to run some commands in root.. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] fhem:
+1
[Nexus 9 Q&A, Help & Troubleshooting] mtbowen:
I tried this, but manage to screw something up. The device updated and booted fine, but I lost root and also could not get into recovery. I even tried reflashing the stock recovery. I finally reset and used Skipsoft's root and it is working now.

Thanks for your help.

Mike
[Nexus 9 Q&A, Help & Troubleshooting] fhem:
You're very welcome. For the next time http://xdaforums.com/showpost.php?p=57261113&postcount=17
[Nexus 9 Q&A, Help & Troubleshooting] mtbowen:
Ok, now I feel really bad. I had found some similar instructions, but they did not contain any of the info in step #2 (meaning, I did not format or erase anything). So basically, I just did 1, 3 and 4 and I think I flashed SuperSu from fastboot instead of TWRP (though that is fuzzy, I was up way too late...).

Thank you so much for all the help.

Mike
[Nexus 9 Q&A, Help & Troubleshooting] babylovebabie:
No, you can't but i'm not sure
[Nexus 9 Q&A, Help & Troubleshooting] Bjorn.e:
I am totally new to this. Rooted devices 5years ago and feel a bit afraid, because i know that you can disable a device for ever...

Got my Nexus 9 today.

Android 5.0.1 (build LRX22C).

The guides i find is "old" and dosnt seam to be up to date. Ex: youtube video: watch?v=hukQmcDeTfk#t=100

Can i follow that video or wont it work because my device is updated with newer software?

Ayuda por favor!
[Nexus 9 Q&A, Help & Troubleshooting] mtbowen:
There are a couple of root choices now I think. Personally, I like Skipsoft's. Menu driven, automated, and frequently updated. I use it on a lot of devices and it just works.

http://www.skipsoft.net/?wpdmpro=unified-android-toolkit-v1-3-3

Hope this helps,

Mike
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Unlock part is same. There is now a TWRP recovery. Install it and then flash the SU root zip. No longer need all those root commands or patched kernel. Need to read some more. Read the root, recovery and update threads. Need fastboot and adb to survive on Nexus. Here are basic fastboot commands to do anything you need to. :cool:

FLASH STOCK IMAGE, FLASH CUSTOM RECOVERY. FLASH ROOT

Drag and Drop or Copy/Paste Images to {}

STEP #1

fastboot flash bootloader {bootloader.img}

fastboot reboot-bootloader

Step #2

fastboot erase recovery

fastboot format system

fastboot erase boot

fastboot format vendor

fastboot format cache

fastboot erase userdata {optional}

Step#3

fastboot flash recovery {recovery.img}

fastboot flash system {system.img}

fastboot flash boot {boot.img}

fastboot flash vendor {vendor.img}

fastboot flash cache {cache.img}

fastboot reboot-bootloader

Step #4

Fastboot flash recovery {TWRP Image}

Step #5

Flash latest SuperSU zip in recovery

Step #6

Install Sterikson's Busybox from Playstore.

---------- Post added at 07:53 PM ---------- Previous post was at 07:45 PM ----------

Only those that know manual should actually use the toolkits. Once understand what the toolkit is doing it all good. Don't learn anything if start with toolkits. If it don't work your lost. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] beats4x:
Does the modified boot.img work on the LTE model? Not trying to brick this thing cause of a different ramdisk or something ?
[Nexus 9 Q&A, Help & Troubleshooting] di11igaf:
I would bet the ramdisk is different, but could be wrong. I would think the LTE radio/firmware is initialized in ramdisk. I wouldn't try it unless you have a factory LTE boot.img to flash, and if you do have one, just unpack and do a diff.
[Nexus 9 Q&A, Help & Troubleshooting] 80centjack:
Sorry if this is the wrong place, I'm struggling to find an answer to my issue. I used the Nexus root toolkit to root my new Nexus 9, but now the update for 5.0.1 won't work. I have tried ADB, the actual OTA and the root toolkit, but they always error out. Can someone direct me to some sort of instructions? I hope I'm not the only one who this is new to.

okay guys, I found the correct thread.
[Nexus 9 Q&A, Help & Troubleshooting] jd1639:
Flash twrp in fastboot. Then flash supersu 2.4 in twrp. Learn how to use fastboot and not a tool kit
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Can only update if pure stock. Once root or any file modded can not OTA update. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] Vnavekul:
Does anyone know a mirror to Chainfire's autoroot download? His site is down and I just got myself a Nexus 9. :P
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Need to go to SkipSoft Unified Android Toolkit for Nexus 9 thread for help. Have no clue what it has to do with SU and root. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] Hum3rus:
Well, I shall try that again. I believe I posted there, but I did also receive a message saying my post was redirected (because I'm new to the site). This is where I found it.
[Nexus 9 Q&A, Help & Troubleshooting] SamLeach:
Nexus 9 cannot update to 5.0.1 after root

Hi

I used the root method originally described in this post when the Nexus 9 was released.

http://xdaforums.com/nexus-9/orig-development/root-t2929118

Rooting meant that the OTA updates no longer work. I have been fine without updating for a few months but now I want to update.

I have tried the factory reset but the 37MB update fails to install at setup after the factory restore.

I have tried to flash to 5.0.1 from Google but cannot get ADB to connect to my Nexus 9.

How can remove root so I can get the OTA or flash?

Thanks
[Nexus 9 Q&A, Help & Troubleshooting] jd1639:
Flash the factory image with fastboot. Google 15 second adb install xda. That should get fastboot and adb set up correctly. See this also http://xdaforums.com/showthread.php?p=58956577
[Nexus 9 Q&A, Help & Troubleshooting] SamLeach:
Thanks for your reply.

I cannot enable USB debugging because I cannot skip the update. (skip is greyed out at the setup screen after I connect to WiFi)

How can I use fastboot to flash the factory image in this state?
[Nexus 9 Q&A, Help & Troubleshooting] jd1639:
You don't need usb debugging enabled. Just boot into the bootloader and use fastboot.
[Nexus 9 Q&A, Help & Troubleshooting] dino_world:
How can i root my nexus 5?

IS there any other 3rd party software needed?
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
Unlock bootloader. Flash custom recovery. TWRP recommended. Flash Chainfire's SU zip in recovery. Install Stericson's Busybox from the playstore and run it. Profit. :cool:
[Nexus 9 Q&A, Help & Troubleshooting] cam30era:
Nexus 5? Typo, or wrong forum....
[Nexus 9 Q&A, Help & Troubleshooting] prdog1:
I figured didn't matter as long as a Nexus. LOL :cool:
[Nexus 7 Q&A, Help & Troubleshooting] Dantefire:
Anyone knows if xposed framework will be avaliable for lollipop?
[Nexus 7 Q&A, Help & Troubleshooting] Mikey:
learn how to search for forums...........search read and then debate whether to post or not.

Dont depend on being spoonfed....

http://xdaforums.com/xposed
[Verizon HTC One (M7)] bdizzle1686:
So , I'm S-off, unlocked bootloader,rooted, 4.4.3 Sense 6 stock Rom, and on SuperSu 2.01 ,however I've noticed in Play store, SuperSU has been updated to 2.16, however I've seen VERY mixed reviews for it, and can barely find ANY reviews for the m7 on 2.16... Matter of fact, the ONLY M7 reviews I've seen for 2.16 are all on CM Roms... Just wondering if anybody running sense has updated to 2.16, and if it caused any problems after installing. Also, what method of updating it did u use? Did u update the app and then update through letting the app install/update the binary, or did u flash the 2.16 zip yourself?
[Verizon HTC One (M7)] michaelbsheldon:
Running BoneStock here.

It updated thru Play Store to v. 2.16, and just after updating, it updated binaries

with Normal choice without issues.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] ryz4eva:
I have recently been sent the update to android 4.4.2 on my note pro however my WiFi will not connect now.

I've tried restarting the device and it keeps saying "network connection unavailable".

has anybody else had a similar experience with this device?
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Spere:
Use search, here are couple topics about broken wifi after update. Factory reset should fix it.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Polar67:
Hi!

Have you got Passpoint running?

This might be a totally different issue but if a factory reset or reflashing doesn´t help you might try looking here.

Regards

Elo
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] huebinger:
I have the same effect!

A full reset won't fix this problem. I contacted Samsung support and the said that I should send them the tablet.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] ShadowLea:
A reset usually isn't sufficient, you need to reflash the firmware.