I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
anyone else know if this works?
i just flashed the new sprint rom and now the data connection does not work.. no internet.. ? I was just wondering if anyone else had this problem and does this fix it?
After some more time with this ROM installed I have found that it is not neccessary to change the ##DATA# (##3282#) user name settings. Just change the HKEY_LOCAL_MACHINE/Software/OEM/DIM/EnableCurrentUserName value to zero, save changes and then you can run the IOTA update successfully (or at least I can).
I have found that I need to do this every time I do a hard reset of my device. I hope this helps someone else.
Scruffy
this did not work for me.. I Get error code 67
i started a new thread here........ http://forum.xda-developers.com/showthread.php?t=415666
so maybe someone will chime in... the ##3282# does not work for me at all.. you hit that on the dial pad and nothing happens... so i can not access that menu...
For now i went back to a OEM rom and called sprint and they got me working by doing a MASTER RESET... also ##3282# works on OEM roms but i think the file EPST.EXE is missing from the CUSTOM roms... any input would be great..
Not working for me.
i'm sure a master reset from within #778 or whatever would work but i don't feel like
putting in the data again.
Scruffy said:
I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
Click to expand...
Click to collapse
how do i find [email protected] where would that be?
Scruffy said:
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Click to expand...
Click to collapse
I just upgraded to NFSFAN's latest ROM, everything went well but I can not get my internet to work. The one thing I did notice is under the services tab, internet is not an option. I loaded the dcd sprint carrier 20090714 cab am I missing something else?
Thank you for any help you can provide.
Update:
Well I went back and flashed to the HTC 6.1 rom, then back to the 6.5 rom. That fixed my internet issues, but that option is still missing for me. Then after all of that my MSID was really screwed up. Everything seems to be good now.
please please help me clear the instructions
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
electricfeel_2012 said:
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
Click to expand...
Click to collapse
The path of HKEY.... is actually on the registry. You need to use a registry editor (like PHM Regedit) to make the necessary changes to the registry. I would recommend you to re-read those instructions as they will not get any easier than that. Alternatively, if you are on Sprint's official rom and have absolutely no clue what you are doing, you can always call them and ask them for help.
As far as the IOTA zip file, if you cannot open it, that means that you do not have any program to extract from compressed files in your device. Your best bet is to transfer the file to the desktop and extract it there. Once you are done, place the extracted contents back in the device and run it in there.
NOTE:
If you came here looking to fix recent problems with LoS in recent builds of Jelly Bean, be aware that this utility has not been tested with JB or ICS at this time. I figured LoS was a solved problem, so retired the project. I'm looking into it again, and may have something out later depending on how much has changed in the OS updates.
Introduction
Has your phone ever had a circle with a line through it instead of signal bars? Has your phone ever shown signal bars, but all calls and texts fail until you reboot? Well, those situations are called Loss of Service, or LoS, and while we can't actually stop them from happening yet, those situations can be detected and repaired. The Loss of Service Daemon (LoSD) does that, so you don't have to!
It does this by:
Restarting problematic radio daemons when detected.
Rebooting when all attempts to fix have failed.
In addition, it can create a log dump of various system logs for debugging purposes.
Requirements
Phone must be rooted.
An init.d compatible kernel.
Busybox must be installed.
Many ROMs and custom kernels do this automatically, but check the feature of your basic tool-chain before installing.
Installation
All files are located in my github projuct, if you'd like to get a closer look at how all LoSD works. But what you really want to to know:
Download LoSD
This will be a file you can flash using ClockWorkMod. Simply copy it to your internal or external SD card, reboot into recovery, and flash. The next reboot will be running LoSD.
NOTE : Installing LoSD will automatically remove -viperboy-'s LoSChecker, as they should not both run at the same time.
Download LoSD Uninstall
The above package will fully remove all traces of LoSD from your phone. Flash if you're having problems or no longer need/want LoSD.
WARNING! Do not wipe anything before or after install of this utility! It is not a ROM. You will be left with an unbootable system.
Usage
If you installed the flashable zip, your phone will automatically launch the LoS daemon at every boot.
Or you can call it manually to obtain debugging logs!
Code:
LoSD dump
When called with the 'dump' command, LoSD will dump all debugging logs and exit, creating a timestamped directory in LOGPATH (/data/local/LoSD by default), as well as a tar archive named logs.tar.gz. This lets you capture situations where LoSD did not detect a LoS, and send the logs for analysis.
Frequently Asked Questions
These are taken from the README file that gets installed with LoSD. There's more dev-related info in that file, so give it a look!
Q: Will this restart the radio or the phone if I lose 4G?
No. 4G is actually a separate radio from the CDMA radio used for texts and phone calls. This script ignores the 4G radio entirely and can not trigger no matter what happens to the 4G radio.
Q: Will this restart the radio or the phone if I'm using WiFi?
No. Turning on WiFi *will* disable your 3G data, but will leave the CDMA radio in an available state so you can still receive phone calls and texts. The LoS daemon knows the difference, so feel free to use your WiFi as you please. LoSD may restart your radio while you're on WiFi, but only because your CDMA radio stopped responding and you wouldn't have received any texts or phone calls if it didn't try and fix the radio.
Q: Where do I find the logs?
Logs produced when the radio is restarted, or the phone is rebooted, are stored by default in /data/local/LoSD in a directory time and date stamped for when the fix was attempted, or a reboot was triggered.
Q: Help! My log directory is getting huge!
By default, LoSD will not dump system logs when it repairs a LoS. But you may have enabled it on your own if you modified the configuration file. If you're in a spotty coverage area, the log directory may start to fill with several timestamped log dumps, each of which are around 5MB. If you'd like to stop this, please ensure your LoSD.ini configuration file does not contain the following line:
Code:
DUMPLOGS=1
Such a line will enable log dumping, which again, is disabled by default!
Q: I think I have LoS the daemon didn't detect. How do I get logs?
Very easily! LoSD has a built-in logging command! Just type this into a terminal, or an 'adb shell':
Code:
su
LoSD dump
This will create a timestamped directory just like LoSD had detected it. In addition, a file named logs.tar.gz will be dropped in your LOGPATH directory (that's /data/local/LoSD by default) you can send to us. We recommend putting it in dropbox, or some other binary-file hosting site.
Credits
Many thanks to -viperboy- for the original concept of checking for LoS with a script.
HaiKaiDo gave us the idea of restarting the radio daemon before rebooting.
If I'm forgetting anyone, please PM me!
Configuration
There are several settings you can apply to the LoS daemon while it's working. These settings should be placed in a file named LoSD.ini in the /data/local/LoSD directory of your phone. If you change any settings, you must either restart the daemon, or reboot your phone.
Currently recognized settings:
DEBUG
Many log entries are only informative in nature and can be very noisy. If you are having trouble and want to see LoSD activity reported in the system logs and LoSD.log, set this to 1. Default is 0.
DUMPLOGS
Whether or not logs should be dumped during a LoS repair or system reboot. Should be 0 for false, or 1 for true. Default is curently 0.
LOGPATH
Full path to where logs should be dumped. This is also where LoSD keeps its own LoSD.log file. Default is /data/local/LoSD because the daemon knows that directory exists. Feel free to place it somewhere on your SD card. If this directory does not exist, LoSD will attempt to create it for you. Please make sure the path is writable!
RESTARTS
How may times should the daemon attempt to restart the radio before giving up and initiating a system reboot. Default is 2. This setting was primarily defined because ghost LoS can sometimes degrade into full LoS, and subsequent radio restarts may be necessary to regain service.
RESTART_LIMIT
How many successful radio restarts before LoSD considers the phone state tainted? Too many RILD restarts may damage other services, or cause other unknown side effects. After this limit is reached, further LoS events will not result in an RILD restart, but a full reboot. Default is 3.
SLEEP
How long to wait between radio checks, in seconds. Default is two minutes.
Example:
Code:
LOGPATH=/sdcard/los
RESTART_LIMIT=1
Again, if these settings are changed, you must either restart the LoS daemon, or restart the phone. To restart the daemon, execute the following in an ADB shell or terminal:
Code:
su
killall LoSD
nohup LoSD &
The 'nohup' is there to prevent the command from attaching to your TTY, so you can disconnect without your session hanging. Feel free to omit this if you were just going to close your TTY.
Change Log
Version 1.3.1
Added third Airplane mode check for ICS firmwares.
Third firmware check also works on phones with disabled logcat.
Version 1.3.0
Improved CDMA connection FAILED detection.
Added second Airplane mode check for EL13, EL26, EL29 firmwares.
Version 1.2.0
Added debug log level.
Moved several informative messages to debugging only.
Debugging is now disabled by default.
Tweaked RILJ error detection for RIL_REQUEST_CDMA_GET_SYSTEMPROPERTIES.
Can now ignore false positive ghost LoS caused by phone calls.
Phone call and Airplane mode now checked before anything else.
CONNECTING status no longer skips LoS check.
Added ghost LoS check for CDMA 'Unknown data error' messages.
Version 1.0.0
Log dumping is now disabled by default.
Now uses 'setprop ctl.stop/ctl.start' to try restarting RILD nicely.
Does a quick check to prevent multiple running copies.
Added a radio restart limit to avoid glitchy post-fix systems.
Clear radio log in case of false positive ghost LoS.
Version 0.9.0
Added non-LoS check for transient CONNECTING status.
Now check for ghost LoS *after* standard LoS.
Calling LoSD with 'dump' now dumps and tarballs all debugging logs.
Version 0.8.1
Fixed bug in grabbing bugreport dump.
Now removes -viperboy-'s LoSChecker on install.
Removed LoSD logcat dump in favor of persistent LoSD.log.
Version 0.8.0
Now maintains a separate log for tracking all LoS events.
Added DEBUG configuration setting.
Version 0.7.1
Fixed typo in AirplaneMode check. Should no longer reboot in airplane mode.
Version 0.7.0
Fixed bug in radio log dump.
Now tries multiple times to restart RILD before reboot.
Added DUMPLOG as boolean to disable / enable log dumps
Added RESTARTS as number of RILD restart attempts before reboot.
SLEEP, LOGPATH, DUMPLOG, and RESTARTS are now user configurable.
Now searches for /data/local/LoSD/LoSD.ini for config settings.
Version 0.6.0
Initial public release
Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Sent from my SPH-D710 using xda premium
Just_s said:
Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Click to expand...
Click to collapse
Haha. Thanks. The way I see it, Viper has his hands full with way more important projects right now. With his ROM, the EK02 pull, the ICS work... why should he have to worry about this too? He was going to rewrite his script anyway, so I just took the opportunity to do it while he was distracted being useful.
While I was at it, I just... added a few things. That's all.
installing now.. thanks for this, and thanks viper
How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.
gedster314 said:
How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.
Click to expand...
Click to collapse
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium
Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Sent from my SPH-D710 using XDA App
grandmastem said:
Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Click to expand...
Click to collapse
Just flash it over the old one. I've made the install smart enough to install over previous versions of LoSD. If you're running -viperboy-'s LoSChecker, you should run his uninstall first, though.
Also:
Edited OP to reflect new 0.8.0 version. Added a setting to suppress the Info-level log messages. Now it also keeps a LoSD.log in the LOGPATH directory so you can keep a log of its activity between reboots without having the log dumping enabled.
I also updated the Configuration and Change Log sections.
After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium
pats4life100 said:
After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium
Just_s said:
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 sir.....+1.......
Also thanks for the shoutout trifthen! Nice work
Giving this a go. I'll report in with anything that seems odd. I definitely get LoS on occasion, and the girlfriend doesn't approve haha.
trifthen said:
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
And you can also add a line to remove my logs as well if you want. The files might be taking up a good bit of space...
Code:
delete_recursive("/data/local/LoS");
Those should be right, I'm at work so I'm typing from memory
For counting when LoS happens, you could just write a timestamp or something else into a file (>> adds into a file, > overwrites any data in a file) and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.
Yay no more this ****
Sent from my SPH-D710 using xda premium
-viperboy- said:
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
Code:
delete_recursive("/data/local/LoS");
Click to expand...
Click to collapse
Thanks man. I'll do that. I'll be waiting in anticipation for those enhancements. I actually just got a reboot following a ghost LoS where I couldn't send any texts. It couldn't restart the radio, and boom. The best enhancement we could get is to have no need for this utility. Heh.
... and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.
Click to expand...
Click to collapse
Yep. The new /data/local/LoSD/LoSD.log is basically everything it sends to the system log, so it's like a mirror that persists after reboots, unlike the system logs. In addition, you can turn off those pesky "Radio appears normal - no LoS." information messages by setting DEBUG=0 in the config file.
I just found a cut-n-paste bug in the line that dumps the bugreport, so I may just add the lines that remove LoSChecker along with that fix.
Thanks again, Viper!
Is anyone else running a hacked PRL and running into issues like I am?
EDIT: Rebooted manually, held up at splash screen, weird series of beeps and now back up....running Blazer v.12 on EG31.
DizDroid said:
Is anyone else running a hacked PRL and running into issues like I am?
Click to expand...
Click to collapse
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.
trifthen said:
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.
Click to expand...
Click to collapse
Thanks for the reply, keep up the great work. If I wasn't trying so hard to get out of my Sprint contract I'd ditch the .000000000000000000000000000 in a heartbeat.
Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.
Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.
A couple hours ago, the AFTV wouldn't play any Prime video and would just hang on the Netflix screen with the loading icon. Fairly certain it was on 51.1.1.0_user_511070220. Definitely 51.1.1.0. This was rooted with updates turned off using the adbFire app and a few Amazon URLs blocked in my router's access restrictions. After rebooting the AFTV a couple times, I read that a lot of solutions online were to delete the Prime/Netflix apps' data/cache. That didn't fix it. So then I followed the next common step and deauthorized the account. This is where the AFTV starting going crazy. After putting the user/pass back in, it started very quickly flashing between the "Authorizing Your Device" screen and the "Could not connect screen." A lot of button mashing broke the loop but every time I entered the user/pass, the loop would begin again. Hard and soft rebooting had no effect. Turning off the router (running AdvancedTomato) access restriction didn't help. I even used adbFire to very temporarily re-enable updates. Still no access.
I figured that this was a sign I should protect my root better. It may have been a mistake, but I decided to try and install Clockwork recovery. I left the "pm disable com.amazon.dcp" from adbFire enabled. So Amazon updates were still blocked. I downgraded to 51.1.0.2_user_510058520 kinda not realizing that this would kill my root and maybe also not realizing that Clockwork would need root to install.
I now have the same exact problem as before. I am stuck on the registration page and cannot sign in. It either says that the "sign in failed" or that the "connection was lost." At least on this earlier firmware, it doesn't seem to get stuck on the flashing loop between those two screens. There is some new weirdness where it seems to be pressing buttons on its own somehow. The text entry menu will disappear as if I closed it. And then when I select it again, it's in a broken format with all the keyboard buttons there, but the input field names missing.
I have verified that the current firmware is 51.1.0.2_user_510058520 with "grep fingerprint /system/build.prop".
I am 99% sure that nothing else from amazon is blocked besides "pm disable com.amazon.dcp", which I'm now unable to turn on again as I don't have root. adbFire says that "Amazon updates are off". I thought that this was reset by a downgrade? I can't think of anything else to check. I used to use dnsmasq to block three Amazon URLs before I found AdvancedTomato's Access Restriction but dnsmasq is empty and the rule in Access Restriction is deleted.
I am 99% sure I never edited my AFTV's hosts file. I just did "adb pull /system/etc/hosts" and all it has in it is "127.0.0.1 localhost".
Is there anything else I should check?
Just tried it again this morning. After every "sign in failed," if I let it sit on the failed screen with the keyboard where it wants me to enter user/pass again and touch nothing for 5-10 seconds, it will suddenly close that keyboard pop up and then immediately reopen it -- except it will be broken in that it's missing all the labels for fields like "Enter email here".
?
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
{ParanoiA} said:
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
Click to expand...
Click to collapse
I don't know where the router block could be. The rule in Access Restrictions is deleted and the Dnsmasq field is empty. I'm going to try using a cell phone hot spot to register it. Probably won't change anything but I can at least rule out the router as a problem.