yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] brizey:
Yep, no point in paying off 0%.

We just moved from VZW. My wife was an employee once upon a time (got swept up when Frontier bought a bunch of the landline business). We still got the discount, but now we pay less than we did on VZW even with the discount. We are not heavy data users, so we just have the new family plans with 1 GB each LTE. I'm using my VZW S4 (everything works...mostly Band 4 LTE around here so I am good to go). She got a new iBend 6 :rolleyes:, mostly for the better keyboard case options once the accessories get rolling (she is coming from a Droid 4). We pay $80 for the service.

(About that 1 GB: we have guest wifi at work and I use OpenVPN. There just is not that much time that I am away from wifi, and when I am, I'm busy doing something, not dorking around on my phone. I'm a middle aged dad...no music streaming, watch movies on a real TV with real surround sound, and play games where God intended: on a PC.)
[T-Mobile Samsung Galaxy S 4] Android_Monsters:
55 x 2 = s4 and s2

Unlimited everything

Get throttled by the end of the month, though.
[T-Mobile Samsung Galaxy S 4] ShinySide:
And their throttle suckkkkssssss. I hit it almost every month for the last 3-7 days before my bill is due. I can get Google search results via snail mail faster than on their throttle haha
[T-Mobile Samsung Galaxy S 4] Sanadrate:
same $30 plan here
[ONE Q&A, Help & Troubleshooting] cutiedoggy:
As above..sometimes my wifi can't be turned on once i switched it off..and i have to reboot my phone for it to work again..isit cause of the new update? :crying:
[ONE Q&A, Help & Troubleshooting] kenfb1:
Hi

Hi,

Similar issue. The WiFi doesn't auto connect to wherever I may go.

It used to auto connect to previous WiFi that I connected to and entered passwords

when needed. If I'm connected and then go outside for a while and come it won't

reconnect. I have read a slight trick. I turn Airplane mode on then off and then it

will reconnect. Any ideas on this. Seems to have happened lately after 33r update,

Ken
[ONE Q&A, Help & Troubleshooting] tech virus:
jus flash stock rom...you guys wil be okay :)
[Android Q&A, Help & Troubleshooting] DanillaTech:
Hello! Sorry me English, I'm Russian.

I tired of android structure: A lot of .* folder, a lot of program's rabbish. It's bad for PC, but in phone with little screen it's much more worse.

So, I have an indea, how can we fix it.

The first move is mv all of folder like books, downloads etc to !books, !downloads!

Then, we need to mkdir books, downloads etc

The we should mount -o bind !books to books - we need to do it on a startup

Somebody say that you can just rename folder and sune some program, but it's veeery boring.

As for me, I can not realize that because I am noob and have some glitches with my computer, phone... So, can anybody make this?

My script did not work, i tried make it different, but it was nothing

#!/system/bin/sh

mkdir huu

busybox mv /mnt/sdcard/hu /mnt/sdcard/huui

mv /mnt/sdcard/Books /mnt/sdcard/!Books

mv /mnt/sdcard/Download /mnt/sdcard/!DownLoad

mv /mnt/sdcard/Music /mnt/sdcard/!Music

mv /mnt/sdcard/Movies /mnt/sdcard/!Movies

mv /mnt/sdcard/Pictures /sdcard/!Pictures

mv /	mnt/sdcard/DCIM /mnt/sdcard/!DCIM

I tried cd /mnt/sdcard but it said me that folder's is not exist, even if I make it with y hands!

For mount folder I tried something like

#!/system/bin/sh

mount -o bind /mnt/sdcard/!Books /mnt/sdcard/Books

I hope that you will help me, and I beelive it helps to many people improve efficiency of android using.
[Galaxy S 5 Q&A, Help & Troubleshooting] jtl_777:
Hey guys, I have a Galaxy S5 that I'm 99% sure is fake. I have uploaded some screenshots of the system and hardware info. Can anyone tell if it's definitely fake? If so, would it be safe to use? I factory reset it to clear any apps or anything that might leak personal information but I don't know if that's enough. I was thinking that the manufacturers of fake phones could hide malicious code deep into the system that could potentially leak my personal information like my email address and password and other passwords I enter online.In the case that they do intend to get my personal info I have a VPN service I pay for, so would connecting to the VPN before doing anything online keep them from being able to get information or could they still have a keylogger that logs my keystrokes and what windows are up when I enter them? Are there any roms I could download for it? Also I tried to boot into download mode like my old S3 and it went to a mode that was all in Korean (or Chinese or whatever). So I mean I pretty much know it's fake :silly: Is there any reason I should be worried? I am also having network issues. I have tried many different APN settings (it's unlocked and I have T-Mobile) but I cannot get anything more than a very poor edge connection. Any ideas?

***As you can see it only has 1GB of internal memory lolololololol
[Galaxy S 5 Q&A, Help & Troubleshooting] gee2012:
You can be sure for a 100% thats is fake. Yes you should be worried, if there is an issue with your device in the future you won`t have warranty and 0% afterservice, so you`re pretty much on your own and may have to buy another phone.

PS: Don`t flash anything fom the S5 forum or you`ll brick your phone.
[Galaxy S 5 Q&A, Help & Troubleshooting] vndnguyen:
Install Phone INFO ★Samsung★ app, open Menu > 'Refurbishment Check'. It will tell you exactly if your phone is genuine or a fake one.
[Galaxy S 5 Q&A, Help & Troubleshooting] jtl_777:
I'm not concerned with the warranty. I actually haven't bought it yet but my friend did and she didn't know it was fake. I would buy it for 50 bucks if I can get 4g to work so what would you guys say? I'm doing some investigating to see if it's safe to use with my gmail and other accounts. What would be the best way to ensure that my information doesn't get sent out? I rooted it last night and found a couple forums for fake samsung phone roms but some of the numbers didn't add up. Thanks for your help.
[Galaxy S 5 Q&A, Help & Troubleshooting] KenPhotsawi:
If it is fake then you shouldn't use it. Your information and passwords may leak and there's a possibility that the device may explode.
[Fire TV Android Development] roligov:
Awesome! Thanks so much for your hard work Rbox :good: :highfive:

Edit:

Installed without issues. Remote not working as expected so I switched to the K400 and works 100% :) Great work, donated $10 for your efforts!
[Fire TV Android Development] AFTVnews.com:
Here are some guides with step by step instructions:

How to install ClockworkMod Custom Recovery on the Amazon Fire TV

http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/

How to update ClockworkMod Custom Recovery on the Amazon Fire TV

http://www.aftvnews.com/how-to-update-clockworkmod-custom-recovery-on-the-amazon-fire-tv/

How to remotely control ClockworkMod on the Amazon Fire TV using ADB

http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/

How to install a Custom ROM Image on the Amazon Fire TV

http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/

How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root

http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/

How to Revert back to Stock Recovery and Stock Software

http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
[Fire TV Android Development] Luxferro:
Should adb sideload work over tcpip rather than just usb?

If so it doesn't work for me; soon as it's toggled in recovery the firetv isn't accessable over adb tcpip anymore.
[Fire TV Android Development] rbox:
I never tested it. The problem with sideload is I believe it restarts the adb daemon. I'll see if I can figure out what's wrong with it.

Update: So I just tested it and looked in to the code. It looks like when recovery starts, it uses the full adbd. But when you go to do a sideload, it switches to the internal version called minadbd. minadbd only supports USB. So for the next version I will add in network support.
[Fire TV Android Development] AFTVnews.com:
Any way to use CWM to make a backup when there isn't enough free internal memory for the backup files? Like backing up to a mounted USB drive or network location.
[Fire TV Android Development] rbox:
If you have a USB drive plugged in before it starts, it *should* see it. I haven't tested it in a while but it was working at one point. But like I said, I was having problems getting it to work with a hub with a flash drive and a keyboard. I suppose if you created a commands file that told it to backup to the external storage and reboot afterwards, it wouldn't need a keyboard plugged in. If you can't get your USB drive to work, I'll figure out the commands file.
[Fire TV Android Development] CLran619:
nice job :) i thought before summer ended we would have a recovery. i cant wait for a ROM for the FTV . fingers crossed. also can i use firmware version 51.1.0.1 instead of 51.1.0.2? id rather not "update" if it isn't necessary and im guessing the difference between the two makes no difference.

edit: dosent matter i upgraded and installed. recovery working just fine. thank u rbox.
[Fire TV Android Development] alex1301:
I don't have the fire TV yet and I don't know anything about the software of this thing, but wouldn't it be easier if we can boot into fastboot? With that every firmware version could be flashed. There was a fastboot cable for the fire tablet. Can't we build something like this for the fire tv?
[Fire TV Android Development] rbox:
Yes, it would be easier. And a fastboot cable for the Fire TV is just a plain USB A to A cable. But the bootloader is locked and prevents one from using fastboot boot and fastboot flash.
[Fire TV Android Development] alex1301:
Alright, I hate it when they lock the bootloader so deep that we can't unlock it :D
[Fire TV Android Development] Kramar111:
No :(

Can you upload "stock_recovery.img"? I didn't downgrade to 51.1.0.2 :silly:
[Fire TV Android Development] rbox:
I ask one simple thing. That people follow the directions. Is that so hard to do?

http://www.mediafire.com/download/6q1c96y5tcc4xgc/recovery-stock-51.1.0.img
[Fire TV Android Development] collindv:
I am wondering the same thing as I am still on 51.1.0.1 as well.
[Fire TV Android Development] rbox:
I just updated the post to reflect that you only need to downgrade if you are on 51.1.1.0.
[Fire TV Android Development] rbox:
I was able to get sideload over network working, so that will be included in my next update. Thanks!
[Fire TV Android Development] jocala:
Anyone know a way of determining firmware revision from the command line?
[Fire TV Android Development] rbox:
grep fingerprint /system/build.prop
[Fire TV Android Development] AFTVnews.com:
Is there anyway to boot into ClockworkMod recovery other than via the "adb reboot recovery" command? I'm guessing the Alt+PrintScreen trick would take you there, yes? Any other ways?
[Fire TV Android Development] rbox:
None. You can't just slap a kernel on it and call it a day. It has to be compiled for the Fire TV with something based off the Amazon kernel.
[Fire TV Android Development] Y314K:
Thanks for the update....

Was wondering if another update would be needed to be able to directly do backups in CWM to an EXT4 external storage when using the following script ??? Or is it a mount issue ??

CWM Flashable: Mount external USB storage to /data and /sdcard
[Fire TV Android Development] rbox:
You would do the standard backup to usbdisk. Although I don't know if it work with ext4.
[Fire TV Android Development] Y314K:
Asking because of this post over at the scripts thread.

If I remember correctly phones do let you backup to ext4 SD cards if I am not mistaken. How much space does a backup take on a stock FireTV vs a loaded FireTV ?
[Fire TV Android Development] rbox:
Well I don't know how it reacts to multiple partitions... I think it'll see the first, and try to use it and fail. I could probably just fix it so it works with ext4 to begin with...
[Fire TV Android Development] Y314K:
I guess that guy was trying something extra with the split HDD. Specially since the EXT4 needs to be primary. But yeah, would really appreciate if CWM was fully compatible with that script aka EXT4 since it seems like the best option we have to an expansion of storage that acts as much as the original system storage.

This is what the FireTV script is based on in case you need more insights on how it works or how it would interact with CWM: http://xdaforums.com/showthread.php?t=1716124
[Fire TV Android Development] rbox:
I'll play around with an ext4 partition and see what's up.
[Fire TV Android Development] rotor00ter:
Being able to use the EXT4 partition for back-up instead of having to use a dual-partition with Fat32 would suit my needs as well. The only reason I wanted to have a Fat32 partition was so I could use cwm recovery to back-up and recover my system, but it didn't work with my drive that had an EXT4 partition. I also couldn't get it to work plugging a second Fat32 formatted drive into my usb hub either. Seems like the system will only recognize one drive. If rbox could get the recovery to work with EXT4 then only one good size drive would be needed for everything. Just my opinion, I have no idea how feasible it is but I think this would help alot of people get this finally set-up the way they want it.

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------

Appreciated, and I just threw a little donation your way to help with the cause.
[Fire TV Android Development] rbox:
I think originally when people started trying to use NTFS i may have put in something to only allow fat32. I think if I switch it back to auto it should probably be fine. Either way, I should be able to get it to work some how. I only have limited time this week and am going on vacation this weekend, so it might not be until next week. I'll see if I can squeeze it in on Wed.

Thanks for the donation!
[Fire TV Android Development] Y314K:
Sounds good. Maybe Auto + a NTFS exclusion. Not sure how that works. But I bet folks will always try to stick NTFS in there. Thanks a again & have a great week. I know how a pre-vacation week can get very hectic.
[Fire TV Android Development] rbox:
So it looks like it's currently set to auto. I'm going to have to debug vold and figure out why it's rejecting the partition.
[Fire TV Android Development] Y314K:
Maybe rotor00ter should try with a full EXT4 formatted drive to see if that makes a difference. Or are you testing the script on your end?

I just rooted my 3rd FireTV I just got in the mail from Staples. Everything went fine like with my first two but this time the latest CWM gave me a scare. I didn't realize it was part of the new kernel flashing option until I started typing this...

Now CWM fills my whole screen. I did not have to do anything. Looks great now. Using the same pre-rooted .zip I had used on my first 2 FireTV's 513011820. I sideloaded the .zip to /SDCard/0/Downloads with v25 of one of the apps. When into install from zip and found the zip and told it to install.

Bug 1 - This time when the install was running. Andy the robots guts that graphically tell you it's doing something where above Andy instead of in his belly. That is just a graphical bug so no biggie. I call it drunk Andy.

NON-Bug 2 - Towards the end of the FW install I got the following message in red letters right under "Installing update...". The message was "Amazon Kernel detected: not patching". Then it said "Install from sdcard complete.". At first took this to mean there had been a error/problem flashing the FW. I still rebooted back into the FireTV. It told me it was updating & when done it seems everything went as plan. Also I was able to update the remote just like before too.

Now that I've typed this out I've realized it's not a bug but just part of the new Kernel flashing. Not sure red is a good color for it since usually red means FAIL/ERROR/PROBLEM instead of informing of a patching bypass.

Keep up the good work... Guess the only thru bug was Bug #1 :fingers-crossed:

Got pics of drunk Andy if you need it...
[Fire TV Android Development] rbox:
It's red for two reasons. One, I didn't think blue looked good. For two, it's important that it stands out so you read it. As for a pic, that would be good.
[Fire TV Android Development] Y314K:
Humn.. Myabe bolder or bigger & Purple or Violet. :D

Added Drunk Andy's pic...

Was wondering if you could help with this...

http://xdaforums.com/showpost.php?p=56177690&postcount=46
[Fire TV Android Development] rbox:
Unfortunately it's one size fits all for the font. But I will play around with different colors. As for the other question... The apks are all in /system, but their data is in /data. So if they access /data a lot, it will be slow. It depends on what the ultimate goal is. If it's just to make /sdcard bigger, then that would be fine. Or if you don't care about apps and their internal storage. I would suggest he try mounting it at /data/media if all you care about is /sdcard.
[Fire TV Android Development] Y314K:
Thanks, will let him know. For me the most important thing is stopping the FireTV's low memory problem usually caused by XBMC & being able to install a good amount of other apps without making the device slow as molasses...
[Fire TV Android Development] rotor00ter:
I tried this evening with a 1TB drive formatted only as EXT4 and it didn't recognize it. Sounds like rbox has a handle on whats happening and some ideas to get it working. His recovery with factory restore has already saved me a few times when trying out new things and having issues. I'm sure if there is a way to do it he'll figure it out and if not its not the end of the world. I might actually get some time to enjoy this box rather than always messing around with it.:silly:
[Fire TV Android Development] jmandawg:
rbox have you successfully compiled a kernel? If so which toolchain/version did you use? Thanks.

edit: nevermind 4.6 seems to work, but they are missing one file so far:

In file included from sound/soc/msm/qdsp6/q6adm.c:21:0:

arch/arm/mach-msm/include/mach/qdsp6v2/audio_dev_ctl.h:15:36: fatal error: mach/qdsp6v2/audio_def.h: No such file or directory

edit: got uImage to build. before I go any futher is there any way to get into CWM when my boot fails?
[Fire TV Android Development] to0:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/

Looks like you hit Alt + PrtSc + i repeatedly as you turn it on to get into recovery.
[Fire TV Android Development] rbox:
Unfortunately no.

That method only works if the kernel actually boots. If it's bricked, that won't do anything. What that does is it kills all running processes and restarts init. After doing it a few times, the kernel says "screw this" and reboots into recovery. If the kernel doesn't boot, there is nothing listening to that key press. I am fairly confident there is some way to make it boot straight in to recovery from the bootloader, but have not been able to figure it out.

As for something to do to prevent bricking... the easiest thing to do really, is to flash recovery onto the boot partition. And flash your test kernels on to the recovery partition. That way when booted into recovery, you can do adb reboot recovery, and it'll reboot into your kernel. And if your kernel doesn't work, power cycling the box will make it boot back in to recovery.

It is extremely important to know that if you do wind up flashing a bad kernel on to boot, I really know of NO WAY to get back to recovery. So the safest is to do what I described above. Additionally, a uImage won't work. You need an android kernel with the ANDROID! header on top. I build my kernels with the AOSP build system, that generates the boot.img correctly.

I want to create a sticky thread for this. I also am working on some ideas with kexec and a boot menu like safestrap uses on some (all?) devices, to make it a little easier to test kernels.
[Fire TV Android Development] to0:
Is there an option inside of CWM to choose the destination partition when flashing? Or can you just do it from adb, even though the bootloader is locked?
[Fire TV Android Development] rbox:
You make an update.zip that copies the kernel to whatever partition you want.
[Fire TV Android Development] jmandawg:
Sounds risky. I might give it a go later, or if your bored i can send you the boot.img and you can give it a whirl.

And just to be sure, you are saying if i do:

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

dd if=/sdcard/myBoot.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

reboot recovery

It should boot to my boot.img? and booting normal should boot to recovery?

or do i have to flash recovery to boot partition in CWM since it has to be signed. And can flash kernel to recovery partition in shell or ADB?

Have you actually done this?
[Fire TV Android Development] rbox:
I've done the swapping, but you have to be careful. The problem is your kernel won't be signed so it wont boot it, and recovery will only fix something flashed to the boot partition. I'll have to come up with a better process. What you could try, even though it's going to be awful:

Make an update.zip that flashes your kernel to the boot partition.

Boot in to recovery and flash that update.zip

Before rebooting, use adb shell in recovery and dd from boot to recovery.

Then dd recovery.img onto boot.

It's extremely important to not reboot before you've dd'd recovery onto boot. I think maybe the easiest is going to be if I make some kind of boot menu. But this will let you limp along until then.
[Fire TV Android Development] jmandawg:
This doesn't sound right.. Afte step 2, my boot.img is flashed to boot partition, step 3 copies my boot partition (containing my boot.img) to recovery [At this point both partitions contain my boot.img) and step 4 copies recovery(which is now contains my boot.img) back to boot? You sure this isn't a brick recipe?
[Fire TV Android Development] rbox:
Oh sorry, I wasn't explicit. I meant to dd the recovery.img file, not the partition. I edited the original post incase someone looks at it later.
[Fire TV Android Development] jmandawg:
ok, thanks. i'll probably just wait until we have a full proof way to get into recovery. I'm sure I will eventually screw something up doing it this way and end up with a brick.
[Fire TV Android Development] rbox:
Probably a good idea. I've gotten close to bricking mine a few times.
[Fire TV Android Development] jmandawg:
Can you make a build that patches when flashed to recovery partition
[Fire TV Android Development] rbox:
I've got something better coming soon. :)
[Fire TV Android Development] jmandawg:
Cool can't wait.

---------- Post added at 07:27 PM ---------- Previous post was at 07:17 PM ----------

Any way you could also mount usb as ext4?
[Fire TV Android Development] rbox:
That is on my list of things to add.
[Fire TV Android Development] bovoro:
i think i bricked mine, i had the first version 51.1.0_user_510047320 and make flash recovery from Amazon Fire Tv utility App , and then automatically reboot and stuck on amazon white logo. sometimes on colored logo.
[Fire TV Android Development] Y314K:
Where you trying to downgrade to install CWM. Working with someone with the same problem will see if it helps. You can follow it here: http://xdaforums.com/showthread.php?t=2796067&page=10 .
[Fire TV Android Development] bovoro:
Thank you man, I've reading the usefull thread that you share
[Fire TV Android Development] sajid44:
Need help

I had CWM recovery and pre rooted latest firmware installed.

Somehow XBMC stopped working so I went into CWM recovery and foolishly wipe data and format system.

Now when I restart, it is stuck at white amazon screen. It does not even go to colorful firetv screen.

Cannot connect via adb, tried alt, prnt scrn + I but nothing happened.

Please help if it is still possible to debrick.
[Fire TV Android Development] jmandawg:
If you formatted system, i don't know what you can do. I thought if you still had /boot up you could get into recovery. Did you format /boot too?