A friend gave me her old Cricket Dream. I did a factory reset, logged into my Google account, no issues except it's not letting me tap the build and enable developer options.
Easter egg pops up when I hit the section that triggers it. Just doesn't register that I'm tapping the Build section. Looks like it may be greyed out.
I apologize in advance if this has been covered. I did a search and didn't find any other posts under this phone where someone has faced this issue.
Nevermind. Didn't realize there was a second Build number.
In my defense, the build number on every Android I have seen has been under About>Software. This is the first time I've seen it listed under Software and grayed out but have a second location at the very bottom of the main tree under About
I don't know how many people have run into this, so I'll leave it to the mods whether or not to leave this post up or delete it.
Related
well its a discovery to me, and i haven't seen anything about this here so i though i would post this
also, long time reader, first time poster. lol
anyways, i have been trying to figure out why voice command would not do what i picked it up for: announce caller id.
well everyone said you had to go to settings an enable caller id, well alot of us couldn't because we don't have the settings shortcut and i was one of them.
well i found how to access to settings, for at least me. i use nrg roms, but i don't use sense even though its pretty sweet, i prefer spb.
but anyways i was playing with the settings "pane" in sense and noticed another entry called "other"-"misc settings" so i opened it up and there was voice-command settings????
the strange thing is that now that i have accessed the vc settings from sense now i can access these settings from the start menu and spb in addition to sense.
so now i am able to enable caller id announcements, but it still wont send the announcement to my bluetooth, which i believe is a known issue that hopefully can i can figure out
i believe all of this worked before i started using custom roms.
oops i guess i have posted on a non related topic before
Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?
I've got the icon, but no updates as yet...
mwako said:
Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?
Click to expand...
Click to collapse
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before
skeet94 said:
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before
Click to expand...
Click to collapse
Can't believe i didn't notice that , I remember now thinking it was an odd feel before when it didn't vibrate inputing the codes, after every other touch/input/exit on the device makes it vibrate, Seems they are doing something then. Lets see if anyone finds any new interesting menus inside ?
The "root menu" doesn't work any more it seems. I don't quite recall the command since I always check the Focus threads.
Updated Service Codes
We have extracted about 90% of the Service Codes from the latest Version I have downloaded. So far, not much in additional options. Maybe some changes in the old ones. Needs to be checked. There are again, some dead codes which are not referenced, so this is normal and not a wrong code from me.
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
AUDIOGAINCONTROL <-- What a shame as I still need to tweak the Volume on Level 1/30. Which should play more this Level.
(Yes I know, I have tweaked the Sound Tuning options)
The App runs a functions called "check cable" and this one calls "JIG_UART"
This function checks for two conditions. Unfortunately just some numbers, which cannot be explained because of a number code only..
This seems to be a Service Cable, as I was not able to run those codes, even when changed from USB to UART in the menu. So lets get an UART cable
If the UART Service Cable is not needed, maybe someone else finds out...
There are also two commands which check a registry value from the phone, and start not for me:
FTAMAIN
VIEWHISTORYNW
So far I have seen only the following new ones:
SerialNumber --> Starts but does not show anything
TFlashUnPairing --> Starts but have not tested it. I don't need to know everything
Some Menu Item was deleted, forgot which ones...
I have attached the Commands and the Hash table. It does not make sense to transfer every hash code, because most of them are already resolved.
I explain how to resolve it, in case you want to try one:
As an example I have chosen the SMDINFO (Open the TXT file)command, because it has only 5 digits:
The first Number: (4) Tells you the length of the code. Because we use 0 too, this code has 5 positions:
Next to the number in the brackets, is the number you put into the DiagApp Tool, starting from the last. Because SMDINFO shows, you only two of them in the same line, you just continue downwards. You can also use the search option:
This results in:
*#03#
Again you look for the numbers next to the numbers in the brackets. So you need to find the numbers for:
(4) (3) (2) (1) (0)
(4) (3) are easy, on the same line... the looks for the next (2), which can be found under: DisableSellOutSMS If you are unsure, use search...
Its easier as it sounds...
If I find anything new and useful, I will let you know...
Let me know any interesting file to disassemble. The is always more then the eye can catch.. At least with a debug guru in the team...
MC
mchabr said:
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
Click to expand...
Click to collapse
I guess the well known workaound, will result in the same root access.
*#1111# continue to press any number, until the long number at the top gets a minus symbol. Then just press back, until you jump into the main menu.
amazinglarry had posted a few items up here, and allegedly had them taken down and all mod comments point to finding the stuff on "HIS OWN WEBSITE" only problem is his profile doesnt have a website listed, and a google search doesn't work either...
and surprisingly... the mods lock up anything referencing him quickly... hopefully i can get an answer before an overzealous mod locks this up as well.
Hello all, I am new and this is my first post. So to start off proper, let me say thanks to DCZ, famewolf, and unjustified dev for working so hard to getting this working root, and to anyone else whos had a hand in it or in improving its functionality. I sincerely and deeply appreciate it.
I own this phone (6045X) & has been rooted and is using twrp recovery 2.8.7.0. In any event, upon its being rooted it was discovered that the mms was not working. I notice that it had been brought up but had not noticed a fix for this posted.
Fear not, for I am here to help. (If possible) Or hopefully to get some of you pointed in the right direction. A friend who went and got the same phone as I, (hybrid) & I figured out that it was as simple as changing a few things in the APN. Not everything. In fact for those new to this please do research. That involves going to your carriers website, selecting support and somewhere in there you should find the apn settings. Another thing you should do is goto Android A-Z and search for apn.
They will explain to you what it is as well as tell you not everything need be changed & they will go so far as to tell you that everything has to be typed precise down to the spacing and all. They will also explain how to get to your apn.
I hope someone finds this helpful. Other than that all i can say is, Whew! I feel like I just wrote a thesus
Two separate topics.
I have the LS777 Boost version running Nougat. I broke the screen and it sat for a couple years before I decided to replace it. Either I forgot the pattern lock or it did because I can't get past it. key points:
USB debugging IS on. It shows up as unauthorized
I can access the recovery screen
NOT rooted (yet, seeing it can be on here prompted me to fix it)
NO custom recovery
No dialer in emergency call mode
When I go from the lockscreen to the camera, take a pic, then hit the pic to preview it, then hit the share button, a bunch of social media icons pop up. If I hit one, it ALMOST goes past the lock screen trying to pull up the app to share.
I have it registered with LG, but I can't find a way to do anything with my device, let alone unlock it, you know like Samsung has.
Account device manager experiment: It had all five of my main accounts on there, but since I regularly change my passwords, I get the Account Action Required notification. If I can get it to authenticate on one of them, then I should be able to go to Where's My Device and set a new lock. I know all of the passwords I have used on my accounts, but I don't know what password I was on when this phone was active. Using my hotspot and changing the name to one of an open wifi I know I conneted that phone to, I am able to get it online (hence the notifications). I took one account and started changing the password on it, waiting 24 hours between each change and waiting a few minutes (until the notification hits my main phone at least) before powering it on. I'm on the third password and no luck.
It's theoretically sound, but I'm wondering if anyone knows for sure whether my device will authenticate the account when I get to the right password.
And yes, I know I can just wipe it. It's an old phone running Nougat that I haven't factory reset. The data on there isn't important, it's just a perfect situation to run some experiments on.
Second thing, because the issue of unlocking LG bootloaders still exists:
I have up Windows Device Manager because I'm working with various phones here. It's on the lock screen (booted normally) and is showing up under Portable Devices. If you co to the Details tab, scroll down to Capabilities, it has a second value: "CM_DEVCAP_SURPRISEREMOVALOK"
Remove a lock? Is this something we can exploit, or is LG pouring salt into the wound caused by them refusing to give us the codes to unlock the bootloaders.
Upon further research, that description in device manager is "surprise removal ok" and had to do with unplugging it.
Still, screw LG for keeping their bootloaders locked even after they decided they were getting out of the cell phone business. Makes the fact they had to shut down their forums even funnier.
On password number 4 of 5. I have a feeling this experiment isn't going to work. I'll report back after the next be password change.
I'm fairly certain I have tried every password from that account by now, and it didn't work.
However there are three other counts on there, stop I'll run the same experiment with them and see what happens.
I mentioned something about sharing pics from the gallery. From the lock screen,
1. Go to the camera icon and pull up camera,
2. Take a pic,
3. The picture will show up in the gallery preview box in the lower right corner. Press (or long-press) it and a pop-out menu will appear just above it.
4. If you pull the menu out, you'll see a bunch of links to various social media sites.
5. Click one of them. I've tried them all, but I usually pick Tumblr because it's the first one.
6. The screen changed to the app's background and it appears to start loading the app and will hang there for about 3 seconds, but then you get sent back to lock screen. It's 3 seconds can be maddening because looks like you're allllllllllmost there and then...no, no you're not.
If anyone knows if there's an exploit there, in all ears. I'm going to restart that password experiment with the second account now.
And I know most "plz help me get past me locked screen" posts are sus and address likely people trying to either scam someone by stealing their info or trying to spy on their significant other. So if anybody has any questions I'll gladly verify that I do own all of the accounts, that they're on this locked device, but due to the time that has passed they don't show up in the device lists in the accounts (not even in the web version of the Play store), and due to password changes wile it was broken, it won't sink now and allow me to reset the lock through "where's my device."