No audio comes across speaker while playing music, etc.. Microphone also only works in a call. Google Now, etc. can't hear me talk.
I've tried different firmwares(via odin), kernels, and roms. No luck. Tried on both Lollipop and Marsh mellow. Anyone seen anything like this or have any ideas on solution? I figure its got to be software related since the speaker/mic work in the phone app once a call is initiated.
TeamHackura said:
No audio comes across speaker while playing music, etc.. Microphone also only works in a call. Google Now, etc. can't hear me talk.
I've tried different firmwares(via odin), kernels, and roms. No luck. Tried on both Lollipop and Marsh mellow. Anyone seen anything like this or have any ideas on solution? I figure its got to be software related since the speaker/mic work in the phone app once a call is initiated.
Click to expand...
Click to collapse
Well, you can start by telling us the model of your device (some people post in the wrong place)
We also need to know the firmware versions you've tried and what you wiped, if you wiped, kernels, mods, roms....etc.
Odin to stock. Factory reset.
N920T. I tried latest official Odin and T-Mobile leak from November i think. Updated bootloader and all. Which exact firmware do you think I should try? Forgot what I bought it with.
Sent from my SM-N920T using Tapatalk
Aoge
flashes in odin failing. keeps returning with SW REV CHECK FAIL DEVICE:2 BINARY:1
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
TeamHackura said:
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
Click to expand...
Click to collapse
Yes it is.. and you can get the bootloader only in a thread somewhere around here ..just Google cokc boooader
TeamHackura said:
tried smartswitch, odin, and klies, flashing firmwares the whole time. tried all tmo ones. i think error is due to me updating bootloader to MM. Is it possible to downgrade BL?
Click to expand...
Click to collapse
You still haven't said if it's rooted or has a custom rom, custom recovery or anything. We can't help you unless you give us the information we need.
Do you have a custom recovery installed?
Sent from my SM-N920T using Tapatalk
So i have pretty ,muc h flashed every single TAR, ZIP, ROM, Kernel, etc. that can be flashed. I just bought a Nexus 6P and now i figured out the issue. After flashing Roever loco rom i forgot to install a small app used to control one of those headphone plug button things. without app it makes it think it has headphones plugged in without actually stating such. pulled out the headphone button thing and all is well. thanks guys.
Related
HI,
I've updated the Verizon version of the Galaxy Note Pro 12.2 and I really don't like it. There's too many instability issues that I haven't seen before! I rely heavily on the S-Note and it keeps crashing on me after a few minutes when it is opened up. I can write for a bit but then it just stops working and brings me back to the home screen. The other problem is the SD Card. I never had an issue with it before, but I am now! Sometimes it goes missing when I go into a file manager looking for a document. And it occasionally freezes up!
Oh, and the best part? I like the fact that Samsung has added the "Galaxy Apps" in this Lollipop version like it is on my Galaxy Note 4 (SM-N910F), BUT IT'S ALL IN DUTCH LANGUAGE!!!
And this is suppose to be an American model with the preference language set US English?? Go figure...
I never had this problem before with KitKat 4.4.2, and I want it back!
Now I've tried using ODIN 3.10.7, 3.07, and 3.09, but I can't get it to connect. It keeps saying "added!! removed!!" when I try to use Home-Volume Down-Power" to reboot in Odin mode.
So does anyone have any suggestions on how I can downgrade?
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
tdetroit said:
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
Click to expand...
Click to collapse
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
sjbrother said:
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
Click to expand...
Click to collapse
Did you ever get this figured out? I, myself, am having a terrible time with the lollipop upgrade on my 905V. I've tried to ODIN back to 4.2.2 with no luck. ODIN fails every time I try to push one of the older versions to the tablet.
I am like you where I had to use ODIN to upgrade to 5.1.1. I was rooted and I had done a few other things which required me to factory reset a couple times after using ODIN to install an original factory package.
It is possible we are S.O.L. There is simply no DEV support for a device few people have, I don't expect much.
My only shot to try next is to see if putting one of the older versions in a specific folder will give me an option in Kies to revert back.
There is always a chance someone will come along with the answer we need.
Lollipop haywire
I to have the Verizon Note Pro and recently did the update to lollipop and is having a horrible experience... The system seems to be unstable all my apps are crashing a lot... Ive tried to revert back to 4.2.2 using Odin as well but no luck. Ive factory reset numerous times... Ive even reinstalled lollipop several times, with no luck. If any one has any insight on what this problem is or have anyway of going about fixing the crashing, please let me know...
Has this ever been figured out? When I first got my NP 12.2 on verizon I rooted it, but then I OTA updated it, like a dummy, to 5.1.1. I want to flash back down to 4.4 or whatever version it WAS so I can root 4.4 then update to a 5.1.1 or 6.0.1 rooted rom. * Any help would be appreciated.
In the same boat
Any help on this? I would really like to downgrade my NP12.2 to Kitkat to root it.
I pretty much a novice to Android, but have 20+ years with PC and MAC. This doesn't seem like it should be that big of a deal. Thanks for any help!
I've had an issue with the headset jack on my G930F that I've been trying to diagnose with no luck.
The symptoms:
* Using regular headphones I get no sound from the headset jeck. Doesn't matter what set I use, and I've checked all sets in other devices.
* Using the Samsung headphones with a mic that come with the phone, I get sound as long as the volume is set below about 1/3 of the total volume range.
* Above 1/3 volume, the sound immediately goes to static, and often the phone thinks I've pressed the button on the microphone for voice input.
The history:
* I just purchased this phone off eBay a few weeks ago. It was in near perfect stock condition. No scratches, rub marks, or anything else.
* I immediately started trying root and different ROMs on it. Ended up with SuperStock Kernel and SuperStock ROM with a US AT&T CSC before discovering the headset issue.
* Does not appear to be any physical issues with headphone jack. I get a very solid click as any headphone jack is put in. No lint or anything inside the jack. Plugs appear to be fully inserted into the jack.
* The fact I can get some sound at low volumes would indicate to me that's it's a software issue of some sort, though that doesn't explain why a standard headset without a microphone doesn't work.
* None of the equalizer settings seem to change anything.
* I've tried backing up the phone and completely resetting it to stock firmware, even going back to the earliest version of Nougat that I could find. Behavior is exactly the same. Tried to go back to Mashmallow ROM's, but no luck downgrading further.
Has anyone else had a similar issues with headphone audio? Are there any other settings or software that I could try? I've returned to SuperStock ROM and Kernel, so root isn't an issue.
I know the headset jack is relatively easy to repair, but I'm hesitant to open the otherwise mint condition phone for that if I don't know if will fix the issue.
Thanks,
Jason
How were you resetting the firmware? All 4 firmware files (BP, CSC, AP, CP) via Odin?
I know that having a bootloader firmware version that doesn't match your Android version can cause various sound issues.
Beanvee7 said:
How were you resetting the firmware? All 4 firmware files (BP, CSC, AP, CP) via Odin?
I know that having a bootloader firmware version that doesn't match your Android version can cause various sound issues.
Click to expand...
Click to collapse
Yeah, grabbed the official versions with the original BTU CSC and updated all the firmware files with Odin. No luck on the headphone sound. Is there a block on going back to Marshmallow once a phone has been updated to Nougat?
When I change back to the Superstock Kernel and ROM, I install TWRP and then use the Aroma installer to put in the newest BP and CP with the ROM, then use the CSC Select tool to change the CSC to US AT&T, and finally restore a backup of the original EFS partition.
Nah no limits, I've gone between MM and N and back a few times. Updato.com as all the versions with all firmware files if you want to roll back.
Beanvee7 said:
Nah no limits, I've gone between MM and N and back a few times. Updato.com as all the versions with all firmware files if you want to roll back.
Click to expand...
Click to collapse
Hmmm....odd. I kept getting errors in Odin when I tried the version of MM that I grabbed from sammobile.com. I'll have to try again just to see, though I still don't know why I would have an issue with stock N ROM.
I didn't even think to try the headset jack right when I got it. Obviously I tripped Knox when I did TWRP and root, but that shouldn't any effect on the audio.
Yea shouldn't do, I've got TWRP, root and used SuperMan N without issue, but am currently on SuperMan MM.
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Modzmarvin said:
I've spent months now trying to find a modem update for my Samsung SM-G920F 8.1 oreo without any luck. I get none stop wifi disconnections and in tired of this. I have searched every place I can even think of. Can anyone help?
I'm in the UK and can only find any info on US modems.
Any time any questions are asked about this, people seem to avoid the question or just point to dead posts.
Click to expand...
Click to collapse
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Maybe the issue is not with the modem?
From the time that the issue started, what did you initially try and what have you tried since then up to now?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Modzmarvin said:
I have come to this conclusion from a bug report i made to lineage. There solution they have been giving everyone was "update modem/baseband", although i must admit, i haven't had any issues on another Samsung i have (SM-G910N) which i found strange as that's never had a modem update since like 5.1)
I've tried a few customers kernels (AldeXus kernel, fk r5+r7 anytime kernel, quantum oreo g920x v2, stormguard oc mido 6.2, + few more), that have all failed to install due to "unsupported device" but claim to support sm-g920f, but in all honesty i really don't know what else to try.
I get this issue on 8.1 lineage and 8.1 resurrection and the highest stock ROM available for this phone is 7.1 (don't get this issue on 7.1).
I've searched everything direction i can and so far the only solutions i could see that make sense is baseband as of course it controls communication with WiFi and network.
Lineage refuse to help as that is there only solution and point me to a thread that is for a nexus who have a 8.1 stock ROM to take the modem from (decompiling a stock ROM and flashing the modem)
Regards
Click to expand...
Click to collapse
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
The modem i currently have installed is from the 7.1 stock ROM but i think what ill do is download the latest 7.1 and try and see what if it has any improvements as it has been a few months since i flashed the 7.1 modem so there could possibly be an improvement in one of the latest updates.
Truly hope so because although lineage it disconnected often, it would reconnect rather easy but resurrection its become a right pain cause its making me turn the wifi off and back on again before it can find any wifi around me!
Thanks for the links pal, I'll give it a shot once i finally manage to download the ROM lol
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Updated the modem. Now to wait and see if it any better haha. THanks for the links!
Found it was super simple to do.
Pulled the tar.md5 apart with 7zip and then zipped it back up with 7zip and it flashed with odin nice and simple . Links are useful for the img files tho! also good to learn from!
Droidriven said:
Have you tried extracting the modem from the 7.1 stock firmware then flashing the modem?
Here are guides for extracting the firmware to get a copy of the modem.img.
https://forum.xda-developers.com/showthread.php?t=2138885
https://www.rwilco12.com/forum/showthread.php?tid=74
Here is a guide to take the extracted modem.img and convert it to an Odin flashable .tar.md5, flash it via Odin in the AP slot in Odin.
https://forum.xda-developers.com/showthread.php?t=2154762
Here is a tool that might make it easier to create the Odin flashable file.
https://forum.xda-developers.com/showthread.php?t=2446269
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Modem updated and still getting random wifi drops
Modzmarvin said:
Modem updated and still getting random wifi drops
Click to expand...
Click to collapse
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you at any point, tried booting to recovery and wipe the cache partition?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Modzmarvin said:
Yep done it a fair few times. Also gone through like 5 lineage updates and 2 resurrection updates. Wipe dalvik/cache each time. Plus wipes cache when rooting, getting any laggy points so on.
Can the kernel help improve the wifi? Its so far the only thing that not been updated (although i can't seem to find a single kernel that works but curious if that may be the issue).
I assume it is an issue I'm having unlike most on 8.1 with a sm-g920f as I'm not seeing many saying they are having the same issue
Click to expand...
Click to collapse
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Droidriven said:
I'm doubting whether the kernel is related with the issue.
When you flashed Lineage, did you perform a system wipe and then clean install the ROM?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Modzmarvin said:
Damn, there's hoping haha.
Yep every time i install a new room i wipe everything (other then internal storage). This issue has only come about when i wiped everything on 7.0 then installed 8.0. Then wiped it again and put 8.1 cause i didn't notice there was a 8.1 update.
Click to expand...
Click to collapse
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Do any of the updated that you've taken, have locked bootloader that prevents downgrading the stock firmware? If you can flash back to what you originally had when you first rooted the device, then root and install TWRP again, it might clear things up and return to its original working state before whatever update started the issue.
In other words, if you can get back to what you originally had, then work your way back through all the way up to just before the update except don't do that update this time, maybe you can figure something out from there to update the device without causing the same issue this time.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out ?. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Modzmarvin said:
I don't believe I've ever had any bootloader locks. Been unlocked from the first day i unlocked it and never re enabled.
I just realised this started on 15.1 as just checked my lineage but report and it was for 15.1.
When i made the bug report, this was the link they gave me then closed the ticket: https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1890
even typing this out the wifi dropped out [emoji58]. when it was on 15.1, it used to need the wifi to be turned off, the phone would freeze then after a few minutes the wifi would turn off. I'd then turn it back on and all wifi would pick back up. the closest i could find to the wifi issue is:
https://www.google.co.uk/amp/s/foru...xy-s6/524916-s6-wifi-drop-out-issues.html?amp
That some one said "I also have this issue I would know wifi disconnects and reconnects becoz the phone will stop responding. It not that I get ANR notif but the phone is jsut froze and only responsive when wifi reconnects. "
Which is as close to my issue i have.
I think i may just go back to stock and see if it works, then as you say slowly move up bit by bit till i start getting the issue and see what happens.
Click to expand...
Click to collapse
Once you get flashed back to stock and then get TWRP installed, make sure you make a nandroid backup before performing the next step, if the issue starts, you can restore the backup and be back to what you had before performing that step. Each time you successfully step up without issues, make a new backup and remove the backup from before that, then perform your next step, always keeping a backup from just before that step.
Sent from my LGL84VL using Tapatalk
Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
SABN said:
Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
Click to expand...
Click to collapse
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
LlamaQ said:
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
Click to expand...
Click to collapse
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
SABN said:
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
Click to expand...
Click to collapse
i have tried different versions of odin, different basebands but i keep getting the same results
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
jwoegerbauer said:
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
Click to expand...
Click to collapse
been there done that, originally it comes with a rom released in 2014 and the other one that is newer released in 2015 try with both just in case but I'm still stuck , reading about it I'm starting to believe it's a hardware problem