yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] locolbd:
I flashed the stock images from Google. So I always started from scratch. I did not modify anything else.
[Nexus 6P General] binglejellsx2:
At the very least, Android Pay is confirmed as still working.
[Nexus 6P General] GCbard:
I have read through the thread. It is still not clear to me that if I modify the bill. Profile that I will still receive OTA updates. I wanted to try to add the multi window feature. Also a few other small tweaks in build Prop. Can anyone confirm that OT I will still happen after the build. Prop file is modified
[Nexus 6P General] yusukemik:
I have been having the same issue for one week now. I modified build.prop to allow thetering, since then I had device is corrupted message as well. Basically I think that we add a line to build.prop and the device is detected as corrupted.

I confirm OTA update will fail as well. There seems to be a thread for nexus 5x on this as well. I received the November security OTA install starts but fails.

Modifying speaker sound might be OK as you are just changing a value.

I had relocked my bootloader so will need to wipe/clean device and will try foxfi for thetering.
[Nexus 6P General] locolbd:
I gave up on this last week. I would prefer to get my security updates.
[Nexus 6P General] TemporaryTester:
You still receive notifications for security updates.

You just have to manually flash them using the factory images and reapply your changes, though. I think the actual OTA will fail when it tries to verify against whatever system modifications you've done.
[Nexus 6P General] a1exus:
I'd assume one can reflash system.img and then take OTA)..

I big "Thanks" to OP, excellent guide! I now have hotspot)) Is there anything else that I can "profit" from modifying /system?)
[Nexus 6P General] surveyganga:
Can call recording be enabled with this method. I haven't found a working call recorder for Nexus 6P.
[Nexus 6P General] altezza2k2:
i modified my DPI and added homescreen rotation using this method and can confirm android pay is no longer working for me :(
[Nexus 6P General] Gloff:
Tethering active! Thank you!
[Nexus 6P General] xSilas43:
Most system modifications will disable android pay, DPI is known to do this.
[Nexus 6P General] l_stevens:
Android Pay

Using this method, if you ONLY add the tethering mod, will Android Pay still work?
[Nexus 6P General] sumguyatvt1128:
What settings do I change under mixer paths?

Very helpful thanks! What settings (code) do I change in order to make the volume louder?
[Nexus 6P General] Roland Deschain:
It's the only change I've made, I have the system is corrupted message on boot and OTAs fail to install, but Android Pay *DOES* in fact still work. I have my tethering and Android Pay, which is all I wanted. :) I tested it at an Android Pay-compatible Coke machine at a Car Toys in Tukwila, WA.
[Nexus 6P General] dratsablive:
I used systemless root, and actually modified the build.prop using root explorer and it did not affect Android Pay.
[Nexus 6P General] MrKaon:
With recent SuperSU, Android pay is working.
[Nexus 6P General] gg22:
This method doesn't work anymore on Nexus 6p with Android N preview? After doing

"fastboot boot twrp-3.0.2-0-angler.img"

my phone is stuck on TWRP splash screen - no options/menus/etc.

Worked perfectly on Marshmallow.
[Nexus 6P General] nadiros:
Let me guess, you're encrypted right? Its not this method. TWRP and angler's newer builds are wonky.
[Nexus 6P General] gg22:
Yep, I tried older TWRP build (2.8.7.2) and it works. I was able to modify build.prop but still my N6P ignores the line:

"qemu.hw.mainkeys = 1",

my nav bar is still there.
[Nexus 6P General] rohit25:
getting the following error with the May image.... any help??

C:\SDK\android-sdk-windows\platform-tools>fastboot boot C:\SDK\android-sdk-windows\platform-tools\twrp-3.0.2-0-angler.img

downloading 'boot.img'...

OKAY [ 0.635s]

booting...

FAILED (remote: unlock device to use this command)

finished. total time: 0.664s
[Nexus 6P General] SlimSnoopOS:
For anyone that intends to help, this user has posted for help here...

http://xdaforums.com/nexus-6p/help/help-using-adb-t3382737/post66938865#post66938865
[Nexus 6P General] tomz997:
My Nexus 6P is unlocked! (Android N preview 3 beta)

I was able to do the "adb pull" of the file mixer_paths.xml

Booting with "fastboot boot twrp-2.8.7.2-angler.img"

Mounted System and enabled MTP (only way I was able to copy with abd command in recovery)

Copied file with modified values for RX1 et RX2 ... : 88 (adb push c:\nexus6p\mixer_paths.xml /system/etc)

Then reboot to system

Try a pull of the file and value are still to 84.... why ??

I try to CHMOD 644 and still 84 value after a reboot
[Nexus 6P General] tomz997:
Encryption is activated on my device, can be why the file is automatically replaced ?
[Nexus 6P General] s3rioussam:
same here. I can make modifications and push them back to the phone. After that i changed permissions. Reboot. And the settings are gone. Anyone knows what goes wrong?
[Nexus 6P General] manyone:
could it be, that "adb reboot bootloader" does not work on Galaxy S7 stock rom without any modification
[Nexus 6P General] ajejawa:
I use this "adb pull" method to move app (base.apk) to /system/priv-app

The problem is the app is not recognized as system app because the original app folder is remain in /data/app

Is this possible to erase the remaining folder from /data/app on unrooted phone?

or is it possible to move the entire folder from /data/app to /system/priv-app?
[Android Apps and Games] stranzenbach:
Hi

I've found out how to create and fill a play list for the music scope.

I've used a browser starting a song. While playing i can add the song to the play list.

This is time consuming work.

In some descriptions i found the music scope supporting .M3U files. Is this true?

For me they do not seem to be recognised.

How to fill a play list with several hundred songs at the same time?

Best regard Eddy
[Miscellaneous Android Development] Omar Champ:
HI!

Is USSD really fixed? Can I port to my device Primo H3 -MTK6582
[Miscellaneous Android Development] Tran Tien:
yes, U can Port For Primo H3

USSD i dont know, From VIetnam Me not Work
[Miscellaneous Android Development] Omar Champ:
I ported this ROM but I got bootloops! I tried the CM12.1 bootloop fix, but it didn't work either! I didn't flash xposed.zip! Can that be the cause of bootloops?
[Miscellaneous Android Development] mirrr46:
Hi, nice rom thanks for fixes.

I did port to my device but i have two bugs;

playstore didn't work and second is high volume speaker to high.

Tell me how to fix this.
[Miscellaneous Android Development] mirrr46:
ok playstore works fine :) how to fix second bug?
[Miscellaneous Android Development] Tran Tien:
secound ?
[Miscellaneous Android Development] Tran Tien:
inbox me

https://www.facebook.com/Tien.lun1999
[Miscellaneous Android Development] rabin69x:
I have ported ur rom too. And i am not having any kind of bootloops. But the problem is my front camera and Bluetooth isn't working. Could u help me on it plz? :(
[Miscellaneous Android Development] mirrr46:
How to fix high volume issue? Sound from loud speaker is to high.
[Miscellaneous Android Development] Omar Champ:
Okay!
[Miscellaneous Android Development] rabin69x:
I cant sent u any msg coz u probably blocked it. So i sent u friend request.
[Miscellaneous Android Development] Tran Tien:
Replace all libcam
[Miscellaneous Android Development] rabin69x:
I already have done it not only lib but also etc files.

I think i need to do something with boot.img

I have tried other cm12.1 too. Its the same as always.

Plz help me
[Miscellaneous Android Development] Tran Tien:
update Final 3
[Miscellaneous Android Development] nikhilvnik:
Failed to copy files for swap ram

Anyone have proper solution for that?

How I do properly?
[Galaxy Note 10.1 (2014 Edition) General] s2mishappy:
Download : http://www.sammobile.com/firmwares/download/59270/P601XXUDOJ2_P601SERDOJ2_SER/

GALAXY Note 10.1 2014 Edition 3G - SM-P601

Model	: SM-P601

Model name	: GALAXY Note 10.1 2014 Edition 3G

Country	: Russia

Version	: Android 5.1.1

Changelist	: 5984967

Build date	: Fri, 09 Oct 2015 11:08:17 +0000

Product code	: SER

PDA	: P601XXUDOJ2

CSC	: P601SERDOJ2

anyone tried it? and is there any trouble when I use Russia version?

my original is Indonesia: P601XXUCNJ4

thank you
[Galaxy Note 10.1 (2014 Edition) General] marcosmjpa:
How to root?

Tks
[Galaxy Note 10.1 (2014 Edition) General] falouzzi:
Can you please send a direct link because I can't download from sam mobile, thanks
[Galaxy Note 10.1 (2014 Edition) General] Hatsune Meo:
Same problem. :(

I live in VietNam and have a same problem like you. I have been waited for a long time so i really really want to enjoy android 5.1 in my device. The last update was november last year, quiet disappointed when my old samsung galaxy s4 updated in may , 2015.
[Galaxy Note 10.1 (2014 Edition) General] abdalrhim:
i get same error when i try to upgrade to indian LP but when i change my 4.4.2 to Uzbekistan firmware_ P601XXUCOF1_P601OXECOF1_CAC it work

if you want this rom to work you have to be on kk 4.4.2 for same region like panama or other
[Galaxy Note 10.1 (2014 Edition) General] arses:
When I flashed russian 5.1.1 I got black screen but for 2nd or 3rd time with a complete format of internal memory, it worked finally.

HTC ONE ULTIM8
[Galaxy Note 10.1 (2014 Edition) General] LenAsh:
Thread closed - duplication of this THREAD
[Fire Original Android Development] ggow:
Disclaimer

I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before using it! YOU are choosing to make these modifications.

Notes

- The recovery cannot boot if flashed to the recovery partition instead it must be booted via fastboot using:

fastboot boot recovery.img

- The reason it cannot be flashed is that the bootloader is signature checking the flashed image against Amazon's RSA keys.

- External sdcard is not accessible from the recovery at the moment - will fix

- The touchscreen panel is not usable at the moment - instead use the volume up/down keys to navigate and power button to select

- The volume up/down keys are swapped - will fix this

- Apply update from internal memory and sideload are working.

- This is a basic recovery - it has no backup or restore function

- This does the job until TWRP is available

Download

- Amazon Fire Cyanogen Recovery

XDA:DevDB Information

Cyanogenmod Recovery, Tool/Utility for the Amazon Fire

Contributors

ggow

Version Information

Status: Beta

Created 2015-11-04

Last Updated 2015-11-06
[Fire Original Android Development] Awesomeslayerg:
So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.
[Fire Original Android Development] ggow:
- Pretty much anything we want to sideload, we can

- I have sideloaded:

Official Amazon Firmware

SuperSU.zip

Modified Gapps Package.zip

Xposed​

- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
[Fire Original Android Development] Awesomeslayerg:
Oh ok. So we can try sideload in or flashing a custom image now?
[Fire Original Android Development] ggow:
Yes, we can flash a custom rom :)
[Fire Original Android Development] Vlasp:
And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.
[Fire Original Android Development] ggow:
- The bootloader has no knowledge of the Android ROM AFAIK

- We have to bear in mind that we are limited to the stock boot.img therefore

- Any rom we produce should be based off the stock boot.img

- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.

- On the HDX, when it was a locked device I was able to boot AOSP in this manner
[Fire Original Android Development] Vlasp:
We should be able to use custom boot.img when we get safestrap, right?
[Fire Original Android Development] inscythe:
I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.

Do you mind sharing which gapps package did you use and what modification you did?
[Fire Original Android Development] patt2k:
this works on t he 50$ fire tab?
[Fire Original Android Development] Awesomeslayerg:
This is FOR it dummy
[Fire Original Android Development] ggow:
- Yes, I'll post it shortly

- I have only flashed it so far with no testing

- My Fire hasn't been online yet because I haven't blocked OTA updates yet

- Will test and provide a link for download

EDIT: Good news the Gapps package works with full play store functionality :)

I'll upload it and post a link in the General Section
[Fire Original Android Development] ggow:
- I started investigating this and Safestrap may not be possible

- Safestrap is usually for locked devices granted, however...

- Even if it were possible our kernel doesn't have kexec capabilities

- As with other amazon devices we really need a way to unlock the bootloader.
[Fire Original Android Development] ggow:
Modified Open Gapps Package

- I have posted the Modified Open Gapps package here.

- Tested and seems to be working fine.
[Fire Original Android Development] patt2k:
Very nice will have to play around with this later :D have this tablet for my grandma so at least with root and custom launcher I can make it easier to use at least :D
[Fire Original Android Development] Moogagot:
ggow is the ****ing bomb!

Between all your work on the FirePhone and this tablet, tell me what I owe you!
[Fire Original Android Development] GoughGhan:
Your first born maybe? :)
[Fire Original Android Development] sandman512:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
[Fire Original Android Development] theophile2:
No problem. You can find instructions here.
[Fire Original Android Development] sd_shadow:
you need adb and fastboot files

several options there are some basic information in my Amazon Fire Index

Fire Index: Which Amazon (Kindle) Fire Do I have?

once you have adb setup

boot Fire into fastboot mode: power off, Hold volume down, power on

if it boots to recovery select bootloader

once in fastboot mode check device manager Fire should be listed as Android adb interface

If so you should test fastboot commands with

fastboot -i 0x1949 getvar product

should get this back

ford

if so

place recovery.img in the same location as listed in command prompt

then boot recovery.img with

fastboot boot 2015-11-04-cm-12-recovery.img
[Fire Original Android Development] sandman512:
Thank you.
[Fire Original Android Development] Awesomeslayerg:
Hope someone creates a rom soon
[Fire Original Android Development] kylemaguire:
So I booted it and just tried to wipe cache. I was surprised there was no confirmation that it was going to do something. It was strange that it took a long time to wipe. I let it ran for about two hours. I came back and it still had the android with "erasing" still running. So either I slipped and pressed the full wipe, or there was a bug. Stupidly I pressed and held the power button and forced it to reboot. Got the amazon logo and now its stuck on the fire logo. Any way I can get the files off the internal partition (assuming they are still there?)
[Fire Original Android Development] ggow:
- To access your files

- Fastboot into cyanogen recovery, then you can use adb
[Fire Original Android Development] petermg:
So I was able to get into fastboot and boot into this recovery image... is there currently no backup option? I didn't see one but I'm rather tired right now, could've missed it. Sorry if this is the noob-est question in this thread :confused:
[Fire Original Android Development] ggow:
- No there is no backup option in this recovery

- It's very basic but does the job until I have TWRP working.
[Fire Original Android Development] ldeveraux:
I see a backup section in my flashfire. If you work through the "+" function, it seems you can create backups that way. Are you guys using flashify? Or are we talking about something different?
[Fire Original Android Development] csolanol:
Hi [MENTION=5749760]ggow[/MENTION] i am building TWRP too but touch screen is really an asshole. Tried all conf options for TWRP in BoardConfig.mk and no way to make it work like it should. Are you in the same trouble?

Edit: Gotcha!, fixed it.
[Fire Original Android Development] ggow:
Did an initial build and yes it was the same for me it was booting to a blackscreen. Then I just thought it might be a pain so went for the easier option to get something running, until we got TWRP.

Glad you got it working :)
[Fire Original Android Development] Awesomeslayerg:
Can you also make sure you can wipe system if you have tooo?
[Fire Original Android Development] csolanol:
TWRP fully working here. Just testing and trying to fix sdcard issue. Will post when issues are sorted out.
[Fire Original Android Development] Awesomeslayerg:
Yeah we now have twrp
[Fire Original Android Development] KLit75:
I think that's where I'm going wrong but the op in the root thread doesn't specify a boot.img They just have 3 files at the bottom of the op. The first is boot.img zip that's about 7.97mb I think? Is that the one I need? I'm sure that's why it hangs on "downloading boot.img" but I want to be really careful not to flash the wrong file. Thanks
[Fire Original Android Development] sd_shadow:
no use https://www.androidfilehost.com/?fid=24269982086987951
[Fire Original Android Development] KLit75:
No. That's the one I flash in fast boot but it returns "downloading boot.img" in the terminal. If you re-read the post i quoted of yours you said "boot.img" so I thought you were talking about something else.

It just hangs on that like it's trying to grab a file to flash but it doesn't finish. When I pull the plug it gives and error like read failed.

Now it's really puzzling. Fastboot is working and confirmed. "FORD" appears as the device then it keeps the connection but it's just not flashing.
[Fire Original Android Development] sd_shadow:
yep that's a typo it should be recovery.img

---------- Post added at 10:51 PM ---------- Previous post was at 10:29 PM ----------

maybe there is something wrong with the bootloader?

could try reflashing the firmware with adb sideload

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

[HOWTO] How to restore firmware on your device + Amazon Firmware
[Fire Original Android Development] ldeveraux:
Once I install Cyanogen, how do I get back into it? If I reboot the device and enter FASTBOOT, then bootloader, it just goes back to FASTBOOT MODE. Do I have to ADB the img every time?
[Fire Original Android Development] ggow:
You have to fastboot boot every time you want to boot a custom image.
[Fire Original Android Development] ldeveraux:
so you have to adb fastboot each time? I assume that's the same with TWRP too. Well at least it's recovery!
[Fire Original Android Development] Joshmccullough:
I keep thinking that I'll just update my Fire to the newest Slim build in a couple of minutes, but then remember that I'm not at home/at my computer to fastboot/recovery :). Oh well, it'll happen one day, or at worst it's not the worst thing in the world, I figure.

Sent from my Slim ROM'd Amazon Fire
[Fire Original Android Development] Pond-life:
Well it may be possible.

http://xdaforums.com/showpost.php?p=64278314&postcount=727
[Fire Original Android Development] k4y0z:
[MENTION=5749760]ggow[/MENTION] in these two commits, I've swapped Vol UP/DOWN:

https://github.com/chaosmaster/andr...mmit/ce83151e297debae645b663bd31fce762a337374

https://github.com/chaosmaster/andr...mmit/b95b3853a1cab5226f45442fcad70903b0589714
[Fire Original Android Development] 4t701:
can confirm it works. I dirty flashed CM latest build, gapps.zip, and SuperSu.zip yesterday and everything worked fine. Only took like a minute.
[Fire Original Android Development] Scot2001:
Is there a possibility this will work on fire os 5.1.1
[Fire Original Android Development] sd_shadow:
no
[Fire Original Android Development] ttcontributor:
Referred from this thread: http://xdaforums.com/hd8-hd10/development/root-amazon-fire-hd-8-10-5th-gen-2015-t3240024

Is this compatible for Fire HD 10 5th Gen? I am with Fire OS 5.0.0
[Fire Original Android Development] DB126:
If it were there would likely be posts/threads/discussion is the forum you referenced. This is not the place for HDxx questions.
[Fire Original Android Development] ldeveraux:
Doubt it, different device.
[Fire Original Android Development] jakiejohnson:
would i need to root my device beforehand to flash a rom?
[Fire Original Android Development] sd_shadow:
This recovery only works with the bootloader that comes with Fire OS 5.0.x.x for the 2015 7in Fire
[Fire Original Android Development] Chillmann:
Since most of the users need to use flashfire to flash a rom, u need to be rooted first
[Fire Original Android Development] wilsonj59:
I installed ADB drivers and did everything correctly. going into fastboot etc. and my device is all fine. I'll do 'fastboot boot cm.img' (cm.img is the name i named it) and it will give me this error: FAILED (remote: the command you input is restricted on locked hw). Any ideas what I need to do?
[Fire Original Android Development] DB126:
Can't boot a custom recovery on this device (locked bootloader). You will need to root and use FlashFire assuming on/below FireOS 5.3.2.
[Fire Original Android Development] wilsonj59:
Sorry I’m so stupid. I read this acknowledging it was for 5.3.2 or lower - and I attempted on my 5.6.0.1 device ? I have 2 of them so i should probably do it on the right device now with 5.1 on xD
[Fire Original Android Development] DB126:
Some clarifications:

- a custom recovery can not be installed on any 5th-7th gen Fire device

- early 5th gen models that never advanced past FireOS 5.0.1 can boot (but not install) a custom recovery like TWRP

- 5th gen devices that never advanced beyond FireOS 5.3.2 can be rooted and utilize FlashFire to install a custom ROM, Xposed framework, etc

- as of this writing there are no known root exploits for 5th gen devices running FireOS 5.3.2.1 or above or any 7th gen device

It doesn't sound like either of your devices meet the qualifications for booting a (now obsolete) CyanogenMod custom recovery.
[Fire Original Android Development] wilsonj59:
I understand what you said. I do actually own a 5th gen on 5.0.0 so I used TWRP and am currently installing a custom rom. Thanks anyways :)
[Fire Original Android Development] DB126:
Your previous post said 5.1 which is what prompted elaboration. Hopefully the extended detail will help someone else (but probably not...who reads old posts?).
[Nexus 6P Q&A, Help & Troubleshooting] belloni:
Is anyone else having problems with this? I plug my (new) headphones in then load up Poweramp, play a song and it just plays through the speakers. It worked before, and I can't remember what I did to make it work! All settings are fine as far as I can tell.
[Nexus 6P Q&A, Help & Troubleshooting] __NBH__:
I've used Poweramp fair bit and never had this issue, maybe try cleaning out the headphone socket with some compressed air in case there is something in there causing a bad connection.
[Micromax Canvas 2 Plus A110Q] Rohit Kapdi:
hey ,

My device is micromax A110q and now i m use COLOR OS KK, that's a cool and awesome ROM , but i want default USB mass storage in this rom i don't like this Oppo mass storage in this ROM so please give Solution any file flash then give me link ...thnx
[Micromax Canvas 2 Plus A110Q] Calin:
Hi and thank you for using XDA Assist :)

Try asking over here

The experts of the device will know better how to help you with that.

Good luck!