Hi there,
I have an issue with my S-Pen. it suddenly have stopped working with my device.
I own a N976B Note.
I guess it is an issue with the firmware, because the stylus is recognized on my other devices and the other styluses are not recognized on my note.
To help you understand the history i want to sum up some steps.
1. my phone had a t-obile branding, witch i wanted to remove, so i flashed another csc rom to get rid of that. (back in 2020)
2. After some annoyance by advertisement and the wish to get root and a custom rom, i installed Dr.Ketan Rom and was pretty satisfied, but the hassle with manual updates was a draw back, so i decided to roll back to complete stock to get OTA.
3. After some huslte and some rookie mistakes by trying to install a n975 stock rom on my device, i figured it out and flashed the matching rom. but now the stylus or the digitizer seems to be corrupted. the firmware version is not recognized by the phone. see the screenshot below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some attempts to get it running again, i installed the very stock rom for my phone several times. (N976BXXS7FUI1)
I even checked "re-partition" and flashed with the matching pitfile in odin.
But there still no luck.
do you guys have some tips?
big thanks in advance!
greeting
Play with it. Spen's can be ornery as mules, once you get it going you're good.
They don't like being neglected for months.
My stock one was neglected. Took a couple days of playing with and then boom it stated charging like nothing ever happened.
Until it shows it's taking a charge it will do nothing. It will play dead.
Try clearing the system cache, reset network, pray to the pagan gods, play with it more... in and out, etc. Try enabling multiple spens, try disabling same... don't cross your spens, use the one for the 10+
Guess it just needs a good fk to get it going
I have 2 10+'s, both stock* and both run very well. Loading custom roms isn't needed, can kill desirable features and makes troubleshooting** much more difficult. That said if you're back on a stock rom the spen and associated hardware/firmware/software are likely good... it's just showing you who's boss. Play with it at least once a day, it will likely perk up in a week and stop it's wallflower act.
*with a package disabler and heavily optimized. I never update if it's running fast and stable; many apps are still running on their factory load as well. One 10+ is running on Pie, one on Q.
**Do Not enable power management. Make sure you didn't disable a needed parent/dependency apk! Do not ever, ever load Android 11 or higher, the kiss of death. Of course I could be mistaken, but probably not...
Related
Certain apps are missing from my phone I first noticed this with Lookout the app is present because I get notifications but it is no where to be found in my app list. Also did they do away with the basic calculator from the aps list in the N900T? I know there are plenty of other calculators but just odd that this is missing also? Not sure yet what else is gone.
Did you look in the Samsung folder in the app list?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok there is a few things in there but still many apps missing. Like Lookout and several tmobile apps as well as many others factory installed apps after a factory rest I only have 24 aps showing on a single app page but I can find the apps in other places and like I said even though Lookout isn't showing up in the app list/grid it is still running.
btw the calculator was in the sam folder.
I know its something Ive done just hoping there is a way to reverse it. I was rooted via the Root_de_Vega method and all went well I had started to try and flash JediElite rom with twrp but never could get it to take and after reading a bit more decided that ID keep my KNOX 0X0 and just used some Xposed and some themes but somewhere along the line I did something to cause the loose of viewable apps on the grid/list.
Im not sure when it happened during which process I was trying. I thought I was sailng along ... rooted...customs themes and then bam.
I flashed back to stock through ODIN and they still did not reappear..So I have since rerooted via the same method and am rooted again hoping this might help me locate what I have don't to hide these apps.
I had started the process of the 5x5 SecLauncher but I think this had happened before that.
Im guessing it was my failed attempt to load up the Jedi ROM as it started partially through but I could never get it to work I was thinking maybe I had only gained limited root access with the Root_de_la_Vega ? Has anyone been able to flash ROMS after rooting this method? Wasn't sure if I needed to us CF method if I planned on ROMs?
Shouldn't a flash of stock with ODIN replace any app (even bloatware) if JEDI ROM had deleted them? And as I said they seem to still be there just hidden....
Sound dumb, Ive spent several hours over sevreral days trying to learn how to do this. Like I said Im sure if probably a simple fix
.
OK never mind ... Ive figured out whats going on. Sorry to have sounded like a total noob.
Sometimes just cant see the forest for the trees lol
Thx krelvinaz for the Reply before
So I guess AllShare was replaced by Samsung Link...
Hello,
I have had my phone for a while now, but today was the first time since I got the phone that I looked at the device administrators area (settings / security / device administrators) and I noticed that there was an item called "Phone Info" that was activated by default and after reading about what it is supposed to do, I decided to deactivate it, but I was unable to do so. My questions therfore are:
1.) what is the purpose of this item?
2.) why can I not deactivate it?
3.) is it normal for it to be activated by default?
4.) if is not needed than how do I get rid of it?
In case it helps, my phone is rooted and I am still running the stock 4.1.2 ROM that came with the phone.
A few days ago I tried out the "All In One" 4.3 Stock ROM from Thunder Stick, but it was not working for me to well so I restored my nandroid backup of my original stock ROM so I am not sure If the other ROM has anything to do with it or not or if the setting has always been like that, but as I said before, I just noticed it today and would like to know what it is and how to deactivate it if I can.
Thanks for any and all replies,
Mtcell
Can you post a screenshot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is another one that shows the permissions dialog and where I should be able to deactivate it, but pressing the deactivate button has no effect.
That is weird. I am checking my s3 now but this is all it shows on my optimus G. Maybe it is a Samsung thing?
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."
Edit: here is what my s3 shows under those settings, but remember, my s3 isn't activated. Maybe it is just the activation stuff?
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."
Thanks for the reply. After doing some research I have discovered that it is part of some corporate security thing that sprint has on some of the newer s3's (see the attached screenshot) Anyway, I have frozen the app since there is no way to disable it. That will work for now until I change my stock ROM in a few weeks.
If anyone else has this app setup as a device administrator and wants to disable it than you can use the pro version of titanium backup or the free version of sd maid to freeze the app like I have done. Note, your phone must be rooted to use these apps.
I purchased 3 FTVs for my home net purely to run xbmc and dont have a lot of interest in amazon prime or the stock FTV setup.
2 of the 3 boxes were fine, blocked updates on my net, rooted, disabled updates, XBMC on, everything worked great. Still need to do some tweaking but all good.
1 of the 3 boxes already knew of the update, and is trying to get it, but is of course blocked. As I have never booted it, I have no way to know what FW its on now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried waiting of course.. Tried pulling the network cable after it finds the DHCP and before 'checking for updates' (actually doesnt say that it seems to already 'know').
Is there a way of resetting the knowledge of the update ??
What is my best course of action with the greatest probability of securing root ??
Is there a way of stopping an update if I let my router connect to the update links ?? As I have never done that I dont know how the process goes ??
Or is there a way of on the first boot, when it updates, enabling ADP and rooting and disabling before the next boot (I read this works but perhaps not in this situation, eg from a normal boot not a first boot).
Lastly, I am not in the US, I dont know if it will even allow me to get the updates outside of there and I cant VPN via my router.. Which would lead to a useless if not bricked FTV stuck in a loop of an update it cant get.
Sorry for the Qs.. I did search but theres a lot of variables and one mistake could lose root on this box, where possibly the right combination or sequence can preserve it.
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
Just did this.. With a reset of user data and cache.. really thought it would it would work..
Booted.. had to discover the remote.. then.. Exactly the same.. Update detected (blocked with openDNS) and in the same loop ??
Can I block update system by ADP ?? Given the recovery option of update by ADP, is that any use here ??
Hi.
I have this phone since months but I could not figure out which rom to install. I don't want to lose the Sony's camera so RR and CM is not an option. (Tried to flash it from cross-dev thread topics but just killed the rom)
The other problem is that from the stock roms the latest (D5503 14.6.A.1.236) has a prerooted version wich I still use but after a month it started freezing and rebooting and now doing it almost every hour.
I don't want to use previous builds because the latest has the best battery life.
Any idea?
redcon275 said:
Hi.
I have this phone since months but I could not figure out which rom to install. I don't want to lose the Sony's camera so RR and CM is not an option. (Tried to flash it from cross-dev thread topics but just killed the rom)
The other problem is that from the stock roms the latest (D5503 14.6.A.1.236) has a prerooted version wich I still use but after a month it started freezing and rebooting and now doing it almost every hour.
I don't want to use previous builds because the latest has the best battery life.
Any idea?
Click to expand...
Click to collapse
Personally, I start from scratch, (flashtool ftf), then build, (root, busybox, recovery, mods, Xposed, etc.). I always keep a backup of base rooted rom, then make a backup whenever I do any major system changes successfully.
I'm pretty much satisfied with MX ROM. Few quirks here and there, but nothing major. Battery life is better than on stock, put Z5 camera libs, amplify and MobileRadioFix and it's very good. Probably there will be some new update soon.
Thanks for your answer.
I solved it. I use RR (this is my favourite) and the OpenCamera app seems better than the Sony's Camera app
I prefer kitkat. I can make it run for days on end whithout charging. Lollipop and MM just sucks the juice out of the phone. I don't feel either LP nor MM has that much that make it interesting for me to change to either of them.
Picture: mobile used for three days on battery (and yes, I have taken calls on it)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
wase4711 said:
So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
Click to expand...
Click to collapse
I got the same build number when i bought phone from best buy. I was able to unlock bootloader and root.
Edit: just unlock bootloader and then flash full factory image using adb and fastboot tools..
i've unlocked the bootloader, but not rooted or twrped yet, since there is really nothing to flash yet..
which image did you flash?
thanks
I downloaded the play services update from all mirror and it now gives the option to check for updates, you'll find the appropriate play services in my screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel XL using XDA-Developers mobile app
I have the same version of play services as in your screenshot, and when I go into dev options/about/check for updates, it says no updates available...weird
still no update for me, very strange