Title says it all. I updated to one ui officialy . (The update came to the phone.) Can i downgrade to N960FXXS2ARL4 using Odin? Is there any brick chance or etc. ? (I don't know much about this stuff.)
Edit: My region is Turkey. The latest android oreo update was N960FXXS2ARL4 (December security update) Android Pie (OneUI ) update is N960FXXU2CSA2.
Flash stock firmware through ODIN, make sure you wipe your device. Everything should be fine.
Should i wipe first or after flashing the stock rom?
After flashing is a must.
Choise for flashing csc_oxm.
Thanks for your replies. I managed to downgrade it. But i have a problem. S-Pen slot doesn't recognize my s-pen. I tried resetting etc. I tried reflashing the rom but it doesn't work.
Galaxy404 said:
Thanks for your replies. I managed to downgrade it. But i have a problem. S-Pen slot doesn't recognize my s-pen. I tried resetting etc. I tried reflashing the rom but it doesn't work.
Click to expand...
Click to collapse
Did you try to pair it from the settings s-pen menu? There is pairing option.
Also downgrading to oreo is understandable, but kinda temp solution if you are not willing to sacrifice a year worth of updates/security patches.
Doesn't work Phone doesn't even detect it when its inside the slot. I had s pen problems before downgrading but it was probably because i dropped spen to water. It made ghost touches while using so i dried it using rice. It was working again but now it doesnt work and the spen button is shown as constantly pressed. In screen of memo its shown as eraser. I cant use it to draw.
Note: After trying everything i figured out that if i reboot my phone with s pen inside it, it would understand that the spen is inside when it boots up. But when i start using my spen, it doesn't register presses on the screen only on the notification bar and air command button. While drawing it recognizes it as an eraser. It thinks that the button is pressed and higlights the texts when pressed.
Related
Hi All,
Australin Optus GT-I9305 (4G/LTE Ver).
Android 4.1.2
Download mode: Binary dowload 3 - Current binary Official - System status Official
I tried to root my SGS3 today with Odin however I used the wrong root from my old Note 2 which caused the screen to do weird things and then the screen would not boot up or respond. I have reinstalled the stock software on it with Odin and now the phone starts up but still does not respond to my touch's.
I can boot into recovery and download mode no problem. I have cleared the cache and performed a factory reset still no response from screen. I am stuck in the first set up screen atm the menu key, back & home key all make sounds when I touch them.
If I unroot the phone will it fix this issue? if so how?
Is the phone gone/dead/unfixable?
Or can I use USB OTG to control the phone so I can use triangle away and return for warranty?
I also think USB debugging is off as well as I cannot get into the phone.
Any help will be really appreciated thanks guys.
Although extremely similar in hardware the screen's digitalizers are different causing issues like this instead of a plain brick that you would get if you tried a I9300 firmware. Try using Samsung Emergency Restore on Kies.
If that doesn't work then you may have to send it into a repair center as you could have, put bluntly, ****ed it.
Sent from my GT-I9305 using xda premium
I've read of several cases where people have used Roms or recoveries intended for the Note 2 on their S3 and it literally fries the screen.
It allows too much current through or something like that.
I think you will need to get a new screen mate.
Hi,
I have a T710 that's about 6 months old and had fairly light use.
Yesterday after charging up to 100% while off, it turned on only for the touch screen to fail to respond. The capacitive keys and fingerprint sensor and physical buttons all work perfectly, the tablet boots normally, and even responds to OK Google - but no touch is registered on the screen at all.
There is no screen protector on it and it has not been dropped or damaged. I noticed a day or two ago when playing a game that the screen was a little slow to respond, but put this down to maybe greasy fingers or a laggy game.
It is currently running a stock 5.01 Rom, although there was an update or week or two back - but I've had it working since then.
This happened once before about 3 months ago and I was in the process of returning it when I flashed a stock ROM through ODIN, which solved the problem and it worked fine until yesterday - this seems to suggest that it's not a hardware issue.
Before I go down the Odin process again and hence wipe it, are there any other things I can try that might work?
I've never rooted and the Knox counter is not tripped, so I could send it back under warranty, but that will mean sending it away and as I imported it from Hong Kong I don't know if Samsung will raise an issue (I'm UK based).
Previous googling when I had the issue before found a post or two suggesting that it was something to do with charging after letting it run down that led to others seeing the same issue - but can't find anything in this forum.
You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.
ashyx said:
You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.
Click to expand...
Click to collapse
I didn't realise that Odin flashing didn't wipe! Useful to know thanks.
I connected a mouse with a OTG lead last night so was able to back up what I wanted with Smartswitch - I then tried the device reset through smartswitch, which does wipe.
Unfortunately, that didn't resurrect the screen, so I've tried a couple of different ROMs through Odin since, with similar lack of success
Unfortunately, I don't want to find out that it needs warranty repair after installing TWRP and possibly getting that repair rejected because of a knox trip. Has anyone had experience of returning a knox tripped device with a screen fault and their response to it?
I'm going to let the battery run down fully and recharge to see if anything changes - as that is what seemed to work last time (don't ask me why though!)
My Touch Screen DiED!!! (A Sad Story that Ends Happily)
I have flashed many a rom on my N910T Note 4. But yesterday I thought I'd update my TWRP install, and elected to use the new TWRP app to do so. Right TWRP file (double-checked). Fired up the app... and apparent success. On reboot, however, what looked to be
*DISASTER*
I touched my screen but nothing happened. Then I moved my finger and something elsewhere than under it opened up. In short, the sensors had become non-calibrated - they no longer properly detected where on the screen I was touching. The fact they did at all was better than nothing... but not much.
First, then, I did at least have some ability to still do things.
Second, better, I found that the s-pen's sensors worked just fine! Boy, was that helpful when it came to trying to type in my pin number / password.
Third, initial looks on the ol' google revealed people saying I'd have to buy a new sensor for the touch screen. Arrrgh!!
BUT THEN THE GOOD NEWS... I HOPED!
I discovered a number of folks suggesting what sounded almost James Bond-ish... a code, input into the phone touchpad, that when "called" could result in a calibration reset. Over and over again, there it was:
=================================
"dial *#2663# and update the touch FW by pressing TSP FW update (General)"
=================================
Okay, said I. Tried it from my new TWIZd rom. But no love. I got an error message. But then it occurred to me to read the many posts on this code more carefully... and sure enough, they did suggest that using the OFFICIAL rom provided by Samsung/my provider was necessary. Sigh... that meant navigating TWRP -- which by the way was also affected by the bad calibration. It was doable... just... by figuring out where my touches were actually activating the screen (it was less severely affected at the top but very severe near the bottom). Eventually got the phone wiped (Thank God I had just backed up my sweet TWIZd install to the ext sd card!). Luckily, I had a generic old copy of my phone's original rom on the ext sd, though it was one that had been debloated and rooted. I hoped it would work....
The flash hung. Forever. heading for 20 minutes. Finally I pulled the battery, not hopeful, and restarted the phone. *WHEW* it came up with the rom installed. Skipping both google and samsung installs, I went right to the Home screen and used my s-pen to type in the code then hit the call key.
Up came a screen of buttons, including a greyish TSP FW update (General) button. (See pics; neither is a Note 4 but both give accurate idea of what the screen looks like when the code given above is dialed in and works correctly.)
I tapped it with the s-pen.... and my screen was fixed!!
I made sure to use TWRP to backup that generic rom to my 128g external sd card - that way if this happens again I can "restore" it via TWRP and repair the phone quickly.
One thing is for certain... I sure appreciate this community of folks, which is where I found much of the info. And I will not be using that TWRP app (created by commercial interests anyway) again. Back to installing TWRP the old way, via either a *.tar TWRP file and ODIN via a PC or via flashing an *.img file w/ TWRP itself.
That's my story and I'm sticking to it.
Hit thanks if you found this amusing / helpful / or just plain odd.
Hi,
SO...I am pretty much in the same boat you were... but I have not been able to get the dialer thing to work...
when I type it in, it just flashes something to fast to see.. and then says "MMI complete" .
So far the ONLY thing I have done with this phone is root it (using Odin and chainfire) ... and install the wrong TWRP ... and then install the correct TWRP.
As far as I know, I still have the original ROM on it! I had not gotten to the point putting a rom on!!
Any suggestions?
Thank you for any help...
Thanks Shonkin, this worked for me on my SGN4, after flashing the bootrom with a Vodafone stock image.
Much appreciated
Hi everyone, this morning the OTA update notified me that the october update was avaible for my phone, i started the update and after then it was working perfectly. When i was trying to unlock the phone, it started having some trouble recognizing or my face, either my fingerprint. So i decided to restart the phone, but back then it is contiously turning on and off, and sometimes it says "Android is updating your apps". When it is on i can try to use it but there is nor notification bar neither the back, home button. If i try to connect the phone to the pc, it is recognized. Can somebody help me? It is the european model, with exynos, 128 GB and 6 GB of RAM.
(sorry for my bad english, it is not my native language)
Wilson22087 said:
Hi everyone, this morning the OTA update notified me that the october update was avaible for my phone, i started the update and after then it was working perfectly. When i was trying to unlock the phone, it started having some trouble recognizing or my face, either my fingerprint. So i decided to restart the phone, but back then it is contiously turning on and off, and sometimes it says "Android is updating your apps". When it is on i can try to use it but there is nor notification bar neither the back, home button. If i try to connect the phone to the pc, it is recognized. Can somebody help me? It is the european model, with exynos, 128 GB and 6 GB of RAM.
(sorry for my bad english, it is not my native language)
Click to expand...
Click to collapse
I would get the current stock firmware files for your phone model and the current version of Odin onto your laptop. Then just flash over everything. Try dirty flashing first (without wiping) as to not lose any data. If that doesn't work, wipe everything while flashing. You'll lose all your data and will have to set everything up again.
I honestly wouldn't bother trying to sort this yourself (And potentially making things worse), I'd just go straight to Samsung, you shouldn't be having to fix their mistakes.
RaymondPJR said:
I would get the current stock firmware files for your phone model and the current version of Odin onto your laptop. Then just flash over everything. Try dirty flashing first (without wiping) as to not lose any data. If that doesn't work, wipe everything while flashing. You'll lose all your data and will have to set everything up again.
Click to expand...
Click to collapse
After a while the phone battery discharged. When i tried to turn it on, it started working again like nothing happened. Thanks for helping
Wilson22087 said:
Hi everyone, this morning the OTA update notified me that the october update was avaible for my phone, i started the update and after then it was working perfectly. When i was trying to unlock the phone, it started having some trouble recognizing or my face, either my fingerprint. So i decided to restart the phone, but back then it is contiously turning on and off, and sometimes it says "Android is updating your apps". When it is on i can try to use it but there is nor notification bar neither the back, home button. If i try to connect the phone to the pc, it is recognized. Can somebody help me? It is the european model, with exynos, 128 GB and 6 GB of RAM.
(sorry for my bad english, it is not my native language)
Click to expand...
Click to collapse
Now this is what I worry about! Samsung needs to do better than this! It's bad enough that we dont get OTA updates in time and to then mess up my phone while giving me an already late update is so not good. Hopefully some day, we will see a change ?. I will surely know to back up all my data before any updates.. for whenever it comes....
william-johnson said:
Now this is what I worry about! Samsung needs to do better than this! It's bad enough that we dont get OTA updates in time and to then mess up my phone while giving me an already late update is so not good. Hopefully some day, we will see a change [emoji849]. I will surely know to back up all my data before any updates.. for whenever it comes....
Click to expand...
Click to collapse
I agree, the problem is that, before updating, i checked online if someone had issues with this update but i found nothing, so i decided to update... i won't do it again without backing up the phone before updating[emoji28][emoji28]
Inviato dal mio SM-N960F utilizzando Tapatalk
Hi,
I recently bought this phone knowing the touch was not responsive and just looking for any clues on where to start.
The screen works and using the side buttons can adjust volume (visible on screen) and bring up power menu but can't do much else since the touch is not working.
the phone has been factory reset so it loads into the MIUI 12 setup guide. I've tried linking it up with Mi PC suite with no luck. is this looking like a hardware failure or software maybe?
Also there is no damage to the screen
Thanks in advance
Lee
i think you will need to find xiaomi mi flash tool for your device and flash the stock firmware
you can download it here. I dont know much about that phone though so im only making suggestions.
Try to flash the whole MIUI firmware again.
Thanks for the help, I suspect it might be a firmware issue but had no luck with flashing using some tools so far but I'll try that link and see what happens
I've applied for the bootloader to be unlocked and waiting the 7 days for that, is there anything I can do in the meantime?
I've confirmed that the phone works and is not crashed as I plugged a mouse into it and am fully able to use the phone this way.
I tried to flash update via local but got an error that I cannot flash lower version.
Anything I'm missing?