Database Users

Possible to run Tetherbot on an RC-30 G1?

My G1 is two days old so came from the shop (T-Mobile, UK) with Android RC-30 already on. I've been trying to use it as a modem for my laptop on public transport (without success).
So far I have Tetherbot installed and the Socks service started on 1080, Android SDK is installed on the lappy (Ubuntu 8.04 LTS) and 'adb forward tcp:1080 tcp:1080) creates a port to which I can telnet to (and terminate from by pressing return). FF is configured to use a manual proxy on localhost:1080..
Also set the about:config network.proxy.socks_remote_dns flag to true.
All good, except when I enter any URL into FF, the status bar immediately shows 'Done' yet there's no rendering being done at all - still looking at a blank screen.
I've yet to try FoxyProxy which I'll give a go tonight - but I was wondering if it is currently possible to configure a instance of RC-30 w/o root access at all? Reading around, some people say it is while others say it isn't..
Many thanks,
Duncan

Definitely works in ota RC30. Snippet from the Tetherbot thread:
Make sure that you set FoxyProxy to use SOCKS for DNS lookups(under Global Settings)...this stumped me too at first
Click to expand...
Click to collapse

Thanks! Web-browsing now works with FoxyProxy although I have to keep re-entering the ./adb forward tcp:1080 tcp:1080 command every few minutes..
Setting up the port-bouncer for ssh on 22 was less successful though, as it usually causes the Tetherbot application to crash.
Any ideas why T-Mobile wouldn't want you to use the phone as a modem anyway? Having come from an O2/Xda package I'd just expected that all modern phones would work as modems. Shame about the root lock-down too, I was half hoping for a meaningful bash shell and porting/installing Gnu utils, etc.
I guess the G1 would have the same data problems even if it were paired with a tablet like the N-800?
Many thanks,
Duncan

dsmith1974 said:
Any ideas why T-Mobile wouldn't want you to use the phone as a modem anyway? Having come from an O2/Xda package I'd just expected that all modern phones would work as modems.
Click to expand...
Click to collapse
My guess is it has to do with anticipated network usage. I don't know how tethering works with data plans in the UK, but generally in the US unlimited data is divided into handset-only and full unlimited (e.g. for pc cards). Not only is data usage generally lower for mobile applications, you're also highly limited by battery life.
Shame about the root lock-down too, I was half hoping for a meaningful bash shell and porting/installing Gnu utils, etc.
Click to expand...
Click to collapse
A lot of people were hoping for that. The G1 isn't that device though. Full unencumbered shell access would just be a nightmare from a customer service POV. The G1 is first and foremost a consumer device. A lot of those people could end up easily and irreversibly bricking their phones from a root shell.

Yeah i hear that, thats why i really dont care if i have root access. I'm sure in time all that we are wishing for will come out for g1, dont wanna ruin my phone!!! All i really want is internet sharing on mine.

A lot of people were hoping for that. The G1 isn't that device though. Full unencumbered shell access would just be a nightmare from a customer service POV.
Click to expand...
Click to collapse
It has nothing to do with customer service, but T-Mobile's desire to retain control over things. They probably don't want people to do internet sharing, because it will slow down their network. What they don't realize, is that soon there are going to be a lot of unlocked android phones available which wont be subject to their policies.
What I don't get is that with any other HTC device you can boot the phone into SPL mode and flash a new image. With the G1, that is not possible.

Datruesurfer said:
It has nothing to do with customer service, but T-Mobile's desire to retain control over things. They probably don't want people to do internet sharing, because it will slow down their network. What they don't realize, is that soon there are going to be a lot of unlocked android phones available which wont be subject to their policies.
What I don't get is that with any other HTC device you can boot the phone into SPL mode and flash a new image. With the G1, that is not possible.
Click to expand...
Click to collapse
Your speculations are incorrect. T-Mobile stated that they will not stop or block internet sharing, but they will not help you either. Basically they remain neutral and that is why you think T-Mobile is against you.
Google blocked the usb mode image flash. So far we just don't know how to flash a new image because we are not sure if it is supposed to be DREA100.IMG or what is even in the image itself.
Back on topic, I think you will see a real solution when Android 1.0 is released. Or at least have a way to get full root. Basically from what has been said root was locked down not because of anything we did but because the source is not open yet. They are working on things behind the scenes and they need to finish those before they want us to fool around. Give them time to finish their projects and then they will let us start our own.

Datruesurfer said:
It has nothing to do with customer service, but T-Mobile's desire to retain control over things. They probably don't want people to do internet sharing, because it will slow down their network. What they don't realize, is that soon there are going to be a lot of unlocked android phones available which wont be subject to their policies.
Click to expand...
Click to collapse
It's funny you should make that statement in a thread about tethering on OTA RC30. Almost like you didn't know what the heck you were talking about...

neoobs said:
Your speculations are incorrect. T-Mobile stated that they will not stop or block internet sharing, but they will not help you either. Basically they remain neutral and that is why you think T-Mobile is against you.
Google blocked the usb mode image flash. So far we just don't know how to flash a new image because we are not sure if it is supposed to be DREA100.IMG or what is even in the image itself.
Back on topic, I think you will see a real solution when Android 1.0 is released. Or at least have a way to get full root. Basically from what has been said root was locked down not because of anything we did but because the source is not open yet. They are working on things behind the scenes and they need to finish those before they want us to fool around. Give them time to finish their projects and then they will let us start our own.
Click to expand...
Click to collapse
A few things...
1. The source code has already been published (minus a few hardware specific drivers) at source.android.com. You can build an image from source and boot it on the emulator that Google has packaged with the android sdk. There still is no way to load said image on a G1 unless you have root of course.
2. Google didn't lock down SPL on the dream, HTC did. And it was probably because T-Mobile didn't want people loading their own firmware on a device that is already running on open source software.
3. Ever since this root nonsense has come to light, I don't buy the whole neutrality thing. If everyone had root access, we would have a much easier way to tether.
@jashu: I know exactly what I'm talking about because I tried doing the same thing on my friends G1 with the official RC30 firmware on it.

Datruesurfer said:
A few things...
1. The source code has already been published (minus a few hardware specific drivers) at source.android.com. You can build an image from source and boot it on the emulator that Google has packaged with the android sdk. There still is no way to load said image on a G1 unless you have root of course.
2. Google didn't lock down SPL on the dream, HTC did. And it was probably because T-Mobile didn't want people loading their own firmware on a device that is already running on open source software.
3. Ever since this root nonsense has come to light, I don't buy the whole neutrality thing. If everyone had root access, we would have a much easier way to tether.
@jashu: I know exactly what I'm talking about because I tried doing the same thing on my friends G1 with the official RC30 firmware on it.
Click to expand...
Click to collapse
1. Google hasn't released the entire source code, even they have said that officially on the android site.
2. Google asked HTC to do that.
3. Google is the one that locked down root not T-Mobile. Again this goes back to them not having 1.0 released.

Datruesurfer said:
@jashu: I know exactly what I'm talking about because I tried doing the same thing on my friends G1 with the official RC30 firmware on it.
Click to expand...
Click to collapse
Not only does this convince me you don't know what you're talking about, it also leads me to believe you don't know what you're doing either. Just because you can't figure out the simple instructions to perform socks-based tethering when everyone else already has doesn't mean it is broken.
neoobs said:
3. Google is the one that locked down root not T-Mobile. Again this goes back to them not having 1.0 released.
Click to expand...
Click to collapse
Android was 1.0 at the launch of G1. See the official release notes.
Thread is going off topic.

jashsu said:
Android was 1.0 at the launch of G1. See the official release notes.
Thread is going off topic.
Click to expand...
Click to collapse
it is 1.0 RC30... meaning it is still beta. Not released yet.
This thread should have been closed quite some time ago.

Just fine on OTA RC30, Vista. I had to use Proxifier as I prefer Chrome to Firefox, but it works just fine. ADB crashes on very high performance downloads, but otherwise its fine.

rc-30 ?? i think not
dsmith1974 said:
My G1 is two days old so came from the shop (T-Mobile, UK) with Android RC-30 already on. I've been trying to use it as a modem for my laptop on public transport (without success).
So far I have Tetherbot installed and the Socks service started on 1080, Android SDK is installed on the lappy (Ubuntu 8.04 LTS) and 'adb forward tcp:1080 tcp:1080) creates a port to which I can telnet to (and terminate from by pressing return). FF is configured to use a manual proxy on localhost:1080..
Also set the about:config network.proxy.socks_remote_dns flag to true.
All good, except when I enter any URL into FF, the status bar immediately shows 'Done' yet there's no rendering being done at all - still looking at a blank screen.
I'v
e yet to try FoxyProxy which I'll give a go tonight - but I was wondering if it is currently possible to configure a instance of RC-30 w/o root access at all? Reading around, some people say it is while others say it isn't..
Many thanks,
Duncan
Click to expand...
Click to collapse
Duncan, I think you should have another look at what device you have, tmouk devices came out with rc-7 and an ota put them upto 8, so before you start askin questions get your facts right. Also it wasn't tmobile alone that blocked the device being used as a modem it was a joint effort between htc google and tm to promote the use of the open source to its full potential. It also doesn't breach any fair use using the hset as a modem which if it 'wasnt' allowed then you would be breaching the fair use. Ta

jashsu said:
Definitely works in ota RC30. Snippet from the Tetherbot thread:
Click to expand...
Click to collapse
Thanks this helped me a lot.

HOWTO: Using Whatsapp on Kindle Fire (Jelly Bean/SGT7)

I'm using twa_priv's Jelly Bean ROM with SGT7 enhancements on my (first-generation) Kindle Fire, and wanted to install and use WhatsApp on this device.
Not having an Android phone, I found that the instructions here worked well: use Bluestacks on my PC to help get the needed code to install and start up WhatsApp. But when I actually tried to enter a chat on WhatsApp, the application kept crashing.
After seeing that someone else was having the same problem, and looking through the logcat.txt, I figured out that the crash has something to do with a bitmap/image operation in WhatsApp. That led me to a workaround, and now I can use WhatsApp on my Kindle Fire running CM10.
The relevant setting is found in Settings -> Chat preferences -> Wallpaper. I simply set it to "No wallpaper" (it's the conversation, not the background, that matters to me!). But I found it also works if I choose an image somewhere in my filesystem ("Android System"); selecting "WhatsApp" prompts me to download the WhatsApp Wallpaper package, which I don't really care to do. Just don't set it to "Default" -- that's what leads to the app crashing.
This workaround works using WhatsApp Messenger 2.8.4930. Hope this helps others!

Update for WhatsApp 2.9.2871
With the latest version of WhatsApp as of this writing (2.9.2871) running on twa_priv's version of the CM10.1 port, I no longer have to set the chat wallpaper to "No wallpaper" to avoid a crash when entering chats. I'm not sure whether it's because of a fix in CM10.1 or in WhatsApp, but that's one less workaround needed. Hurray!

ezekiel_quacks said:
With the latest version of WhatsApp as of this writing (2.9.2871) running on twa_priv's version of the CM10.1 port, I no longer have to set the chat wallpaper to "No wallpaper" to avoid a crash when entering chats. I'm not sure whether it's because of a fix in CM10.1 or in WhatsApp, but that's one less workaround needed. Hurray!
Click to expand...
Click to collapse
I have recently bought a kindle fire and was hoping to use whatsapp on it. I was pleased to find the recent messages re this, however I am a middle-aged grandmother and I'm sorry but they may just as well be written in an alien language from another planet! Is there any way instructions can be given to me that I could easily follow? Thank you for any help.

you can use Whatsapp if you are willing to use a custom ROM...
mario's mum said:
I have recently bought a kindle fire and was hoping to use whatsapp on it. I was pleased to find the recent messages re this, however I am a middle-aged grandmother and I'm sorry but they may just as well be written in an alien language from another planet! Is there any way instructions can be given to me that I could easily follow? Thank you for any help.
Click to expand...
Click to collapse
Before I attempt to do so, I'd have to first ask some preliminary questions:
1. Which version of the Kindle Fire are you using? My instructions were based on my experiences on the first generation Kindle Fire, so if you have something different, then I'm not 100% sure this will work for you.
2. Are you running the default software/firmware for the Kindle Fire?
3. If so, are you willing to install a custom firmware (like the various kinds being discussed on these forums), or would you prefer to stick with the default firmware? Installing a custom firmware ("flashing a custom ROM") is not for the technologically faint of heart, even though it's in practical terms not that difficult.
I'm not sure if my instructions will work with the default ("stock") firmware on any version of the Kindle Fire. But depending on your answers, I might still be able to offer some pointers...

ezekiel_quacks said:
Before I attempt to do so, I'd have to first ask some preliminary questions:
1. Which version of the Kindle Fire are you using? My instructions were based on my experiences on the first generation Kindle Fire, so if you have something different, then I'm not 100% sure this will work for you.
2. Are you running the default software/firmware for the Kindle Fire?
3. If so, are you willing to install a custom firmware (like the various kinds being discussed on these forums), or would you prefer to stick with the default firmware? Installing a custom firmware ("flashing a custom ROM") is not for the technologically faint of heart, even though it's in practical terms not that difficult.
I'm not sure if my instructions will work with the default ("stock") firmware on any version of the Kindle Fire. But depending on your answers, I might still be able to offer some pointers...
Click to expand...
Click to collapse
Thank you,
1. How can I find this out? I've looked on the box and the two small leaflets that came with it and all I can see is Model Number D01400? I have literally just bought it.
2. I presume I am running the default/firmware as I haven't made any changes or downloaded anything - would you agree?
3. I'm willing to give anything a go - as long as I can understand what I am supposed to be doing and also as long as it is not going to cause any lasting damage.
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!

mario's mum said:
Thank you,
1. How can I find this out? I've looked on the box and the two small leaflets that came with it and all I can see is Model Number D01400? I have literally just bought it.
2. I presume I am running the default/firmware as I haven't made any changes or downloaded anything - would you agree?
3. I'm willing to give anything a go - as long as I can understand what I am supposed to be doing and also as long as it is not going to cause any lasting damage.
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!
Click to expand...
Click to collapse
Swipe down from the top of the screen. And press more, from there go to the device section, What does the software version say?

read the beginner's guide first
mario's mum said:
Actually I think I should not have bought the kindle and what I wanted was an android tablet - my mistake. But if by installing anything you suggest this would enable me to download Whatsapp - and any other app that Amazon does not seem to allow - then I would be happy. Is this what may be achieved?
Thanks again, sorry I'm not good at all this technical stuff!
Click to expand...
Click to collapse
Well, let me be the first to say that I admire your courage, at least! :good: You need to understand, though, that you probably have to do more than just install some app -- this is more like completely replacing the operating system (e.g., Windows) on your PC with another one (e.g., MacOS X). If you make it through these minefields, you'll effectively have a pretty fully functional Android tablet, but it's generally more for the technically minded (i.e., geeks) to attempt and maintain.
Maybe a good first step would be for you to go here and read through a Beginner's Guide: http://forum.xda-developers.com/showthread.php?t=1552547. If that's too intimidating, then you probably won't be able to get to the point where I can help you install Whatsapp on your Kindle Fire.

ezekiel_quacks said:
Well, let me be the first to say that I admire your courage, at least! :good: You need to understand, though, that you probably have to do more than just install some app -- this is more like completely replacing the operating system (e.g., Windows) on your PC with another one (e.g., MacOS X). If you make it through these minefields, you'll effectively have a pretty fully functional Android tablet, but it's generally more for the technically minded (i.e., geeks) to attempt and maintain.
Maybe a good first step would be for you to go here and read through a Beginner's Guide: http://forum.xda-developers.com/showthread.php?t=1552547. If that's too intimidating, then you probably won't be able to get to the point where I can help you install Whatsapp on your Kindle Fire.
Click to expand...
Click to collapse
Hello again, thanks for that - but after reading what you've said I don't think my courage extends that far! Anyway, not just so I can Whatsapp when I've got it on my phone. I'm hoping I'll get used to the kindle in time - while I save up for what I really wanted in the first place!
Thanks again.

might be just as well...
mario's mum said:
Hello again, thanks for that - but after reading what you've said I don't think my courage extends that far! Anyway, not just so I can Whatsapp when I've got it on my phone. I'm hoping I'll get used to the kindle in time - while I save up for what I really wanted in the first place!
Click to expand...
Click to collapse
You may find that the Kindle Fire, other than its awkward launcher, may fit the bill just fine as you get used to it. Try browsing the Amazon App Store, and you will probably find most of the apps you'd regularly use on a generic Android tablet. As for Whatsapp, you can't really run it with the same account on more than one device at the same time anyway, so it might be just as well that you only use it on your phone. :cyclops:

ezekiel_quacks said:
You may find that the Kindle Fire, other than its awkward launcher, may fit the bill just fine as you get used to it. Try browsing the Amazon App Store, and you will probably find most of the apps you'd regularly use on a generic Android tablet. As for Whatsapp, you can't really run it with the same account on more than one device at the same time anyway, so it might be just as well that you only use it on your phone. :cyclops:
Click to expand...
Click to collapse
Oh that's made me feel a bit better about the Whatsapp!, and you're right I am getting used to it. Thanks for your advice.

Aplogies for bumping an old thread
I have a rooted Kindle Fire (first generation).
I would like to install WhatsApp Messenger on it. I don't have a CUSTOM-ROM. This is rooted without any customizations.
Is there something I can do, to get this started? Any pointers in the right direction are appreciated.

Well, it's been over a year since my original post, and I no longer run Whatsapp on my Kindle Fire now, so I can't be sure what works now. But I'd suggest you follow the links in the first post on this thread for starters, and see if that gets you anywhere.

Fire TV software update 5.2.1.0 is now rolling out!

Amazon has released yesterday a New software update 5.2.1.0, for all the FireTV units:
http://www.aftvnews.com/fire-tv-software-update-5-2-1-0-is-now-rolling-out/
Some FireTV users, are already complaining that some APPs like "HBO GO/HBO NOW" (if you have Kodi/SPMC installed), "Mouse-Toggle 1.04", "Wukong Remote 1.9.0EN" and "Firestopper" now do not work at all...
Fo Realz, has mentioned on www.aftvnews.com, that after the update he can’t use "HBO NOW", unless he uninstall Kodi... Because he always get the following message:
“For security reasons the following apps must be uninstalled to use this app: Kodi”
Luckily, KODI and SPMC are still working flawlessly!!
Others users, have noticed that it looks like Amazon has changed the FireOS Font, that now it looks a bit like “Trebuchet”... And that the Remote-Control, the Wifi-Direct version, got a new update too…
It is not known yet whether this 5.2.1.0 update is Rootable or not!
Someone who has received this 5.2.1.0 update, has noticed something new or any improvements?

I just got the update yesterday as well. Netflix doesn't load properly anymore, gets stuck at 99%. Amazon videos don't play they load the video and I just see like a screenshot of the video and it doesn't play. I've lost all audio. Tried resetting, clearing cache, data, reinstalling Netflix etc.

ulises.rodriguez said:
Amazon has released yesterday a New software update 5.2.1.0, for all the FireTV units:
http://www.aftvnews.com/fire-tv-software-update-5-2-1-0-is-now-rolling-out/
Some FireTV users, are already complaining that some APPs like "HBO GO/HBO NOW" (if you have Kodi/SPMC installed), "Mouse-Toggle 1.04", "Wukong Remote 1.9.0EN" and "Firestopper" now do not work at all...
Fo Realz, has mentioned on www.aftvnews.com, that after the update he can’t use "HBO NOW", unless he uninstall Kodi... Because he always get the following message:
“For security reasons the following apps must be uninstalled to use this app: Kodi”
Luckily, KODI and SPMC are still working flawlessly!!
Others users, have noticed that it looks like Amazon has changed the FireOS Font, that now it looks a bit like “Trebuchet”... And that the Remote-Control, the Wifi-Direct version, got a new update too…
It is not known yet whether this 5.2.1.0 update is Rootable or not!
Someone who has received this 5.2.1.0 update, has noticed something new or any improvements?
Click to expand...
Click to collapse
Did you get a chance to grab the URL for this? I can start tearing apart the update to see what changed.

I'm very sceptical about the comment on my site claiming that HBO Now won't work with Kodi installed. I have not received the update myself yet, but a reader I trust has received the 5.2.1.0 update on his Fire TV 1 and says he can launch HBO Now with Kodi installed and with Kodi running in the background. He does not have an HBO Now subscription, so it's possible the message only appears when you try to play content, but he said he does not receive a message when launching the app and going to the login screen.

Wukong Mouse mode is dead on Firestick after latest OS update
Xfinity TV does not allow clicking after the update. Mouse mode is DOA. Maybe something to do with the prompt that comes up stating . "You don't have a controller" when you bring up the TVGo app. BTW I have not 'rooted' my FireStick.

Surprised you took it seriously in the first place. Obvious troll is obvious.
There's also a comment that ADBFire doesn't work. Not believing that either.
AFTVnews.com said:
I'm very sceptical about the comment on my site claiming that HBO Now won't work with Kodi installed. I have not received the update myself yet, but a reader I trust has received the 5.2.1.0 update on his Fire TV 1 and says he can launch HBO Now with Kodi installed and with Kodi running in the background. He does not have an HBO Now subscription, so it's possible the message only appears when you try to play content, but he said he does not receive a message when launching the app and going to the login screen.
Click to expand...
Click to collapse

Claude Koch said:
Surprised you took it seriously in the first place. Obvious troll is obvious.
There's also a comment that ADBFire doesn't work. Not believing that either.
Click to expand...
Click to collapse
Well you never know. When the first couple comments started rolling in that 5.0.5.1 was removing FireStarter, my initial reaction was to assume it was a troll. I'm not going to go posting about something based on a comment or two, but I've learned my lesson to not dismiss anything entirely.

I'm curious... In theory, if I were to repack/recompile the Kodi APK into a different name and then installed on my Fire TV, would I survive an Amazon Kodi block if it were to happen? Is it really that simple to avoid a software block?

AFTVnews.com said:
Well you never know. When the first couple comments started rolling in that 5.0.5.1 was removing FireStarter, my initial reaction was to assume it was a troll. I'm not going to go posting about something based on a comment or two, but I've learned my lesson to not dismiss anything entirely.
Click to expand...
Click to collapse
Elias, I understand your point of view and that is precipitated taken as certain some news only based on one or two comments... But, there are many users complaining about Adb-Fire problems (that not allows applications sideloading anymore) and also problems with the Mouse-Toggle1.04 and Wukong-Remote1.9.0EN APPs, that Amazon might have changed something in this new 5.2.1.0 update.
Maybe as you already said in aftvnews.com, the issues trying to run HBO-GO or HBO-Now, with Kodi installed or running, could be "a troll comment meant to stir up concern with a false statement", however I am very worried because I'm starting to see more complaints about Netflix and Amazon Video, that are not working well after installing this update:
1 - When I watch a movie with Netflix, it don't load completely and gets stuck on 99%.
With Amazon-Videos, movie loads, but the video does not play, and does not have audio"
2 - "I am having amazon issues, and Netflix Issues stuck 99% and no audio"
3 - “Netflix doesn’t load properly anymore, gets stuck at 99%.
Amazon videos don’t play they load the video and I just see like a screenshot of the video and it doesn’t play.
I’ve lost all audio”
Since I still have not received this new 5.2.1.0 update, I would appreciate if you could contact some users who have received it, to ask if they have experienced these strange behaviors with Netflix/Amazon-Videos, and to also confirm issues with adbfire and the sideload of apps.
Thank you Elias, for your Excellent comments, your Great AFTVnews site and always help with all our requests!!

ulises.rodriguez said:
... But, there are many users complaining about Adb-Fire problems
Click to expand...
Click to collapse
adbFire worked for me on 5.2.1.0

trek70000 said:
I'm curious... In theory, if I were to repack/recompile the Kodi APK into a different name and then installed on my Fire TV, would I survive an Amazon Kodi block if it were to happen? Is it really that simple to avoid a software block?
Click to expand...
Click to collapse
Yes, currently Amazon is only blacklisting apps by package name. FireStarter and FiredTV are the only two apps on the list as of the 5.0.5.1 updated. I haven't received the 5.2.1.0 update yet, so I don't know if the list has changed, but several people have said Kodi installs/runs fine on 5.2.1.0
---------- Post added at 11:13 AM ---------- Previous post was at 11:09 AM ----------
ulises.rodriguez said:
Elias, I understand your point of view and that is precipitated taken as certain some news only based on one or two comments... But, there are many users complaining about Adb-Fire problems (that not allows applications sideloading anymore) and also problems with the Mouse-Toggle1.04 and Wukong-Remote1.9.0EN APPs, that Amazon might have changed something in this new 5.2.1.0 update.
Maybe as you already said in aftvnews.com, the issues trying to run HBO-GO or HBO-Now, with Kodi installed or running, could be "a troll comment meant to stir up concern with a false statement", however I am very worried because I'm starting to see more complaints about Netflix and Amazon Video, that are not working well after installing this update:
1 - When I watch a movie with Netflix, it don't load completely and gets stuck on 99%.
With Amazon-Videos, movie loads, but the video does not play, and does not have audio"
2 - "I am having amazon issues, and Netflix Issues stuck 99% and no audio"
3 - “Netflix doesn’t load properly anymore, gets stuck at 99%.
Amazon videos don’t play they load the video and I just see like a screenshot of the video and it doesn’t play.
I’ve lost all audio”
Since I still have not received this new 5.2.1.0 update, I would appreciate if you could contact some users who have received it, to ask if they have experienced these strange behaviors with Netflix/Amazon-Videos, and to also confirm issues with adbfire and the sideload of apps.
Thank you Elias, for your Excellent comments, your Great AFTVnews site and always help with all our requests!!
Click to expand...
Click to collapse
It's very tedious and slow to check/verify update changes by contacting people who have already received the update. I just keep a list of all the issues I've heard about and check them myself once I receive the update. I'd rather be a few days late with postings than be inaccurate because information is being relayed to me.

AFTVnews.com said:
Yes, currently Amazon is only blacklisting apps by package name. FireStarter and FiredTV are the only two apps on the list as of the 5.0.5.1 updated. I haven't received the 5.2.1.0 update yet, so I don't know if the list has changed, but several people have said Kodi installs/runs fine on 5.2.1.0
---------- Post added at 11:13 AM ---------- Previous post was at 11:09 AM ----------
It's very tedious and slow to check/verify update changes by contacting people who have already received the update. I just keep a list of all the issues I've heard about and check them myself once I receive the update. I'd rather be a few days late with postings than be inaccurate because information is being relayed to me.
Click to expand...
Click to collapse
I totally agree, it is very tedious and time consuming too, trying to contact users who already have received this 5.2.1.0.update.
I meant to get in contact with only known and trusted users, that have received the new update, as you already did with the user who confirmed that he had not received any safety message launching HBO-NOW, with Kodi installed or running.
However, maybe you're right, it is better to keep a list of all problems reported and once you receive the update, check to see if they are true or not...
I really hope that in a couple of days after receiving this update, you will have the time to write a full review in AFTVnews.com, about the negative things and also the new features of this 5.2.1.0 update.

Deleted post

I'm from Germany and I received the 5.2.1.0 update on my Fire TV Generation 1. After this Update the aftvnews.com Update blocking methode 2 isn't working anymore. No Feedback from adb when I send the command. My 2nd device, a Fire Stick hasn't got the update to 5.2.1.0, and there the blocking Methode works I think, because adb shows a Feedback after sending the command.
Gesendet von meinem E6653 mit Tapatalk

harlekinade said:
@aftvnews: Just as a small critique (well - thats how it started out, anyways... ) - when people looked at you in the past to provide context, this is what they got as first responses in return.
Click to expand...
Click to collapse
First off, thank you for posting this long and detailed criticism. Feedback, even negative feedback, is always welcome. I'll respond inline.
- When Firestarter first stopped working - it was pronounced by you "probably just an incompatibility issue".
Click to expand...
Click to collapse
I did not say "probably." I said "one theory is." There's a distinct difference. At that point nobody knew why FireStarter wasn't working yet. I hadn't even received the software update yet (which I pointed out), but thought people would like to know sooner rather than later that the update was causing some unknown issue with FireStarter. I'd love to have weeks with an update to fully dissect it before posting anything about it, but by then it would be too late for many people to avoid the update if they suddenly want to.
- When Amazon started blacklisting apps and banning Firestarter you first repeated the same notion, then celebrated Amazon for providing "their own launcher" and therefore "making it easier for most people". And only afterwarts wrote about the issues it created, also for the company itself (reputation damage).
Click to expand...
Click to collapse
The first thing I wrote about the 5.0.5.1 update was that sideloaded apps were added to the home screen and there was a quicker way to get to apps. That's what Amazon told us about the update so that's what I reported. Nobody had any idea apps were blacklisted at that point. I didn't first write about app banning and "then celebrate Amazon" like you say.
- When people asked you why to root Fire TVs, you "couldnt tell them, because everyone is different" - nfts support (circumventing the 4GB filesize limit), running a smb server, using VPN services (currently also possible without - but generally speaking), blocking software updates, using open APIs or a web interface to control the device -- are all usecases I'd argue most people should know about that are possible by now - even though Amazon put in extra effort to specifically take them out of base Android one by one. So by glancing over those - you actually follow Amazons product politics once more -
Click to expand...
Click to collapse
I assume you're referring to when people ask about why they should root in the Q&A portion of my podcast. That question comes up nearly every week and if I listed all the reasons why someone would root in every episode it would not be interesting to the listeners. Heck, if I listed and talked about just the things you mention above, which is still just a small portion of the reasons to root, it would take up the entire time I allocate to Q&A. If you want to compile a full list of all the reasons to root and keep it up to date with links to guides, I'd love to point people to it every single time this question comes up. But nobody, including myself, has created such a list because it would be very time consuming to create and maintain.
- to put it out in the open, I have a problem with you having become the gatekeeper of most information in the Fire TV ecosystem.
Is saw german mainstream technology outlets copying your first statements on issues verbetum - even if they turned out to be beside the point (as in the blacklist issue case)
Click to expand...
Click to collapse
Other websites not covering the Fire TV more or not doing their own research is out of my control.
and I ultimately hold you personally responsible for Amazon being able to --
Put blacklist routines into Android, uninstalling apps from their users devices - which they dont like because of anti competitive reasons - and allowing them to spin this feat to be just something thats "easier for the user".
Click to expand...
Click to collapse
Holding me personally responsible for that is just plain stupid.
You maybe single handedly prevented the "Amazon uninstalls its users Apps" headline and made it a "Great new feature" story.
Click to expand...
Click to collapse
You over estimate how much influence I have over other tech blogs. Every time Amazon does something negative to Fire TV owners, I contact numerous tech blogs to let them know. They simply don't care. It's not newsworthy to them. The issue isn't that the headlines were "Great new feature," it's that there were no headlines at all outside of my site.
I also hold you responsible for maintaining an atmosphere where every slight new feature, change, or tidbit Amazon "creates" gets received with unfiltered optimism first ("cheerleading"). Even down to overly detailed changelog analyses that are made to be seen as newsworthy - just because they are something new to report on. Something of general interest to your audience.
Click to expand...
Click to collapse
I'm sorry everything I write about isn't newsworthy to you. I write about what I find interesting. It's not that I think everything Amazon does is worth cheering about, it's that I don't write about things I don't think are interesting. It might be a shock to you, but a headline like "Amazon did a thing that you shouldn't care about" is not at the top of my list of articles to write.
When you made them care more about ES File explorer (by pronouncing it "the easiest way") than if adb (which was first limited, then got puposely rewritten (?)) actually remains usable for things not predetermined by Amazon - you did this entire community a disservice.
Click to expand...
Click to collapse
I didn't "make" anyone do anything. My sideloading guide lists 7 methods. The ES File Explorer method is by the the preferred method by most for obvious reasons. The fact is ADB is confusing to many people. A GUI, even if limited, is usually preferred by most. Hence the popularity of utilities like adbFire before ES File Explorer was even an option.
When you let tutorials regularly get pushed off of the front page of your blog by 12 times the "Amazon echo appreciation messages" - something important changed - combining the "how to tinker with the device" angle with the actual product messaging of the manufacturer - created a hybrid that I'd argue actually resembles a frankensteins monster that produced more harm than good.
Click to expand...
Click to collapse
If you're saying I deliberately push guides off the front page, that's just stupid. I cannot control when something newsworthy happens. If something happens that results in a bunch of posts right after I release a guide, that's out of my control. I'm not going to hold back news just because I wrote a guide.
You managed to commercialize most aspects of device hacking, for - and mostly in the name of the company that produced the device - while Amazon itself promoted a purely anti right to modifications message at the same time. You tried to moderate this conflict - and somehow it never quite worked.
Click to expand...
Click to collapse
If I didn't make money from the website through ads, it wouldn't exist. Not in the same capacity at least. The same way XDA wouldn't exists if it didn't have ads to make money off of device hacking. If you have an issue with me turning my hobby of tinkering into a means to support my family, then so be it.
When Amazon put the blacklist into the Fire TV firmwares - you werent the person that first discovered the database entries - they were reported (In here or on your comments section) and you picked it up - but now you are promoting yourself to be the person we should look at for a confirmation if Amazon has added new entries to their blacklist, or if they didn't.
Click to expand...
Click to collapse
I never took credit for discovering the blacklist. I said "XDA forum member jkchr1s has discovered that FireStarter is being explicitly disabled by name" in my post and linked to his XDA post. jkchr1s and I were going back and forth via XDA private messages trying to locate the, at the time, theoretical blacklist. He explicitly asked me to not credit him with certain things, so I left some things vague.
I am not "promoting" myself to be "the person we should look at" for anything. It's simply a fact that I'm in a position to be the first one to know if the blacklist has been updated, since I know where to look and I have several Fire TVs and Fire TV Sticks dedicated for the sole purpose of capturing the update package to pass along to rbox.
Something about all of this just feels wrong. You were more a Steward of public opinion towards your cause (a world where a advertising message can stand eye to eye to a "how to intall Kodi" tutorial - ) and at least created an information silo - that kept out certain aspects of what is possible, or what happened in the past, and overemphasized others (I see ES File Explorer use as a real problem to people learning better ways of interacting with their devices, f.e.) at least I don't agree with.
Click to expand...
Click to collapse
I agree that learning ADB is far superior to any GUI like ES File Explorer. The only guides where ES File Explorer comes up is when I write "no pc needed" guides for rooting and sideloading, since those two topics are the most popular types of guides. But for every "no pc needed" guide I have ever written, there was always first an equivalent guide posted that did everything with just ADB.
Now that the hype is mostly over, Firestarter is no more and we are gossiping whos next on Amazons in Android blacklist - where do we actually stand considering discoverability of methods or tutorials, do we understand the actions Amazon has taken, do we promote best practices - and do you - for example know - why not letting Amazon blacklist Kodi is actually important?
Click to expand...
Click to collapse
Despite what you think, I don't control the future of FireStarter, the actions Amazon has or will take, or where the Fire TV community stands.
You take both sides on this issue as well - why? And when you, a few months from know - write your article about how it was actually necessary and beneficial to the average user - will you still be part of this community? Or do you just want to feature its work? And tell your readers to mostly use Alexa ("the service economy"), just because it is there by default.
Hey - and buy an "order from Amazon" WiFi button for 20USD while you are at it, because maybe one day you will be able to launch an App on the Fire TV with it. Great pitch.
Click to expand...
Click to collapse
I don't "take both sides on an issue", but I do try to explain both sides of an issue. When Amazon does something the community thinks is negative, I don't blindly defend their actions. I do give my opinion on why I think they chose to do what they did, regardless of whether I agree or disagree with it. There is a distinct difference.
I've hid my reply to the comments that were deleted to help clean up this thread.

@harlekinade
So your old account was banned? And you decided to come right back in here with your obvious rants now directed at the main person who keeps this community going? Good job dude.

Biggest question (for us "pros") is actually: Is root (and downgrade) still possible on the fire tv 4ks that ship with that firmware?!

harlekinade said:
I'm glad to see that the posting got some kind of of recognition, I'll take some time reading through the responses and give another rebuttal in the following days.
Click to expand...
Click to collapse
If you do reply, I encourage you to do it in a new thread and link to the posts in this thread as reference because discussions of your opinion of me and my site do not belong in a thread about a Fire TV software update. This is potentially an important thread (depending on what is discovered in the update), so it should not be cluttered with off-topic conversations. I absolutely will no longer reply to you in this thread regarding myself or my website.

zroice said:
Biggest question (for us "pros") is actually: Is root (and downgrade) still possible on the fire tv 4ks that ship with that firmware?!
Click to expand...
Click to collapse
I don't know if anyone whos gotten it yet has confirmed if the preloader hack is still active.

harlekinade said:
@aftvnews:
.
Click to expand...
Click to collapse
Dude, quit it. No one's reading your responses, you're acting like a sorry little git. If the mods bothered to read these, expect your second ban real soon. Quit starting fights and leave everyone alone.

Future of the AFTV

Is it just me, or does anyone else not see much hope in this platform? I got into the game a little late and it seems these havent been rootable for nearly a year... Ive been looking for an app that can remotely control any AFTV platform without root, and im not having any luck. Its extremely frustrating to be so locked down and the other android options are sketchy and unstable. Just going through several websites it seems these lost a lot of support, would I be wrong?

hyperblu said:
Is it just me, or does anyone else not see much hope in this platform? I got into the game a little late and it seems these havent been rootable for nearly a year... Ive been looking for an app that can remotely control any AFTV platform without root, and im not having any luck. Its extremely frustrating to be so locked down and the other android options are sketchy and unstable. Just going through several websites it seems these lost a lot of support, would I be wrong?
Click to expand...
Click to collapse
What's the big deal.
I never rooted mine and it does everything I need it too.
I use a USB airmouse and the Amazon gamepad for Kodi, NES, SNES, n64, Mobdro ect ect.
Sent from my FRD-L04 using Tapatalk

hyperblu said:
Is it just me, or does anyone else not see much hope in this platform? I got into the game a little late and it seems these havent been rootable for nearly a year... Ive been looking for an app that can remotely control any AFTV platform without root, and im not having any luck. Its extremely frustrating to be so locked down and the other android options are sketchy and unstable. Just going through several websites it seems these lost a lot of support, would I be wrong?
Click to expand...
Click to collapse
Remotely control? Elaborate on that a little. I'm running 2 boxes and a new and an old stick in my house since I cut cable in January. Boxes are rooted, but I haven't gone as far as messing with Xposed with those. Between Plex, Kodi, emulators, Netflix, PSVue (for now) and the fact that I have had Amazon Prime for some time, all of my bases are covered plus some just with one box or stick. I can easily stream from my PC or phone, and watch or listen to whatever I want. What is it you are looking for these to do? Just curious. I would also note that besides the fact that it disables automatic updates and I can update at will, I don't see much use myself for them being rooted. I don't utilize root access on my boxes. Except to get PsVue to run.

I'm flashing my kodi build to a few firesticks for Christmas presents and need to be able to access them remotely/screen share to update them or provide help if it's needed. I am able to sideload TeamViewer Quicksupport and screen share, but the Fire tv OS requires root to actually control input. So now I am limited to file transfers in the background, or casting a pointer on where they need to click. The only way I can think of doing both would be to port forward their routers to use a remote. Just a nice inconvenience I get to deal with.

I've tried just about every option there is. Chrome extensions, splashtop, vnc, all of them run into the same issue.

I have a couple sticks nib that have been sitting over a year that should be rootable. Tons on eBay as well.

Why not use TeamViewer or Skype to connect to a PC at the location the device is and do what you need to do? ADBFire will let you side load almost any app from a Windows/Linux/Mac. Small download and easy to use. You can also use ADBFire for SSH access and ADB commands. Putty may work in this scenario as well.

Bowflex Velocore

Has anyone had any luck unlocking / rooting the Bowflex Velocore? It's a pretty new exercise bike with an Android tablet which is locked into the Bowflex JRNY app.
So far, I've managed to get to the Android home screen where I can get to the play store and install other apps and basically use it just like a normal tablet. The problem is that by doing so, I can't use the JRNY app anymore. It requires another app, NautilusLauncher, to be running. NautilusLauncher runs a few background services. One of them connects to the telemetry of the bike, which is what JRNY requires. Another background service kills any foreign applications, basically locking you to the JRNY app.
I'm at the moment trying to find a way to disable the 'unwanted' services, but so far with no luck. Things I've experimented so far have been: Trying to find a user mode app that would kill the services when they start, find some way to edit the AndroidManifest or some way of just blocking them from starting. Unfortunately, haven't gotten anywhere with any of these approaches so far.
Rooting the device would probably help. Looked into Magisk documentation, but it didn't seem to have Bowflex Velocore as supported (and not sure how I would be able to find the firmware for it to extract boot.img/recovery.img). Also, the docs said you'd need to be able to connect with adb. While I can enable the usb debug mode in developer settings, for some reason I can't see the device when I run 'adb devices' (another place where I'm stuck).
The model / version reported by tablet is as follows:
model: NFTM-LAR
android version: 9
kernel version: 4.4.167
build number: 3.3 release-keys

Could you tell me how you got to the point of "using it like another tablet"? I have the velocore and my wife finds the bowflex classes boring. She would much have the pelton app displayed on her screen.

xasmx said:
Has anyone had any luck unlocking / rooting the Bowflex Velocore? It's a pretty new exercise bike with an Android tablet which is locked into the Bowflex JRNY app.
So far, I've managed to get to the Android home screen where I can get to the play store and install other apps and basically use it just like a normal tablet. The problem is that by doing so, I can't use the JRNY app anymore. It requires another app, NautilusLauncher, to be running. NautilusLauncher runs a few background services. One of them connects to the telemetry of the bike, which is what JRNY requires. Another background service kills any foreign applications, basically locking you to the JRNY app.
I'm at the moment trying to find a way to disable the 'unwanted' services, but so far with no luck. Things I've experimented so far have been: Trying to find a user mode app that would kill the services when they start, find some way to edit the AndroidManifest or some way of just blocking them from starting. Unfortunately, haven't gotten anywhere with any of these approaches so far.
Rooting the device would probably help. Looked into Magisk documentation, but it didn't seem to have Bowflex Velocore as supported (and not sure how I would be able to find the firmware for it to extract boot.img/recovery.img). Also, the docs said you'd need to be able to connect with adb. While I can enable the usb debug mode in developer settings, for some reason I can't see the device when I run 'adb devices' (another place where I'm stuck).
The model / version reported by tablet is as follows:
model: NFTM-LAR
android version: 9
kernel version: 4.4.167
build number: 3.3 release-keys
Click to expand...
Click to collapse
Not sure if you saw this...https://www.reddit.com/r/Bowflex/comments/m111p4/bowflex_jrny_workout_including_system_settings/
I wish he would share how this was done but he has not shared that info

alacard052003 said:
Not sure if you saw this...https://www.reddit.com/r/Bowflex/comments/m111p4/bowflex_jrny_workout_including_system_settings/
I wish he would share how this was done but he has not shared that info
Click to expand...
Click to collapse
Yes, seen the video. At this point, we (me and a few others working on it) have managed to unlock the Velocore, but still working on a few kinks etc as well as making detailed easy-to-repeat instructions on how to do it. I only have the Velocore, but assume the same method works on other new Bowflex products with an Android tablet that are locked into JRNY. And we intend to share
Anyway, at this point our instructions are still a bit sketchy, so if you are willing to go through some pain, I can share what we have so far in private. Otherwise, we hope to have the it documented better (hopefully) by the end of the week.

xasmx said:
Yes, seen the video. At this point, we (me and a few others working on it) have managed to unlock the Velocore, but still working on a few kinks etc as well as making detailed easy-to-repeat instructions on how to do it. I only have the Velocore, but assume the same method works on other new Bowflex products with an Android tablet that are locked into JRNY. And we intend to share
Anyway, at this point our instructions are still a bit sketchy, so if you are willing to go through some pain, I can share what we have so far in private. Otherwise, we hope to have the it documented better (hopefully) by the end of the week.
Click to expand...
Click to collapse
Awesome! Please share in private. I am willing to go through some pain... It cant be as painful as the jrny app

alacard052003 said:
Awesome! Please share in private. I am willing to go through some pain... It cant be as painful as the jrny app
Click to expand...
Click to collapse
xasmx said:
Yes, seen the video. At this point, we (me and a few others working on it) have managed to unlock the Velocore, but still working on a few kinks etc as well as making detailed easy-to-repeat instructions on how to do it. I only have the Velocore, but assume the same method works on other new Bowflex products with an Android tablet that are locked into JRNY. And we intend to share
Anyway, at this point our instructions are still a bit sketchy, so if you are willing to go through some pain, I can share what we have so far in private. Otherwise, we hope to have the it documented better (hopefully) by the end of the week.
Click to expand...
Click to collapse
Could I get those instructions as well? It would be much appreciated. Also, did the buttons to access to Safe Mode change?

val247 said:
Could I get those instructions as well? It would be much appreciated. Also, did the buttons to access to Safe Mode change?
Click to expand...
Click to collapse
Sure. I'll send in private. Yes, it seems so. I haven't been able to access safe mode since the last update.

Posted the method in public at:
Unlocking Bowflex Velocore
Note that this post is being updated with new information as we figure things out. This jailbreak should allow you to use the console like a normal Android tablet, install and run any software on it from the Play Store and sideload software as...
forum.xda-developers.com

xasmx said:
Sure. I'll send in private. Yes, it seems so. I haven't been able to access safe mode since the last update.
Click to expand...
Click to collapse
Did you do the multi-tap at the startup screen? I did a factory reset on mine and wound up with a normal Android Tablet, which is fine if when I reinstall JRNY it acts like the old one, but would like to now how to restore it to the way it shipped if it comes to it.

snatale1 said:
Did you do the multi-tap at the startup screen? I did a factory reset on mine and wound up with a normal Android Tablet, which is fine if when I reinstall JRNY it acts like the old one, but would like to now how to restore it to the way it shipped if it comes to it.
Click to expand...
Click to collapse
Not sure what you mean with the multi-tap.
Yes, you can get a factory reset tablet to its original state by installing all the custom software. You can find all the apks in a comment in the following thread:
https://www.reddit.com/r/Bowflex/comments/mi8wdo

xasmx said:
Not sure what you mean with the multi-tap.
Yes, you can get a factory reset tablet to its original state by installing all the custom software. You can find all the apks in a comment in the following thread:
https://www.reddit.com/r/Bowflex/comments/mi8wdo
Click to expand...
Click to collapse
When you get the Bowflex screen with the serial numbers in the corner if you keep tapping the left bottom corner you get a menu, one of the options is factory reset, when you do it you wind up with a stock android tablet. No software installation required. That’s what I did but would like the ability to return the unit to how it shipped if that doesn’t work out. When I did it, I was only trying to get around a botched update, not turn it into a tablet.