Related
Hi, I urgently need help,
I was just watching something when I kept hearing a strange noise, turns out it is the vibrate that the phone does when you turn it on, I looked at it and it was on the Google logo and kept restarting, tried a battery pull, taking sim out etc, and it's still doing it.
I have no idea why it's doing this as I haven't rooted or installed any custom roms or anything?!
I have an interview tomorrow in London and really need to have Google Maps etc, as well as being able to contact people I'm supposed to be meeting! I can't believe this has happened at all, let alone at this moment!
Edit - I'm using the GSM version, running 4.0.1.
Thanks in advance
Bump..
There is something called odin which you can use to flash the stock rom, is that correct? Or fastboot?
I suppose what I want to know, is if you can flash the stock image without being rooted/having an unlocked bootloader? And does it have to be a certain image file?
Hey
case0 said:
Bump..
There is something called odin which you can use to flash the stock rom, is that correct? Or fastboot?
I suppose what I want to know, is if you can flash the stock image without being rooted/having an unlocked bootloader? And does it have to be a certain image file?
Click to expand...
Click to collapse
You can used odin to load a stock image and it will return the phone to the day you got it. You can also use the adb/fastboot method. Search the forums here and you will find very clear instructions for both methods.
Same happened to me a while back and was easy to fix.
Good luck.
Ok thanks!
Edit- Ok I fixed it with the ODIN method, instructions here - http://forum.xda-developers.com/showpost.php?p=20302409&postcount=2
So glad I don't have to send it to get repaired, bit pissed off I lost some of my pictures and stuff (I was 30% through GTA III!) but what can you do I guess! At least I have a working phone again
I've done some searching and I haven't found any problems like mine yet. I ran the SGS unlock tool meant for Vibrant on my SGS2 (i know i know) and it didn't work. Ever since my touch keys don't work. I just reflashed my rom and they still don't work.. help!
PS. I'm odining now. Hopefully that'll fix it.
Crap crap crap crap crap odin didn't fix it.
Try entering *#*#2663#*#* in the dialer. It should reset the touch firmware.
http://forum.xda-developers.com/showthread.php?t=1308406
one5 said:
Try entering *#*#2663#*#* in the dialer. It should reset the touch firmware.
http://forum.xda-developers.com/showthread.php?t=1308406
Click to expand...
Click to collapse
Thank you, sadly the phone is bricked now.. lol
Real sorry, I should have tried it first. Can you still get into download mode?
one5 said:
Real sorry, I should have tried it first. Can you still get into download mode?
Click to expand...
Click to collapse
I'm so sorry! I didn't mean to imply that what you suggested bricked it. I had a bad odin flash that bricked it. I bet your information is great, I just wish I had it sooner! Thank you
Tynen said:
I'm so sorry! I didn't mean to imply that what you suggested bricked it. I had a bad odin flash that bricked it. I bet your information is great, I just wish I had it sooner! Thank you
Click to expand...
Click to collapse
dude, did you unbrick your phone yet ?
I got mine solved by inputting
*#*#86824#*#*
and press update firmware.
credit goes to Memeber - ecips
If anyone is reading this and their soft keys don't work, its a corrupt efs issue. Flash my fix to resolve it
my s2 touch keys wont work
icenight89 said:
If anyone is reading this and their soft keys don't work, its a corrupt efs issue. Flash my fix to resolve it
Click to expand...
Click to collapse
my Galaxy S2 touch keys wont work and it is stock, I did occational app dl from market but I WASNT ROOTED or ANYTHING, HELP PLZ
Jinseiganai said:
my Galaxy S2 touch keys wont work and it is stock, I did occational app dl from market but I WASNT ROOTED or ANYTHING, HELP PLZ
Click to expand...
Click to collapse
I ended up having to replace the hardware touch keys. It was a long time ago that I did this. It was a member of the community that I sent it to, he was really helpful and quite quick. I literally couldn't figure out any other way to fix this problem! The SGS2 community may have a solution by now. But I haven't had my SGS2 for a while.
Hi all,
First of all i would like to inform you that this is my first ever post on this forum... or any other forum for that matter. I have an issue on my mobiel device.
This morning I installed original firmware update on my samsung galaxy note 2.
The menu and back buttons have stopped working ever since I installed the official android 4.3 firmware update.
Other than this issue I have not yet encountered any other problems.
Can any one help or give suggestion on how I can fix this issue? And thus make the device's buttons work again?
Thanks alot
Try factory reset than report if problem still occurs...
buttons are not working
ubabic said:
Try factory reset than report if problem still occurs...
Click to expand...
Click to collapse
Also i have same problem. After 4.3 update via OTA my phones buttns are not working. I tried factory reset from setting and from recovery menu but it didn' t make sense. After that i tried to reinstall update from kies also it is not sense. Could you help us please. My phone has United Arab Emirates rom
I think i'm going to send the phone to service for repairs.
By the way i might try to flash 4.3 via ODIN, do you think it may cause any problems or trigger knox counter.
Can you please advise?
clevent said:
I think i'm going to send the phone to service for repairs.
By the way i might try to flash 4.3 via ODIN, do you think it may cause any problems or trigger knox counter.
Can you please advise?
Click to expand...
Click to collapse
Official firmware flashing doesn't trigger knox counter
dear all;
I reflash the official 4.3 rom via odin, but capacitive buttons still not working.
Could you help me urgently for this reason?
helpppppppppp
55845535225
we didn't find any solution for this and nobody help me
pawlu88 said:
Hi all,
First of all i would like to inform you that this is my first ever post on this forum... or any other forum for that matter. I have an issue on my mobiel device.
This morning I installed original firmware update on my samsung galaxy note 2.
The menu and back buttons have stopped working ever since I installed the official android 4.3 firmware update.
Other than this issue I have not yet encountered any other problems.
Can any one help or give suggestion on how I can fix this issue? And thus make the device's buttons work again?
Thanks alot
Click to expand...
Click to collapse
First i tried to flash with another official rom via ODIN, but nothing change, after that i tried to flash with leakage rom for return to 4.1.2 but my phone gave DEVICE UNSUPPORTED error.
Could anybody help me for my problem
Once u get the official, u will get the bootloader as well.
With the new bootloader, u r unable to downgrade in a normal way via odin.
But I did few updates on several N7105 through OTA, and nver got problems with capacitive touch.
Sent from SM-N9005 with xda-app
ring samsung
I was going to say do a factory reset but that was mentioned above. before I take my phone ever to Samsung service center call Samsung tech support in your country. when I first got into rooting my phone and modifying it I got into a few small problems such as yourself and I posted on forums but did not have the patience to wait so I ring Samsung and speak to tech support and always got the problem fixed. give it a go, you got nothing to loose
shotgun1976 said:
I was going to say do a factory reset but hat was mentioned above. before I take my phone ever to Samsung service center call Samsung tech support in your country. when I first got into rooting my phone and modifying it I got into a few small problems such as yourself and I posted on forums but did not have the patience to wait so I ring Samsung and speak to tech support and always got the problem fixed. give it a go, you got nothing to loose
Click to expand...
Click to collapse
Yes you are correct but in my country warranty system is different. My phone has other companies warranty. So when i call them they said sent yiur phone to our service. But i think they are not very experience for this issue and they can say this is customer mistake your phones buttons get a damage. Therefore i m sure this is software problem and i m waiting an answer from here. If nobody can find a solution for my problem as a last solution i should sen my phone to service
Up
clevent said:
Up
Click to expand...
Click to collapse
Have you tried wiping the cache?
devcon69 said:
Have you tried wiping the cache?
Click to expand...
Click to collapse
yes i tried but problem continue 10 days ago sent my phone to service and i m waiting service answer
Hey guyz....I have the same problem....got my update throw OTA the menu and back buttons didnt work tried flashing throw pc odin, mobile odin and anything u could imagine and didnt work.....downgraded to 4.1.2 rooted thats the only solution right now for the buttons to work.....I hope its fixed soon....please if u find anything dont hesitate to post thank u so much
P.s. : my note 2 running UAE XSG
Have a nice day
I can't download the 4.1.2 official ROM
I tried to download the brazilian rom ZTO at sammobile, but the rom is too big for free download at terafiles... A torrent address could help me so much...
Hi all
Service send my phone and buttons are working. But they downgrade my phone to4.1.2 and update section is deactive, know has a flag
After that i tried to install other 4.3 roms custom or stock but when i installed, i saw same button not working problem.
And also tried 4.4 rom but buttons are working. I think my phone has some problem about 4.3 system.
Now i want to use ditto or like that rom but i see same problem in these roms, could you give me some advice about solution of this problem
clevent said:
Hi all
Service send my phone and buttons are working. But they downgrade my phone to4.1.2 and update section is deactive, know has a flag
After that i tried to install other 4.3 roms custom or stock but when i installed, i saw same button not working problem.
And also tried 4.4 rom but buttons are working. I think my phone has some problem about 4.3 system.
Now i want to use ditto or like that rom but i see same problem in these roms, could you give me some advice about solution of this problem
Click to expand...
Click to collapse
Try this app, it will not fix the problem but will enable you to use the phone without problems. You may even do so with minimal loss of display space by making buttons overlay the actual display and making them semi transparent.
mat9v said:
Try this app, it will not fix the problem but will enable you to use the phone without problems. You may even do so with minimal loss of display space by making buttons overlay the actual display and making them semi transparent.
Click to expand...
Click to collapse
Thanks for your reply, but i do not like this kind of buttons.
I want to solve my problem with any software correction. Because it seems only 4.3 os problem and if i don' t find any solution for 4.3 i will wait kitkat updatefor note 2
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
My stock rom I made doesn't have that problem, my wife records my kidz all the time, no issues... try wiping if you left your data, I always wipe all data before upgrading to any rom...
check my signature or in the Tmobile development thread.. completely stock...
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.
chetancc said:
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.
Click to expand...
Click to collapse
I have the same issue. Wiped the entire phone including internal sdcard, went back to stock firmware but nothing worked. Taking pictures works but as soon as press the record button it freezes and a few seconds later the phone will reboot.
Just to let you guy know what I am sure is going on, this video recording damage has been caused by none other than aosp! if you all have previously installed liquid smooth like I did in 3 separate devices
1.tmo s4
And 2 note 3's (one is tmo and one is sprint) I think it is any asop although each person having this damage to their device should answer if they previously installed aosp and specifically liquid smooth.
I was going to assume this damage was only going to happen on tmo note 3, so I tested it on 2 other phones and sure enough they must be forced to remain running asop (the s4 has candy 5) the sprint note 3 currently has the ever so bugging liquid smooth. I also have tried every clean Odin delete everything known to us layman's on the planet and now I am looking for a NV restore. I already tried so sort of a NV item restore Using the dialer *#9090# then pressing Q and then pressing 0000 then option 2,1,2,3 then all with no change. I read somewhere in the xda's grapevine lol about a flash able zip called "Brick_Loop_FIX_afterRestoringBackup" that starts an built in feature that restores or rebuilds the modem then upon boot restores the NV items. I am assuming they are the same thing. Although, with no thought it will fix anything I will flash the zip tomorrow and let you know. I got a couple things to back up incase whatever may happen capin, unless one of you guys try it first, let me know
Haven't heard from the grapevine what protocol, ims or a static rebuild even does except if your imei is all zeros and your don't have any network or stuck in a boot loop after a nandroiid restore I erpose this will fix those couple thing I have read. Although I assume the dialer hidden menu NV rebuild does not really NV rebuild all like it says it does or the all its referring to is really just the first 2 options that are just a couple basic stuffs or it would have fixed my aosp camera damage. Well never listen to anyone who says aosp is all the rave and how you should try it out lol its blackmail to get you to stay on a bugged out ROM forever! LOL
jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
I had this same exact problem and i fixed it finally after hours of research and trial and error. I noticed that my baseband and bootloader was Nb4 even tho i had flashed lollipop, so i ended up flashing stock lollipop using odin from http://forum.xda-developers.com/note-3-tmobile/general/5-0-n900tuvufob6-extracted-stock-t3047672 then after flashing i downloaded the lollipop bootloader and used odin 3.09 to flash that bootloader in BL, and the modem in ap, video camera works now and youtube has been fixed also.
How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.
revized said:
How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.
Click to expand...
Click to collapse
Try https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
it tells everything including bootloader version
OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!
revized said:
OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!
Click to expand...
Click to collapse
yeah cool let me know please if it helps!! this was the main reason i had flashed back to kitkat so many times.
I recently flashed an FM Radio app on my Note 3 (rooted SM-N900T w/CM 12.1), flashed without issue but ever since then I do not have sound through my earpiece. I am unable to take calls unless I use a headset or use the speakerphone. I have already wiped and reflashed, not only CM 12.1 again, but have also done a full factory reset and flashed stock as well but the problem persists. Anyone have a clue to get the sound back in the earpiece? This is driving me up the wall!
gimik28 said:
I recently flashed an FM Radio app on my Note 3 (rooted SM-N900T w/CM 12.1), flashed without issue but ever since then I do not have sound through my earpiece. I am unable to take calls unless I use a headset or use the speakerphone. I have already wiped and reflashed, not only CM 12.1 again, but have also done a full factory reset and flashed stock as well but the problem persists. Anyone have a clue to get the sound back in the earpiece? This is driving me up the wall!
Click to expand...
Click to collapse
Not sure if you've resolved the issue yet, but I'll try to help if you haven't. You could try formatting everything in recovery instead of just wiping. Format all except your external sd of course, and then try to flash a ROM. If that doesn't work you'll probably need to use Odin to flash stock firmware and re-root and so forth. That should definitely clear up the issue if simply formatting and flashing a ROM doesn't work.
For future reference, do not flash any FM apps. It probably messes up the drivers and the apps won't work correctly for us at the moment regardless. Our N900T has an FM chip but it's not active at the moment. However, our team is currently trying to find a driver to get it functioning.
Sent from my SM-N920T using Tapatalk
ludeawakening said:
Not sure if you've resolved the issue yet, but I'll try to help if you haven't. You could try formatting everything in recovery instead of just wiping. Format all except your external sd of course, and then try to flash a ROM. If that doesn't work you'll probably need to use Odin to flash stock firmware and re-root and so forth. That should definitely clear up the issue if simply formatting and flashing a ROM doesn't work.
For future reference, do not flash any FM apps. It probably messes up the drivers and the apps won't work correctly for us at the moment regardless. Our N900T has an FM chip but it's not active at the moment. However, our team is currently trying to find a driver to get it functioning.
Click to expand...
Click to collapse
Hello and thank you for the reply, this issue is still very much unresolved so your help is much appreciated! I have already tried using Odin to flash stock firmware to no avail, the problem still persists, however I will certainly try formatting everything in recovery and hopefully that'll clear things up, that didn't even dawn on me to try. Thank you for the suggestion, I will report back my results here. And absolutely will NOT be flashing any FM apps in the near future! :laugh:
gimik28 said:
Hello and thank you for the reply, this issue is still very much unresolved so your help is much appreciated! I have already tried using Odin to flash stock firmware to no avail, the problem still persists, however I will certainly try formatting everything in recovery and hopefully that'll clear things up, that didn't even dawn on me to try. Thank you for the suggestion, I will report back my results here. And absolutely will NOT be flashing any FM apps in the near future! [emoji23]
Click to expand...
Click to collapse
Ah man... that doesn't sound good if Odin didn't fix it. No pun intended. Lol
Yeah hopefully formatting will do the trick. If not it almost seems like a hardware issue and the speaker actually went out. Using Odin and stock firmware should flash back all the correct drivers.
Sent from my SM-N920T using Tapatalk
ludeawakening said:
Ah man... that doesn't sound good if Odin didn't fix it. No pun intended. Lol
Yeah hopefully formatting will do the trick. If not it almost seems like a hardware issue and the speaker actually went out. Using Odin and stock firmware should flash back all the correct drivers.
Click to expand...
Click to collapse
I had such high hopes for the formatting but unfortunately it did not work. I formatted everything in recovery and used Odin to reinstall stock but the problem persists. I can't imagine the FM app killing the earpiece as it worked prior to flashing the F'n thing but I guess I'm stuck to using a headset! If you have any other suggestions let me know. :good:
gimik28 said:
I had such high hopes for the formatting but unfortunately it did not work. I formatted everything in recovery and used Odin to reinstall stock but the problem persists. I can't imagine the FM app killing the earpiece as it worked prior to flashing the F'n thing but I guess I'm stuck to using a headset! If you have any other suggestions let me know. :good:
Click to expand...
Click to collapse
I personally don't know of anything else to do. You've gone through all the steps to fix it I believe. Like I said, it does sound like a hardware problem now.
Sent from my SM-N920T using Tapatalk