yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] yosmokinman:
Gaining root access is very simple.

Flash twrp with fastboot.

Then from twrp flash the su zip of your choice, phh's superuser or SuperSU.

That's it. No loss of data. Of course make a nandroid first just in case of any problem.

Edit: In your other thread that you link to this one in (didn't see it earlier) you may not have needed the clean install. Either flashing the boot.img and system.img for that os version with fastboot OR deleting the "-w" from the flash-all script in the factory image would have kept your apps/data. Just for future reference if you choose to stay on 6.0.1 and something goes wrong.
[Nexus 7 (2013) Q&A] Michael Carleone:
I think there is some confusion and there are different variations on how to flash to TWRP. What is the most recommended flash process?
[Nexus 7 (2013) Q&A] jshamlet:
I just did this the other night, though I did go from one MM build to another.

1a) Grab the factory image from Google in ZIP form from the developer site

1b) Grab the latest version of TWRP for the 2013 N7 Wifi (flo) from their website

1c) Grab an appropriate super user app flash-able from TWRP. I prefer SuperSU, but the choice is yours. Make sure it supports systemless installation, as traditional SU installs can run afoul of Marshmallow's new integrity checks. (Yes, there are permissive kernels available, but I prefer to stay as stock as possible)

2) Unpack ZIP from 1a into a folder on your PC. I tend to drop a minimal copy of fastboot/adb into the folder to make things easy, but you can just use whatever is in the path.

3) You can choose to use the batch file or not, but if you do, remember to remove the -w from the fastboot command that flashes the OS image unless you want truly clean install. I personally prefer to flash the bootloader separately, then flash the system, rather than using the batch file, but they are equivalent. The tablet will automatically restart after the image is uploaded.

4) Kick back and relax while all your apps get recompiled. When it finally comes up, make sure everything is working okay.

5) Copy your SU flashable image to the tablet. If you have ADB debugging turned on, you may have to toggle MTP mode in developer options to re-enable it.

6) After everything is nice and stable, and everything you need is on the tablet already, reboot to bootloader.

7) Flash the TWRP image from 1b using 'fastboot flash recovery twrp_<version>.img'

8) Reboot into your shiny new recovery and install the SU package from 1c

9) Reboot again into the new, newly rooted, system and verify SU works.

10) Enjoy!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] pitguy3:
I screwed up and was trying to flash an updated ROM and erased my EFS on my N8013... How do I get it back to factory??

Steps please!!

Thanks in advance!!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
You restore your backed up EFS folder .

Failed to backup EFS then read the identical multiple posts on EFS IMEI on here .

Stock factory roms are on sammobile .com
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] pitguy3:
Thanks for the help... I have read the multiple posts on here...
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Rolo42:
Sure?

https://lmgtfy.com/?q=N8013+restore+EFS
[Android Head-Units] hurtgen:
Just found this cool amp the other day. Sorry if it's been mentioned before.

For those who don't know, head units have an amp, per say, built in to them. However, most are junk and just large enough to get you by. Even the ones that have high claims. Like 50watts X 4, but your really only getting like 15 watts per channel. A lot of people don't want to mess with all the wiring and connections and cost/space issues with installing a traditional outboard amp in their trunk. I came across this little bugger that has great reviews and may be the ticket for some of you. It's an amp, but with a slim profile and able to hide in your dash behind your headunit. Idk, just thought I'd share.

https://www.amazon.com/Alpine-KTP-445U-4-channel-Power-Amplifier/dp/B003VVYL46
[Android Head-Units] CadillacMike:
well i clicked on this thinking i would not be interested, but now I'm thinking I might get this
[Android Head-Units] doitright:
45RMS, not terribly small there.

FYI: Those head units that say 40 or 50 watts x4 aren't lying -- they're quoting MAX, not RMS.

Generally speaking, you don't need more than about 40-50 max. If you send too much power, you will damage your speakers. The speakers that cars come with are a reasonable match with the FACTORY radio, which will give you around 40 max. Sustained use at even factory radio's highest output will dramatically shorten the life of the speakers, AND, is enough to cause permanent hearing loss.

Some aftermarket speakers can take a higher amount of input power, but they aren't necessarily LOUDER. They actually require more power to generate the same volume. Now of course, I'm not going into the discussion about which *sounds better*, rather just about raw power. My only point, is that if you have factory speakers, then even this amp is overkill. If you want to improve the sound QUALITY, then of course, by all means, knock yourself out. But don't forget to upgrade your speakers as well, or you're just throwing the money down the toilet.
[Android Head-Units] hurtgen:
The number one cause for blown speakers is driving them with an underpowered amplifier resulting in clipping. It's much more advisable to over power a speaker than to under power, which is the case in most cars in Stock form. This amp would be a great addition to a vehicle with either stock speakers or entry level coaxial or even some components. In my situation I'm running a pair of Infinity Kappa 60.11cs rated at 90 watts rms each @ 2ohm and powering them with a Rockford Fosgate p300x2 putting out 150 watts rms @ 2ohms per channel.

Reading the reviews, it sounds like many people are installing this with stock speakers in place and are having great results.
[OnePlus X Q&A, Help & Troubleshooting] carmelizing:
So I was trying to flash CM13 on my rooted OPX but I think I may have accidently deleted my recovery and now my phone is stuck in a boot loop where it loads the OxygenOS setup screen freezes then reboots. I would really appreciate it if someone can help me. Thanks in Advance :)
[OnePlus X Q&A, Help & Troubleshooting] Exodusche:
If you have none of these you should be sending for repairs. You sure you don't have fastboot? Have you taken a look at the mega unbrick guide?
[OnePlus X Q&A, Help & Troubleshooting] ajmcklosky:
If you havent tried , first press power button for few seconds till your phone switches off. Then press vol up+power button simultaneously to go in fastboot mode.

If you are successful then follow the Mega Unbrick guide for Oneplus X else head over to service center.
[OnePlus X Q&A, Help & Troubleshooting] carmelizing:
Oh thanks, couldn't figure how to get to fast boot, but thanks
[HTC 10 Questions & Answers] hansglx:
Guys any chances to hack into UHL SKU (EMEA/Asia) model of HTC 10 inorder to support CDMA networks ?

Because as listed in htc.com/mea-en/smartphones/htc-10 SPECS section UHL SKU (EMEA/Asia) model doesn't support CDMA whereas WL SKU(America) model does support for the same.
[ZTE Axon 7 Questions & Answers] Senjaya:
Hi. User of Chinese Axon 7 (A2017)

And im currently cannot install large app from Google play Store. Everything above >50MB will trigger play store to Not responding (after download near 100%)

Ive tried install other version playstore and play service and it did the same thing. Is there any fix? Thanks
[ZTE Axon 7 Questions & Answers] yoavtabakman:
It happened to me too. I've cleared the chach from the play store app and also from the play service, then reboot.
[ZTE Axon 7 Questions & Answers] Pharecyde:
Hi, had the same problem

Check the premission of the Google Play Store, Google Play store must have premission to the "Storage"

In Settings - Apps page,slecte Google Play Store ,tap permission).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] jericko:
I am sick of trying to install screen-guard on my Tab Pro 10.1. I always have a few flaws and I use my Tab primary for reading books and comics so my eyes tend to gravitate towards the flaws. I thought about not using a screen-guard and taking my chances. Anyone here not use one and if so has your screen developed any scratches or cracks?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] Ichijoe:
I bought my Tab Pro 8.4LTE second hand. It had a minor scratch, and one tiny rub spot. Neither of which really effect the use of the Device, and only show up though massive screen glare. My old Man swears by those things, and I guess if you're proficient enough to get it on right, and not live in a Dust bowl they can be ok.. For a while.

Personally I just use mine in a magnetic hardback flipcase, and keep the Device in my upper inner Coat Pocket, and although it leaves stripes on the Glass those can be gently wiped off.

As such I've not noticed any new scratches on my Tab.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] BlueTaurus:
I have had mine since the tablet was released without a screen protector on and there isn't a single scratch on it, i use it every day. Just get a case that folds over the screen when you're not using it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] jericko:
Thanks, that makes me feel better! I use mine primary for reading and have it in a decent case, I just hate using a screen-guard as they always have flaws.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] _salguod:
I've had mine since new as well, never a screen guard but always in case. Screen looks perfect.
[G4 Q&A, Help & Troubleshooting] vandyswa:
Unlocked phone, and I was able to enter fastboot from adb under Android. Installed a ROM which won't boot.

Without Android booting, I can't get to adb and enter fastboot. The power+voldown only reaches a Factory

data reset menu. My fastboot tool does *not* see a device.

I can get the phone into LG's proprietary firmware update mode, but that's about it. Does anybody know of

any other way to reach fastboot? Or do I have to go dig up a Windows machine to retread this LG phone?
[P3600 General] dwphoto:
When I soft-reset my dopod d810, it shows arond 22-23 mb program memory. This drops very quickly and sometimes to less than whats required to run stuff (2-3 mb)

I do a quick clean with memmaid but it doesnt do a lot.

Can anyone explain this or do I just need a soft reset every day or 2 ?

Thanks, Dean
[P3600 General] dmcgroggan3:
allot of info on this question, just do a search next time before you post because if your question has beedn addressed again and again, no one will reply.:)
[Nexus 6  General] Face_Plant:
I don't understand why this isn't a feature of stock Android. They did it with the notification bar, but why not the navigation bar? The main reason for doing this is to prevent the navigation bar from being burned into your screen. There are Xposed modules for Lollipop/Marshmallow that do this exact same thing, making this mod unnecessary on those versions of Android. Since there's no Xposed for Nougat (or if you don't like using Xposed on Lollipop/Marshmallow), doing this mod will make your navigation bar dynamically change color to match your notification bar.

***Please Note***

This isn't perfect. In applications like Google Messenger the navigation bar doesn't change to match the color of the contact you're texting, but it's better than nothing.

Prerequisites:

- Nexus 6 with USB debugging enabled in developer settings

- TWRP

- ADB fully setup and functional

- Text editor (gedit (Linux), NotePad++ (Windows), or whatever you like to use)

- Archive Manager (Linux) or 7Zip (Windows)

- Apktool 2.2.2 (link at the bottom of this post)

- Apktool Windows wrapper script (Windows only)

Step 1: Boot into TWRP

Step 2: Select mount, then select system

Step 3: Connect your Nexus 6 to your computer and fire up a terminal (Linux) or command prompt (Windows)

Step 4: Navigate to the folder containing ADB (platform-tools).

Step 5: Type "adb pull system/framework/framework-res.apk".

Step 6: Type "apktool if framework-res.apk" This installs the framework

Step 7: Type "apktool d framework-res.apk" This decompiles the apk

Step 8: Navigate to res, values, and open styles.xml with your text editor of choice

Step 9: Search for "navigationBar". There will be three instances of it. You only have to change the last two. Change "@colorBlack" to "?colorPrimaryDark" and save your changes

Step 10: Open colors.xml and search for "input_method_navigation_guard". Change "ff000000" to "00000000" and save the file. If you don't change this, the navigation bar will turn black when you open the keyboard

Step 11: Go back to your terminal window/command prompt and type "apktool b framework-res". This recompiles the apk

IF YOU SKIP THE FOLLOWING STEP YOU WILL END UP IN A BOOTLOOP!!!!!!!!!!

Step 12: Delete META-INF and AndroidManifest.xml from the modified framework-res.apk and copy over the ones from your original framework-res.apk

Step 13: Push the modified framework-res.apk to your device with ADB or by boot into recovery, copy it to your phone, and use the TWRP file manager to move it to /system/framework. If you do the TWRP method, be sure to set the permissions to 0644 or your​ phone will not boot.

Step 14: Boot up your Nexus 6 and test it out!

Link to Apktool
[Nexus 6  General] Strephon Alkhalikoi:
Nice tutorial. However, the reasons you're having issues "reusing" an existing modified copy of framework-res.apk are twofold.

1. You're re-signing a system app. Unless things have changed in the four years since I last modified framework-res.apk, system apps are not signed.

2. The apk can also be moved into /system/framework using a file explorer on the device. It simply cannot be done in one shot as the permissions need to be changed prior to the final move into /system/framework.

The framework is Android version dependent, so an Android 5.x framework will not work in Android 6.x or 7.x. However, replacing the framework on multiple copies of the same version of Android is certainly possible. I have to head off to work, but when I have a spare moment upon getting home I'll generate a "reusable" framework, and a flashable zip as well.
[Nexus 6  General] Face_Plant:
1. The first time I did this I didn't sign the app and ended up in a bootloop. After researching the issue I came across a post that said signing the app was necessary. Signing it fixed my problem, so I've signed it ever since out of habit. Next time I do this I'll skip signing it and see what happens. If I don't get a bootloop I'll remove it from the guide. It's possible I had a permissions error or something.

2. While moving it with a file explorer is possible, I just prefer ADB, so that's why I used it in my guide.

I realize that they're version dependant. I wasn't trying to use a modified framework-res from Marshmallow on Nougat or anything like that. For example, when I tried reusing one from the November factory image on the December security update, or one from the November image on Pure Nexus, I get a bootloops, so that's why I assumed it necessary to create a new one each time. It's not like this mod is hard or takes a large amount of time, so why not redo it each time just for fun? ;)
[Nexus 6  General] Strephon Alkhalikoi:
Not everyone likes playing around with app mods. When I last did it, it was to enable the network location service on a Coby tablet running Android 4.0.3. That was NOT fun as it involved smali editing. At least this is only an XML edit.
[Nexus 6  General] Face_Plant:
I didn't mean for all mods, just this one. Like you said, it's only simple changes to two XML files.

After getting some practice by doing this a couple of times it only takes a few minutes to complete, depending on the speed of your computer. It takes me about 30 minutes since my Ubuntu machine is an old early 2000's PC that takes about 10 minutes to decompile the app, 10 minutes to sign it, and 10 more to recompile it... I'll be able to knock 10 minutes of that time if what you're saying is correct and signing it is unnecessary.

I'll try it again after class today and remove the signing bit if all goes well [emoji106]
[Nexus 6  General] RMarkwald:
Great write-up, worked well OP!

You can after recompile of the framework-res folder, you can delete the AndroidManifest.xml in the new APK, and copy the AndroidManifest.xml and META-INF folder from the original framework-res.apk into the newly built APK...hopefully that makes sense.

No need to sign. That's what I did and it worked just fine, eliminates a step. I use 7zip to do all of that BTW.
[Nexus 6  General] Face_Plant:
Good to hear. Those steps have been removed from the guide.

I wonder why signing it fixed my problem when I did this on Marshmallow earlier this year... I guess I screwed up something else and the second time around when I signed it I didn't screw up whatever I did wrong the first time.
[Nexus 6  General] RMarkwald:
Could depend on the app maybe? Not too sure there. I started wanting to learn modding apks (mainly making color changes, etc) by guides similar to this, the whole "I wonder if I can do that?" thing. Hopefully this will encourage those looking to try something like this that isn't too difficult to do to give it a shot and try it, just remember to have a backup of framework-res.apk handy, always can be adb pushed back via recovery if something goes south. :)

Thanks again for this OP, so far working great!
[Nexus 6  General] jmart518:
Awesome write up!

Not trying to hijack the thread, but for those not comfy making mods, there is "an app for that" Navbar Apps

Simple app that will dynamically change your nav bar color as well as other goodies.
[Nexus 6  General] kidhudi:
recompiling it fails. i get this error on Ubuntu 16.10 I even tried using sudo :eek:

I: Using Apktool 2.2.0-dirty

Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml

at brut.androlib.Androlib.readMetaFile(Androlib.java:258)

at brut.androlib.Androlib.build(Androlib.java:270)

at brut.androlib.Androlib.build(Androlib.java:263)

at brut.apktool.Main.cmdBuild(Main.java:224)

at brut.apktool.Main.main(Main.java:84)

Caused by: brut.directory.PathNotExist: apktool.yml

at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:105)

at brut.androlib.Androlib.readMetaFile(Androlib.java:254)

... 4 more

how do i deal with this?

i see the yml file right in the folder
[Nexus 6  General] Face_Plant:
Is Apktool installed correctly? Have you tried using Apktool 2.2.1? Maybe 2.2.0 isn't compatible for some reason? These are obviously just guesses. I'm no master at reading error logs...
[Nexus 6  General] kidhudi:
ok i figured that out..

will this technique work on nitrogen version 7.1.1 because the nav bar doesnt change but when i pull the framework-res.apk the xml files are in fact altered.

---------- Post added at 09:13 PM ---------- Previous post was at 08:24 PM ----------

no the command in the tutorial didnt work. because i was compiling a folder named framework-res and not an apk all i did was remove the .apk from the command supplied and it worked finally :)

also i dont know if it is an error but the push command has an lsystem for the location to be pushed. that wasnt working either.

thanks for the reply bro
[Nexus 6  General] kidhudi:
Thanks face_plant. It was working the whole time. I thought I would get the pixel icons lol. My bad

Great tut thanks
[Nexus 6  General] Face_Plant:
Pixel buttons are from the Substratum theme I'm using. You can get those too by being on a Nougat ROM that supports Substratum and using Pixel UI theme from the Play Store.

Just a heads up, if you're on 7.1.1 the theme won't work. It needs to be updated to support 7.1.1. Haven't tried it on 7.1, so it may or may not work.
[LG G5 Questions & Answers] unixwise:
I switched from V10 (H860N) to G5(F700L) recently, and realized the voLTE is no longer available, and/or need some extra effort to get it available. the matter without voLTE is data qualify will drop during and few seconds after the call is end.

The carrier I am subscribing provides 450M LTE-A, I reckon I could leverage their voLTE to archive HD call but no longer on my F700L. Please advise if you have any hints on override the setting on this Korean phone
[Desire 816 General] OronDF343:
I managed to track down the RUU for A5_DUG with CID: HTC__622 (Asia_HK version). The filename is:

0P9CIMG_A5_DUG_L50_DESIRE_SENSE60_MR_hTC_Asia_HK_2.34.708.1_Radio_1.13.3230.27.0303_13.19.3230.00D_F_release_443977_combined_signed_2_4.zip

I have uploaded it to MEGA here: [url]https://mega.nz/#!28QiwDqA!NovlOSELHcoW7D8LgT2UdYVfQn07QDtmhvC7AMEJz-4[/URL]

Please note that this RUU is of the Lollipop version. It is possible downgrade to it from marshmallow, and then update via OTA (and I recommend that you do so for more memory space. I have done this myself).

How to flash an RUU:

NOTE: This guide is relevant to all variants and CIDs of the device. However, the RUU that I linked above ONLY works for the specific variant+CID mentioned above! If you have a different variant OR CID you will need to find the correct RUU for your device. You can get your CID with:

fastboot oem readcid

NOTE 2: This guide is formatted incorrectly, and does not display correctly in the XDA app...

If you have unlocked the bootloader, you need to lock it. Run this command in FASTBOOT (ignore any errors that appear):

fastboot oem lock

Copy the RUU file to a MicroSD card. You must use a MicroSD card, it does NOT work on the internal storage! (I haven't tested with OTG but it might work)

Rename the file to 0P9CIMG.zip

Insert the MicroSD card into the device. Now boot to the bootloader (if you are in FASTBOOT choose HBOOT) and after a few seconds it will ask you if you want to update.

Choose yes. The process will take a while and the device will reboot at least once.

At the end it will tell you to press power to reboot. That means you are done and the device is restored to stock conditions.
[G3 Q&A, Help & Troubleshooting] dsilx:
So i looked for awhile but i couldnt find anything i have a lg g3 that i got for 40 dollars and it has lollipop can i use towelroot or king root to root it or is their a complicated process to it like my g4 some one help asap

By the way its the us990 variant or us cellular
[ZenFone 2 Q&A, Help & Troubleshooting] Cencourang:
Hello guys, Im very sorry for my bad english. But I really need some guide here..

So yesterday, finally I successfull to install CM13 in my Zenfone 2 ZE551ML. I already use it for a day, and I really like it.

Hours ago, usually in my free time, I read web novel on my Zen, and I just think, maybe there is good browser after using custom rom and root. So I search and found the browser. But the browser required to uninstall the default browser, so I need some tools to installed it, and it need to install from TWRP.

So I enter recovery mode, but I only enter basic recovery mode (not the TWRP).

Try to google it, but not found how to enter TWRP recovery, what I found was how to install it. And I found the way to enter it, but it exactly how I do it, but for me it ended enter basic recovery mode (not TWRP).

So, how do I enter TWRP mode?

Do I need to do the same way when I install CM13 using PC? Or there is another way?

Please help me.. Already google, but not found any answer (maybe incorrect keyword)
[ZenFone 2 Q&A, Help & Troubleshooting] prc.kailas:
first of all flash a permanent twrp
[ZenFone 2 Q&A, Help & Troubleshooting] Cencourang:
so, when I install CM13, there is a step when I install/using TWRP, is that only temporary?

so I need to reinstall the TWRP?
[ZenFone 2 Q&A, Help & Troubleshooting] sukhwant717:
buddy just go to twrp wesite and download compatible recovery for you device. use fastboot to flash recovery

fastboot flash recovery recovery.img replace recovery.img with the name of ur downloaded img.

now important step. do not reboot to system yet. use volume button to find option of recovery mode at the top off screen. click power button it will boot into recovery and install in permanently. it is very important else stock recovery will replace ur custom recovery