yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Po5tHuMaN:
Hi everyone,

the reason I'm starting this thread is because after two days of trying to solve my issue by reading threads and trying various things, I'm still stuck. The scenario is this, my Kindle Fire HD is stuck at teamwin screen and I cannot access TWRP. I have no idea if this is soft-bricked or corrupted or whatever. What happens when I switch on the tablet is that I get the orange Kindle Fire logo, then the blue Kindle Fire logo and then teamwin screen which flashes every 5 seconds and is stuck there.

During this process, the Device Manager from Windows 8.1 successfully recognizes the tablet as 'Android Composite ADB Interface'

If I start CMD as Admin mode and key in 'adb kill-server' and then 'adb devices' I can see the device listed as '0123456789ABCDEF recovery'

Another issue is that when I go into 'adb shell', all the commands I type, I get '/sbin/sh: command not found'. I also tried 'KindleUnbrickV1.1.jar', but every option I select I get <waiting for device> and stays like that. I left it overnight.

I also tried Kindle Fire Utility, but was unsuccessful as well.

At this point I don't think there's anything else I could do and I guess it's time to say goodbye to my little fella. At least managed to finish univ with it.

If anyone has some opinions or suggestion, you're more than welcome to do so and they will be highly appreciated. By the way, I don't have any important data on the tablet so it's ok if I need to format it without taking backups.

Kind regards,

/pH-
[Android Q&A, Help & Troubleshooting] tleaf100:
hi folks,I cannot be the only person on xda with this problem,which is,how to search through 4000 apps in MY APPS that I want to keep listed but would like to be able to find the one I want/need in less than a week.

any ideas/advice ?

I would prefer an app that can use different filters,like age,device etc etc.

I presume google refuse access to apps/software that would make this possible,its ridiculous that I have to install a seperate app to find the apps I have paid for,or muck about in a browser at my google account history to even do that simple task.

have looked for years and still not found a tool for searching my apps,and google do not appear to want to make it possible.
[Android Q&A, Help & Troubleshooting] Telyx:
I just use the search function in Google Play Store.
[Shield Android TV General] Steel01:
I finally got a response from Gnurou about this and it seems very promising.

One note is that his staging/nouveau branch doesn't have the DTS, but his staging/work branch does. I'm going to assume that's what he meant.

Unfortunately, like he mentioned, this isn't upstream yet. And apparently there's some discussion on how to implement the new platform in the upstream kernel. Guess for now that means we stick with Gnurou's forked kernel until that gets sorted out.

There's one major problem that needs solved (and I won't be able to actively debug and test it for a couple days). There's no known way to pass the bootloader a different dtb. My first thought is to use this patch temporarily to allow appending the dtb to the image. Now like the first reply to the patch states, this is a horrible idea, but it should at least get the device booting. Once I get multirom working, I can load in a new dtb before kexec which will be much cleaner. That doesn't help anyone that wants to fastboot boot, though. Anyone have any ideas on that?

When I'm able to run new builds and start testing this, I'll post more info. Just wanted to get this out there for other interested who might get it done first.
[Shield Android TV General] Gnurou:
You are correct, staging/work is the branch you should use for any upstream-based X1 work. staging/nouveau is my staging area for Nouveau-related patches. staging/work is the same branch merged with the latest -next and many staging Tegra-related patches (including decent X1 support) from the Tegra maintainer (tagr). These patches will make it upstream eventually, but it will take some time.

So yeah, staging/work is actually a linux-next with extra X1 support patches + a few other staging patches of mine, I know this sounds scary but we are careful to keep it in a decent shape. :)

Does bootloader unlocking/fastboot boot work as expected? I haven't been able to check so far.

Regarding device tree: it seems like Android and the bootloader use the same device tree, which is convenient but has the undesired side-effect that if you replace the DTB partition with an upstream DT, the bootloader doesn't work anymore and if you try to boot upstream with the Android device tree, you will have lots of features missing (if it boots at all).

That's something that really ought to be fixed in a future OTA. Can you state the problem precisely and what you think would be a good way to work it around? I can think of using a separate DT for Android, or maybe a way to embed the device tree in the boot image (although the boot image format doesn't seem to allows that?).

I will try to get my hands on a retail device so I can experiment with it myself as well, but not sure when that could happen.
[Shield Android TV General] Steel01:
Well, I tried to boot a kernel to no avail, just a black screen. I reverted:

https://github.com/Gnurou/linux/commit/61bd93ce801bb6df36eda257a9d2d16c02863cdd

and applied (not cleanly, one chunk had to be manually patched):

http://lkml.iu.edu/hypermail/linux/kernel/1506.0/03053.html

Nothing. I used an old bbfs from Roth testing. But I didn't spend too much time on it, so it might be as simple as early printk not being on and the kernel was trying to tell me I'm stupid, but couldn't.

Bootloader requests? Well first, the command line support needs fixed. I was working on porting CM and added the disable selinux kernel cmdline flag like I did for the Portable and Tablet and it got completely ignored. That's embedded in the boot image, haven't tried fastboot -c.

So, when I saw the question on how to handle dtbs, I had what I thought was a crazy idea, but turns out I wasn't the first.

http://www.cnx-software.com/2014/05...device-tree-file-from-android-firmware-files/

Hijack the second boot section of the boot image and stuff the dtb in there.

The precise problem is that the bootloader doesn't support swapping dtbs. And worse as you stated, the bootloader won't work unless an android dtb is on the dtb partition. (Incidentally, that partition just got added to my list of never touch partitions on my Shield devices...)

Oh, and yes, fastboot oem unlock and boot work as expected. As does flash and erase. It justctakes the next half of forever to erase the pros user data partition.

I finally had a breakthrough on CM, so I may not have as much time to tinker with this over the next couple days as I expected. But I'll try to get a basic bb booting as soon as I can. It just might drive me up a wall to stare at a black screen with no way to know what's wrong first...
[Shield Android TV General] Steel01:
[MENTION=2826079]Gnurou[/MENTION]: Any progress on the inside on this? Fastboot is even worse in the latest release. Can't bring it up via a hardware method (have to 'reboot bootloader' to get to it) and fastboot boot is completely broken, just hangs the system when passing it anything, official or not). So doing more testing on the consumer side is much more difficult. Especially since I still haven't figured out how to get kexec/multirom working still...
[Shield Android TV General] Gnurou:
Hi! I still need to put my hands on a Shield device to be honest. I have been making progress on the GPU front though, to a point where acceleration is now starting to work with upstream to a point where it should be soon possible to use X.

Thanks for pinging me though, I will ask for a Shield retail device and see by myself what needs to be done.
[Android Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Tool] New tool for Unpack and Repack MTK boot.img

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Tool] New tool for Unpack and Repack MTK boot.img. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] GeorZ:
Compatibility ??

Can this tool be used for boot.img of any type

Pls specify compatible boards,eg. Mt65XX or MT65YY and also the android versions compatible
[Nexus 6 Q&A, Help & Troubleshooting] upstate240sx:
I'm trying to unlock my nexus 6 from AT&T. I tried cellunlocker.net however they don't have a code for me :( I'm somewhat reluctant to try another site. I tried installing a t-mobile baseband for the nexus 6 (after reading the sim lock was part of the baseband) no luck. Is there anything else I can do aside from contact AT&T for the unlock code.
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
A couple of questions:

Is the N6 paid off?

Are you still on AT&T?

If yes to the above, has device been in use on AT&T for more than 45 days?
[Nexus 6 Q&A, Help & Troubleshooting] upstate240sx:
The N6 is not yet paid off, I don't mind paying it off however It was a part of a family plan in which there are other devices not paid off. The ATT unlock code request page cites that the accounts must not have a past due balance. Even just entering the imei into the web form page to begin submitting the request says that it does not recognize the imei to even submit the request... Seems strange to me
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
AT&T will not issue a SIM unlock code until the device is paid off. You might be able to get one from a 3rd party, but I'm not sure.
[Nexus 6 Q&A, Help & Troubleshooting] upstate240sx:
i tried cellunlocker.net ....they didnt have a code. Is there anyone out there more reputable?

Dave
[Nexus 6 Q&A, Help & Troubleshooting] upstate240sx:
will installing a t-mobile nexus 6 rom work? is there anything i can do in terms of rooting the phone?
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
No, it won't carrier unlock your phone. The only way is with the unlock code.
[Nexus 6 Q&A, Help & Troubleshooting] upstate240sx:
and everyone code is phone specific? I cant just format whatever part of memory that contains the sim lock function...?
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
No, you can not. Code is device specific.
[Nexus 6 Q&A, Help & Troubleshooting] majormar:
DON'T use cellunlocker.net. It took them about 4 days to come up with a code that didn't work. After being forced to upload several videos of me trying the unlock code and proving that my phone wasn't rooted or running a custom ROM, they still refused to issue a refund claiming my phone was modified. It's been 17 days and they still can't come up with a working code. Avoid them like the plague!

I have heard swiftunlocks might be better.
[Nexus 6 Q&A, Help & Troubleshooting] quicksilver53:
I have gotten unlock codes from sellers on eBay with success on other devices.

---------- Post added at 11:34 PM ---------- Previous post was at 11:32 PM ----------

I just checked on eBay and there is a seller selling at/t unlocked codes.
[AT&T LG G4] Tomyk89:
Hey guys,

Big thanks to [MENTION=2684188]autoprime[/MENTION] for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.

If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.

If System Update is constantly bugging you to update, follow the directions below:

1) Enable USB Debugging

-Go to About phone and tap on Build number 10 times to enable Dev Options

-Enter Developer Options and enable USB Debugging

2) Download and Install the Debloater tool (this happens on your computer)

-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe

-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg

3) Connect your phone via USB. Make sure to install any drivers needed

4) Watch for pop up requesting ADB Access on your phone

5) Launch the Debloater tool

6) Select OK on the popup

7) Click the top left button

8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top

Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
[AT&T LG G4] kindofabuzz:
I just got the G4 yesterday. I didn't do my homework first and did the updates. Am I screwed when it comes time to root? (If ever)
[AT&T LG G4] creaky:
Delete
[AT&T LG G4] BobEvatt:
I just went into Settings/Apps/Google Services Framework and unselected Show Notifications. This took the warning out of the Notification Bar.

Not certain yet in the event that it will keep the popup for the framework OTA overhaul.
[AT&T LG G4] GvIn2it:
Deleted
[AT&T LG G4] Slowfrost:
I saw on a website that there were other things listed in addition to what you blocked to avoid OTA updates. Should these be taken into consideration?

LGUpdateCenter.apk

LGFOTA.apk

LGLDB.apk

EDIT: I used that debloater tool and disabled that stuff. I've had no problems with the phone after that except for the AT&T bloatware.
[Networking] fatblokes:
hi, i have unlocked my 700tv and managed to set up mms for orange but i can setup gprs, can anyone help?

thanks
[Networking] Rudegar:
do a search in this forum(being Networking) for "orange AND gprs"
[Networking] drsqueggy:
go on orange.co.uk. look for a phone with a similar os! or just any phone! the settings are the same. they have a full guide to most phones they sell (the htc universal guide is good!)
[G4 Q&A, Help & Troubleshooting] Tomyk89:
Hey guys,

Big thanks to [MENTION=2684188]autoprime[/MENTION] for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.

If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.

If System Update is constantly bugging you to update, follow the directions below:

1) Enable USB Debugging

-Go to About phone and tap on Build number 10 times to enable Dev Options

-Enter Developer Options and enable USB Debugging

2) Download and Install the Debloater tool (this happens on your computer)

-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe

-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg

3) Connect your phone via USB. Make sure to install any drivers needed

4) Watch for pop up requesting ADB Access on your phone

5) Launch the Debloater tool

6) Select OK on the popup

7) Click the top left button

8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top

Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
[Sprint LG G4] Tomyk89:
Hey guys,

Big thanks to [MENTION=2684188]autoprime[/MENTION] for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.

If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.

If System Update is constantly bugging you to update, follow the directions below:

1) Enable USB Debugging

-Go to About phone and tap on Build number 10 times to enable Dev Options

-Enter Developer Options and enable USB Debugging

2) Download and Install the Debloater tool (this happens on your computer)

-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe

-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg

3) Connect your phone via USB. Make sure to install any drivers needed

4) Watch for pop up requesting ADB Access on your phone

5) Launch the Debloater tool

6) Select OK on the popup

7) Click the top left button

8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top

Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!

**A couple people are still getting updates after performing this. Please check here for more things you can try.
[Sprint LG G4] kangta05:
Great i took mine 10 minutes ago and just saw this.. oh well guess Im stuck with no root options
[Sprint LG G4] Tomyk89:
I'm optimistic that the devs will be able to release a root method that will still work for those who took the update. I would still run the above process so that it doesn't receive any more updates.
[Sprint LG G4] andypiznti:
to add to this, once i did this (I blocked 6 apps in total, instructions from a different post) and once i reset my phone, i still got the notification to update (I dont think it would work if i ran it, but i didnt try), so i long pressed the notification, hit the the little circle with the letter i in it, then disabled notifications from google play services. havent seen it since and im still on ZV4. also before i installed debloater i installed the LG united drivers, not sure i needed to but figured id mention it.

edit: this was the post i originally used. http://xdaforums.com/g4/help/how-to-prevent-updates-g4-t3148650
[T-Mobile LG G4] Tomyk89:
Hey guys,

Big thanks to [MENTION=2684188]autoprime[/MENTION] for mentioning this info on this in the general G4 forum. Figured I'd sum up the steps and repost in our sub-forum for anybody who may be struggling.

If you're like me, you're waiting on root and don't want to accidentally take that new OTA update that was pushed out about a week ago. This OTA has been found to prevent rolling back to previous versions of android, and may also block some/many of the root methods that the developers are preparing to release to us.

If System Update is constantly bugging you to update, follow the directions below:

1) Enable USB Debugging

-Go to About phone and tap on Build number 10 times to enable Dev Options

-Enter Developer Options and enable USB Debugging

2) Download and Install the Debloater tool (this happens on your computer)

-Windows http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater-setup-v3.85.exe

-OSX http://rootjunkysdl.com/getdownload.php?file=Gates/DeBloater/Debloater.v.3.85.dmg

3) Connect your phone via USB. Make sure to install any drivers needed

4) Watch for pop up requesting ADB Access on your phone

5) Launch the Debloater tool

6) Select OK on the popup

7) Click the top left button

8) Find LGDMSClient.apk and put a checkmark next to it. Then select Apply at the top

Congratulations! You no longer have to worry about pocket-updating your G4 and not being able to root down the road!
[T-Mobile LG G4] Ryslegit:
I just ran this and it doesn't show LGDMSClient.apk.....weird
[G Pad 8.3 General] player911:
I picked up the new X8.3 GPad from Verizon during the Verizon G4 promo launch.

Is this a special unique Verizon model because I figured it would be launching on other carriers or something? It has been a month and there are only a few threads on this.

It just seems like it is a super nice tablet that is flying under the radar. It has a new SnapDragon 615 processor, nice screen, stylus, full sized USB, IR Blaster. It is just getting no love.
[G Pad 8.3 General] roirraW "edor" ehT:
The VK810 was the only carrier model too, and only for Verizon just like the VK815. The other variants of the VK810 are WIFI only and aren't associated with any particular carrier. I have no idea if there'll be other variants of the X8.3 or not.

Support for the VK810 is just barely there, but with the help of several devs I'm happy we have at least the amount of support we do. Since the VK810 and 815 are carrier-specific, it's natural that as many people won't get this tablet because only those with Verizon will get it, whereas the WIFI only ones get bought by everyone else.
[XDA Assist] sudhabhootra:
Motorola Moto G (2nd Gen) boot loop issue.?

I have a Motorola Moto G (2nd Gen) running on Android L 5.0.2 Stock ROM. Bootloader is unlocked and I have rooted it.

Yesterday I wet my phone in water and the device turned off in a while. Later I discovered it has gone into an infinite bootloop. The device was starting with the message "boot loader unlocked" (which is usually shown when I reboot my device generally) and turning off before anything else appeared. The phone restarted again and again and again until the battery drained. I need a solution for this issuer and getting my data back would be great.

Thankyou.
[XDA Assist] Razvan:
Hi there,

You'd be best served asking for help from the experts who own your device, here:

Moto G (2014) Help and Troubleshooting

Good luck
[Xperia SP Q&A, Help & Troubleshooting] Phoenix854:
I was on CM12.1 earlier this morning. Suddenly I realised that my earpiece is not working while on calls. Neither did the screen turned black in effect of proximity sensor while on call. So I right away flashed stock to check whether its a hardware or software issue.

Digging more into the problem I could make out that its not the earpiece that is damaged but its the phone that thinks the headphone is still connected. I used an app called SoundAbout to check the media output. And it was confirmed that headphones is used for media output. Then I checked playing a song, it didnt through loudspeaker which also confirms that phone is detecting the headphone is plugged in while it is not.

Below I upload the screenshot of that app called SoundAbout which I used to find the problem. Sorry for such a long post.

Any help, suggestion, or any strange or extraordinary experience that could help?

Any help is appreciated!!!!!!!!!!!
[Xperia SP Q&A, Help & Troubleshooting] somberchocks:
Well if you are using SoundAbout why don't you then select where you want the sound to come out from? Isn't that the whole point of that app?

Also dunno about your proximity sensor issue but my phone suffers from similar ear piece issues as well and the issue crops up sporadically so I am still not sure sure its completely a hardware issue. I spent months looking for a solution but was finally about to hand it in for repairs when I the came upon the strangest solution somewhere. Here's what I do when this happens -

Plug my headphones in

Make a call

When you can hear anything in the headphones (call being connected, recipient's voice...heck just dial a non existent no. so you can hear the operator say it doesnt exist, any sound at all) , pull the headphones out and the sound comes out the earpiece.

I know it sounds silly but it works for me. It might not work the first time but after a couple of tries, it always does. Till date the only workaround I have found to this issue albeit a temporary one. Lasts me a few weeks before it happens again. Rinse and repeat.

One of these days I am gonna bite the bullet and hand it in for repairs. Remember reading someplace that this could be because some chip or something that supposed to switch sound depending on the task fails to do so though I am talking from memory here and this might be completely inaccurate.