yashsingh1/xdaforums huggingface dataset:
[Fire General] K5LK:
Ok tnx. Not sure where to look now to root 5.1.2. Kingroot goes to about 30+% and then gives up. Tried a dozen times with this method.
[Fire General] sd_shadow:
restore 5.1.2 in recovery using adb sideload

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire General] Dunard:
It will not say 5.1.2.1. The .1 is cut off from it. The date of the build is different. If you tried over 5 times then you do have the 5.1.2.1 installed.

Trust me. I had that issue before. I re-install the 5.1.2 and then run KingRoot to rooted the device. No problem.

Just have to look at the date.
[Fire General] K5LK:
You are correct! Got it working. Thanks so much for the help.

I used SuperTool and now running LP-Fire-Nexus rom. Haven't had so much fun for $40 in a long time. This is cool. :D
[Fire General] ShanMan14:
I installed the 5.1.2 .bin file, was able to use KingRoot to root it. I installed Nova (after editing the Suptertool .bat files) but I really want to run a custom ROM. I went through this with another Fire and I'm running CM12 on it. This newer one, every time I attempt to run a custom recovery via adb it fails.

Flashfire says, "Root access could be acquired"
[Fire General] sd_shadow:
see rootjunky's supersume video

https://www.youtube.com/watch?v=3O3DcpeS_Ic

or manually install supersu with a terminal emulator

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
[Fire General] ShanMan14:
The terminal emulator worked! Thanks!
[Fire General] dvazriel:
Thinking about getting a new Fire 7 today.

Are those rootable? Or do i need to look for older versions?
[Fire General] Phustercluck:
I'm having trouble rooting my fire. My device says 5.1.2 but my kingroot fails at 30% everytime, so I'm assuming that its actually 5.1.2.1. Doing a factory reset from within fireos and from recovery mode yields the same results.

I attempted to sideload 5.1.2 from fastboot mode but after typing in "adb sideload..." it says null something device not found. I've installed and tested the adb\fastboot (am I blind, where tf is forward slash?) and they both function. Devmgmt shows either the composite or bootloader driver. However, when I put it in fastboot mode the fire device disappears and I get a kffowi with a hazard sign under other devices. I usually don't have this much trough men figuring things out like this so its becoming increasingly frustrating.

Regards
[Fire General] Phustercluck:
I've completed that list. Sorry in advance for the swedish.

What my driver manager looks like with amazon fire 7 connected and on Note that I have an android device and fire device.

My options after update driver > on computer> let me choose

I did install the bottom 3, and rebooted when it asked.

My options after doing the same on the fire device

Roughly translated "the given folder doesn't have a compatible driver. If there IS a driver in the given folder make sure it's compatible with x64 systems"

I've never seen the screen that allows me to choose what type of device, ie android or android phone when doing as you said for either my android device/fire device, both take me directly to where the images show.

Screenshot from earlier of the null error but what I continue to see even after completing these steps.

I appreciate the expedient reply.
[Fire General] FaLLenJinX:
Hey guys

when I try to boot into TWRP recovery via cmd it says:

downloading 'boot.img'...

OKAY [ 0.259s]

booting...

FAILED (remote: unknown command)

finished. total time: 0.265s

What should I do to sucesfully boot into recovery?

My Fire is running FireOS 5.1.2

Thanks for help.
[Fire General] DB126:
Booting a custom recovery is only available on FireOS 5.0.0-5.0.1. You can not rollback to an earlier version. Everything you need to know is in first few posts of this thread: http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire General] bibikalka:
Updated with Flashfire instructions, with the 5.1.2 bootloaders' preservation (just in case ...)
[Fire General] daniel3016:
I had this problem it is ' adb sideload' the space is in front of 'adb'
[Fire General] beezar:
Ok, just want to make sure I got this right before I do anything. I'm on 5.0.1. By follow the OP, I can install 5.1.4 but still have a 5.0.1 bootloader for TWRP access and still have root, and I can go back to 5.0.1 if I wanted to no problems?

And after installing 5.1.4, can I use the rootjunky Supertool to install Google Play store and Xposed, and block OTA updates? I'm assuming the Supertool doesn't mess with the bootloader at all...
[Fire General] daniel3016:
I'm not sure but I know that 5.1.4 need to be taken back to 5.1.2 and them you can use super tool to root and install FlashFire and exposed.
[Fire General] bibikalka:
Yes, you are correct ! The bootloaders are totally separate from the FireOS version. So you can keep 5.0.1 bootloaders, but run the 5.1.4 kernel and all the rest of the FireOS. Then during any upgrade/downgrade remember to run TWRP and follow these instructions, so that you keep 5.0.1 bootloaders, and TWRP access !
[Fire General] beezar:
Anyone try this with 5.3.1.0 and keep the 5.0.1 bootloader for TWRP?
[Fire General] bibikalka:
I've checked the "updater-script" in 5.3.1.0, it's identical to the prior versions. So the upgrade via TWRP/Flashify should work just fine (as before).
[Fire General] bibikalka:
Updated to 5.3.1.0 via Flashfire, all is good. Post #1 is updated accordingly.
[Fire General] Venio2000:
Beginner question...

Just for clarification:

If I just received an Fire with 5.1.2 and (dumb...) updated it to 5.3. I can't downgrade it with this tutorial since I didn't root it at 5.1.2. right?

Thanks!
[Fire General] Dunard:
Nope
[Fire General] bibikalka:
Actually, you could try this :

1) downgrade to 5.1.2 (+ brick)

2) flash 5.3.1 bootloaders back (tee1 + uboot)

3) hope the preloader version did not change, so after 2) you can boot with 5.1.2 OS and 5.3.1 bootloaders, which would let you use Kingroot

To flash 5.3.1 bootloaders, follow this :

http://xdaforums.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747

Ideally, it'd be nice to read UART output, in order to figure out if the preloader version changed from 5.1.2 or not ...
[Fire General] Kramar111:
[MENTION=3565108]Venio2000[/MENTION]

Stop!

[MENTION=6680544]bibikalka[/MENTION]

AFTV tools didn't work on 5.1.2
[Fire General] bibikalka:
Thanks for the info !!! I've checked just now, indeed, the 5.1.2 preloader no longer works :(
[Fire General] Venio2000:
Thx!

Will wait and keep my fingers crossed :)
[Fire General] Stonkers:
root/downupgrade

Any word on root or downgrading 5.3.1? I just fixed a 4 month old brick and unfortunately installed 5.3.1 without knowing. I read that the new bootloader isnt compatible for a downgrade. Any help would be highly appreciated. Thanx
[Fire General] DB126:
No root, no rollback, no timeline. Could happen tomorrow or never. Best get use to FireOS as you may be stuck with it for awhile.
[Fire General] Stonkers:
Bummer.. but thank you so much for reply.
[Fire General] trlkly:
Fire OS isn't my issue. I just want an adblock that works. None of them seem to. I was hoping root would fix it.

I just kept putting it off, not realizing I would be upgraded without seeing a prompt first, like I did the first time I updated.
[Fire General] DB126:
Adguard (banned from Google Play) works a treat, does not require root but does need underlying VPN support on unrooted devices unless you feel comfortable configuring a proxy. Not sure where FireOS stands on the latter item. Give it a whirl. App ad blocking requires a subscription; browser (web) blocking comes as a freebie.

https://m.adguard.com/
[Fire General] Dunard:
https://play.google.com/store/apps/details?id=com.adguard.android.contentblocker Look like they still hosting it on Google Play Store. Fully free? Name change?
[Fire General] DB126:
Different, limited function product by same company. Only supports ad blocking in Yandex and Samsung browsers. Most users would be better served by full app that supports ad blocking in any browser (still free).
[Fire General] trlkly:
One more question: Is it possible to prevent a subsequent update, just in case a root exploit is found for 5.3.1? You know, so that Amazon doesn't patch it out in a subsequence update?

I presume that a factory reset does not reset the OS, right? Everything says it resets the device back to what it was when you got it, but if it reset the OS, people would be trying that, right?
[Fire General] DB126:
- no fully effective way to block OTA updates without root

- unregistering device reduces update exposure but limits functionality

- factory reset (misnomer) only clears data partition; OS (rom) remains intact including all corruptions introduced accidentally or otherwise
[Fire General] bibikalka:
The reset deletes the user stuff, but leaves /system untouched. And all the updates go into /system.

The update will be prevented if you followed this:

4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
[Fire General] DB126:
Unless I'm mistaken that file can not be renamed unless rooted.
[Fire General] bibikalka:
Indeed, my bad ! Fire 2015 started out with a lot more holes than Fire HD 2014, but ended up more and more locked down. So even blocking updates cannot be done without root :(
[Fire General] anixan:
Hi,

I have a new Fire HD 7 (5th Gen) and its on 5.3.1.0.

I want to root the device however this guide seems to be focused more on Downgrading. Can someone please tell me what I have to do to root this device?

Thanks
[Fire General] DB126:
FYI - there is no "HD" in the product name; it's simply a 5th gen Fire.

At present there is no rooting or downgrade option for FireOS 5.3.x. Nor can OTA updates be blocked. There are a few hacks that can be applied via the SuperTool (eg: install Google Play Store) but you are stuck with rootless FireOS for now.
[Fire General] anixan:
Thanks for the information I will wait.
[Fire General] ahecht:
I currently have a rooted Kindle Fire 7 that was downgraded (probably from 5.1.4, I don't remember) to 5.1.2 and rooted. Am I correct that if I follow the instructions in the first post using the fire_boot_5.1.2-5.4.2 file that I will be upgraded to 5.3.1 and rooted?
[Shield Android TV Q&A, Help & Troubleshooting] kyrusdemnati:
anyone know if i root, can i update to the latest firmware updated from nvidia

i want to root for dual shock 4 wireless play

but i also want android 6.0 for the external drive feature space... so i can move apps etc

thanjs
[Shield Android TV Q&A, Help & Troubleshooting] skymera:
If you root, you can update yes. It might unroot, but you can re-root simply enough.

Android 6 isn't out for the Shield.
[Shield Android TV Q&A, Help & Troubleshooting] the.teejster:
Have you actually tried and confirmed this ?

It's my understanding that since the introduction of Lollipop, ANY changes to SYSTEM will cause OTA updates to fail. There is a brand new, experimental system-less root option out there now but it still needs to be tried, tested and verified.
[Shield Android TV Q&A, Help & Troubleshooting] skymera:
Not tested, just an educated guess.

Doubt I'll root as for me, there's no benefit just yet.
[Shield Android TV Q&A, Help & Troubleshooting] kyrusdemnati:
yeh i know its not out yet, 6.0 but it would make life easier as you can use external drive more efficiently

i don't mind having to download the nvidia 6.0 rom file and loading it that way, if the process isn't complicated...
[Nexus 6P Q&A, Help & Troubleshooting] musclegym:
I got my Nexus for four days and every day for no apparent reason I get no network. The network card is new and still used a week on my Nexus 4 without ever having happened this.

I have everything stock
[Nexus 6P Q&A, Help & Troubleshooting] .vermilion:
Have you checked your APNs in settings? For me there wasn't any APN "built-in" and selected, so I had to manually set one with the provider data.
[Nexus 6P Q&A, Help & Troubleshooting] musclegym:
Everything ok with apns
[MTCB Android Head Units General] dazza007:
Hi

A while back I thought I toasted my motherboard using the 7floor mod. I managed to get the board up and running. I ordered a replacement from HK and it has now arrived.

Now looking at the new motherboard there is a different radio chip TDA7388 which is mounted in the rear (no chip on the original board). Do you know if this chip would have improved reception as the older boards radio reception is poor with a chip TEF6686, lock does not work too :(

Here are the photos.

View attachment 3567907

View attachment 3567906

thanks
[MTCB Android Head Units General] peti007:
This is the amplifier IC, not the radio!
[MTCB Android Head Units General] nFKT:
I have great reception with the TEF6686
[MTCB Android Head Units General] mike.s:
The best is the Placebo brand chip.
[MTCB Android Head Units General] coromonadalix:
your tunner is the metalized cage box at the left dont go there it wont work ... tried that
[General Questions and Answers] droid_god:
Hi guys

So the thing started as this.

I have a samaung galaxy core 2 running kitkat 4.4.2

I wanted to develope a custom rom for it.

And for that i have to decompile many apps and do some modding and recompile them again.

I am using apktool vesion 4.1

At first i installed the main framework-res.apk into the apktool and set the default folder correctly.

I decompiled systemui.apk without any error.

And just removed 6 lines from the layout/signal cluster.xml

And not apktool shows error in compiling the app

So my problem is how can i get rid of the error.

I: Smaling...

I: Building resources...

Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [/data/data/per.pqy.apktool/lix/aapt, p, --min-sdk-version, 19, --target-sdk-version, 19, -F, /data/data/per.pqy.apktool/APKTOOL5220112300896973543.tmp, -0, arsc, -I, ?/apktool/framework/1.apk, -S, /sdcard/apktool/SystemUI_src/res, -M, /sdcard/apktool/SystemUI_src/AndroidManifest.xml]

at brut.androlib.Androlib.buildResourcesFull(Androlib.java:358)

at brut.androlib.Androlib.buildResources(Androlib.java:283)

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

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

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

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

Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [/data/data/per.pqy.apktool/lix/aapt, p, --min-sdk-version, 19, --target-sdk-version, 19, -F, /data/data/per.pqy.apktool/APKTOOL5220112300896973543.tmp, -0, arsc, -I, ?/apktool/framework/1.apk, -S, /sdcard/apktool/SystemUI_src/res, -M, /sdcard/apktool/SystemUI_src/AndroidManifest.xml]

at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:357)

at brut.androlib.Androlib.buildResourcesFull(Androlib.java:336)

... 5 more

Caused by: brut.common.BrutException: could not exec command: [/data/data/per.pqy.apktool/lix/aapt, p, --min-sdk-version, 19, --target-sdk-version, 19, -F, /data/data/per.pqy.apktool/APKTOOL5220112300896973543.tmp, -0, arsc, -I, ?/apktool/framework/1.apk, -S, /sdcard/apktool/SystemUI_src/res, -M, /sdcard/apktool/SystemUI_src/AndroidManifest.xml]

at brut.util.OS.exec(OS.java:93)

at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:355)

... 6 more

Caused by: java.io.IOException: Cannot run program "/data/data/per.pqy.apktool/lix/aapt": error=13, Permission denied

at java.lang.ProcessBuilder.start(ProcessBuilder.java:1042)

at java.lang.Runtime.exec(Runtime.java:615)

at java.lang.Runtime.exec(Runtime.java:483)

at brut.util.OS.exec(OS.java:84)

... 7 more

Caused by: java.io.IOException: error=13, Permission denied

at java.lang.UNIXProcess.forkAndExec(Native Method)

at java.lang.UNIXProcess.<init>(UNIXProcess.java:135)

at java.lang.ProcessImpl.start(ProcessImpl.java:130)

at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023)

... 10 more

And if my version is wrong recommend me a correct one

Help will be appriciated. Thankyou
[General Questions and Answers] droid_god:
Plz anybody solve my problem
[Samsung Gear S2] spinman:
Hell, i've got a problem with my Gear S2.

I had a Galaxy Note 2 (Android 4.4.1) with the option to automatically lock the smartphone when the gear is too far and it was right.

Il bought a Galaxy Note 4 (Android 5.1) and set the watch on it, but on the Note 4 I can't find the parameter to lock the smartphone. I tried to uninstall / reinstall Gear Manager but I still cant' find it.

Does anyone can help me ?

Thanks

(Sorry for my english ;-] )
[Samsung Gear S2] ffarber:
I think in the newer versions of Android the autolock feature has been replaced with SmartLock which will automatically unlock the phone when the device of interest (in this case the S2) is in range. However, it will not automatically lock the watch when the device is out of range. The phone will lock with whatever settings you have in your Security.

Fred
[Samsung Gear S2] spinman:
Thanks a lot Fred, I think you're right !!

It's the difference between Android 4.4 and Android 5.1.

I've just activate the function and i will test it now but it seems to be what i need.

Thanks again
[8525, TyTN, MDA Vario II, JasJam ROM Development] debonairone:
Oh Sh!!T... I just changed the bbsecurity service to manual from automatic, now I cannot get back into my TyTn... does anyone have a quick fix other than HR... I've tried SR several times, but that didn't work... I can connect via ActiveSync, I just need to start the BBSecurity service, then I can input my password (theoretically anyways) and should be fine... I used Memmaid to make this change... Just another example of using advanced tools without knowing the ramifications....

:eek:

I guess i should have asked for more clarification first...

I almost hijacked someone else's thread, so had to start my own.... Mods, I apologize in advance...

originating thread is here
[8525, TyTN, MDA Vario II, JasJam ROM Development] debonairone:
Never mind, I bit the bullet and HR... now for my next trick...
[Android Q&A, Help & Troubleshooting] taimoor0070:
dear n respected developers hw r u all? hope u r all set

can any 1 knw how to install custom rom on gfive Glory A86???

i recently install cwm based touch recovery but i dnt knw how to find stable n correct rom for my mobile i knw i'm big noob

Model Name :

Gifive Glory A86

Android Version :

4.0.4

Basedband Version :

MAUI.11AMD.W12.22.SP.V5,2012/07/25

20:13

Kernal Version :

3.0.13 USER@LINUX-USER#1

SMP PREEMPT MON APR 22 10:40:57 CST 2013

BUILD NUMBER :

GFIVE GLORY(A86) 20130422-104156

this is my phone specs plz if any 1 knw how to install custom rom then plz tell me

Thanks
[E 2015 General] wogeboy:
Got my 2 moto E LTE's up and running with T-Mobile. (mote e Verizon lte)

I used the Debloater program to disable the Verizon sim card warning.

Would like to know what other apps you all have debloated/frozen/disabled etc.. thru the debloater program

Thanks
[E 2015 General] Sands207:
Can you link us to this debloater program so it might help others?
[E 2015 General] wogeboy:
http://xdaforums.com/android/software/debloater-remove-carrier-bloat-t2998294
[Verizon LG G4] raidflex:
Anyone else having issues with wireless charging since the 13B update? I do not if it is just coincidence or not but both my wife's and my G4 refuse to charge through wireless. This problem seemed to begin after both phone's were updated to 13B. The light on the charging pads does not even come on. In the case of my G4, I have actually wiped the phone after the 13B update and still encounter the issue.
[Verizon LG G4] DarkWolf747:
You should check to make sure it's not that the sticker on the back has stopped making contact with the wireless charging pads... All of mine have consistently stopped working after awhile because of that, however, if I take the sticker off and press it to the contacts physically it still works.

Although after fighting it for weeks I've given up on wireless charging for this phone. :(
[Verizon LG G4] raidflex:
Hardware issue is a possibility but, I have two LG G4's here that both stopped working at the same time. I experience the issue on multiple charging pads also. This was right after both phone were updated to 13b.
[Verizon LG G4] jhanson:
I'm on 13b and my wireless charging works as well as it ever did, which isn't spectacular. I'd say 1/10 times I wake up and its not charged. I even bought the official flip cover case with qi as I originally blamed my sticker back application skills.... but both work equally crappily....
[Verizon LG G4] dcorrea:
Wireless charging on my 13B is rock solid. FWIW this is the wireless charger I use: http://www.amazon.com/Wireless-Yoot...9605910&sr=8-3&keywords=lg+g4+yootech+charger

As long as I ensure that it is steady green on the charging light by properly aligning the phone to the pad, I have never had an issue with it not charging properly.
[Verizon LG G4] raidflex:
I am not sure why I am still having issues. I did a battery pull on both phone and they started charging. But now half the time neither phone charges or I will wake up with the phone only partially charged. I just find it really hard to believe that both phones are having issues with two different chargers at the same time and that it happened right after I updated to 13b.

This is the charger I am using: http://www.amazon.com/gp/product/B00JA7HNZO?psc=1&redirect=true&ref_=oh_aui_detailpage_o03_s00
[Verizon LG G4] dcorrea:
OK stupid question but does it charge regularly? Maybe you have battery issues.
[Verizon LG G4] raidflex:
If I plug either phone in using the same cable that goes to the charging pad I have no issues.
[Verizon LG G4] dcorrea:
Thats what I figured, but had to ask. Have you tried charging it with the phone off? Could be the new software requires a greater amperage than before so charging with the phone on could cause issues. I know your charger comes with its own USB cable but what about the actual wall wort? Are you using the standard LG wort? Im just drawing at straws, but hopefully something gets your issue fixed. Other than that I guess at this point, since you already tried different chargers you could see if replacing the Qi sticker in the phone has any effect.
[Verizon LG G4] raidflex:
I will try tonight charging with the phone off, and I do use the wall plug that came with the phone. Thanks for the help.
[Verizon LG G4] rudyo78427:
The LG G4 doesn't support wireless charging unless the NFC sticker on the back cover is changed out for one that is NFC/Qi charging capable. Look at the NFC sticker on the inside of the back cover. If it only has one section of the sticker with two metal pads, then it's only NFC capable. There should be two sections / arms with two metal pads on the sticker. one for NFC and the other for wireless charging. You can buy a new pad online for $10. My Verizon LG G4 didn't come with the wireless sticker , only the NFC one. See the picture for details of the NFC/Wireless charging sticker. :good:
[Verizon LG G4] raidflex:
I bought a new sticker that had both NFC and QI, and it was charging without a problem for a couple months. Now mine does not work at all and my wife's G4 only works sometimes.
[G2 Q&A, Help & Troubleshooting] mubashiriqbal55:
I have lg g2 ls 980 with cloudy v 3.3 installed my data connection working properly but my call and sms nt working i flashed stock rom but still giving problem....in status bar giving emergency call only...
[G2 Q&A, Help & Troubleshooting] amin44:
Try another modem
[Shield Android TV Q&A, Help & Troubleshooting] koftheworld:
Good morning all,

I wondering if someone has a solution to this. My official gamepad won't turn off when I put my system to sleep using it. I am on the latest shield TV firmware and I have tried forgetting and repairing the game pad. This problem started after I updated I believe. I am not rooted or unlocked btw.
[Shield Android TV Q&A, Help & Troubleshooting] garbagerich:
Mine has been doing this too.