yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Q&A, Help & Troubleshooting] dr.ketan:
1.You can root without touching bootloader.

2.Yes

3.Yes

4.Yes. but you have to flash stock ROM manually with odin (Never heard you can't flash ROM with odin bcoz of rooted status)

5.There may be some app got broken like S health,screen mirror and some banking app etc . but almost have FIX for it.

6.Your linked content is from XDA source only, search in theme and app section

7. My preferred method is flash CWM/TWRP and flash SuperSU zip (CF auto differ only by keeping recovery stock, which actually have no meaning but lot limitation is there)

No method there to root without tripping knox

PS : This topic goes to Q&A NOT in development
[Galaxy Note 4 Q&A, Help & Troubleshooting] genius.lizard2:
1.i don't think any note4's BL is Locked...or if there is any there will be unlockers soon.

2.yes, with odin.

3.yes.

4.you can update it with Odin.where do you Read it??! (if there was any problem you can use Custom Roms..Or Deodexed Lollipop Roms and Flash Them via Recovery)

5.i know if you root New Samsung Devices With CF-Root Method and others like it KNOX Will Trip...its mean All Security things that Use Knox will not work anymore Like Billing Services...go to settings/about phone and see them.

6......i don't know too

7.see 5.

i didn't root my N910C too and waiting for new procedure

---------------
[Galaxy Note 4 Q&A, Help & Troubleshooting] lee.n:
Thanks, dr.ketan and genius.lizard2.

I;ve been looking for CF-Auto-Root file for Note 4 SM-N910C, and I only found this.

SM-N910C (Thailand, Exynos): CF-Auto-Root-trelte-treltexx-smn910c.zip

I am from Philippines , do you think above file will be compatible? What will be the effect? and I am not sure where my SM-N910C came from as I also saw bunch of SM-N910C from different country.

Thanks.
[Galaxy Note 4 Q&A, Help & Troubleshooting] jvtrigo:
Hi guys do you know if we can expect a knox 0x0 root method, like towelroot for our notes?
[Galaxy Note 4 Q&A, Help & Troubleshooting] lee.n:
Not at this point, definitely rooting will trip Knox 0x1, at least for now.
[Galaxy Note 4 Q&A, Help & Troubleshooting] genius.lizard2:
yes CF-Auto-Root-trelte-treltexx-smn910c.zip is for N910C Find it From Here:

http://xdaforums.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428

now that i'm thinking....i can't wait anymore for Another method..i'm going for CF Root too.
[Galaxy Note 4 Q&A, Help & Troubleshooting] lee.n:
Please update us when you already rooted it and how it goes. My note 4 will arrive next week.

The cf-auto-root I found is Thailand version of SM-N910C, I'm afraid that it might not compatible with other version SM-N910C, or we encounter issues (different langauage?)

Anybody who tried this on any SM-N910S?

Thanks
[Galaxy Note 4 Q&A, Help & Troubleshooting] geniusrehan:
Dr. is there any way to flash stock recovery without flashing stock rom from odin? I mean u have to flash stock rom only then we can get stock recovery?
[Galaxy Note 4 Q&A, Help & Troubleshooting] genius.lizard2:
i did it.it worked perfectly...

My Friend, All N910C Versions Are The Same. there is no differences!
[Galaxy Note 4 Q&A, Help & Troubleshooting] dr.ketan:
You needs to have stock recovery in tar version.
[Galaxy Note 4 Q&A, Help & Troubleshooting] genius.lizard2:
download official .tar.md5 ROM file from sammobile or if you have one use it.open it with Winrar.there is recovery.img , extract it.

make a tar file with this img file...you can do it with linux or a batch file in windows like: http://xdaforums.com/showthread.php?t=2446269
[Galaxy Note 4 Q&A, Help & Troubleshooting] lee.n:
HI guys,

After rooting, would you recommend installing TWRP or just use stoxk recovery? And what is the advantage of TWRP over stock recovery?
[Galaxy Note 4 Q&A, Help & Troubleshooting] D F:
With TWRP or other recovery, you can flash custom ROMs and MODs. That is the only purpose of it.
[Verizon HTC One (M8)] ddodge68:
I'm searched for an hour tonight, and am probably looking right over it. My phone is currently on 4.4.3 and is very slow to restart. Can someone help me to find a video tutorial on how to flash 4.4.4?

Thanks!!
[Verizon HTC One (M8)] ddodge68:
I did download the 4.4.4 firmware zip file from here. I am very rusty with using the command terminal on my pc though. This is where I'm hoping for a video tutorial.

xdaforums.com/showthread.php?t=2723159&page=4
[Verizon HTC One (M8)] The Stig 04:
Are you S-OFF and rooted? Custom ROM and recovery? Stock rooted?

The more info you give about your phones current state the better we can help point you in the right direction.
[Verizon HTC One (M8)] ddodge68:
I'm sorry....yes, I am S-off, and rooted. I currently have a custom ROM on my phone, but my android version is currently 4.4.3
[Verizon HTC One (M8)] The Stig 04:
Cool, just wanted to make sure. There is a video on there from DMX that shows how to flash the firmware. I linked that below. He does it on mac but the commands are the same if you do it on a windows computer. If you open the command window in your fastboot folder (shift+right click, open command window here) you can skip the long command he types at around the 3:40 mark and jump right into the commands at 3:51.

https://www.youtube.com/watch?v=e21qb7iZAOo&feature=youtube&app=desktop

Sorry it took so long to respond, but work calls! :) If you have any trouble let us know!
[Verizon HTC One (M8)] ddodge68:
As long as you're being so helpful, again, I've downloaded the zip file from the above link. Do I need any of the other files?
[Verizon HTC One (M8)] berndblb:
You downloaded the 4.4.4 firmware zip (no boot.img, no recovery.img) from Tigerstown thread? Then no, you don't need anything else to update your firmware.

This will only update your firmware. You will be on the same rom with the same recovery and remember to flash it twice as he described it in the instructions.

UNLESS you use the HTC fastboot.exe from here:

http://xdaforums.com/showpost.php?p=56890497&postcount=3

This fastboot version will do everything needed in one flash.

I installed this fastboot version alongside my "normal" fastboot/adb which I use for my other devices and use it for the M8 exclusively.
[One (M7) Q&A, Help & Troubleshooting] xhamadeex:
Hello

I noticed that the speakers volume of the m7 are very low compared to my friend's sony Z3 speakers volume...

I have done some research about this issue, and found that HTC has purposely lowered the volume in the 4.3.3 update..

I know this is an old problem, but I did not notice it until I compared the speakers with the other phone...

Is there a way to return the speakers as they were before?

Thanks!
[Galaxy Tab S Q&A, Help & Troubleshooting] chris9000:
I've been eyeing the Galaxy 10.5 for a while and have been vacillating between it and the Nvidia Shield. Nvidia seems to already have released an update for the Shield as owners of the wifi version got Lollipop for it recently. Meanwhile, it's been said that the 10.5 won't get Lollipop until early next year.

So I'm curious. Has Samsung been known to be proactive about getting updates to their tablets in a timely manner and for at least 2 years from each line's release date?

Thanks in advance!
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
Well Samsung takes a while to get updates out. Ussally 3-4 months after a release after an new os.
[Galaxy Tab S Q&A, Help & Troubleshooting] barth2:
Fwiw we're still on 4.4.2. We'll probably never see 4.4.4' hopefully there'll be lollipop.
[Galaxy Tab S Q&A, Help & Troubleshooting] redenfredaesh:
Slow

I have the 8.4 inch Samsung galaxy tab S running 4.4.2 and the Galaxy Note 4 running 4.4.4. I don't expect I will receive lollipop for either device in 2014(from what I have researched online) however there appears to be a lot of online developers that assist in bringing forward greater roms and mods for us to use on our devices. You can always use this website to keep in contact with the latest firmware (official) :

live.samsung-updates.com/index.php?device=SM-T700

You can view on that website ALL official Samsung firmware. For some devices you can even install a firmware for a different region to where your device is located (but make sure to do your homework / research beforehand)
[Nexus Player Original Android Development] jscat1:
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.
[Nexus Player Original Android Development] defconoi:
good work

This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms
[Nexus Player Original Android Development] npjohnson:
OP download links updated. My apologies.
[Nexus Player Original Android Development] npjohnson:
Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.

Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.

CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.

CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP
[Nexus Player Original Android Development] jscat1:
I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?
[Nexus Player Original Android Development] zarthan:
The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.
[Nexus Player Original Android Development] jscat1:
Is there not a subforum for the adt1?
[Nexus Player Original Android Development] bunchies:
hmmmm CWM
[Nexus Player Original Android Development] npjohnson:
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD
[Nexus Player Original Android Development] gullatec:
thanks so much for this. the ADT-1 needs more love on xda
[Nexus Player Original Android Development] defconoi:
twrp

if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
[Nexus Player Original Android Development] npjohnson:
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.

I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?
[Nexus Player Original Android Development] mknrls:
might work on getting twrp for for the adt-1 with mouse and keyboard support.

just received mine tuesday.

has anyone created repos for this device yet?
[Nexus Player Original Android Development] npjohnson:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
[Nexus Player Original Android Development] mknrls:
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose

https://github.com/adt1-dev

PS: im new to this and learning on the way.

Edit: are your sources on github?
[Nexus Player Original Android Development] Luxferro:
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.
[Nexus Player Original Android Development] lafester:
Any plans on making recovery for nexus player? Just curious
[Nexus Player Original Android Development] illuminerdi:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?

Thanks
[Nexus Player Original Android Development] efrant:
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.
[Nexus Player Original Android Development] Dees_Troy:
TWRP has had mouse support since 2.7.0.0 and keyboard support for even longer.

Supporting OTA updates has little to do with the custom recovery and more to do with the fact that any modification that you make to your device can break the OTA process. It's gotten worse in 5.0 where even the act of mounting the system partition as read/write can "break" the OTA process.
[Nexus Player Original Android Development] npjohnson:
That's what the edit was for [emoji14]

When I wrote that post, I knew a considerable bit less about building android/recoveries than I do now. Haha.
[Nexus Player Original Android Development] halfluck:
Hey Guys,

Does anyone have Stock boot.img for ADT-1 LRX22G 5.0.2?

Cheers Rob.
[Nexus Player Original Android Development] npjohnson:
PM Me this weekend and I can get one.
[Nexus Player Original Android Development] EvgeniX:
Hi,

Can some one re-upload Stock Recovery Image LPX13D pls?
[Nexus Player Original Android Development] toebee76:
Hoping someone can help me out. I fear I may have turned my adt-1 into a brick. I was in the process of rooting. I did the Fastboot boot process and my unit has been stuck on the android logo ever since. I went back and downloaded the image again and it is a different file size than the first one I flashed. I think I flashed a bad image. Now it will not recognize it as an adb device. Am I screwed?

Also tried holding down the button on the back but it just sits on the android logo.
[Nexus Player Original Android Development] mskip:
You haven't hard bricked it. You need to reboot directly to fastboot mode and flash the stock image back to your device. Even flashing just the system image should fix it so you could extract the system image from the stock file and then fastboot flash system system.img whilst in the fastboot screen.

Mark.
[Nexus Player Original Android Development] toebee76:
Hi Mark thanks for taking the time to reply. I appreciate it. I don't know how to get back to fastboot mode. It will no longer show up as an adb device. Is there another way to get into fastboot mode?
[Nexus Player Original Android Development] npjohnson:
Unplug and replug whilst holding the button on the back.
[Nexus Player Original Android Development] toebee76:
Thank you so much for this. Much appreciated. I am able to get to the bootloader which makes me feel somewhat better. However I still can't connect via adb. My pc shows it is connected to fastboot but adb detects no devices. If I use the button on the back of the device I can scroll down to fastboot protocol and select it. Then it says its "erasing" before just going to a black screen. After that it just stays like that. The lights still on but no video output to the TV. I tried re-installing drivers but it didn't help. I don't know how I can flash anything from here without adb. Any suggestions? Thanks again.

**More info**

If I adb "fastboot devices" it shows it's connected.

If I try to "fastboot flash boot boot.img" I get a "Failed <command write failed<no such device or address>>
[Nexus Player Original Android Development] mskip:
When the device is in fastboot mode you do not use adb for any commands you use fastboot. Adb is for when your device is booted in to Android.

Download the stock image, open it with winrar, winzip, 7zip, then open the zip file inside and extract the system.img file to your pc (same folder that has adb and fastboot files).

Reboot the device manually to fastboot.

Open a command prompt from the folder that has adb/fastboot files (browse to the folder in windows explorer, hold shift and right click and select "open command prompt here".

Type fastboot devices and if you see a serial number then the device is connected.

Type fastboot flash system system.img to flash the system image to the device.

Wait for it to finish.

Type fastboot reboot to reboot the device and it should boot.

Mark.
[Nexus Player Original Android Development] toebee76:
Thank you for the instructions Mark. I was reading about the difference of fastboot and adb this morning. I have a much better understanding now. I am having trouble finding a few files. First where is the stock image? I thought maybe you meant the files in the op or maybe the file here http://xdaforums.com/hardware-hacking/chromecast/adt1-stock-molly-images-unbricking-t2927888 however none of them have the contents you mentioned. Been googling but haven't found anything with the contents you mentioned. Also while trying to find my own solution last night I flashed the custom recovery in the OP, but could not flash SuperSu because adb still isn't working. Should I revert back to a stock recovery before flashing the system.img? If so where is the stock recovery? The link is no longer working in the op.

(I know it's not much but hopefully the donation will buy you a coffee or a beer)
[Nexus Player Original Android Development] npjohnson:
Get to this site and download this: http://coggy.euroskank.com/LatestADTSystem.zip

Then Download the CWM Recovery in OP, and boot it from fastboot by issuing "fastboot boot whateveryourrecoveryiscalled.img" OP

Then, use the HW button on the device (quick press move, long press select) to select install zip, then choose from adb, then adb sideload the first zip.

You'll be on Stock 5.0.2, and if you want root, just side load the SuperSU zip after using flashing the other zip (preferably before rebooting).
[Nexus Player Original Android Development] toebee76:
Thanks for the link npjohnson. Unfortunately I have't gotten adb to work since I flashed the bad image. It is showing molly in my device manager under other devices like it has no drivers. I have tried installing the drivers again but no change. Is it possible that my adb isn't working because I flashed a bad image?

Is this the stock image you mentioned? http://coggy.euroskank.com/LatestADTSystem.zip I tried to flash the system.img from it but it gave me the error "target reported max download size of 577100 bytes Invalid sparse file format at header magi"

---------- Post added at 04:33 PM ---------- Previous post was at 04:04 PM ----------

I think I have it guys. I flashed the stock boot then recovery and I just now got to the welcome screen! Man I thought this thing was dead thank you so much for the help!
[Nexus Player Original Android Development] mskip:
Glad you got it working again. Keep hold of the Stock image just in case you need it again.

Mark.
[Nexus Player Original Android Development] rgill420:
Mark, i had a quick question. I have ADT-1 on 5.0.2 LRX22G... this process should work correct?
[Nexus Player Original Android Development] KazeOne:
I followed the steps but something went wrong, I get bad command when it reboots with error, what can I do? I want to go back to 100% stock so I can update to 5.1.1
[Nexus Player Original Android Development] zarthan:
The ADT-1 can not be updated to 5.1.1 It is no longer supported. If you are using a different device check the proper thread.
[Nexus Player Original Android Development] darker_slayer:
The question was regarding the nexus player
[Nexus Player Original Android Development] zarthan:
This thread is about the ADT-1 not the NP. The NP uses an X86 processor, while the other Android TV devices use ARM. Trying to use downloads or instructions meant for one device may cause irreparable damage to another.
[Nexus Player Original Android Development] NapalmDawn:
So my ADT1 updated a few times when I first plugged it in last night (I had had it for a long time now but finally got around to trying to play with it as most of my time was focused on the Shield). I got it into fastboot, did a temp recovery image (the boot, not the full flash) and pushed SU. SU was available when the unit booted up it would hang trying to update the binary and I lost my controller being able to work with the device. Putting it in pair mode did not seem to work either (the controller, not the unit). My keyboard still worked fine. I rebooted it a few times and SU refused to update the binary and the controller just would blink the blue lights and turn off without ever syncing. It DID work for a little bit prior to the updates and the rooting.

Edit-woops wait. I was hitting on and back and not home and back. Do you turn it on, then hit home+back to get it to re-pair?
[ONE Q&A, Help & Troubleshooting] nicnaknic:
Ok so i flashed Calkulins ROM v2.1 last night, along with Franco Kernel r34 onto my oneplus one; i did a full wipe, including /Data, /System, /Cache (etc) with TWRP which.

I flashed the ROM and Kernel (one after another) onto my device, wiped Dalvik cache/cache, booted it up and let it go.

Instantly i noticed that the device was lagging when doing basic things such as typing, scrolling through web pages (etc). After time with the phone and repeating these tasks throughout the day the lag and jitter went away. It does show up from time to time in other parts of the OS, but not nearly as common as it used to.

How ever now my big issue is the terrible battery drain. I haven't kept a full log of my battery usage for the day, but i did do a little testing. From 69% battery-13% i had 1h 40min SOT which is completely terrible compared to what i usually get.

this evening i did another little test where i charged the device from 10%-67% then played music from youtube, played a few games, fiddled around on it (web browsing-Google+ etc) and left the screen off for a few minutes.

Currently the phone is at 41% with 1h 15min SOT; Screen draining 27% battery, but the interesting thing is Android OS is reading 50%. It used to average from 7%-20%. The total time on my battery is at 1h 25min while CPU usage under Android OS is reading 1h 31min.... that doesnt make any sense since i wiped the battery stats only 1h 25min ago.

Anyways i really have no clue why Android OS is running so high right now causing battery drain.

Please if you have any suggestions on what may be doing this to my OS, or why i get random jitter spikes Please let me know!
[ONE Q&A, Help & Troubleshooting] nicnaknic:
Possible answer

is it possible that my phone is acting up from screwed up battery logs? but how would that run Android OS so high?
[Nexus 6 Q&A, Help & Troubleshooting] Dasin:
i'am interested in getting the Nexus 6 .

But i do need some help in modifying the firmware on the device, for example.

Rooting

Modifying the Carrier Bundles

Keeping apps open in the background.

Also other Android Mods.

I need someone to help me learn how to do these things.

I can offer someone a ATT Data iPad Unlimited Plan, its prepaid and cost 29.99 a month, unthrottled truly unlimited data, research the plan it is valuable. I need someones time of a skilled person that is good at Android etc..
[Nexus 6 Q&A, Help & Troubleshooting] iboj007:
PM ME
[HTC Droid DNA] cat boss:
Just want to clarify. I have this

Locked

Monarudo pvt ship s-on rh

hboot 1.57.00000

radio 1.02.01.0818

openDSP v12.120.274.0909

os 4.09.605.5

emmc boot 2048mb

If i understand correctly there is no way for me to unlock the bootloader or s-off or even flash the ROM to aa earlier version.

I've tried firewater, rumrunner, moonshine, tried manually flashing with fastboot/adb and a million different zips. Each return error 12.

Ive watched a ton of videos and read a lot. The only thing I think I found that would be useful is sunshine but even that is not updated to 3.0 yet which supposedly will be able to s-off and unlock the 1.57.

Either I missed something or I need to wait till sunshine updates.

Just need someones' quick thought on this because maybe i overlooked something.