Hello fellas, I know that theres a lot of another topics about this subject. But I see each of this and dont found a solution.
Whats happen is that I accessed the menu *#2663# and I clicked in Touch Key FW update. After this, no more touch works.
I tried a custom rom (Cyanogem 10, 13, Albe95,Ressurection)
I tried a stock rom (last rom, fist rom with android 4, using .pit files, using ap, bl, cp, csc files)
I tried wipe data factory
I tried wipe cache
I tried wipe dalvik
and nothing works! my buttons back and menu work but my touch not work!
I suspect that my firmware touch is corrupted. I don't know.. There's a way to restore this?
I'm a brazilian developer (c# , desktop and webapp) and i follow xda a long time... I used any other rons with my old devices (Milestone, defy)... but this time I don't know that I can do.
Sorry my poor english, and tanks a lot
Arkanes said:
Hello fellas, I know that theres a lot of another topics about this subject. But I see each of this and dont found a solution.
Whats happen is that I accessed the menu *#2663# and I clicked in Touch Key FW update. After this, no more touch works.
I tried a custom rom (Cyanogem 10, 13, Albe95,Ressurection)
I tried a stock rom (last rom, fist rom with android 4, using .pit files, using ap, bl, cp, csc files)
I tried wipe data factory
I tried wipe cache
I tried wipe dalvik
and nothing works! my buttons back and menu work but my touch not work!
I suspect that my firmware touch is corrupted. I don't know.. There's a way to restore this?
I'm a brazilian developer (c# , desktop and webapp) and i follow xda a long time... I used any other rons with my old devices (Milestone, defy)... but this time I don't know that I can do.
Sorry my poor english, and tanks a lot
Click to expand...
Click to collapse
Well, you could try Jtag and force the touch firmware onto the phone.
I don't think there is any other way.
There was a computer program that allowed you to see the screen of your phone on the PC, and navigate it.
Maybe you can use that to somehow force update it.
Tks Dobra..
This Jtag is a update by hardware? like a z3 box? or can I do it by my computer?
Arkanes said:
Tks Dobra..
This Jtag is a update by hardware? like a z3 box? or can I do it by my computer?
Click to expand...
Click to collapse
It's a piece of hardware you connect to your PC and Phone. I don't know much about it.
But I know it can force software on a phone.
GDReaper, tks for reply, dear friend.
Ok, It is exactly what I thought..
I don't have this hardware.. I think that I will send my phone to authorized.
tks again!
Related
First of all thank you very much and sorry for my English .
I had a problem updating my b5510l , load stock rom via ODIN and then made the grave mistake of trying to update the firmware of the touch pad * # 2663 # ! Result: wifi error and stops operating the touchscreen .
Second rookie mistake , re-flash the stock rom and the phone stays on ... touch the android to continue ..
After reading several posts on this forum I've accomplished something and these are the steps:
1. Flashing stock rom with odin : PIT , bootloader , pda, moden and csc .
Two . Root with update.zip
Three . Connect my phone to pc and achievement androidscreencast I access the system .
The problem is that when trying to open the phone to dial * # * # 2663 # * # * and reflash the firmware of the touchscreen, I get:
*the phone application ( process.com.sec.android.app.dialertab ) has stopped unexpectedly . Try again ...
I installed exDialer and dialing the code have the same problem but with the application lcd.test
P / D: I also tried custom rom 's have the same result
I hope you can help me, Thank you so much for trying
Marcos
if it force closes when you try to open the dialer its wrong firmware/rom
if it force closes when you try to enter that code you havent got the apk installed that it relates to most likely
you can try and install the following apks with system app installer (playstore) dont install them as a normal apk as they wont install
you can also put them in a flashable zip and flash them with system mounted
you can also download the correct firmware from my thread
http://forum.xda-developers.com/showthread.php?t=2700169
hello namesake! Thank you very much for the reply, I will try both methods you have given me. Also I commented that I flashed with the stock rom download from samobile, besides other roms.
closes the dialertab alone fails to open. when I load the code in the exDialer lcd.test title screen appears but takes time and displays the closing force.
I got up to date with the results.
Greetings!
Mark
hello friend, I flashed via odin the stock rom you told me and I still have the same problem, even on the home screen with the emergency call button to force me off the phone application.
installing the applications you have given me not get results.
I am clueless
marcospincha said:
hello friend, I flashed via odin the stock rom you told me and I still have the same problem, even on the home screen with the emergency call button to force me off the phone application.
installing the applications you have given me not get results.
I am clueless
Click to expand...
Click to collapse
if you cant sort it via flashing stock rom via odin take it to repair shop and ask them to reflash your firmware and bootloaders using a jtag
hello friend! sorry for the question, If the phone responds via Odin and loading the latest stock rom with bootloaders still having the same problem. What else will make the sat with jtag?
marcospincha said:
hello friend! sorry for the question, If the phone responds via Odin and loading the latest stock rom with bootloaders still having the same problem. What else will make the sat with jtag?
Click to expand...
Click to collapse
it shouldnt be force closing if you have flashed the correct firmware via odin and everything has been done properly
this is why I said take it to a repair shop when they can erase everything off the phone and redo every part of the firmware with a jtag to ensure everything is done properly
anyway I want to avoid going to a sat. I have another query, if I get a nandroid backup from another phone and charge it via cwm on mine could solve the problem?
another dumb question I have to ask is: what if the active box nand erase all in odin? this would erase all of my phone? lose download mode doing a hard brick?
or would allow me to fully charge the stock rom from scratch?
excuse me by the insistence and if my question is very silly. Your interest is a great help to me.
marcospincha said:
anyway I want to avoid going to a sat. I have another query, if I get a nandroid backup from another phone and charge it via cwm on mine could solve the problem?
another dumb question I have to ask is: what if the active box nand erase all in odin? this would erase all of my phone? lose download mode doing a hard brick?
or would allow me to fully charge the stock rom from scratch?
excuse me by the insistence and if my question is very silly. Your interest is a great help to me.
Click to expand...
Click to collapse
never tick anything else in odin - you will risk damaging your phone
you can google what the other things do
the nandroid backup would have to be from the same phone using the same kernel and recovery as you or you need to flash the kernel and use the recovery from which the backup was made
you would also need to data wipe after flashing it else you will have all their data
I´m exact in the same point as Mark....
were you able to solve it?
I´m looking for a nandroid backup or a 2.3.4 or 2.3.5 firmware.
By mistake I uploaded Odin Asian ROM, which reportedly has a different structure in the flash memory of the phone.
When returning to the European ROM device has bootloop but or system boots with errors (eg no modem).
I understand that now I need a multifile rom to restore right structure on Flash. Am I right?
The only question is where these files to take?
Thanks for your help.
You could try to restore Your Whole OS, and all the partitions and stuff with this: http://www.sammobile.com/firmwares/3/?download=31790
I have flashed that like a week ago on my Note 3, and it seems to work really nicely.
I tried to do this - without results.
ibanezq said:
I tried to do this - without results.
Click to expand...
Click to collapse
try do this install again one asian firmware remember what you installed first and try upgrade with the area from there . don't change any bootloader but , after ODIN reset do a fast up volume plus home plus power and you should have back everything but (choose english ) that is the only prb.
Today I made what you are writing above.
This is a only solution I think. Next I need to wait for EU ROM with my language.
Thanks for your support.
ibanezq said:
Today I made what you are writing above.
This is a only solution I think. Next I need to wait for EU ROM with my language.
Thanks for your support.
Click to expand...
Click to collapse
DON'T TRY PIT FILE PLEASE IT WILL STUCK YOU SO BADLY LIKE IT STUCKS ME :crying:
Hey guys bare with me long story,
Last week I decided to try out Cyanogen Mod (12.1). I had not flashed anything to this phone previously or rooted it. I wanted to flash Cyanogen due to less bloat but I did not want to root because I have work software that needs to go on the phone which will not activate with root enabled. So I flashed cyanogen and it was great but my battery started draining and bluetooth was not working properly on it. I decided to give Temasek 's last Lollipop release a try after this because it did not install root either. I gave that a go and still got severe battery drain. So I decided to flash back stock (N900W8VLU2DOH1), but as soon as I did I noticed my two soft key's were not working upon doing so. Back button would not work at all and the other would just open search. So I did multtiple wipes , update from kies etc. But no luck fixing the soft keys. FInally I read that flashing a custom kernal would fix the softkey issue for now until another Samsung update comes out. So I flashed Idle kernal and it fixed the softkeys but now I keep getting a "Unfortunately Knox has closed" message upon start and sometimes out of knowhere. This is really annoying.
Has anybody else ran in to this and know any fixes for it ? Even for just the knox popup. I think it may have to do with the touchkey's firmware from what I read and I'm hoping the next official update from samsung will fix this. I would try another custom rom as long as root is not enabled and battery and bluetooth are functioning properly, just not sure what else to try.
Any help would be much appreciated.
Thanks!
Hi.
This happened to my twice.
After much try and error, the solution I found is to REPARTITION the phone using a PIT file for your Phone.
Please find the PIT file for your variant and flash an official samsung rom while selecting the PIT file in ODIN.
Should work. please let us know the result.
Hi Suroky,
Thank you very much for the reply. I will try this later today and let you know how it goes.
Suroky said:
Hi.
This happened to my twice.
After much try and error, the solution I found is to REPARTITION the phone using a PIT file for your Phone.
Please find the PIT file for your variant and flash an official samsung rom while selecting the PIT file in ODIN.
Should work. please let us know the result.
Click to expand...
Click to collapse
I flashed the PIT file as mentioned and reflashed the stock samsung firmware with Odin. Still no luck. Upon boot I am unable to press the back button and when I press the left softkey it takes me into the search screen. Any other ideas ?
Thanks,
Hi.
Did you select REPARTITION into ODIN? Please be aware this can brick your phone as well.... Be sure to use the PIT file for your device, as there are many variants with different partitions.
Suroky said:
Hi.
Did you select REPARTITION into ODIN? Please be aware this can brick your phone as well.... Be sure to use the PIT file for your device, as there are many variants with different partitions.
Click to expand...
Click to collapse
I selected the PIT file but I did not check the box that said re-partition. Sorry my bad! I will try this again and see if it makes a difference !
Thanks!
Isn't OH1 the latest for Canadian carriers? Maybe try that version.
http://www.sammobile.com/firmwares/database/SM-N900W8/
audit13 said:
Isn't OH1 the latest for Canadian carriers? Maybe try that version.
http://www.sammobile.com/firmwares/database/SM-N900W8/
Click to expand...
Click to collapse
Hi Audit,
I flashed the latest (OH1) as well. That's the firmware I am on at the moment, still no luck though. Thanks for the suggestion though. Going to try reflashing with PIT and repartition selected as Suroky suggested. Hopefully that does the job.
Suroky said:
Hi.
Did you select REPARTITION into ODIN? Please be aware this can brick your phone as well.... Be sure to use the PIT file for your device, as there are many variants with different partitions.
Click to expand...
Click to collapse
Just tried this again with the proper PIT and Re-Partition checked on in Odin. Still no luck, softkeys still not working. Anyone else have any ideas ?
Thanks!
Repartition MUST BE ON.
Adding a PIT file automatically checks re-partition in Odin 3.07 for me.
Try this:
uncheck everything in Odin except f.reset time, flash just the ROM without a PIT file, when you see the word "reset" in the status window, remove the USB cable, remove battery, wait 5 seconds, replace the battery, use the key combination to boot into recovery, perform a factory wipe, and reboot to the ROM.
Are you using an original Samsung USB cable? Maybe try flashing on a different USB port?
Suroky said:
Repartition MUST BE ON.
Click to expand...
Click to collapse
Sorry Surokey, I meant repartition was on not off. Still no luck
audit13 said:
Adding a PIT file automatically checks re-partition in Odin 3.07 for me.
Try this:
uncheck everything in Odin except f.reset time, flash just the ROM without a PIT file, when you see the word "reset" in the status window, remove the USB cable, remove battery, wait 5 seconds, replace the battery, use the key combination to boot into recovery, perform a factory wipe, and reboot to the ROM.
Are you using an original Samsung USB cable? Maybe try flashing on a different USB port?
Click to expand...
Click to collapse
Re-Partition does the same for me in Odin. So I did try it twice with the PIT and RePartition on with no luck.
No I lost the original usb cable not long ago. Just using a standard usb 2.0 cable. I've tried on multiple usb ports as well.
I will test out what you mentioned and see what happens.
Thanks!
I fix it
my softkey on my note3 (sm-n900w8) stop working after a update to 5.0. i did a lot researche on the web but no clue
here what i did
first: *#2663# to check the version
phone touch key fw 0x09
part touch key fw 0x12
try to do a touch key fw update the phone give me an error about version number is higher already installed
secound: tried to find hlte_cypress_tkey.bin to do the update manualy but i couldn`t find it anywhere. i found this site github.c0m/friedrich420/Note-3-AEL-Kernel/tree/master/firmware/tkey/ I downloaded hlte_cypress_tkey.fw
copied it on my phone renamed it to hlte_cypress_tkey.bin next I did *#2663# and clicked on touch key fw update (internal storage) reboot voila! it did work!!!!! :laugh:
the version now is
phone touch key fw 0x10
part touch key fw 0x10
im so happy I hope this tuto gone a help someone
sorry for my bad anglish
P.S change the 0 by o in the web address
Is this still working for you? Where did you put the firmware update file?
mathieu0524 said:
my softkey on my note3 (sm-n900w8) stop working after a update to 5.0. i did a lot researche on the web but no clue
here what i did
first: *#2663# to check the version
phone touch key fw 0x09
part touch key fw 0x12
try to do a touch key fw update the phone give me an error about version number is higher already installed
secound: tried to find hlte_cypress_tkey.bin to do the update manualy but i couldn`t find it anywhere. i found this site github.c0m/friedrich420/Note-3-AEL-Kernel/tree/master/firmware/tkey/ I downloaded hlte_cypress_tkey.fw
copied it on my phone renamed it to hlte_cypress_tkey.bin next I did *#2663# and clicked on touch key fw update (internal storage) reboot voila! it did work!!!!! :laugh:
the version now is
phone touch key fw 0x10
part touch key fw 0x10
im so happy I hope this tuto gone a help someone
sorry for my bad anglish
P.S change the 0 by o in the web address
Click to expand...
Click to collapse
Thanks a ton man, this worked for me. It was really annoying not having my back buttons working. Now I just have to figure out how to reroot my phone after upgrading my boot loader.
To root the n900w8, you can try using cfautoroot or flash twrp and supersu from twrp.
Now I just need to get the lights on my soft buttons working again. plus fix my text messaging so I can receive messages again.
Hi, my Samsung S4 I9505 does not boot with anything, it just stay at samsung boot logo loading colors.!
Its driving me Crazy, at firts i thing it was Software so i started to flash with odin like many other phones. but its always the same.
I start upgrading to 4.4.2 ... nothing
trying diferent version of 4.42.... nothing
them to 5.0.1.... nothing
Last 5.0.1... (2016)...... nothing
flashing recovery twrp-3.0.2-0-jfltexx..... succesfull but doesnt make difference
Rooting with CF-Auto-Root-jflte-jfltexx-gti9505.... succesfull but doesnt make difference
Star trying some custom roms.... nothing
Always wiping cache, dalvik cache, internal data, system before install roms, or later, or not erasing at all.. all kinds of combinations.
Star flashing PIT files, diferent PIT with some 4 files firmwares again all kind of combination, (just PDA, just bootloader, diferent versions, alll together)............ Nothing
Reading al kind of post, suggestion... decide to try Downgrading, and again reading all kind of dowgrade methods has been using here and there....
Start triying downgrading from 5.0.1 to 4.4.2..... succesfull task but same s****t
them from 4.4.2 to 4.2.2... again.... good but not enougth............ same result
start doing some exercises and taking breath... nothing...
thinking my next move. call a witch maybe?
sell the screem cheaper an go fo a chinese cheaper mobile ..
Whats your opinion?
If nothing helped then I guess only a Jtag may fix it.
GDReaper said:
If nothing helped then I guess only a Jtag may fix it.
Click to expand...
Click to collapse
to do what? i mean Erase? flash trought jtag? repair something maybe?
leroi2 said:
to do what? i mean Erase? flash trought jtag? repair something maybe?
Click to expand...
Click to collapse
Jtag forces the software on the phone.
From my point of view, the phone is dead and you probably can't fix it without pro help or pro tools.
Hi, I might have messed up.
Took backup of all media, except that I'd forgotten that I also had a lot of photos saved as mms, directly in the messages. I'd also like to keep some of the messages, from my grandparents etc.
I'm stuck on "breathing" Samsung-logo.
I followed this recipe, as I've used it once before with success. Not this time though.
http://mobilesiri.com/galaxy-s7-edge-exynos-root/
I downloaded the auto-root from chainfire, but it might be outdatet?
https://download.chainfire.eu/930/CF-Root/CF-Auto-Root/CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip
I used Odin 3.12.3. Loaded the tar-file in AP.
Com + text comes up as good.
Started, and it came up as passed in a matter of seconds.
Phone turns off after a little while, and turn on again.
It won't go past the Samsung-logo when I power it on.
Safe-mode doesn't work, but it will go to download mode. I've tried wiping the cache, didn't help.
I might be mistaken, but could it be possible to flash stock rom from Odin, using this firmware: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935F/NEE/download/G935FXXU1DQJ2/193815/
It does look like it according to https://forum.xda-developers.com/showthread.php?t=2583588 and https://android.stackexchange.com/q...flashing-stock-rom-via-odin-delete-phone-data
If this isn't the case. Is it possible to install a recovery-program with Odin, even though the phone is "stuck"?
I've heard some people say it *might* be possible.
All the best, and thanks for any input
Chris
Well, I advice you to wait for second opinion, but I was in the same situation, for the exception I knew my current firmware details, re-downloaded the same firmware from sammobile and flash it with ODIN. Whatever firmware you flash, you must use HOME_CSC which is included in the zip package, not the "pure" CSC. Saying it again, it helped me, but I knew my current CSC (changing CSC triggers factory reset AFAIK) and factory reset wasn't made, so you should wait for second opinion before attempting anything. Good luck
MrYoan said:
Well, I advice you to wait for second opinion, but I was in the same situation, for the exception I knew my current firmware details, re-downloaded the same firmware from sammobile and flash it with ODIN. Whatever firmware you flash, you must use HOME_CSC which is included in the zip package, not the "pure" CSC. Saying it again, it helped me, but I knew my current CSC (changing CSC triggers factory reset AFAIK) and factory reset wasn't made, so you should wait for second opinion before attempting anything. Good luck
Click to expand...
Click to collapse
Thank you for replying MrYoan! I'm glad that you got your phone up and running again.
If anybody has a second opinon, I'd love to hear it.
Sorry if my text is too long/wrong etc.
Thanks again, Chris.
You need to put every file in, not just AP
tactical bacon said:
You need to put every file in, not just AP
Click to expand...
Click to collapse
Every file? The tmax.dll and zlib.dll?
The tutorial said only the AP?
Thanks for replying btw. This thing is driving me nuts.
ChrisSolt said:
Every file? The tmax.dll and zlib.dll?
The tutorial said only the AP?
Thanks for replying btw. This thing is driving me nuts.
Click to expand...
Click to collapse
You should have a folder with BL, AP, CP and CSC. Try redownloading the firmware from another site like sammobile
I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.
tactical bacon said:
You should have a folder with BL, AP, CP and CSC. Try redownloading the firmware from another site like sammobile
Click to expand...
Click to collapse
But only on the firmware one right? That one looks ok.
I thouth you were talking about the autoroot itself.
Thanks!
pufnasti said:
I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.
Click to expand...
Click to collapse
Could you tell me which app? The phone is non-responsive (except power + volup or voldown, etc.)
Thank you
anybody have any more input? I know it's busy with christmas and all, but it's really appreciated
pufnasti said:
I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.
Click to expand...
Click to collapse
How? Was your phone correctly rooted beforehand?