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!
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
AndroidLEK said:
Hi all,
Ever since updating to the latest MGA via OTA firmware nearly 2 weeks ago the Wifi has been causing me a lot of issues. The following evening after updating the firmware, the wifi just randomly turned itself off and would refuse to turn on again. When I attempted to turn it back on via the widget, it would go grey as it's attempting to turn on but then it would just stay at that and it will not turn on at all. After a few minutes it will either go back to being completely turned off or the phone would just reboot itself.
Now, I have tried several things to rectify the problem i.e. applying the MGA wifi fix, factory restoring the phone via the settings and also in Kies, downgrading back down to the MEA firmware, re-flashing the stock MGA firmware via Odin and re-flashing both the MEA & MGA modems seperately - all to no sucess!
At the same time while all this is going on, the phone itself will sometimes randomly reboot itself when attempting to turn on the wifi or even in the rare case when the wifi does turn on and it will work for 5 or so minutes - the phone will reboot itself again while trying to simultaneously update various apps through the play store.
Lastly, the phone has already been sent back to Samsung a few days ago regarding this issue and the phone was returned back to me yesterday with Samsung apparently stating that they had diagnosed and found an issue with the phone (even though they could not tell me what??) and that they had sucessfully repaired it. Upon turning the phone back on going through setting up the phone again, I come to the wifi connection and guess what... it doesn't turn on. Yep that's right, I'm still stuck with the same problem!
I got straight onto Samsung on the phone and complained about this as I'm not happy at all, and they have agreed to have the phone back in for another repair and apparently something will be done properly this time.
It's not good enough though, to me all it looks like that Samsung have done their end on the original repair is re-flash it with the MGA firmware once again, shove it back in the box back to me and hope for the best. Even the Samsung agent on the phone yesterday could not tell me exactly how they apparently repaired the phone as there was not anything on the repair report what so ever, unbelievable!
Anyway, do any of you guys have any ideas with what else I can do my end to try and rectify the problem? To me though, this sounds like a physical hardware fault that only Samsung themselves can sort out...
Thanks - Liam
Click to expand...
Click to collapse
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
PSPNikos said:
Well I have only had this problem with rooting phones etc... to me this happened with so many ROMs I tried. Even certain stock roms. I am not sure fully how I fixed it, but I know now I am running the OMEGA rom and this seemed to have worked for me so possible to try that? Just an option
Click to expand...
Click to collapse
When I first downgraded back down to the MEA firmware that I was linked to from another forum, I discovered straight after flashing that it was a pre-rooted ROM and the wifi still would not turn on then.
The phone has been sent back to Samsung again today for another repair but last night as a last ditched attempt, I downloaded & flashed the stock XXUAMDM firmware from April and the wifi still refused to turn on.
I'm still convinced that the problem itself is hardware related rather than software based going by that the problem is still present regardless of what ROM I'm on, it's just a case of trying to get Samsung to see that. I can understand now why that Samsung the first time round probably only did a fresh re-flash of the MGA firmware instead of going ahead and taking the phone apart/replacing parts as I imagine it's very labour intensive/standard procedure and not only that - the S4's mainboard (from what I've seen the wifi module is part of the mainboard) retails at over £200 which is a hefty repair cost on their part.
Liam
It is some sort of permissions issue.
If you do chmod 777 on /dev/*, /system/etc/wifi/* it should be working.
The only thing I haven't figured out is why
And it has to be done again after rebooting the phone, wich makes me sad.....
How I fixed my WiFi and sound problems after updating to latest firmware over
Hi there. (Sorry for any mistake about my English). By the way, I'm newbie on Android.
After freaking out about my WiFi problem, i didn't even care about the others problems like the sound, and I don't know if there were or if there is still some, but WiFi and sound got fixed.
After a lot of research on Google and XDA I came to the conclusion that if I could just re-install the firmware, I had
1- I Download the same firmware you are on (i guess it safer this way) I got the same (I9505VJUEMKE) that had caused the problem when was update trough Kies.
GT-I9505_PDA_I9505VJUEMKE_4.3
Changelist: 2210919
Build date: Wed, 27 Nov 2013
CSC: I9505ZTOEMKE_ZTO_Brazil
MODEM: I9505VJUEMKE
Gdrive: (créditos ao +Alexandre Affonso - Vlw)
Two links for download this firmware. (really fast download since its on gdrive)
goo.gl / UrZWAE .
goo.gl / omJC9e "
2- Unpack the Zip File
3- Putt the phone in "Download Mode"
4- Open Odin 3.07 and Connected the cable. (check if Odin linked a port to your phone, i didnt get any color change, just the COM Port number and the "added" mentioned on Odin)
5- Load the firmware on "PDA", wait a few seconds till Odin load it.
6- Click Start and wait the whole process. Don't disconnect the cable until Odin says that it was Successfully.
Finished!
After all I did the root with Odin + CF Auto Root + Supersu and So far everything is fine and better than before.
Hope I can help few of you guys.
Thanks.
32GB D802 unbranded model (Hong Kong), same inside case on metal strip(D802/805) and plastic inner housing. Bought brand new with JB.
Used LG tool, CSE Flashed 'Hong Kong D80230B_00.kdz' (KitKat 4.4.2) No problems!
Tried Flashing Lollipop Firmware for 32GB D802 from other countries Spain, Germany, even China, but upon reboot after flashing the screen back-light is lit, but there's no picture or logo, stays like that for 20 mins.
Rebooting into Factory Reset I can see the screen again, but that's it.. So is it possible to flash other countries Firmware? There's no LTE option with Hong Kong.
Another thing, I've checked my IMEI thru the dialer and it's '0'. In Hardware mode a bunch of "0000000000000'
But I still have phone signal and no problems at all. Should I concern myself with that?
Are you really sure its a true d802, did you cechk motherboard.? check this thread
http://forum.xda-developers.com/lg-g2/general/warning-to-people-bought-phones-ebay-t2991195
I'm not game enough to dig that far into my phones hardware, but failing all else I could..
However...I have successfully used AutoRec (D802) to install recovery 3 times already, no problem and IOROOT to root it...
And...I didn't buy this from Ebay secondhand. I bought new from a shop.
After flashing another regions Lollipop Firmware(d802) and encountering the blank back-lit screen on reboot, it didn't brick my phone, I could still enter download mode and go into factory reset (which is where the screen actually worked) Actually tried the factory reset after the flash but it didn't help.
After not being able to see anything I just entered download mode and flashed KitKat back again, no problem. I can't see how others are just flashing any regions Lollipop ROMs on their phones and they're working.
Photo's attached showing under casing markings(not so good quality, I used my old Desire S)
twiice said:
I'm not game enough to dig that far into my phones hardware, but failing all else I could..
However...I have successfully used AutoRec (D802) to install recovery 3 times already, no problem and IOROOT to root it...
And...I didn't buy this from Ebay secondhand. I bought new from a shop.
After flashing another regions Lollipop Firmware(d802) and encountering the blank back-lit screen on reboot, it didn't brick my phone, I could still enter download mode and go into factory reset (which is where the screen actually worked) Actually tried the factory reset after the flash but it didn't help.
After not being able to see anything I just entered download mode and flashed KitKat back again, no problem. I can't see how others are just flashing any regions Lollipop ROMs on their phones and they're working.
Photo's attached showing under casing markings(not so good quality, I used my old Desire S)
Click to expand...
Click to collapse
then i guess if it flashed with no problems then it might be a d802, not sure about the imei though.
i cant really help here, i ive never been into jb,kk on my g2. but it shouldnt be aproblem flashing different region i dont think it matters right as long as its your variant.
I'll try flashing a Hong Kong based Lollipop ROM and see what happens.
Thanks for your input!
twiice said:
I'll try flashing a Hong Kong based Lollipop ROM and see what happens.
Thanks for your input!
Click to expand...
Click to collapse
youre welcomed and good luck. reprot back.
The Hong Kong Firmware worked, no problem at all. It has 4G enabled too which is excellent.
Hi guys, I'm lost, i tried flash almost everything to my freshly bought board from aliexpress but I had only success with "N9005-hlte_PDA-XXUEND6_CSC-OXXEND2_MODEMS-XXUENC2_REPACK.tar.md5" and some others but after locking and unlocking display stays black ( buttons under screen lights up and system seems to work but no visual after unlock - after swipe to unlock. I cant flash any custom rom and only some 4.x official roms. And no, i don't know what firmware was originally on it (stupid me)....
download mode info:
s33.postimg.org/taofdtcnx/P5300326.jpg
Are you saying you bought a motherboard ??
If so the new motherboard defines the firmware not your old setup .
Yeah i got new, i didn't know there's so many variants of software for phone, my good old note 2 is almost unbrickable. Any suggestions how to get it alive ?
Ok guys, I got some progress, I successfully flashed 5.0 SM-N9005_1_20160121153514_7lzesanh3b_fac tgy coz i think this is hong kong board. Everything works but i have extremely low wifi signal even when I'm standing next to router, gsm networks mostly same bad signal and whats odd, I can see sim signal without sim in phone. Isn't it coz of bad modem ? How should i continue ? Thanks.
edit:
And i still cant flash any custom rom trough twrp, always stuck on writing system partition - sometimes with error 7 and sometimes just endless loop of writing system :/
Try Philz Recovery .
I tried philz - works but cant flash rom, stucked on system, cwm - same, twm - works only some older versions not the lastest one, only sometimes it boots to lastest and cmr - not working. After rooting using supersu zip had some random reboots for some time.
Got a slight problem here.
First of all how do I find out the original network / carrier the phone was on?
I stupidly went and flashed the XSA (Australia) firmware without making note of the original carrier. Is there a way I can find out?
Secondly every time I boot the phone up it does a boot loop at least 4 times before it gets into the system.
Any ideas on this?
Thanks
G900i
My device came with Telstra firmware. I have flashed XSA, Optus, Vodafone, Spark NZ and India.
No problems.
Did you use Odin to flash your firmware?
What country are you in?
Hi
Yes I am in Australia and yep I used Odin.
It seems that even flashing TWRP the same issue I encounter but the strange thing is, although it shows up 'Recovery booting' and shows the Samsung Galaxy S5 splash logo I can still press buttons on the phone and I know this because it vibrates. Its almost like TWRP is there and is open in the background but its just not displaying at all. I have honestly tried so much.
I have downloaded (Using Sam Firm) the latest XSA and even found the PIT file to re partition but that made no difference.
The phone has had a total of around 7 LCD screens installed which came from various sellers in China. Due to the constant connection and disconnections of them I would say it may well be responsible for this issue as it has caused no doubt some considerable amount of stress to the motherboard. Maybe I am wrong I am just not sure.
It is a bizarre issue. I have never come across it before.
Standard stock recovery is also behaving the same way... I am getting, in blue, on the top of the screen 'Recovery Booting' then thats it... just that... waiting for ages and nothing happens but I am pretty sure that it is actually open behind the message which says 'Recovery Booting'
The whole things a bit of a mess.... When starting up the OS normally it takes around 5 bootloops for it to actually load up lol
Wow!! That's just crazy. Sounds like your device might have seen better days.
Occasionally I think its good to take the phone back to kitkat then to MM before twrp and custom roms.
I currently run klte version of /e/ pie ROM on my device which works very good. Un-Googled so my tired battery lasts better.
Best of luck with your problem.
Happy New Year mate.