Develop Bugs

[Q] Skip Amazon fire tv registration

Hi all,
I had recently attended a Qualcomm developer conference in San Francisco and they had given an Amazon Fire TV to the attendees. But the problem is that from my home in India, I'm unable to even register the device.
I created an account on Amazon.com with a US address, but it still fails to sign in.
I tried proxy dns services like unlocator and dns4me, but no luck.
Without registering the device I cannot access any menu items , hence no way to enable adb debugging.
My goal is to turn the AFTV into a media centre box / android tv using xbmc and google play store.
Is there a way to skip the registration and enable full access either by -
1. Somehow going to fastboot mode and flashing a pre-rooted image (is that available) ?
2. Or going to recovery mode and adb sideloading a update-zip file which removes the registration hurdle ?
Any help is greatly appreciated.
I dont want a black brick near my TV which does nothing

muteX023 said:
Hi all,
I had recently attended a Qualcomm developer conference in San Francisco and they had given an Amazon Fire TV to the attendees. But the problem is that from my home in India, I'm unable to even register the device.
I created an account on Amazon.com with a US address, but it still fails to sign in.
I tried proxy dns services like unlocator and dns4me, but no luck.
Without registering the device I cannot access any menu items , hence no way to enable adb debugging.
My goal is to turn the AFTV into a media centre box / android tv using xbmc and google play store.
Is there a way to skip the registration and enable full access either by -
1. Somehow going to fastboot mode and flashing a pre-rooted image (is that available) ?
2. Or going to recovery mode and adb sideloading a update-zip file which removes the registration hurdle ?
Any help is greatly appreciated.
I dont want a black brick near my TV which does nothing
Click to expand...
Click to collapse
Short answer is you'll probably need a US or Germany based VPN. Long answer is fastboot is useless because they prevent everything with a locked bootloader. And recovery is useless because ADB over USB doesn't work. Even if you were able to flash rooted builds, you still need to be able to get through registration.

Thanks. Will try the vpn route.
But just out of curiosity, how do I get to fastboot mode?
I know how to enter recovery mode by using the keyboard
alt+prtscrn+i method. Is there any similar key combination
to get to fastboot? Also, i have used the 'fastboot unlock' cmd
to unlock bootloaders before, but of course it will ask for a
password. Does any one know the unlock pwd for AFTV?
Its a long shot, I know.

New Fire TV 4K - blocked Updateserver via Router - won't skip update and go to setup

Hey guys,
I just received a brand new Fire TV 4K. I want to prevent my device from updating to the newest version, so that I can get root easily. However, when I use the following guide in order to skip the initial update procedure it continues to show me the error message instead of jumping to the registration screen. I set up my router to block the domains according to the guide and I turn of my Wi-Fi router the moment "connection succesful" appears on the screen. Any ideas how to fix this? Or does the method do not work if the Fire TV is shipped with the latest firmware?
Guide: http://www.aftvnews.com/how-to-complete-the-fire-tv-stick-initial-setup-without-updating/

wohltat said:
Hey guys,
I just received a brand new Fire TV 4K. I want to prevent my device from updating to the newest version, so that I can get root easily. However, when I use the following guide in order to skip the initial update procedure it continues to show me the error message instead of jumping to the registration screen. I set up my router to block the domains according to the guide and I turn of my Wi-Fi router the moment "connection succesful" appears on the screen. Any ideas how to fix this? Or does the method do not work if the Fire TV is shipped with the latest firmware?
Guide: http://www.aftvnews.com/how-to-complete-the-fire-tv-stick-initial-setup-without-updating/
Click to expand...
Click to collapse
i had the exact issue with my fire stick, it's on 5.0.5
after about 100 tries i was about to return it to the store
i went to try it one more time and took it out of the bag and plugged it in again ,it booted up and went straight to checking for updates without asking me to configure the network settings
so i quickly unplugged my modem from my router and it finally went to the registration screen
now i do not know if this thing remember the DNS /network settings i am guessing that it does not since it usually asks you to reconfigure them every time it is powered on prior to completing the setup
i guess it at least remembered the network and password , but i don't know about the DNS settings
it was not the 1st time it booted up and went straight to checking for updates without me configuring DNS settings , but the other few times it also failed to go to the registration screen, i am thinking that this FW has a block that detects if a proxy or open DNS is being used and then refuses to go to registration if it is,
my guess is that when it rebooted that time with out me going to advanced and entering open DNS settings
that it got through to amazon servers and that is what made the FW finally let me go to registration, also forgot to mention that it was downloading an update, but i was able to stop it in time and block the updates with ADB
so i did manage to prevent the update in the end
my guess is that the 1st step in that guide is the problem ,
my guess is that using open DNS to block amazon servers will make it impossible to get to the registration screen on the newer FW's ,at least on 5.0.5
you could always try to do the guide without blocking amazon servers using open DNS
and be really quick to unplug it after you get past registration , then just enable ABD and unknown apps and disconnect your modem from your router and connect to it and block updates via ADB

gdroid666 said:
i had the exact issue with my fire stick, it's on 5.0.5
after about 100 tries i was about to return it to the store
i went to try it one more time and took it out of the bag and plugged it in again ,it booted up and went straight to checking for updates without asking me to configure the network settings
so i quickly unplugged my modem from my router and it finally went to the registration screen
now i do not know if this thing remember the DNS /network settings i am guessing that it does not since it usually asks you to reconfigure them every time it is powered on prior to completing the setup
i guess it at least remembered the network and password , but i don't know about the DNS settings
it was not the 1st time it booted up and went straight to checking for updates without me configuring DNS settings , but the other few times it also failed to go to the registration screen, i am thinking that this FW has a block that detects if a proxy or open DNS is being used and then refuses to go to registration if it is,
my guess is that when it rebooted that time with out me going to advanced and entering open DNS settings
that it got through to amazon servers and that is what made the FW finally let me go to registration, also forgot to mention that it was downloading an update, but i was able to stop it in time and block the updates with ADB
so i did manage to prevent the update in the end
my guess is that the 1st step in that guide is the problem ,
my guess is that using open DNS to block amazon servers will make it impossible to get to the registration screen on the newer FW's ,at least on 5.0.5
you could always try to do the guide without blocking amazon servers using open DNS
and be really quick to unplug it after you get past registration , then just enable ABD and unknown apps and disconnect your modem from your router and connect to it and block updates via ADB
Click to expand...
Click to collapse
Thanks for the reply. However, it does not help me much. I did not block updates via Open DNS but via settings in my router.
For those you do not understand the problem, I created a short video: https://gaming.youtube.com/watch?v=vt2ntBk4K-M&feature=share
After the update error message, I should setup the Wi-Fi again and when the message "you are connected" appears, I have to turn off the router. This is what I do. However, the Fire TV does not skip to serach for updates and does not go straigth to registration.

wohltat said:
Thanks for the reply. However, it does not help me much. I did not block updates via Open DNS but via settings in my router.
For those you do not understand the problem, I created a short video: https://gaming.youtube.com/watch?v=vt2ntBk4K-M&feature=share
After the update error message, I should setup the Wi-Fi again and when the message "you are connected" appears, I have to turn off the router. This is what I do. However, the Fire TV does not skip to serach for updates and does not go straigth to registration.
Click to expand...
Click to collapse
well mine was hanging on checking for updates for like an hour and would never go to the registration screen, just back to the error screen .
ok you are not using open DNS ,but you are still blocking amazon servers, i think it may be that the new FW will not give you the registration screen until it gets an amazon server and connects to it
or it may have some other method of detecting that we are trying to block domains, be it through open DNS or our routers
or it could just be a huge coincidence that it worked for me when i did not configure the open DNS settings, but i i tried it literally over 100 times with open DNS and it would never go past the error screen
i might have tried it like 3 or 4 times without setting up open DNS and blocking the servers and it still would not go past the error screen, but that one time it worked i did not enter the open DNS settings
you can keep on trying and report back if it works with the domains blocked in your router, but if you get to a point where you give up like i did then you can try it without blocking the domains and see if it will go to the registration screen

Debricked, P2 sees SIM, asks for PIN, but does not register on network, SIM disabled?

So... I stared into the abyss, but I came back from the brink - unlocked bootloader, and the modem/calibration stuff got wiped during what should have been a routine TWRP flash from fastboot, and left me with no radios whatsoever. After flashing S048, and applying all the known OTAs up till S251, I got my wifi & bluetooth radios back, but it didn't seem to recognise my SIM (tried both slots).
After trying for almost a week, I also finally got the diagnostics mode going and was able to put a working QCN backup in place (thank you XDA and uploader).
So I flashed the LineageOS 15.1 20180413, and lo and behold, it sees the SIM and asks for a PIN to unlock it. So far, so good. Then (first time) Android says 'switching to mobile data, might take a while' but nothing really happens (I am on wireless; if I turn off wifi that doesn't make any difference though).
Under 'Network', 'Automatically select network' is enabled but 'Network' (right below) is greyed out. When I untick 'Automatically select network', it says 'Error while searching for networks'. When I re-tick it again, it says 'Registered on network', although nothing really happens.
Under SIM cards, it says slot 1 is populated, but says 'Mobile Vikings is disabled' (Mobile Vikings being my provider). The button to enable it is greyed out. Switching to airplane mode doesn't force anything either.
I've had a logcat instance open when toggling 'Automatically select network', but nothing related seems to show up. Any hints on what I could try/check? Or is this a coaster?

I believe that once you erase the modem stuff you'll always have serious problems restoring it. It seems like most people have to send the device in for service.
I've still no solution for an old P2 of mine and in that case I even had a TWRP backup.
Lenovo should really allow for us to flash stock images . An unlocked bootloader with LESS privileges makes no sense.

Wipe everything in twrp & flash twrp full backup which included efs & modem shared on our p2 forum. then flash Fastboot s48 only systemchuncks 0-14, boot & recovery then do 4-5 OTAs updates till latest one s251, you'll get you mobile network & calls back.

@eried1 Yeah looks like it
@amansehdav I have turned the P2 subforum upside down and I already tried this - restore a working S233 TWRP backup, flash S048 through fastboot, and upgrade with the OTAs till S251. No dice. Wifi and Bluetooth came back with that process, but the stock firmware would not see the SIM.

Reset ZenFone 2. Now asking to verify the account but getting "disallowed_useragent"

Reset ZenFone 2. Now asking to verify the account but getting "disallowed_useragent"
I was having touch-screen issues so I reset my phone. When I boot now I get prompted for language, wi-fi, etc. Next screen says:
Verify your account
This device was reset. To continue, sign in with a Google Account that was previously synced on this device.
Click to expand...
Click to collapse
The problem is that there's no place to enter any information, just a button "Verify account". When I press the button I get a Google error:
403. That's an error.
Error: disallowed_useragent
Google can't sign you in safely inside this app. You can use Google sign-in by visiting this app's website in a browser like Safari or Chrome.
Click to expand...
Click to collapse
...but I don't know the app and I can't do anything else on the phone. Can anyone provide an answer on how to fix it?
UPDATE:
So the OS version was really old. I went through a series of updates by side-loading the ROMs from the ASUS support site. After 3 or 4 upgrades I had a completely different experience and it let me verify my account. All seems well for now.
Just a couple of notes in case someone else has issues:
- Using Fedora (linux) desktop I needed to use "sudo ./adb devices" to be able to start the server and perform the side-load. Without "sudo" I was receiving an error about permissions.
- I performed the upgrades starting with the kernel version that was already on the phone and then upgraded to the next release each time after booting to each upgrade. I did this because I received an error on one upgrade saying I couldn't go there directly.
Peace.

I have the exact same issue with a phone that I'm trying to setup for my kid. Where did you get your firmwares for this phone?

Start by going here: https://icr-am.asus.com/webchat/icr...634.649586617.1546133606-337662955.1546133606
Then select "Download Center" from the chat window pane. Select your specific phone model. Select BIOS & FIRMWARE. Be sure to select the correct version for your phone (WW, CN, JP, etc.)
Good luck!

General Modem always crashing, losing voice/data

Modem always crashes especially when outside. As long as I am at home on wifi, it seems to work, it crashes but not a lot (sometimes even during the night). But going outside and the phone switching to cell/wifi/cell/wifi/etc make it crashes rapidly.
Easy to see because I am losing voice/data. Phone does not reboot.
My F3 is stock, stock rom, never been unlocked or anything. It did this last year already. I am using the latest MIUI 14.0.4.0(TKHMIXM). I'm in Canada with PublicMobile.
error is
modem subsystem failure reason: ssr:MP:rflte_dm_rx.c:8779:rflte_dm_rxagc_config_update_switchpoints_and_lna_offsets_in_d
I have a lot of ramdump, for instance right now I have
ramdump_modem_2023-04-30_17-15-05_dmesg.log ramdump_modem_2023-04-30_23-05-56_dmesg.log ramdump_modem_2023-05-01_06-36-49_props.txt
ramdump_modem_2023-04-30_17-15-05_props.txt ramdump_modem_2023-04-30_23-05-56_props.txt ramdump_modem_2023-05-01_06-36-49.tgz
ramdump_modem_2023-04-30_17-15-05.tgz ramdump_modem_2023-04-30_23-05-56.tgz ramdump_modem_2023-05-01_07-34-55_dmesg.log
ramdump_modem_2023-04-30_19-45-04_dmesg.log ramdump_modem_2023-04-30_23-56-13_dmesg.log ramdump_modem_2023-05-01_07-34-55_props.txt
ramdump_modem_2023-04-30_19-45-04_props.txt ramdump_modem_2023-04-30_23-56-13_props.txt ramdump_modem_2023-05-01_07-34-55.tgz
ramdump_modem_2023-04-30_19-45-04.tgz ramdump_modem_2023-04-30_23-56-13.tgz ramdump_modem_2023-05-01_08-23-14_dmesg.log
ramdump_modem_2023-04-30_21-25-31_dmesg.log ramdump_modem_2023-05-01_01-36-21_dmesg.log ramdump_modem_2023-05-01_08-23-14_props.txt
ramdump_modem_2023-04-30_21-25-31_props.txt ramdump_modem_2023-05-01_01-36-21_props.txt ramdump_modem_2023-05-01_08-23-14.tgz
ramdump_modem_2023-04-30_21-25-31.tgz ramdump_modem_2023-05-01_01-36-21.tgz
ramdump_modem_2023-04-30_23-05-39.tgz ramdump_modem_2023-05-01_06-36-49_dmesg.log
Any way to send ramdump to xiaomi?

Problem seems to be
"External
Modem sending a Fatal Error Interrupt, with a error that Rx Calibration
Data (basically a instruction for what modem have to do with a Band
Receive Commands) is missing, and External Modem calling a "kill itself"
mode because of it can't recover from it.Βasically you go to
countryside, ur band switches from 20 to 3+7+20 and modem crashes"

Magister54 said:
Problem seems to be
"External
Modem sending a Fatal Error Interrupt, with a error that Rx Calibration
Data (basically a instruction for what modem have to do with a Band
Receive Commands) is missing, and External Modem calling a "kill itself"
mode because of it can't recover from it.Βasically you go to
countryside, ur band switches from 20 to 3+7+20 and modem crashes"
Click to expand...
Click to collapse
Would disabling specific bands fix this? Is so, what ones?

In another thread it seems someone tried it and it changes nothing :-/

Dial *#*#663368378#*#* to access modem test tools suite, hopefully something there can tell you more about what is going wrong

It seems I cannot access "MODEM test tools" (aka Rueban / MTB) app on official ROMs without authorized Mi Account according to some search. It only gives me a black screen.

Well that's mildly frustrating. Sometimes theres modem debug options in city (dial *#*#6484#*#*) tucked away in the 3 dot overflow menu in the top right...

Unfortunately there's no such option here :-(
I have a lot of ramdump about modem crash, always the same error. I tried to email poco support but gmail reports back that the server refused connection or something...