yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] classic757:
I previously used the above method you posted to permanent root an LG Transpyre on 5.1.1 that did not have the bootloader unlocked. Glad to see someone else knows about it. :good:

Maybe it will work on a locked bootloader Turbo for those who don't want to unlock their phones but just want root.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Thành67890:
Can not unlock booloader root? I do not have a visa. $ 25 is a huge amount to me
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] HT123:
I don't think that is the case.

What I said was you don't need to install a custom recovery.

Give it a shot report back though. Worst that can happen is it does not work.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] classic757:
Agreed. I was just pointing out that I was able to use kingroot and wolfdroid's method to permanent root a phone (albeit an lg phone) that had a locked bootloader. Other people also had success doing that as well on other brands of phones. Will it work on a Turbo with a locked bootloader? IDK. However I would not be surprised if it does. I had a Turbo with a locked bootloader but sold mine else I would try it myself.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] HT123:
I agree, i apologize if it it came off otherwise. I think the question is if the sunshine process removes the protection and allow writing to the system partition. I unlocked prior to making my root permanent so i cant test again but am very interested to see if it works with a locked boot loader
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] classic757:
My thinking it that it probably will work because temp root can be obtained on a locked bootloader Turbo with kingroot. It's just that kingroot is unstable and often times does not survive reboot. However, wolfdroid's method is similar to using SuperSu Me(or SuperSume). It removes kingroot and replaces it with SuperSu, which of course is more stable and survives reboot.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] HT123:
If security is disabled and the system can write to the system partition it will work, if not, then I assume Sunshine disables it in the process of unlocking the boot-loader. Hopefully someone with a stock Turbo who was going to unlock anyway can verify.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
Not sure why you wouldn't want a custom recovery. With custom recovery you can make backups of your entire phone image in case you screw something up. Many times in the past I've flashed something that didn't work as I expected. And with ROOT, if you flash something you can screw up something system-related. Very easy to boot back into TWRP recovery and restore the previous day's backup I had made. Like a time machine to erase your mistake. ;)

And it's FREE. Doesn't cost anything.

Yes, with Titanium Backup (a powerful app) you can restore previous versions of an another app. (I choose to save 3 days worth of apps in Titanium Backup.) But with a TWRP custom recovery backup (also called a "nandroid"), you can save and restore the ENTIRE phone, including all system apps, all settings, everything. Very powerful, useful tool.

I wouldn't have a rooted phone without custom recovery. That's one of the main reasons I always buy phones where I can unlock the bootloader -- to install custom recovery (like TWRP or CW) and root.

If you screw something up and come asking for help, the first thing someone is going to ask is, "Did you make a backup?" And they are talking about a custom recovery backup.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] HT123:
As far as why... some people like chocolate... some people like vanilla. The question is not the merits of a custom recovery, it is if one is required to have persistent root on the phone.

I personally don't care about a custom recovery. I prefer the stock rom at this point because without fail most custom roms have some minor bug that inevitably annoys the sh*t out of me. I want root because i want an ad blocker. I want an ad blocker because I use my phone as a proxy for web traffic on a computer with network monitoring software and i would prefer my internet traffic not be visible to my employer. There is zero reason for a custom recovery to do what i want to do.
[Google Chromecast] petardun:
Hey guys, i'm looking for best android apps to stream videos to chromecast. The problem is that most of them only support mp4 files. I found only one that supports all file formats, it transcodes the file on the fly on your phone and streams directly to chromecast. its called Megacast. Does anyone know anything similar?
[Google Chromecast] mjs2011:
I usually just stream from es file explorer
[Google Chromecast] zul8er:
BubbleUPNP and Localcast
[Google Chromecast] izati:
Yeah bubbleupnp is q pretty solid app, especially with transcoding for Chromecast.
[Google Chromecast] nurps:
Whats the difference compared to screen mirroring? At least compared with ES Chromecast Player the screen mirroring runs much smoother.
[Google Chromecast] NinjaOne:
Solid Explorer is IMO by far the best I have used. Plays anything from anywhere. 1080p is laggy, but everything else I throw at it works fine. Streaming from phone, NAS and ftp...
[Google Chromecast] DJames1:
I think people are missing the point of the question about transcoding. While there are many good Chromecast-enabled video players on Android (e.g., Avia, AllCast, BubbleUPnP, LocalCast, Plex, AllConnect being just the few that I have on my tablet), mostly they don't support on-the-fly transcoding because phone processors simply aren't up to handling the task smoothly yet, and it would drain battery power at an alarming rate if they could. Some like Plex and BubbleUPnP support transcoding using a remote server. But really it's easier just to transcode all your videos to a common mp4 format that's compatible with everything instead of worrying about on-the-fly transcoding.
[Google Chromecast] bubbleguuum:
Sometimes, just the audio track of videos must be transcoded (DTS, AC3) and Android devices are powerful enough for this task (which BubbleUPnP can perform locally).
[Google Chromecast] mrbabyman:
There are lots of chromecast apps available over the web which you can install on your device. But I find an amazing list of best chromecast apps android. Why don't you check it out.
[Google Chromecast] darkelement1987:
I like this one:

https://play.google.com/store/apps/details?id=com.videostream.Mobile&hl=nl
[Google Chromecast] viappscompany:
ViCast HD Google Cast (Chromecast) player

Guys, please try our new app;)

ViCast is a simple and stable HD Google Cast (Chromecast) player. Can be found on Google Play Market.

Enjoy casting your favourite media to the big screen!

We are working hard to provide you with a great opportunity to seamlessly watch your favourite HD movies. It’s highly optimized for streaming H.264 encoded videos and allows to play incompatible Google Cast media. Moreover, your media content will also be accessible via DLNA server.

SUPPORTED FORMATS:

Video: MP4, MKV, AVI, WEBM, MOV, WMV, MPG, 3GP, M4V.

Audio: MP3, AAC, FLAC, WAV.

Photo: JPG, PNG, BMP, WEBP, GIF.
[Galaxy S 5 Q&A, Help & Troubleshooting] Nikola Bojkovic:
Hello,

I've got a problem with rooting Galaxy s5 running on Lollipop 5.0. I tried CF-auto root, kingroot(pc an android version) ,kingoroot(pc and android version) ,iroot, towelroot, framaroot, other odin options. I also tried to install custom recovery but when I install it and try to enter it with volume up, home and power button on screen it says:

recovery booting

(Something here)

Set Warranty Bit: recovery

And then screen just go black and I need to remove battery to turn it off.

Please help!

Thanks!
[Galaxy Note5 Q&A, Help & Troubleshooting] abodi40400:
Hi guys , i guess its one of the common issues that note 5 users are facing , but i believe my situation is the worst !!

yesterday i have fully charged my note 5 then i slept, and when i woke up today i have touched my phone and it was very hot !! kinda 80c, checked the battery and god ! it was 13% !!!

that's very very weird i mean !! in 7 hours my phone spent 87% of the battery life !!! can anyone please help me ? :crying:
[Galaxy Note5 Q&A, Help & Troubleshooting] fatouraee:
I had similar issue with my phone recently. I installed the latest OS available and now i lose 30% or so battery just letting the phone sit over night. with no notifications or background apps.
[Galaxy Note5 Q&A, Help & Troubleshooting] cxhugh:
Based on which software? The new OK6?
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
If you tripped knox you cant use the stock kernel even if you have stock firmware. It will not go to deep sleep. You must use the different kernel.
[Galaxy Note5 Q&A, Help & Troubleshooting] me_ashman:
That's new. I've not heard that one before.
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
Read stock kernel thread on original development category. I tried with two note 5 and yes i can confirm that issue.
[Galaxy Note5 Q&A, Help & Troubleshooting] MohamedRaafat:
So once I root I can't go back using stock kernels ?
[Galaxy Note5 Q&A, Help & Troubleshooting] Octa_core:
Could you link to the specific thread and post? I can't seem to find it.
[Galaxy Note5 Q&A, Help & Troubleshooting] apd:
Correct. But you can use one of the modded kernels. There are several in the Android Development thread.

The rooting thread makes it clear that you have to flash a modded kernel after rooting

Read the OP in this thread

http://xdaforums.com/showthread.php?t=3205073
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
http://xdaforums.com/showthread.php?p=63225712
[Galaxy Note5 Q&A, Help & Troubleshooting] MohamedRaafat:
But I can use stock kernel if I reflash stock os right ?
[Galaxy Note5 Q&A, Help & Troubleshooting] apd:
Yes. If you flash stock (and therefore are not rooted) you can use stock kernel. The Knox flag will still be tripped though
[Galaxy Note5 Q&A, Help & Troubleshooting] Octa_core:
But the phone still won't deep sleep. I have tried that.
[Galaxy Note5 Q&A, Help & Troubleshooting] apd:
Two main options I would suggest: flash Dr Ketan's L8 ROM if there is a version for your model. It has none of these issues.

Or have a look at the last few pages of http://xdaforums.com/note5/general/how-to-root-note-5-t3205073 - there is an issue with super su 2.6+ and no deep sleep. [MENTION=2316670]drke[/MENTION]tan is trying a fix which is in that thread.
[Galaxy Note5 Q&A, Help & Troubleshooting] MohamedRaafat:
Why it won't deep sleep on stock without root ? Do all note 5 mobiles have this issue ?
[Galaxy Note5 Q&A, Help & Troubleshooting] apd:
No - it has been reported occasionally. If I remember rightly one of the causes is a defective image file for Briefing but I may be misremembering.
[Galaxy Note5 Q&A, Help & Troubleshooting] MohamedRaafat:
Can you elaborate more ?
[Galaxy Note5 Q&A, Help & Troubleshooting] InteliDroid:
I'm also having this issue. I've flashed stock and wiped data/factory reset but I'm still having this issue. Is there any way I can fix this whilst staying on stock? Also, yes I've already tripped knox.
[Galaxy Note5 Q&A, Help & Troubleshooting] Ozgurce:
it is not occasional. Its in the every kernel code on the note firmwares. I linked a post on previous page. If you read it you can get it what I mean. Its samsung side issue and I dont belive its fixed ever. Kernel looks the knox flag and If its tripped makes some memory parts unwritable and when is the boot done try to flush the cache and in the boot process this places maked not writable. Kernel try it over and over again and that is the cause of no deep sleep issue. So it will happen all the note5 variants. Even if you go full stock there will be deep sleep issue once knox tripped. There is no way for the bring back knox to untrip too. I blame samsung on this one.
[Galaxy Note5 Q&A, Help & Troubleshooting] got2trythis:
Samsung might argue it is not their issue and thus they are not fixing it. The Stock Kernel is meant to work with unmodified phones only with Knox=0. Once the Knox is tripped, it is not going to work anymore because they are marking some directories as read only for security reasons if knox is tripped - I would say do not wait for a fix from Samsung so either use a custom Kernel or use a fixed stock kernel on this site from [MENTION=336863]garyd9[/MENTION] if you want to keep some of the hardware functionality.
[XDA Assist] mercenariio1092:
Me gustaría rotear mi z3 pero necesito el firmeware 23.0.A.2.93 y no lo encuentro por ningún sitio, almeno no uno descargable ya que los que he probado a descargar al 80% o así de descarga me da error. Gracias de antemano.:fingers-crossed:
[XDA Assist] Primokorn:
Hi,

Thanks for using XDA Assist.

Please write in english as mentioned in the forum rules.

Thank you.
[Raspberry Pi General] normie2:
As the title may suggest I want to create an ad-hoc network with my rpi. So far I've been successful in creating one with commands in terminal and I managed to connect a laptop using kali with ssh to my rpi using local ips like 10.0.0.2. But my original goal is to control my rpi with something more versatile like a tablet or an android device in general not just computers. So I have two questions:

-is it a hardware problem from the network adapters in the android devices that makes them unable to connect to the ad-hoc?

-is it a software problem instead so I should root my device or change the drivers in the android kernel?

-am I doing sth wrong with the ad-hoc configuration in the rpi?

Or is it sth I cannot think of that makes me fail? :p
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
https://plus.google.com/111438979475450426209/posts/RHoDEshdVpC
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
When I use the camera, the screen turns black. No matter what app I use, every camera app has this problem
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Same here, I think it's in another thread..............I'm still trying to find a fix, hopefully soon.
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
did you see the video?
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Where?
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
Are you running a custom kernel? I know 6.0 kernels keep the camera black at all times, so I wonder if it's just a different kernel bug.
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Still running the stock kernel. So you're saying if I flash another kernel, say Elemental, I will get my camera back?
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
I'm running the stock kernel.
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
The link in the first post
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
In the video, looks like the camera is working.................mine is black all of the time.
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
If you watch the whole video it seems like it turns black after a few taps to focus it.
[Nexus 6P Q&A, Help & Troubleshooting] raafaafaa:
Yes, it turns black after use it a while
[Nexus 6P Q&A, Help & Troubleshooting] dadykhoff:
Same problem with me. Issue started after I flashed 6.0.1 last night. I also noticed that there is a small red light on the visor on the back that usually isn't there (that I've noticed). Could be the laser auto focus I'm thinking. Reboot didn't fix anything for me either.

Is everyone having this issue on 6.0.1? I'm wondering if it's a new bug.

Oh, I'm also using Chainfire's systemless root.

---------- Post added at 10:12 AM ---------- Previous post was at 09:15 AM ----------

I flashed Elemental X 1.00 for the 6P and it's fixed. http://xdaforums.com/nexus-6p/orig-development/kernel-elementalx-n6p-t3240571

I'd prefer to be on stock kernel but I'm not at home and don't have to A -> C USB cable to mess around with reflashing images through ADB. Hopefully this helps somebody.
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
After flashing that kernel, the camera would appear, but force close.

Update: I reflashed SU 2.52, camera is finally working!

Well, after taking a picture and then reopening the app, camera went black. Rebooted, worked fine for a moment and now black again.
[Nexus 6P Q&A, Help & Troubleshooting] tkso:
THIS x 1000

I never had this issue when I was on 6.0 MDB08L with SuperSU 2.52, ElementalX-N6P-0.11 and Xposed Framework sdk 78 arm 64.

I tried flashing 6.0.1 and that's when the issue first started. Since I couldn't get Xposed on 6.0.1 I reverted to 6.0 (MMB29N). The camera stopped working after I flashed something (must have been Xposed or ElementalX kernel). Reflashed MMB29N fresh again but the camera still didn't work. Really frustrating.
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
When you did MMB29N, did the camera work fine?
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
As it's been said many times, flashing custom kernels that haven't been updated for 6.0.1 would cause the camera to only display black and/or freeze.
[Nexus 6P Q&A, Help & Troubleshooting] tkso:
You're right. My bad. I should have checked first to see if the kernel I was using when I was on 6.0 had been updated yet for 6.0.1. When I tried reverting back to 6.0 and flashed an older stock rom, ElementalX kernel showed up as the kernel instead of the stock kernel.

I copied and pasted the following commands through adb:

fastboot flash bootloader bootloader-xyxyxyxy.img

fastboot reboot-bootloader

fastboot flash radio radio-xyxyxyxy.img

fastboot reboot-bootloader

fastboot flash boot boot.img

fastboot erase cache

fastboot flash cache cache.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot format userdata

fastboot reboot

My mistake was, I should have individually copied and pasted each command rather highlight the whole thing as one command and copy paste it into the cmd prompt. The camera app is behaving normally right now on stock kernel on 6.0 after reflash stock.
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Where is the stock kernel?
[Nexus 6P Q&A, Help & Troubleshooting] tkso:
I reflashed the factory image for 6.0 mmb29n so it came with stock kernel. (I need to stop saying stock rom when I really mean FACTORY IMAGE I flash LOL)
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Okay, in the process of downloading angler-mmb29n-factory-b1463752.tgz. After I unzip to c:\angler, run those adb commands?
[Nexus 6P Q&A, Help & Troubleshooting] infamous84:
having this issue as well, flashed newest chroma, on systemless root with the franco kernel everything has been updated for 6.01

everything else is working fine

edit - reflashing the bootloader and vendor img from the newest google image resolved my issue
[Nexus 6P Q&A, Help & Troubleshooting] ycats:
Now I'm in a boot loop of the android circles.................have gotten back into bootloader and flashed other SU's no success.
[Nexus 6P Q&A, Help & Troubleshooting] dadykhoff:
You can flash the boot.img from the official 6.0.1 images to get the stock kernel.

Elemental X has been updated for 6.0.1? See the official thread: http://xdaforums.com/nexus-6p/orig-development/kernel-elementalx-n6p-t3240571
[Nexus 6P Q&A, Help & Troubleshooting] nowy57:
probably you need to instal latest VENDOR.img

https://www.androidfilehost.com/?fid=24269982087014010

so after install ROM, GAPPS then install latest VENDOR and camera will work fine
[Nexus 6P Q&A, Help & Troubleshooting] dratsablive:
I am having the same issue with the Camera after flashing the latest stock image, 6.0.1. Not rooted yet but have custom recovery. I flashed all files including the vendor.img. Camera app opens, but remains black. I had flashed the modified boot.img to allow for the systemless root and thought that might have been the problem so I reflashed the stock boot.img and now the camera works.

Update:

The updated boot.img for systemless root appears to be the culprit. Flashing the old boot.img fixes this issue for me.
[Nexus 6P Q&A, Help & Troubleshooting] infamous84:
you dont need the modified boot img for systemless root, only for the old root method
[Nexus 6P Q&A, Help & Troubleshooting] dratsablive:
The instructions in the thread say to flash the attached boot.img (File Type: zip	angler-mdb08k-boot-systemless.zip)
[Nexus 6P Q&A, Help & Troubleshooting] infamous84:
The guide for systemless root doesnt say anything about a modified boot img.

6. How To Root – Systemless

Prerequisites: unlocked bootloader (section 1), TWRP recovery.

It looks like this is the way SuperSU is heading in the future. There's no need to flash any modified boot.img like with the traditional root method because this version of SuperSU patches the boot.img for you. No mess, no fuss, super easy. Some apps don't work with this root method yet, but that should change. This is my recommended method for root.

Download the SuperSU for systemless root method (2.60+) to your phone.

Boot into TWRP recovery and enter the install menu.

Navigate to where you have SuperSU stored on your internal storage and select it.

Swipe to install.

Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.

Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
[Nexus 6P Q&A, Help & Troubleshooting] dratsablive:
Instructions

You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with eachother. The installer for this experiment will not clean up old root files.

- Flash stock /system

- Flash the attached boot image

- Flash the attached SuperSU ZIP in TWRP
[Nexus 6P Q&A, Help & Troubleshooting] deucebigalow4:
This was the fix for me as well.

I was getting hung up on using Chainfire's original systemless root method where he attaches a modified boot image in addition to SuperSU 2.56 and instructs you to flash it. This is the version of systemless root that is featured in Gadget Hacks YouTube systemless root tutorial. It works, but will rely on updated boot patches for each Android point release or else weird bugs (like the camera not working) can happen.

Chainfire's systemless root V2 eliminated having to flash a patched boot.img because the newest SuperSU (2.60 and above) will take the boot.img downloaded directly from Google and automatically patch it when you flash SuperSU in TWRP.

Steps are (h/t to rsmolen):

1) Download latest factory image from Google on computer with ADB + SDK installed and latest SuperSU onto your phone

2) Extract all .img files (except userdata.img) to your SDK fastboot folder on PC and reboot phone into bootloader menu.

3) Flash the factory bootloader img (NOT boot.img, flash the one with the long name), then reboot bootloader

4) Flash the factory radio img, then reboot bootloader

5) Flash boot.img

6) Erase cache

7) Flash cache.img

8) Flash recovery.img

9) Flash system.img

10) Flash vendor.img

11) Flash TWRP

12) Boot into TWRP and install SuperSU, erase davlik/cache, and reboot. If it asks to install SuperSU, do not install.

When you flash SuperSU in TWRP, the log will tell you that it has patched the boot. Android will optimize your apps on boot and you are good to go.

OTAs will not work because you have to be on stock recovery, so you have to flash updates manually.

The benefit this way is keeping user data and the system partitions intact so you can run the latest stock with benefits of root and not alter the system partition like a traditional root (as long as you don't install XPosed, that is...)
[Nexus 6P Q&A, Help & Troubleshooting] dadykhoff:
Just to clarify, you should only need to flash stock system if you are coming from a non-systemless root method (or upgrading Android versions obviously). Chainfire mentions this in the systemless thread. You should be fine to update SuperSU directly on top of one another as long as the original version is 2.60 or higher.