Hello everyone.
I installed CWM 5.0.2.6 and then Cyanogen mod 9 succesfully. Then I changed it to "MIUI TOCAi 0.1.4" and it was working fine although it could not find my network. I tried searching manually but without success (it kept on showing up that it's not able to register to the network im choosing and that i should try again later.) It had simlock before so I tryed to unlock it using this thread "http://forum.xda-developers.com/showthread.php?t=1204705". I got the code etc but I didnt know where to type it in. I turned the phone off and on hoping that the menu with this code request would pop out but it didnt so I replaced the sim card with another one. It still didnt pop out so I replaced it with the previous one and the phone bricked.
Im not able to get to CWM or to the system at all. Im only able to get to DL mode. I tried to unbrick it using this method "http://forum.xda-developers.com/showthread.php?t=1071970" and few similar ones. I used multi and single package but without success.
The simlock was for "3" network. Tryed O2 and Vodafone simcards.
Is there any way to unbrick it without going to the service?
I'm going to post youtube links to show you how it looks in just a few minutes.
Part 1 : http://www.youtube.com/watch?v=oNln0KJQ-0o&feature=youtu.be
Part 2 : http://www.youtube.com/watch?v=urRAhOq0OCw&feature=youtu.be
Part 3 : http://www.youtube.com/watch?v=EU-EshQdj7E&feature=youtu.be
Looks like your efs partition (either stl5 or bml5) got corrupted. This cannot be fixed by flashing roms or stock roms, since its a sepparate partition. Network Unlocking the ace might result in a brick specially if not done from stock firmware.
i bricked my gio after network unlock too, it was due to the efs partition being messed up, i couldnt get it to boot normally or recovery (screen flashes then dies) but download works, and odin didnt solve anything, so i sent it in to samsung and got a new gio
to sum it up, you now have a nice paperweight
Hi, I hope you guys can help me get this phone back to usable state. Recently I got a S4 Active i537 that was stuck on ATT logo, so I did a little research on how to restore the stock firmware to get it working again and came across with various threads; I finally downloaded the I537UCUBML2 stock rom and used Odin 3.07 to flash the files all worked fine except the BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar but th phone booted anyways so I thinked that was the end of my problems. But after putting a sim the phone did not get any signal so I checked the about screen on settings and found that the IMEI and BaseBand were blank.
I did another search to fix that and finally could make the imei and baseband came again by flashing the Modem.bin 50,791kb file found in the GPS IMEI FIX THREAD but after getting signal I realized the phone was completely muted and calls were not working, at first I believed it was a hardware problem but now Im pretty sure that it must be some software issue because it wont even play music, ringtones. When trying to open a mp3 it shows a message saying Unsupported.
Back when it was stuck on ATT logo it was making the att boot sound so Im pretty sure that the problem its in the software itself. Please help me find the correct rom/firmware to get it working again.
doryan.14 said:
Hi, I hope you guys can help me get this phone back to usable state. Recently I got a S4 Active i537 that was stuck on ATT logo, so I did a little research on how to restore the stock firmware to get it working again and came across with various threads; I finally downloaded the I537UCUBML2 stock rom and used Odin 3.07 to flash the files all worked fine except the BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar but th phone booted anyways so I thinked that was the end of my problems. But after putting a sim the phone did not get any signal so I checked the about screen on settings and found that the IMEI and BaseBand were blank.
I did another search to fix that and finally could make the imei and baseband came again by flashing the Modem.bin 50,791kb file found in the GPS IMEI FIX THREAD but after getting signal I realized the phone was completely muted and calls were not working, at first I believed it was a hardware problem but now Im pretty sure that it must be some software issue because it wont even play music, ringtones. When trying to open a mp3 it shows a message saying Unsupported.
Back when it was stuck on ATT logo it was making the att boot sound so Im pretty sure that the problem its in the software itself. Please help me find the correct rom/firmware to get it working again.
Click to expand...
Click to collapse
Flash the NE3 firmware so you'll be on 4.4.2 and see if that fixes things. If not, report back.
Would you please share the link to that? I don't want to mess this phone even worse by downloading wrong files. Thank you
doryan.14 said:
Would you please share the link to that? I don't want to mess this phone even worse by downloading wrong files. Thank you
Click to expand...
Click to collapse
It's stickied, you can't miss it.
http://forum.xda-developers.com/showthread.php?t=2892445
Im glad to announce that your advice worked like a charm! I used the 444 OTA file pushed with ADB and phone is now fully functional, rooted and region unlocked due to I'm in Central America. Thanks a lot and keep up you rock!
i really need help
my phone was a legit purchase but now all of a sudden the IMEI number is null and the phone does not have any network
through the day
sometimes it fixes itself and the network is available and the IMEI number is visible and all of a sudden it abruptly it goes null IMEI number and the network goes away
please help me how to fix this, I am facing this problem since 3 days
I have tried searching alot across this forum and others but no one seems to have a solution, please help!!!
Try re flashing kdz file
Sent from my Optimus 4X HD using XDA Free mobile app
Need Help "LOST IMEI and Baseband Unkonwn"
I was using Euporia 5.0.1 on LG 4x
I received update notification and I downloaded Update.zip ( which included to 5.1)
By mistake i flashed the zip directly from CWM ( without Formatting any partition )
after restarting there was no IMEI
Following things I have tried
1) Trying to flash Original V20C KDZ. via LG Flash Tool. ( I think it checks for IMEI , and that's why stuck in between)
2) Use LG Software Update tool. ( also can't progress with IMEI)
3) Flashed Original V20c Flashable zip from CWM (But it didn't restored my IMEI)
4) Contacted LG Service Center, and They say You need to change whole Motherboard. ( I was Shocked to know that )
:crying:
If anybody went to same problem. and resolved .
Please Guide me.
Jatin Patel said:
I was using Euporia 5.0.1 on LG 4x
I received update notification and I downloaded Update.zip ( which included to 5.1)
By mistake i flashed the zip directly from CWM ( without Formatting any partition )
after restarting there was no IMEI
Following things I have tried
1) Trying to flash Original V20C KDZ. via LG Flash Tool. ( I think it checks for IMEI , and that's why stuck in between)
2) Use LG Software Update tool. ( also can't progress with IMEI)
3) Flashed Original V20c Flashable zip from CWM (But it didn't restored my IMEI)
4) Contacted LG Service Center, and They say You need to change whole Motherboard. ( I was Shocked to know that )
:crying:
If anybody went to same problem. and resolved .
Please Guide me.
Click to expand...
Click to collapse
I dont think that fleshing update.zip had anything to do with losing IMEI since you cant update 5.01 to 5.1 without wiping u will just have many bugs but u wont brick u device.I think it is hardwer problem my friend on his lg 4x have similar problem (no IMEI and cant connect wifi to any network).
For the last month my wife has been using her new Tab S2 on WIFI only while vacationing abroad. Yesterday we got home and I inserted her sim into the tablet and she was able to connect via the LTE system and access the internet. This morning suddenly she could not access the internet via LTE. In the ABOUT tab the baseband is blank and the IMEI shows up as null. Nothing was installed nor were any updates received that I can tell. It seems clear that the EFS file is corrupted.
1. The information I have found (none of it from XDA) about repairing the problem all seem to assume a backup of the EFS file, which, of course I don't have.
2. Some require root, which I would prefer not to do, as the tablet is under warranty and don't want to void it.
3. There is an EFS Repair tool online, which is a bat file which tries to created a copy of the EFS file and then to have ODIN rewrite it. The backup phase fails with a message that there is no EFS file to backup. (It's not clear to me how backing up and then restoring a corrupt file would help anyway).
4. There is no access to the phones internal control panel via secret code, or the page that comes up is blank.
5. I tried a factory reset but it did not fix the problem.
Any help out there?
thanks
sblevine
sblevine said:
For the last month my wife has been using her new Tab S2 on WIFI only while vacationing abroad. Yesterday we got home and I inserted her sim into the tablet and she was able to connect via the LTE system and access the internet. This morning suddenly she could not access the internet via LTE. In the ABOUT tab the baseband is blank and the IMEI shows up as null. Nothing was installed nor were any updates received that I can tell. It seems clear that the EFS file is corrupted.
1. The information I have found (none of it from XDA) about repairing the problem all seem to assume a backup of the EFS file, which, of course I don't have.
2. Some require root, which I would prefer not to do, as the tablet is under warranty and don't want to void it.
3. There is an EFS Repair tool online, which is a bat file which tries to created a copy of the EFS file and then to have ODIN rewrite it. The backup phase fails with a message that there is no EFS file to backup. (It's not clear to me how backing up and then restoring a corrupt file would help anyway).
4. There is no access to the phones internal control panel via secret code, or the page that comes up is blank.
5. I tried a factory reset but it did not fix the problem.
Any help out there?
thanks
sblevine
Click to expand...
Click to collapse
Just flash rom on it via Oden it will not trip Knox as long as it is a stock rom
stinka318 said:
Just flash rom on it via Oden it will not trip Knox as long as it is a stock rom
Click to expand...
Click to collapse
reflashing did not fix it. The baseband is still unknown and the imei is still null. (I must admit I was wondering where the stock rom was going to get the IMEI from during flashing).
Any other ideas, please?
sblevine said:
reflashing did not fix it. The baseband is still unknown and the imei is still null. (I must admit I was wondering where the stock rom was going to get the IMEI from during flashing).
Any other ideas, please?
Click to expand...
Click to collapse
You may need to send it back to Samsung to get it fixed they will be able to pull a log cat and see what happened.
So I bought a refurb Note 4 and odin flashed it to latest marshmallow. Rooted/twrp and restored my image from my defective old one. Well everything worked except I lost my finger print sensor. So went to twrp and deleted
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Then I could get back into the phone, but still when trying to register fingerprint I get the error message and can't enter them. So I said fine, I will just odin flash stock and factory reset and start fresh. Well I have done that and the phone dialer *#0*# diagnostics sensor shows fingerprint reader as NULL, I lost the version # and all functionality. So I odin flashed the previous two stock T-mobile Note 4 images, factory reset and still even when starting from scratch now the fingerprint sensor is NULL and doesn't work. So I figured somehow I got a defective fingerprint scanner, I returned that phone, got another one that had kitkat and the fingerprint scanner worked. I flashed it to Marshmallow and now the same thing. I am pulling my hair out. How can software stock flash ruin my fingerprint sensor? How do I get it back? I am willing to flash any odin image/factory reset to do this and then just need to know what NOT to do so it doesn't happen again. There is no way both phones have a defective fingerprint scanner, so it is something that persists even AFTER an odin stock flash and factory reset?? Any help would be appreciated. The only other thing I noticed that I don't know what it means is on first boot it said something about no have DRK. Please flash ENG binary then install DRK. What is DRK? How do I install it, and will it get my fingerprint sensor working again?
Thanks in advance for any guru help.
P.S. I think the problem is I used my broken glass Note 4's twrp/nandroid image to restore the new phones, and I overwrote everything. My guess is the new phones where fingerprint sensors don't work have the old phones EFS, and I have no backup of the new phones EFS. I am only guessing this is the problem as I am newbish about EFS. I just don't see why I can't odin flash any version of T-mobile rom and get back to a REAL factory reset, not some partial one where things don't work. Help please.
hotstocks said:
So I bought a refurb Note 4 and odin flashed it to latest marshmallow. Rooted/twrp and restored my image from my defective old one. Well everything worked except I lost my finger print sensor. So went to twrp and deleted
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Then I could get back into the phone, but still when trying to register fingerprint I get the error message and can't enter them. So I said fine, I will just odin flash stock and factory reset and start fresh. Well I have done that and the phone dialer *#0*# diagnostics sensor shows fingerprint reader as NULL, I lost the version # and all functionality. So I odin flashed the previous two stock T-mobile Note 4 images, factory reset and still even when starting from scratch now the fingerprint sensor is NULL and doesn't work. So I figured somehow I got a defective fingerprint scanner, I returned that phone, got another one that had kitkat and the fingerprint scanner worked. I flashed it to Marshmallow and now the same thing. I am pulling my hair out. How can software stock flash ruin my fingerprint sensor? How do I get it back? I am willing to flash any odin image/factory reset to do this and then just need to know what NOT to do so it doesn't happen again. There is no way both phones have a defective fingerprint scanner, so it is something that persists even AFTER an odin stock flash and factory reset?? Any help would be appreciated. The only other thing I noticed that I don't know what it means is on first boot it said something about no have DRK. Please flash ENG binary then install DRK. What is DRK? How do I install it, and will it get my fingerprint sensor working again?
Thanks in advance for any guru help.
P.S. I think the problem is I used my broken glass Note 4's twrp/nandroid image to restore the new phones, and I overwrote everything. My guess is the new phones where fingerprint sensors don't work have the old phones EFS, and I have no backup of the new phones EFS. I am only guessing this is the problem as I am newbish about EFS. I just don't see why I can't odin flash any version of T-mobile rom and get back to a REAL factory reset, not some partial one where things don't work. Help please.
Click to expand...
Click to collapse
Flash n910t2 kitkat firmware in odin this will work 100% with n910t have a look post below.
http://forum.xda-developers.com/not...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
Once flash firmware do wipe data factory reset and wipe cache
Once finish setup at homescreen let the phone rest for few minutes then reboot
Next go check fingerprint scanner.
Once it works go ahead and flash regular n910t marshmallow firmware.
Drk is ( device root key ) i believe your device is rooted before and efs partition+imei is modified and when you tried to flash official firmware things went wrong somehow.and i don't see any working method to fix drk the only fix for drk is replace entire motherboard.
Download link for n910t2 firmware link below
https://mega.nz/#!bZ8nFIaA!u67ewIWGe8HRtI8-OdxFUPoXFvpACIKhtQtbnv7KU18
If this method does not work go ahead and download n910t 5.1 1 repair firmware with pit file from www.tsar3000.com and flash with pit file maybe it will work.and then go take ota update of marshmallow.
My best suggestion will be get rid of this device now dont waste your time and money and get new device instead of refurbished.
report back please.
First method didn't get fingerprint scanner back. And I cant find the n910t 5.1 1 repair firmware with pit file from www.tsar3000.com could you please link me to that file so I can try method #2?
Also is there anything special I should do in Odin like check boxes for Nand Erase All or Phone EFS Clear?? RE-partition? Anything that would get this back to completely erased and stock so fingerprint sensor software gets re-installed. in dialer *#0*# sensor fingerprint it went to null when it used to say a version, so wherever that software for the fingerprint scanner is stored is where my problem is.
Thanks
I found the pit file elsewhere. Can I use that pit file with the firmware I just flashed, and if so how? Or do I need to find the www.tsar3000.com n910t 5.11 repair firmware, because I can't find it anywhere on their site or I am just stupid? Please link to it and instructions, never flashed a pit.
Well I managed to get the pit and firmware to flash in an older odin, newer ones failed. But still when you dialpad *#0*# and go to sensors and down to bottom where finger print scanner is, it says NULL instead of a version and the test doesnt work. When you go to fingerprint scanner in the phone to register fingerprints it just keeps saying Attention an error has occured with fingerprint sensor, reboot.
I find it impossible to believe that there is no way to get the fingerprint sensor software/test back. I have done this on two phones so I KNOW the fingerprint sensor hardware works. Some bad EFS or rom flash lost the fingerprint sensor software and there must be a way to get it back. There is nothing wrong with the hardware of these two phones, it happened on a 910T and 910T3 both due to TWRP restoration of all checked boxes. Please help, I can flash anything from odin or twrp, SOMETHING has to re-install the fingerprint sensor software/dialer sensor info.
I also heard that the Samsung Experience at some Best Buy stores could fix these kind of issues, like they have a machine to REALLY overwrite all of the phone or something? I just don't see how odin flahing the firmware wouldn't do that, unless I need to check that Nand erase box or do something else? Please help or let me know if Best Buy kiosk is worth a shot.
hotstocks said:
I also heard that the Samsung Experience at some Best Buy stores could fix these kind of issues, like they have a machine to REALLY overwrite all of the phone or something? I just don't see how odin flahing the firmware wouldn't do that, unless I need to check that Nand erase box or do something else? Please help or let me know if Best Buy kiosk is worth a shot.
Click to expand...
Click to collapse
Sorry but tsar3000 removed n910t repair firmware
I'll give you pit file for 6.0.1 marshmallow
Flash 6.0.1 firmware with pit file in odin choose nand erase all
Choose pit file in pit tab in odin as in screenshot below.
But i highly suggest you return this device.
Good luck
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Trex888 said:
Flash n910t2 kitkat firmware in odin this will work 100% with n910t have a look post below.
http://forum.xda-developers.com/not...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
Once flash firmware do wipe data factory reset and wipe cache
Once finish setup at homescreen let the phone rest for few minutes then reboot
Next go check fingerprint scanner.
Once it works go ahead and flash regular n910t marshmallow firmware.
Drk is ( device root key ) i believe your device is rooted before and efs partition+imei is modified and when you tried to flash official firmware things went wrong somehow.and i don't see any working method to fix drk the only fix for drk is replace entire motherboard.
Download link for n910t2 firmware link below
https://mega.nz/#!bZ8nFIaA!u67ewIWGe8HRtI8-OdxFUPoXFvpACIKhtQtbnv7KU18
If this method does not work go ahead and download n910t 5.1 1 repair firmware with pit file from www.tsar3000.com and flash with pit file maybe it will work.and then go take ota update of marshmallow.
My best suggestion will be get rid of this device now dont waste your time and money and get new device instead of refurbished.
report back please.
Click to expand...
Click to collapse
Trex888 said:
Sorry but tsar3000 removed n910t repair firmware
I'll give you pit file for 6.0.1 marshmallow
Flash 6.0.1 firmware with pit file in odin choose nand erase all
Choose pit file in pit tab in odin as in screenshot below.
But i highly suggest you return this device.
Good luck
https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
Click to expand...
Click to collapse
Thanks I will try that. As far as returning it, I really can't and I got it for a great deal $150 and it is literally brand new, the screen is perfect, ect. I somehow was an idiot and used my old twrp file to flash the new phone because I didn't want to re-set up everything. Well I checked every box in twrp for the backup and restore. Even though they are the same exact model phone I think it somehow did something to the fingerprint scanner firmware and I still can't figure out why it won't come back. I tried it with two seperate phones that both did this, but other than the fingerprint scanner not working the phone is mint and runs perfectly, any rom. I will probably just keep it without fingerprint sensor if we can't figure this out, it is not like I even use it and this is my backup phone (have an LG V20). It is very annoying, but mainly because it should just work and doesn't. There is no way a flash can fry a fingerprint scanner and make it's software disappear, but this happened twice on two different phones after I did the twrp restore from my previous Note 4 T with all boxes checked. I didn't know you shouldn't check all backup boxes in twrp. Nevertheless it should go back to factory and isn't. GRRR
P.S. I'm wondering if flashing some other totally modified rom would install the fingerprint software again, maybe something like cyanogen? I have been out of rom flashing scene. If you think any might please link me.
I found this, and it seems to be the fix for my problem, except I don't understand step 5 (and obviously I have a N910T and N910T3 to fix) also SmartSwitch just freezes, you can never flash anything with it, so I will use Odin for that, I assume it does the same thing. Still haven't got the fingerprint sensor back and have done everything but step 5. Any other ideas or explanation of step 5 would help. Thanks.
Found a solution if anyone ever stumbles across this thread.
How it happened:
I did a full Twrp backup, including EFS on a n910T. I received a replacement n910t. I thought I could restore the twrp backup from the old straight to the new n910t. I was wrong. EFS is device depending and contains the individual phone info like imei,S/N,etc. Basically my new phone took characteristics of the old one and the EFS became corrupted. My fingerprint sensor didn't work and I had the "dm-vertiy verification failed. If the dm-verity fails, finger print sensor won't work.
How I repaired my EFS, or what I did to get it to work. Your mileage may vary.
All of this on stock rom: I got the stock from by using smart-switch and doing emergency recovery, entering my model number and serial number. I then cf rooted and flashed twrp using odin.
1. I check to make sure my IMEI and S/N numbers stored in the phone (about device) matched the sticker on the back. My IMEI matched but my S/N did not. My S/N was from my old phone, big whoops!
2. I corrected my S/N by editing the serial number file found under your EFS folder. You need root access to edit it. I use room toolbox lite, root browser to edit it.
3. Because my EFS became corrupted, my phone was in limp mode, eg it was slow and lagging, it was stuck in "factory mode".
4. I took the phone out of factory mode. Again you need root access and root browser. Go to EFS folder/factoryapp/factorymode and edit the file. Change it to off. Also go to efs folder/factoryapp/keystry and turn it off also. Reboot.
5. I entered this command:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
6. Do a factory reset, reboot system
7. I then did a stock firmware flash again with smart-switch. Everything works again now. This time I will make sure I back up my efs but don't try to restore it.
Can someone with a T-Mobile Galaxy Note 4 N910T3 that has a TWRP backup INCLUDING the EFS please upload that and give me a link. I screwed up my EFS and if someone with the same phone could please make and upload their TWRP backup (just with EFS box checked very small and not your data) for me it would be greatly appreciated. I know I will have to go into it and edit my serial # from yours, but it should get me back working.
Thanks
hotstocks said:
Can someone with a T-Mobile Galaxy Note 4 N910T3 that has a TWRP backup INCLUDING the EFS please upload that and give me a link. I screwed up my EFS and if someone with the same phone could please make and upload their TWRP backup (just with EFS box checked very small and not your data) for me it would be greatly appreciated. I know I will have to go into it and edit my serial # from yours, but it should get me back working.
Thanks
Click to expand...
Click to collapse
Efs backup from another device will never work because it's related to your phone's specific hardware.
You did big mistake that you flash backup and efs from old phone to new one that completely screw up your efs partitions and drk ( device root key ).
Sorry but you should make always efs backup from twrp in microsd card before start messing with phone. Cuz flashing always risky job.
Trust me odin or twrp will not going to help you.
Dont waste your time You should go to repair center cuz they have tools like dongle box to fix efs and imei.
They will write new cert files and restore your efs but i dont think they can fix drk cuz i see many drk damage cases but didn't see any working method unless changing entire motherboard.
Thank you. I have been doing a lot of research, and an EFS TWRP file from the same exact model N910T3 would work if I flashed it and then went in and edited that serial # to my phone's serial #. It sucks that I did not have a backup of EFS in TWRP and now no matter what rom I flash, wipe, ect, I can not get my fingerprint sensor back. In dialer *#0*# sensor it went to NULL from a version and it doesn't work at all, just get the error when trying to register fingerprints. I read that someone fixed this exact problem by getting a TWRP of just the EFS, flashing it, then editing the serial #'s, so I wanted to try that. But need a TWRP EFS uploaded for N910T3 as I can not find one anywhere. Unless you have another idea. I mean the phone works fine other than the lack of fingerprint sensor, but I think it is also in no verity and factory mode whatever that means. I posted the fix above that worked for someone, but once again I don't have the TWRP EFS and I don't understand how to do part 5. There has to be a way to either entirely wipe everything including EFS and getting my phone back to factory new thru Odin or TWRP flashing an EFS and changing serial # to my sticker # so I can get the damn fingerprint sensor working. I think the problem is I have a N910T EFS on my N910T3 which allows everything to work except fingerprint sensor.
Trex888 said:
Efs backup from another device will never work because it's related to your phone's specific hardware.
You did big mistake that you flash backup and efs from old phone to new one that completely screw up your efs partitions and drk ( device root key ).
Sorry but you should make always efs backup from twrp in microsd card before start messing with phone. Cuz flashing always risky job.
Trust me odin or twrp will not going to help you.
Dont waste your time You should go to repair center cuz they have tools like dongle box to fix efs and imei.
They will write new cert files and restore your efs but i dont think they can fix drk cuz i see many drk damage cases but didn't see any working method unless changing entire motherboard.
Click to expand...
Click to collapse
Thanks. What is DRK and if I go to repair center does it even matter if they can't fix drk but they get the fingerprint sensor working with new EFS dongle? Also are you talking about a local T-mobile store or some Samsung repair center that I have to mail the phone to and pay a lot? Can you link me to repair center in USA Michigan or how to find one? Thanks again
Sorry i dont live in usa no ideas
if you have warranty you go to samsung or go to any local repair shop.
Tell them all issues and hopefully they will fix.