Related
I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.
I also wanted to de-brand my i8730 and had similar issues as you. I tried 4 different firmwares, and the only firmware that really works OK is the original, branded one. With other firmwares (same version, same country but different branding) got me the occasional shutdowns like you described and wifi constantly disconnecting and connecting again.
Now I went back to the XWAMB8, rooted the phone and with Titanium Backup removed all the branded apps.
If you don't want to root your device you can always hide the apps, from the app list click on the Menu button and choose the option Hide applications.
Isn't that weird? I had a lot of Samsung smartphones and flashed a lot of firmwares (both stock and custom) and never experienced something like this. Can you tell me where you bought the phone from (what carrier and country)? Thanks.
ssweays composed
It is indeed very weird. My phone is branded to Portuguese Vodafone, I tried flashing other portuguese firmwares and also from other countries, the only stable one is the original one.
I think the phone is designed to be like that.
Sent from my GT-I8730 using xda-developers app
It is happened to me too, this power of thing in XWAMC4 firmware. (it is happened after less then 5 minuts after i turned out the screen)
finally i went back to the XWAMB8 and it's all work great.
No sound at all - not a problem in Australia
I updated and Optus branded i8730 with the plain vanilla variety and have had no problem.
Is your phone network locked?
99% sure mine is not and that may be what is causing it.
Bazzan
Well, it was a Vodafone Romania firmware but not really branded. I mean, it only had some apps installed by Vodafone. However, I'm getting my hands on an unbranded grey Galaxy Express today. Let's see what's going to happen with this one..
Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...
viges666 said:
Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...
Click to expand...
Click to collapse
I've got the same problem, no sound, when i call someone i can't hear the voice of my friend.
Base band version : I8730XWAMB7
Kernel version: 3.4.0-100842
[email protected]#1
Version number: JZO54K.I8730XWAMB8
Do you have any soluce to fixe this probleme ?
Thanks a lot
Wipe and full reflash with odin or heimdall...
Try full wipe and full reflash of original firmware with odin or heimdall...
Does somebody was able to flash a ROM released for a different carrier and still have sound working on this phone?
I either have no sound at all (after burning a new ROM for different carrier) or have strange sound (like "ET call home" - not my problem description, just found it on this forum too) after mixing new ROM with my original MODEM file.
Of course, everything is fine after burning back my original ROM.
ionutzm05 said:
I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.
Click to expand...
Click to collapse
I have this exact same problem!! Ughh.
Any fix?
Flash I8730XWAMK1, will work and you will not have the brand logo. I use this one and is perfectly ! Good Luck ! :good::good:
hi All
have the same problem
original firmware is AP I8730XWAMB8 / CP I8730XWAMB7 / CSC I8730BOGAMB1
phone freeze , restart , no sound ..........
Solved with I8730XWANE1_OXXANF1 , all is OK , sound OK
After I flashed LineageOS 14.1 for GT-I8730T (mine is GT-I8730) the sound doesn't work, video player and music players too, they open and I can fast forward it, but it doesn't play. I changed it back to I8730UBAMD2 and CM 13.1 but nothing. Please help me!
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
masterof1010 said:
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
Click to expand...
Click to collapse
try with this firmware
lets me see
k thanks i'll try it (once it's slow download is done) and update this post. Looks the same except I guess it's android v5.0.1 (well and it's a different CSC/PDA).
K well i've tried that firmware and it's given me some abnormal problems.
Odin typically just writes in like two minutes and boom done, but when I tried to flash with the firmware you suggested like every 15 seconds it would say ...
"Receive Response from boot -loader"
"Transmission Complete.."
"Now Writing .. Please wait about 2 minutes"
It kept cycling through those 3 messages until it FINALLY finished and it say's PASS but it took 9 min 53 seconds which is like 5 times longer then it's ever taken.
Wheather this is relevant or not i'm not sure just trying to give as much details as I can.
Anyways, after booting the phone the samsung logo came up as usual and usually it takes like 5-10 min sitting at this logo before the phone completes loading, presumably setting up the firmware I imagine.
It's been now sitting at that logo for over 20 minutes and i'm about to try wiping with TWRP the davlic cache/cache/data/internal and either trying again with odin (v3.07) OR
If that contines to not work I might put the tar.md5 on the external SD card and recover a saved backup I have on the SD card (with the stock firmware I had before that doesn't allow Wi-Fi to be enabled nor audio/media to play) and use Mobile Odin Pro .apk (I paid for the pro version) from within that restored recovery to flash the firmware you suggested to my phone again.
This is probably redundant but I just figure I might as well try absolutely everything I can possibly think of with your firmware.
If you have any idea why I might be experiencing these abnormal Odin flashing and/or initial loading conditions of the firmware you (or anybody ) suggested i'd appreciate any advice you can give.
I'm going to try and reflash with Odin on my PC again right now (i'm certain thing's like the USB cable are fine and my PC and phone can transfer data without issue .. but that's why i'm going to try mobile odin if after this next attempt doesn't work either).
I'll keep the thread updated, any and all advice is welcomed and highly appreciated
EDIT: OMG it made a like startup theme sound ... that's the first time it's outputted sound in 3 day's !!! It's at the Samsung screen loading the newly flashed firmware so hopefully that completes because wow my phone made noise finally !! Now to wait, and wait....
It won't go past the Samsung logo. So I guess i'll try Mobile Odin. I don't have much faith but it's worth trying.
Uh the backup of the stock firmware I made won't load ... but the hyperdrive rom did. Sound and the dialer work perfectly fine in this rom now, so I guess thing's are more or less fixed. Even though i've wiped the cache/davlic/internal/data in order to prepare to flash the other firmware or this hyperdrive rom (I wipe it every time) in this rom it's reporting my phone's baseband to be I337MVLUGOC4 which is that of the firmware you suggested ...
I'd still rather not use this rom, I thought it was ok at first but meh i'm going to try to go back to CM (after all this *rolls eyes*), trying to use Mobile Odin to install the firmware that you recommended and that appears to have ... somehow fixed the sound can't detect the model of my phone and is dumping, this is not something that has happened with the app before so I don't think i'll be flashing the firmware you suggested.
If it did something to globally fix the crashing when an app was instructed to play audio as it appears to have I guess i'm going to just go download the full CM now, put it on the SD card and install it with TWRP.
So uh, not 100% there yet but it does appear what you've suggested has solved my problem (because worst case scenario i'll just be stuck with the Hyperdrive rom ... but i'll have a working phone) so thanks so much bud I was quite upset and worried about what I was going to do still paying off a useless phone on a contract i'm stuck with for another year still.
I suppose there's no real need in continuing to update this thread as it appears my problems are solved and all that's left are things i'm doing not to fix anything but just because of personal preference over what rom to use but if you want to know anything more just ask, otherwise thank you so much you saved my ass and i'm very grateful.
Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Teleri said:
Hello,
My girlfriend bought new Galaxy A5 2016 (gold) on 15/03. Already while I was completing some settings (Google acc / Sams acc "in" and install of such mere apps as viber, skype, facebook..) the phone restarted on its own twice, without any logical explanation (no significant load, no root, since the divice was almost stock).
This bug has occured while this week two or three times a day. Unfo I cannot associate it with any app or particular action. The phone reboots even in sleep mode or when screen is active.
It doesn't look like hardware deficiency. I tried to delete Google Play Services updates (suggested by local Sams support), hardreset and etc., however - no success. The phone continues to restart its own
Have no idea what to do Can you help me?
best regards
Click to expand...
Click to collapse
Are you use memory card/sd card? Try to remove that...
It happened to me the same thing on my old Desire S... The battery were not firmly pushed in its location... So, you could verify that!
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
HellBouy said:
hi,
i have the same trouble with my new A5 2016. the phone reboot from itself during the night or the day without any reason... happened 4-5 since March, 14.
a friend with the same a5 2016 has same issues.
We have no SD card, no root, stock.
if anyone have a solution, that would be great !
Model : SM-510F
Click to expand...
Click to collapse
Reflash stock rom...
I don't have this issue at all , try a factory reset or flash a stock rom.
Hi,
I've bought a A5 2016 in February (Rom stock, No root, dev options unmasked) - Since then, I've Had 3 power off on its own. I've followed forums and wiped my cache. But this morning I had my phone restart on its own.
I'm quite mad at Samsung for now.
Maybe try calling samsung support?
I have had this problem with my A5 too. Whenever the device updates some app, it re starts.
What exactly occurs during the restart? Does the phone vibrate and show "samsung galaxy a5 (6) powered by android" or does it simply play the boot animation without audio.
If the second option is happening with you., then I suggest you re flash the stock Rom. You can get the stock rom from you mobile or San mobile.
I have the A5(2016) from 2/3 weeks but I never had this problem. If you have the A510F model you can try the German firmware (A510FXXU2APC4 - (build version LMY47X.A510FXXU2APC4). Flash it via odin and donwload the firmeware from sammobile.com. for odin guide see here http://forum.xda-developers.com/samsung-a-series/help/rom-stock-firmware-samsung-galaxy-a5-t3305863
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Parmaggedon said:
To Ahmad89:
Thanks for your response. I actually had logo A5-6 powered by android during restart. I remember to have switched on WiFi connection before it restart (i know that updates occurs only when WiFi's on). That may be an explanation. there may may have been an attempt to update. But the "switch off on its own" event seems more annoying. I did remember one time my phone went off when charging and at that time i used non official Samsung charger. perhaps it was linked to fast charging and a powerless charger that shuted the phone off. What about the two others occurrences when it went off? (the phone being in stand by mode). I can imagine every scenario but no valid explanation.
To zyxw :
I've had the phone update to XXU2APC4 since 3 hours.
I'll do my best to stay in touch for relevant news.
Thanks.
Click to expand...
Click to collapse
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
zyxw-androidiani said:
which one ?? Germany (DBT) firmware ??
Tell me if you will have again the random reboots!
Click to expand...
Click to collapse
I had the update by Kies I presume. I did it by updating the phone in settings/software update. I had several times used Odin for my note 3 but for my A5 i didn't want to flash the whole ROM. My country is France. The New baseband is A510FXXU2APC4 and the version Number is LMY47X.A510FXXU2APC4.
At this time no restart or shut off by its own - but too soon to validate.
I will do a wipe cache very soon.
I'll warn you once restart or shut down happen, if so. :fingers-crossed:
We have the same build version so maybe you will not have the problem!
I have PC4 too , no issue so far.
Sent from my SM-A510F using XDA-Developers mobile app
I have the phone fro 7 days and reboot it himself one time. I dont remember if do this after or before update to apc4. Will see. For now, I'm happy with this phone. I'm dissapointing about no screenmirror.
Trimis via Tapatalk
No restart on its own since my 8 day's last post. Hope this will last...
Pd1 firmware version, 128mo usd kingston, official usim from provider, no reboots at all, same with february and march update, everything fine, everything smooth...
i had also same problem in my new galaxy A7 2016 but after hard reset it works fine..and i observed this happens bcoz of poor ram managment n samsung touch wiz software issue ...so might b it will ressolve after marshmallow update..i m also waiting for new update.
i have same problem when i use VPN
I have android 6 and not use touchwiz. I use another launcher and OpenVPN and work fine from 1 year.
Trimis via Tapatalk
I have a Samsung Galaxy Note 3 SM-9005 with LineageOS 16. The phone is rootet. From beginning on I have only one problem (everything else is running smooth and fast enough): the WLAN connection is interrupted every few minutes. The interruption longs for about 30 seconds. The GSM connection never interrupts.
The problem is surely inside my phone. My network is running well, I don't have any problems with any other device.
I searched the internet; it seems, that some other phones like Huawei and other Samsungs can have similiar problems. I followed every hint without success.
I gambled with any setting I could imagine like disabling energy management, highest performance, etc, nothing works.
Any idea?
kr,
Bernd Hollermann
Germany.
Does it happen only on Pie?
Which bootloader & baseband versions are you on?
Mohamedkam000 said:
Does it happen only on Pie?
Which bootloader & baseband versions are you on?
Click to expand...
Click to collapse
Hi Mohamedkam000!
Thanks for your attention!
I bought this n9005 about three months ago. I didn't use the original software, first thing was rooting and installing TWRP/LineageOS, both latest versions (LOS 17 wasn't available then, so I installed LOS 16). In the meantime I updated LOS a several times hoping the WLAN-problem will be solved. But it didn't.
Bootloader is TWRP almost latest version. Baseband version is N9005XXUGBOJ1 (I wonder how this can help). LOS version is 16.0-20191014-NIGHTLY-hlte.
kr,
Bernd.
hollermann said:
Bootloader is TWRP almost latest version. Baseband version is N9005XXUGBOJ1 (I wonder how this can help). LOS version is 16.0-20191014-NIGHTLY-hlte.
kr,
Bernd.
Click to expand...
Click to collapse
Most wifi & ril problems are of baseband, try using N9005ZSUGPJ2, i'm using it and it's awesome.
Maybe you should flash N9005XXSGBRL1 bootloader as well. Good luck.
Mohamedkam000 said:
Most wifi & ril problems are of baseband, try using N9005ZSUGPJ2, i'm using it and it's awesome.
Maybe you should flash N9005XXSGBRL1 bootloader as well. Good luck.
Click to expand...
Click to collapse
I dont really get it tho... I have a same issue and a custom ROM that I would like to keep. My baseband version is N9005XXUGBOJ1. My original samsung ROM was Lollipop XME (Malaysia) so I have more that needs to learn. If I flash the Baseband you mentioned above, will my wifi works again and will I LOSE my custom ROM? Since baseband is the controller of all radio features it sounds possible that this is the issue
NafOverlord said:
I dont really get it tho... I have a same issue and a custom ROM that I would like to keep. My baseband version is N9005XXUGBOJ1. My original samsung ROM was Lollipop XME (Malaysia) so I have more that needs to learn. If I flash the Baseband you mentioned above, will my wifi works again and will I LOSE my custom ROM? Since baseband is the controller of all radio features it sounds possible that this is the issue
Click to expand...
Click to collapse
No, baseband doesn't affect your current os, i don't really guarantee that it'll definitely fix your wifi, just try it and see. And don't forget about the bootloader.
Where to find baseband file?
I struggled a bit with "baseband", but now I think, I understood it: as a part of the firmware it managed the way of using radio-connections like Wifi etc.
I tried to download the baseband N9005ZSUGPJ2 without success. I can only find whole firmwares ~1,3GB! I think the baseband file must contain just a patch of a few kB. Additionally this baseband N9005ZSUGPJ2 is for Hong Kong.
1. Am I right, that the baseband patch is a file ~few kB?
2. If yes, Where can I find it?
3. Mustn't it be a baseband for German purposes, as I'm in Germany?
kr,
Bernd Hollermann.
hollermann said:
I struggled a bit with "baseband", but now I think, I understood it: as a part of the firmware it managed the way of using radio-connections like Wifi etc.
I tried to download the baseband N9005ZSUGPJ2 without success. I can only find whole firmwares ~1,3GB! I think the baseband file must contain just a patch of a few kB. Additionally this baseband N9005ZSUGPJ2 is for Hong Kong.
1. Am I right, that the baseband patch is a file ~few kB?
2. If yes, Where can I find it?
3. Mustn't it be a baseband for German purposes, as I'm in Germany?
kr,
Bernd Hollermann.
Click to expand...
Click to collapse
--------------------------------------------------------------------
I think, I found a few answers with the help fo Duckduckgo:
the baseband-files are a part of the firmware. You can download the complete firmware (actually I found a german version from october 2018: https://samsung-firmware.org/de/dow...05-dtm/NmlQY/DTM/N9005XXSGBRI2/N9005DTMGBRJ1/ ). Registration process was a bit confusing as they want to sell premium accounts, but after a while I managed the download the file. It's a zip-file of about 1.4GB. After extracion you can find the related files.
hollermann said:
I struggled a bit with "baseband", but now I think, I understood it: as a part of the firmware it managed the way of using radio-connections like Wifi etc.
I tried to download the baseband N9005ZSUGPJ2 without success. I can only find whole firmwares ~1,3GB! I think the baseband file must contain just a patch of a few kB. Additionally this baseband N9005ZSUGPJ2 is for Hong Kong.
1. Am I right, that the baseband patch is a file ~few kB?
2. If yes, Where can I find it?
3. Mustn't it be a baseband for German purposes, as I'm in Germany?
kr,
Bernd Hollermann.
Click to expand...
Click to collapse
CP files are around ~50 MB, you can find them on Android File Host,
I recommended PJ2 cause i used a lot of versions and PJ2 was the best, you can try a lot as well, check this: https://androidfilehost.com/?w=files&flid=18034
And this: https://androidfilehost.com/?w=files&flid=121230
And also this: https://androidfilehost.com/?w=files&flid=195193
CP = CellPhone = Modem = Baseband
Good luck
Now I downloaded some different Firmware-Updates, 2 complete files ~1.4GB and a cp-File ~50MB. One of the two complete firmwares contained 4 different files, one named BL-... and one named CP-...; the one with CP contains modem-file N9005ZSUGPJ2, what exactly is what you recommended.
First try was to upload modem.bin via odin. This didn't work, the process stood still while showing "checking file" (or something similiar). So I took the N9005ZSUGPJ2-file, which was a tar.md5-file. This worked.
Upload via odin went through without any errors, but here comes the problem: After reboot baseband-version remains unchanged, still original version. I tried a several times, always the same.
I remembered from rooting, that the phone keeps the old version in mind so I had to interrupt the boot process very early. But here this didn't work.
How did you manage this?
kr,
Bernd Hollermann.
I found a solution in a post , but I don't understand exactly what's going on there:
Before flashing I just took out the battery (I did it for about two minutes). Then I flashed, no errors (like before), but now the baseband-info changed to the new version.
Unfortunately the new modem N9005ZSUGPJ2 doesn't work better than my old one N9005XXUGBOJ1, still the Wifi connection interrupts periodically.
But with this I learned many new aspects of my phone. Thanks to Mohamedkam000.:good:
Next steps: try different modemfiles. If I find a good working file or any other solution to my problem, I will post it here.
kr,
Bernd Hollermann.
hollermann said:
Now I downloaded some different Firmware-Updates, 2 complete files ~1.4GB and a cp-File ~50MB. One of the two complete firmwares contained 4 different files, one named BL-... and one named CP-...; the one with CP contains modem-file N9005ZSUGPJ2, what exactly is what you recommended.
First try was to upload modem.bin via odin. This didn't work, the process stood still while showing "checking file" (or something similiar). So I took the N9005ZSUGPJ2-file, which was a tar.md5-file. This worked.
Upload via odin went through without any errors, but here comes the problem: After reboot baseband-version remains unchanged, still original version. I tried a several times, always the same.
I remembered from rooting, that the phone keeps the old version in mind so I had to interrupt the boot process very early. But here this didn't work.
How did you manage this?
kr,
Bernd Hollermann.
Click to expand...
Click to collapse
Installing baseband is kinda strange, you have to pull out the phone battery for a few seconds, once you revert it, get directly to bootloader, flash the CP.
When it finish, don't let it boot to system, directly hold home + volume down, and flash it again.
Do the same thing again.
I don't know why, but it never worked for me from the 1st try.
Mohamedkam000 said:
Installing baseband is kinda strange, you have to pull out the phone battery for a few seconds, once you revert it, get directly to bootloader, flash the CP.
When it finish, don't let it boot to system, directly hold home + volume down, and flash it again.
Do the same thing again.
I don't know why, but it never worked for me from the 1st try.
Click to expand...
Click to collapse
Yes, unplugging the battery worked. Now i have the recommended baseband-version.
Unfortunately the wifi connection still isn't stable. After I watched it a few days I cannot see any difference.
Hmmm...
hollermann said:
Yes, unplugging the battery worked. Now i have the recommended baseband-version.
Unfortunately the wifi connection still isn't stable. After I watched it a few days I cannot see any difference.
Hmmm...
Click to expand...
Click to collapse
Well .. that's really strange, is your hotspot running fine?
Bluetooth? Mobile data?
Try using Audax kernel for stock lollipop: https://www.androidfilehost.com/?fid=24369303960685508
Flash via TWRP, if it didn't work, probably it's a hardware problem, you may have to replace the motherboard.
Mohamedkam000 said:
Well .. that's really strange, is your hotspot running fine?
Bluetooth? Mobile data?
Try using Audax kernel for stock lollipop: https://www.androidfilehost.com/?fid=24369303960685508
Flash via TWRP, if it didn't work, probably it's a hardware problem, you may have to replace the motherboard.
Click to expand...
Click to collapse
I thought about hardware problems too.
My LAN works very fine, I have about 10 devices with LAN/Wifi-Access without any problem. This single Note3 is the only device not working properly.
The Note3 itself runs very well and very fast in any other way: Bluetooth, Audio, LTE, NFC, ...
Next steps are testing one or two other modem-files. If this doesn't help, I'm looking for another device, maybe another identical Note 3.
I will report here.
Now I realized that most of the modem.ini are identical: most of them have the date 2015-10-16. There is one from vodafone with date 2015-10-28. The PJ2-modem.bin, which Mohamedkam000 recommended, is the newest: 2016-10-21.
I tried all, nothing changed. Remarkable: often the Wifi-connection seemed to be stable, but after 1 or 2 hours it starts to interrupt.
Then - after gambling with settings a.s.o - I realized a very chaotic behavior of the 5GHz-Channel. Before I changed the settings of my access point from dual mode 2.4Ghz+5GHz to just 5GHz, so that the phone MUST choose this. The surrounding Wifi's vanished completely from the Wifi-list (no Wifi's could be found at all), reapperaed a few seconds later, tried to connect to my 5GHz-Wifi, mostly didn't connect (sometimes it does), Wifi vanishes ... . This went on permanently every few seconds.
After that I deleted all Wifi-Networks from phone, set up a single 2.4GHz-Wifi-Channel in access-point and conncted to the 2.4GHz Wifi. Now problems seems to have gone: since about 1 hour every ping has got an answer, no dropouts at all. This never did happen before.
Conclusion: 5GHz component is badly supportet or has a hardware error. I wonder what it will be.
Are there any other people having similiar issues?
I don't know if it's a hardware problem or region based or something, even in Mobile Hotspot, i can't share internet using 5GHz band.
You should know that 5GHz band has a small range, you have to be so close to your router.
Glad to hear your WiFi worked : D
Mohamedkam000 said:
I don't know if it's a hardware problem or region based or something, even in Mobile Hotspot, i can't share internet using 5GHz band.
You should know that 5GHz band has a small range, you have to be so close to your router.
Glad to hear your WiFi worked : D
Click to expand...
Click to collapse
I'm glad to report some big improvements.
That's what I did without success:
I changed to many different modem.ini and back to original modem.ini. These are some of what I tried:
----------------------------------------
N9005XXSGBPL7_N9005TNLGBOK1_N9005XXUGBOJ1_HOME.tar
N9005XXUGBOJ1
51.742.464 Bytes
27.12.2016
----------------------------------------
N9005ZSUGPJ2-4Files-5.0-_(By_rajafirmware.com)
21.10.2016
56.493.824 Bytes
----------------------------------------
N9005XXSGBRI2_N9005DTMGBRJ1_DTM
16.10.2015
51.742.464 Bytes
----------------------------------------
CP_N9005XXUGPQB1-Nordic
21.2.2017
56.231.680 Bytes
----------------------------------------
The one from 16.10.2015 is the most spreaded. If you search for "latest version", most are this.
You (Mohamedkam000) recommended the one from 21.10.2016. I installed it; if there were an improvement, it was hard to recognize. I searched hard for newer ones, at last I found the "nordic" from 21.2.2017. Unfortunately the situation has been the same as before. So I switched back to original from 16.10.2015 and - as it turned out, that connectivity seem to be slightle worse - back to nordic.
Then I realized, that GPS is weak too, it takes about 10 minutes to get a sufficient signal (inside my flat; my note 2 needs 30 seconds). Thinking about all my difficulties I decided to disassemble the phone to investigate if there's a recognizable hardware problem. I watched some youtube videos for to know where the screws are and if there's something to be careful about. It's quite simple, but it would be good to have some experience.
I disassembled the inner back cover. Everything seemed to be in a very good condition, but here and there it seemed if there were a slight shadow on surfaces of metal plates a.s.o.; so maybe the phone has been exposed to some moisture. However I cleaned every electric contact on both sides: spring contacts on pcb and plate contacts on cover, with Tunerspray 600 (cleaning fluid for analog tuner parts such as condensator etc, very effective!) and an ear cleaner stick. Beside I bended the spring contacts slightly to have a little bit more contact pressure.
This lead to a big improvement! GPS signal is back to normal (30 seconds for 3D fix using "GPS Test"). Wifi connection is as stable as never before.
I'm going to watch very closely the next days and will report.
kr,
Bernd Hollermann.
hollermann said:
I'm glad to report some big improvements.
That's what I did without success:
I changed to many different modem.ini and back to original modem.ini. These are some of what I tried:
----------------------------------------
N9005XXSGBPL7_N9005TNLGBOK1_N9005XXUGBOJ1_HOME.tar
N9005XXUGBOJ1
51.742.464 Bytes
27.12.2016
----------------------------------------
N9005ZSUGPJ2-4Files-5.0-_(By_rajafirmware.com)
21.10.2016
56.493.824 Bytes
----------------------------------------
N9005XXSGBRI2_N9005DTMGBRJ1_DTM
16.10.2015
51.742.464 Bytes
----------------------------------------
CP_N9005XXUGPQB1-Nordic
21.2.2017
56.231.680 Bytes
----------------------------------------
The one from 16.10.2015 is the most spreaded. If you search for "latest version", most are this.
You (Mohamedkam000) recommended the one from 21.10.2016. I installed it; if there were an improvement, it was hard to recognize. I searched hard for newer ones, at last I found the "nordic" from 21.2.2017. Unfortunately the situation has been the same as before. So I switched back to original from 16.10.2015 and - as it turned out, that connectivity seem to be slightle worse - back to nordic.
Then I realized, that GPS is weak too, it takes about 10 minutes to get a sufficient signal (inside my flat; my note 2 needs 30 seconds). Thinking about all my difficulties I decided to disassemble the phone to investigate if there's a recognizable hardware problem. I watched some youtube videos for to know where the screws are and if there's something to be careful about. It's quite simple, but it would be good to have some experience.
I disassembled the inner back cover. Everything seemed to be in a very good condition, but here and there it seemed if there were a slight shadow on surfaces of metal plates a.s.o.; so maybe the phone has been exposed to some moisture. However I cleaned every electric contact on both sides: spring contacts on pcb and plate contacts on cover, with Tunerspray 600 (cleaning fluid for analog tuner parts such as condensator etc, very effective!) and an ear cleaner stick. Beside I bended the spring contacts slightly to have a little bit more contact pressure.
This lead to a big improvement! GPS signal is back to normal (30 seconds for 3D fix using "GPS Test"). Wifi connection is as stable as never before.
I'm going to watch very closely the next days and will report.
kr,
Bernd Hollermann.
Click to expand...
Click to collapse
Nice that you figured it out, was about to tell you, yesterday I saw a post about s10e with gps problems, the guy solved it with simple disassemble & reassemble!
UPDATE: I used to had this problem where Wifi and wifi tethering will not work in any tries to turn them on. How I fixed it? Idk its randomly. It actually started working fine when my phone stuck on boot and it produce too much heat I can say above 80°C and running on that temp for 8 hours. The heat must have melted the solder under the wifi chip abit enough to make contact to the motherboard. So best bet is using heat on the wifi chip
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse
UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse