Related
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Same here, even 3.2 ROMs flickering for me . The only one that doesn't flick is Task ROM
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Hey man, just got this sorted out
Try to follow this http://forum.xda-developers.com/showthread.php?t=1555984
Key part is that we need to unroot our tabs with North America stock. I think our "Non-NA" stock ROMs weren't really "unlocked" that's why custom kernel won't work well on them.
Super happy now with CM9 + latest pershoot kernel + latest CWM, smooth no flickering
Happy unrooting !
Make nand backup (if recovery flickers use rommanager)
Save it to PC
Wipe everything
Flash P7510UEKMP_P7510XABKMP_XAB.tar.md5 with odin
Reboot
Wipe everything again
Flash recovery.tar.md5 with odin
Reboot
Put this http://www.shabbypenguin.com/users/s0ckm0nk3y/android/acs/galaxytab10.1/Samsung_Galaxy_Tab_10.1_root.zip to storage
Put nand backup to storage
flash the zip
Reboot
Restore nand
Finisch! You can now flash another recovery and any other rom without flicker
In fact there is no way to get the flickering back^^
Files you can get here http://forum.xda-developers.com/showthread.php?t=1555984
ive had the same rolling screen during boot, but recovered with those instructions.
now i have another kind of problem:
roms flash ok, cwm is ok, boot is ok. but when i get to the desktop, if the device goes into standby, ot if i put it in standby withthe power button, when i wake it up, again a rolling screen, but much faster this time!
anyone had this problem before?
only happens on 3.2 custom roms. on the official one its ok, on cm9 from droidbasement its ok
any ideeas?
thanks
here it is a pic of what it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any ideeas?
thank you
nobody knows?
Hello all.
I have the exact same problem as tristan202 which is
Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all.
I am sorry but i think that solutions bringed by "hylde" is not related to this problem but to another problem, through very similar, in clockwork recovery tool : same flickering screen.
I used the link, 2 weeks ago to solve this problem, using 5.5.0.4 version.
But the original thread problem is still unsolved. I tried other ICS roms but with same problem. I'd also like to keep root access.
Thanks to all
cobrax2 said:
here it is a pic of what it looks like
any ideeas?
thank you
Click to expand...
Click to collapse
Well, I have almost the same problem. I am on overcome's rom, and I have a screen similar to yours. It is static, not rolling and it happens only once after reboot for two-three seconds before the lockscreen. After that it is ok, even when I lock the screen. Flashed again but nothing. I haven't found anything about that. Oh well. It may be weird but I can live with it. Has anyone encountered something like that before?
Sent from my amazing 10.1 galaxy tab
I posted this in Task 14 Thread!
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
bugs9477 said:
I had the same problem I fixed it like this!
Click to expand...
Click to collapse
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Galanthein said:
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Click to expand...
Click to collapse
So sorry it was ment to be in response to cobrax2's waking up from screen off!
bugs9477 said:
So sorry it was ment to be in response to cobrax2's waking up from screen off!
Click to expand...
Click to collapse
Ok that's what i thought. Too bad for us, we still have our problem
Thanks anyway !
bugs9477 said:
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
Click to expand...
Click to collapse
thanks for the reply, ill try this as soon as i find a bit of free time
Regarding tristan202 and mine problem (flickering boot screen which stops when we press two times the power button), i tried the nightly builds 19/05 and 22/05 of Cyanogen Mod without solution.
Tristan i'll try 2905 nightly build and keep you in touch
Well, finally it happened--Sprint and HTC released an official ICS ROM! Here is the firmware package for it that will update everything except the kernel, hboot, and recovery to the official ICS versions.
download PG86IMG
MD5: E62D140A3C8CD00A2EB1210CB41D527B
This second package includes the hboot update as well: I've heard that this will write S-ON for anyone who is S-OFF. Rename this file to "PG86IMG.zip" Proceed with caution.
download PG86IMG with hboot
MD5: 58E7D186C15A37C52E45A686DFEB641F
As usual, this file must be on the root of your SDcard and flash this in bootloader while either S-ON (not HTC unlocked) OR S-OFF.
OLD OUTDATED deprecated VM firmware:
Hi guys.
After the last screw up with VM firmware, this time will be slightly different. There will be three different PG86IMG.zips.
One will be for those who have already taken the full firmwrae update last time and are unaffected by it.
Second one will be for those who want updated asdp and radio (which can easily be downgraded)
First let's start with some facts: The following has been updated from the original VM leak:
dzdata_4g.hdr
adsp.img
boot_signed.img
dzdata_4g.img
hboot_SHOOTER_1.57.0000_signedbyaa.img
partition.img
pg2fs_spcustom.img
radio.img
ramdisk.img
recovery_signed.img
rpm.img
sbl1.img
sbl2.img
sbl3.img
system.img
tz.img
wimax.img
What hasn't been updated is:
rcdata.img (pretty sure this is PRI and could also be partly resopnsible for the "Virgin Mobile" banner fiasco)
rfg_1 (this could be reponsible for the "Virgin Mobile" banner fiasco)
rfg_2 (this could be responsible for the "Virgin Mobile" banner fiasco)
splash1.nb0 (splash screen, derp)
Now let's get down to business;
For thsoe who want to live on the edge, there is a way to back up your phone's partitions in an attempt to restore them back to what they were. There are two ways to do it, one requires a "brick" using emmc_recover, and the other is this simple command:
Code:
dd if=/dev/block/mmcblk# of=/sdcard/mmcblk#.img
Where # is the partition you want to back up. The EVO 3D, if I'm not mistaken, has 34 partitions, but the one we probably want the most is partition 19 (radio_config). It wouldn't hurt to back them all up if you have not taken any virgin mobile leaks.
Anyway on to the PG86IMGs!
[size=+3]WARNING:[/size]
PG86IMGFULL.zip: Will contain everything the first one did. This is for people who have taken the first firmware and have no side-effects. ("Virgin Mobile" banner will come back)
PG86IMGLITE.zip: This will contain the radio, wimax, and asdp updates.
PG86IMGEXP.zip: This will contain everything the full one does MINUS the rcdata/rf_1/rf_2. (which should eliminate the "Virgin Mobile" banner but will not update PRI)
Note: You will have to remove "FULL", "LITE" and/or "EXP" from the filename before the phone will attempt to update itself with them.
Now, if closeone and/or Unknownforce wants to take a crack at modifying one or all three of the files (rf_1,rf_2,rcdata) to get rid of the Virgin Mobile banner, and to make it 'Sprintified" so that it isn't just a mask up, then we will be in business.
Nooo...just noooo...(consuela)
Sent from my PG86100 using xda premium
all hail freeza
i hate VM
I'm just going to leave this here as well. Posted it in the other thread.
I'm relatively sure that freeza can attest to this. If everything is working fine right now, and you (the user of the EVO 3D) are satisfied with the experience, I would suggest not flashing it yet. When things settle down, ROM developers will tell you if you absolutely need to upgrade anything. I just wouldn't do it for the sake of doing it.
Sorry. Just my two cents.
Thanks Whosdaman for the leak post, and freeza for the updates in this thread.
~co~
closeone said:
I'm just going to leave this here as well. Posted it in the other thread.
I'm relatively sure that freeza can attest to this. If everything is working fine right now, and you (the user of the EVO 3D) are satisfied with the experience, I would suggest not flashing it yet. When things settle down, ROM developers will tell you if you absolutely need to upgrade anything. I just wouldn't do it for the sake of doing it.
Sorry. Just my two cents.
Thanks Whosdaman for the leak post, and freeza for the updates in this thread.
~co~
Click to expand...
Click to collapse
Completely agree. I would only take this update if you've taken the first one and weren't effected by it. For those who can't boot ICS ROMs, maybe the LITE version will help you (since it does include asdp, wimax, and radio updates. all of which are absolutely reversible) Other than that, like closeone said, it's not really needed.
freeza said:
Now, if closeone and/or Unknownforce wants to take a crack at modifying one or all three of the files (rf_1,rf_2,rcdata) to get rid of the Virgin Mobile banner, and to make it 'Sprintified" so that it isn't just a mask up, then we will be in business.
Click to expand...
Click to collapse
I can defiantly pull out a hex editor and start looking into what changes it makes. You may receive a PM from me in a second.
~co~
I will just point out that I strongly suggest waiting to flash anything like this until it's confirmed that it can be reverted properly.
I'm sure that it can be done, but it's gonna take some time to figure it out. Don't expect a fast turn around. I'm working on it as much as I can.
A lot of flash-aholics are probably going to screw up their phones with this... Don't flash unless you absolutely know what you are doing/getting into
------
3(d)vo one s
Newts my hero.
To anyone who does this, let us know how it goes, man.
buddywiser said:
To anyone who does this, let us know how it goes, man.
Click to expand...
Click to collapse
i am about to flash the EXP version. i have never done anything VM related before... im only doing this one cuz it has sbl1,2,3 whereas lite doesnt... also has som .hdr file. i just did some speedtests with the 2.17 allin one... will post after flash
may i ask what adsp is? ive not seen this one before.
kiewee3 said:
Don't flash unless you absolutely know what you are doing/getting into
.
Click to expand...
Click to collapse
update: for me (in the Miami, FL area) ping is about the same @ ~150-160, download is a bit slower @ 400kbps (from ~700 @ this busy time)... upload gained a nice 200kbps boost (~650kbps). going back to 2.17, testing again... then trying the new one but LITE only.
btw i have all my 3g settings tweaked and tested max... (HA ips tested and selected, DSS/RTSP disabled, 3g Turbocharger script, reverse tunneling and many other things in QPST turned off. at highest peak i get 2.2Mbps, but thats at 3:30am)... so glad my towers have been fixed here
I flashed the full one but I'm on cricket wireless so either way it doesn't effect me
closeone said:
I'm just going to leave this here as well. Posted it in the other thread.
I'm relatively sure that freeza can attest to this. If everything is working fine right now, and you (the user of the EVO 3D) are satisfied with the experience, I would suggest not flashing it yet. When things settle down, ROM developers will tell you if you absolutely need to upgrade anything. I just wouldn't do it for the sake of doing it.
Sorry. Just my two cents.
Thanks Whosdaman for the leak post, and freeza for the updates in this thread.
~co~
Click to expand...
Click to collapse
+1 ^^ I haven't updated any firware on my phone, haven't found a need to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I haven't seen any real side effects, but I have noticed that I can't get all three bars on my 4g. So which one should I flash?
tommy24 said:
I haven't seen any real side effects, but I have noticed that I can't get all three bars on my 4g. So which one should I flash?
Click to expand...
Click to collapse
lite or exp. in your case, i would say lite. the other things in exp are a bit remedial. i have a post on 1st page with what i got in results. however, neither will bring the VM banner.
i was affected by the fist vm firmware every so often my phone doesnt get any text messages or makes calls it takes from5 mins to hours before i get texts so i have to constantly have to reset my phone. would this fw will fix my issues?
my phone went from a auto-bot to a decepticon. wth
ezln_0503 said:
i was affected by the fist vm firmware every so often my phone doesnt get any text messages or makes calls it takes from5 mins to hours before i get texts so i have to constantly have to reset my phone. would this fw will fix my issues?
Click to expand...
Click to collapse
Same here. Should I risk it? If the damn LTE's were in stock by next I would just do it but who facking knows. (No, I did not preorder one, decided on Monday I would get one)
I just flashed the EXT version. I had previously flashed VM firmware and reverted back with RUU 2.17 firmware and then the Sprint renaming fix. New firmware seems to work fine. I can make outgoing calls. The lockscreen and notification bar no longer say Sprint, however. But, like I said, calls go out just fine.
jerofld said:
I just flashed the EXT version. I had previously flashed VM firmware and reverted back with RUU 2.17 firmware and then the Sprint renaming fix. New firmware seems to work fine. I can make outgoing calls. The lockscreen and notification bar no longer say Sprint, however. But, like I said, calls go out just fine.
Click to expand...
Click to collapse
Reverted to "Virgin Mobile"?
I do have a modified rfg_1.img and rcdata.img now.
No guarantees. I'm actually afraid of releasing them.
rfg_2.img contains no data at all.
Depending on the situation. If you don't mind risking a brick, I'll post them. But I'm having some dinner first.
~co~
Trying to diagnose a problem with my Brother's phone. He got his Amaze about 8 months back, no issues whatsoever on the Stock ROM other than a backlighting issue on the bottom buttons that HTC is aware of.
Since installing ARHD Gingerbread, he gets random, and frequent phone shut downs when trying to wake it from lock/sleep statuts. The phone just shuts off and restarts by itself.
We were hoping that migrating to ARHD ICS this week would solve that issue, but it has not. It still shuts down randomly at wake.
Something on your phone is probably causing this, do a full wipe and reinstall.
I was actually experiencing this last night. Happened about 7 times while I was at work. After I cleared cache and dalvik-cache I fixed permissions. So far it hasn't happened again but waiting to see if it does. But maybe our issues maybe totally unrelated. I didn't pull a logcat to see if there was anything that maybe causing it. Next time it does I will.
Running ICS .3 Stock debloated, no scripts but with a theme. But its been on there since I flashed the newest ICS RUU so it can't be that.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Dark Nightmare said:
Something on your phone is probably causing this, do a full wipe and reinstall.
Click to expand...
Click to collapse
Except it has done this multiple times after using superwipe, with both ARHD Gingerbread and ARHD ICS.
Double0EK said:
I was actually experiencing this last night. Happened about 7 times while I was at work. After I cleared cache and dalvik-cache I fixed permissions. So far it hasn't happened again but waiting to see if it does. But maybe our issues maybe totally unrelated. I didn't pull a logcat to see if there was anything that maybe causing it. Next time it does I will.
Running ICS .3 Stock debloated, no scripts but with a theme. But its been on there since I flashed the newest ICS RUU so it can't be that.
Click to expand...
Click to collapse
I'll try this. For whatever reason the RUU on the ARHD page continually fails to update via ADB/Fastboot, I'll try again to see if it works now that ARHD ICS went on it successfully. Will try the Cache Clear and Permission Fix - definitely didn't do that after flashing this.
Weird update. In his bootloader it always said unlocked. I did the S-Off method advertised by JopountBear (sp), but now it seems it is locked? Odd.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Radio still won't install - says remote: not allowed.
Doing one more superwipe -> ROM -> Cache/Dalvik/Permissions Clear. Battery life very bad at the moment (But perhaps Battery Calibration is off?)
gotpriest said:
Except it has done this multiple times after using superwipe, with both ARHD Gingerbread and ARHD ICS.
I'll try this. For whatever reason the RUU on the ARHD page continually fails to update via ADB/Fastboot, I'll try again to see if it works now that ARHD ICS went on it successfully. Will try the Cache Clear and Permission Fix - definitely didn't do that after flashing this.
Click to expand...
Click to collapse
You didn't point this out in the beginning, if the bootloader is locked it won't allow flashing, re-unlock to flash whatever radio you're trying to flash.
Out of curiosity, why would a phone re-lock itself without me telling it to do so?
Dark Nightmare said:
You didn't point this out in the beginning, if the bootloader is locked it won't allow flashing, re-unlock to flash whatever radio you're trying to flash.
Click to expand...
Click to collapse
the bootloader needs to be locked for s-on, for s-off, it doesnt matter
gotpriest said:
Out of curiosity, why would a phone re-lock itself without me telling it to do so?
Click to expand...
Click to collapse
after you s-off'd, it went back to locked
On another note I use 4EXT Recovery. It has been the only recovery, for me, that actually wipes caches correctly and runs the Fix Permissions Correctly. You know that it does because it leaves a log on your sdcard. While any of the CWM that I've used doesn't.
And since you're s-off then don't worry about re-unlocking.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
after the shut down, when the phone comes back on, does your battery % drop significantly?
gotpriest said:
Trying to diagnose a problem with my Brother's phone. He got his Amaze about 8 months back, no issues whatsoever on the Stock ROM other than a backlighting issue on the bottom buttons that HTC is aware of.
Since installing ARHD Gingerbread, he gets random, and frequent phone shut downs when trying to wake it from lock/sleep statuts. The phone just shuts off and restarts by itself.
We were hoping that migrating to ARHD ICS this week would solve that issue, but it has not. It still shuts down randomly at wake.
Click to expand...
Click to collapse
i had same problem when i was on ginger bread and updating the sim to wifi calling enabled sim fixed this problem for me. but i am having this random reboot problem again since i updated to ics. i just do a battery pull if it shuts down by itself else it get stuck in a reboot loop.
Just out of curiosity...do you have fast boot checked on or off in Settings> Power ? Turn the check off and see if issue still happens. Just something to try.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Hi I have a GT-i9300 that worked well over a month, after a hard reset I can do anything but when I'm on a call I have no audio either in or out.
I have checked with skype and viber and the hardware is fine. Also I have tried several firmwares (official and custom) and several modems and I still have the same issue.
I cannot apply my warranty since the phone was purchased overseas, please help me on how to fix this.
I am posting this on android development since it is more likely that some developer know how to solve this, also the thread on Q&A is dead. I apology if this is now the correct forum to post it.
Please help me to get my Galaxy back :crying:
dsv591 said:
I am posting this on android development since it is more likely that some developer know how to solve this, also the thread on Q&A is dead. I apology if this is now the correct forum to post it.
Please help me to get my Galaxy back :crying:
Click to expand...
Click to collapse
1. Relax, it's a common issue nothing to worry about and it can be easily resolved.
2. I understand that you are panicking but development is not a right place for it. In future you may post in q&a section.
3. Are you rooted and have you played with modems lately?
☞ sent from GS3 or Nexus
ceo.mtcl said:
1. Relax, it's a common issue nothing to worry about and it can be easily resolved.
2. I understand that you are panicking but development is not a right place for it. In future you may post in q&a section.
3. Are you rooted and have you played with modems lately?
☞ sent from GS3 or Nexus
Click to expand...
Click to collapse
Thanks for the reply
Right now I'm on the original FW again, but yes, I was rooted and tried at least 8 different modems.
Any suggestion?
Moved to Q/A, questions don't go in the development section.
I had the same symptons after updating stock firmware. Both speaker and earpiece worked fine but not in a cell phone call. You should try and let the connection to the other side last long enough and see if your cellphone modem resets like in my youtube video.
http://www.youtube.com/watch?v=fo46OXWEcX0
If it is like in the video than you're out of luck because with me it was an hardware error. Samsung service center could not repair that, the send it to samsung HQ. After I got it back it stated that a hardware part was replaced under warranty.
Any suggestions apart from above ones?
Sent from my GT-I9300 using xda app-developers app
dsv591 said:
Any suggestions apart from above ones?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I saw your pm now.
If you are familiar with rooting... Root again.
And perform full wipe, install latest check rom v4. It is LG8 firmware and comes with modem.
Then share this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That should fix your issue. Let us know if you have tried this out and it did not fix the issue.
☞ sent from GS3 or Nexus
I just fixed it by installing the latest version of an official software from UK. It started failing like before, but after 5 minutes or so it fixed by itself. Don't know why exactly, and I'd really like an explanation so I can know how this happened exactly, but has been working for over 15 hours with no issues (reboots included).
Of course I don't want to wipe again or try another software at the moment, because I don't want everything to happen again, but if someone can really tell why this happens and why it started working alone this will help a lot to know how to reverse it in case it happens again.
Thanks everyone here
dsv591 said:
I just fixed it by installing the latest version of an official software from UK. It started failing like before, but after 5 minutes or so it fixed by itself. Don't know why exactly, and I'd really like an explanation so I can know how this happened exactly, but has been working for over 15 hours with no issues (reboots included).
Of course I don't want to wipe again or try another software at the moment, because I don't want everything to happen again, but if someone can really tell why this happens and why it started working alone this will help a lot to know how to reverse it in case it happens again.
Thanks everyone here
Click to expand...
Click to collapse
Did you obtain fw trough kies? I got the same problem
I got it from samfirmware.com. however today it stopped working again for no reason... could a simple hard reset damage the hardware??? I think it's silly but I can't come up with another explanation.
Tomorrow I will try the firmware told 3 posts above and post the results. In the meantime I'm trying to find an answer of why it stopped working again...
This is frustrating, I'm located in Costa Rica and Samsung states I can only apply by warranty in Germany... so I guess I'm by myself and all of you guys trying to resolve this
Sent from my GT-I9300 using xda app-developers app
Still the same issue, here is the screenshot after the full wipe and software installation.
Please advise
Hi guys. Has anyone come with a solution to this problem? I'm facing the same issue as the OP.
I was running on stock firmware, then flashed the leaked JB firmware and rooted it again. Then flashed the stock firmware again. Once I did that, I started having this problem.
Any sort of help would be appreciated.
Thanks.
Sent from my GT-I9300 using Tapatalk 2
Similar problem. I can solve it by full wipe but when I restore application data with MyBackup Pro or in CWR nandroid backup, I lost sound in call.
It begun after flashing leaked JB ROM, then flashing original ROM via ODIN and now on CM10.
Advice?
Maybe modem problem. Try to flash different modems. http://forum.xda-developers.com/showthread.php?t=1740061
fallenwout said:
I had the same symptons after updating stock firmware. Both speaker and earpiece worked fine but not in a cell phone call. You should try and let the connection to the other side last long enough and see if your cellphone modem resets like in my youtube video.
http://www.youtube.com/watch?v=fo46OXWEcX0
If it is like in the video than you're out of luck because with me it was an hardware error. Samsung service center could not repair that, the send it to samsung HQ. After I got it back it stated that a hardware part was replaced under warranty.
Click to expand...
Click to collapse
I'm having the EXACT same issue. Everything else works fine. It came out of the blue. Last thing I was running was Omega 13.1 with Siyah Kernel 1.5.3. I've had the phone for about 3 or 4 months, then about 4 days ago it started happening out of the blue. I tried flashing and wiping anything and everything you can imagine, including stock firmware. Sometimes it would work for a few calls, then back to square one. Yesterday I went to a stock firmware, then restored my Omega nandroid and it worked fine until I rebooted. I have no idea what's causing this issue and it's really pissing me off. It seems common with no fix.
I live in the US and this phone is originally from Vodafone UK, bought through Amazon sim-unlocked (real SIM unlocked, not via any app). Samsung UK is asking me for the ROM info I'm on, which I can get by flashing a stock ROM (CSC, Baseband, etc), but they're also asking me for a UK address, which is troubling.
Here's every ICS modem ever for the i9300 (not by me): https://www.wuala.com/UpInTheAir/SGS3/Modems/I9300/ICS/?key=n0KVwtIMZPE8
JB leak back to stock ICS
libb said:
Similar problem. I can solve it by full wipe but when I restore application data with MyBackup Pro or in CWR nandroid backup, I lost sound in call.
It begun after flashing leaked JB ROM, then flashing original ROM via ODIN and now on CM10.
Advice?
Click to expand...
Click to collapse
Have the same problem. Flashed the leaked JB and now then went back to stock ICS (Meteor Ireland) from sammobile.com. Still no luck. I'm flashing every modem I can find but still no audio at all. I had some issues with the JB leak that calls sometimes (more than not) didnt work but then a reset would usually solve it.
Anyone have any ideas what else can be done?
I've read it's hardware failure and that Samsung will fix it. However if you live in a region where the phone isn't sold and you imported it through Amazon, Negri, etc, you need to contact the original seller, because Samsung won't touch it if you send it to them directly.
Have you tried wiping cache and fixing permissions? I've had lots of sound issues on JB, all went away after flashing omega 25, no problems now either on omega 27
Also try flashing the modem again, clear cache/fix perms,
Sent via TCP/IP
Full wipe will always be an answer. However, restoring application can bring the problem again. If you want to backup the contacts just use the export to usb storage in the settings instead of using backup apps in restoring. Also try to perform fix permission.
BelJanss said:
Full wipe will always be an answer. However, restoring application can bring the problem again. If you want to backup the contacts just use the export to usb storage in the settings instead of using backup apps in restoring. Also try to perform fix permission.
Click to expand...
Click to collapse
Issue occurs even before installing the applications. Seems to be something related to the modem firmware, however each modem behaves differently but with the same issue
Sent from my GT-I9300 using xda app-developers app
About a month ago I had issue with phone stuck on HFA. Several great people offer help to try to fix issue. Could never get problem to go away.. sent to Samsung since Knox was 0x0 and sent same phone back notes said they just flashed software.. I got it and ran good till 2 days ago.. my text wouldn't send. Everything else worked fine.. voice and data and apps.. so did the prl and profile update like sprint asked me to .. then text worked but no data... decided to do factory reset.. then issue was couldn't sign in to google(data not provisioned ).. after talking to sprint and Google they said not sure how to fix it.. only solution that worked was roll back to NAB everything working.. anyone else experience anything like this? Phone out of warranty like 3 days wondering if I should try to get a replacement or is a NC5 software issue
kosmo42o said:
About a month ago I had issue with phone stuck on HFA. Several great people offer help to try to fix issue. Could never get problem to go away.. sent to Samsung since Knox was 0x0 and sent same phone back notes said they just flashed software.. I got it and ran good till 2 days ago.. my text wouldn't send. Everything else worked fine.. voice and data and apps.. so did the prl and profile update like sprint asked me to .. then text worked but no data... decided to do factory reset.. then issue was couldn't sign in to google(data not provisioned ).. after talking to sprint and Google they said not sure how to fix it.. only solution that worked was roll back to NAB everything working.. anyone else experience anything like this? Phone out of warranty like 3 days wondering if I should try to get a replacement or is a NC5 software issue
Click to expand...
Click to collapse
I would ask how's it going but here we are again. Lol I remember that, and have to say NC5 has not had that many issues. So, it ran good for about a month, then would not send a text ? Did Sprint say anything about working on a cell tower ? Nothing was changed, added, or deleted prior to it not working ? Try going to settings/connections/more networks/mobile networks/network mode/ and make sure it is on LTE/CDMA not automatic. Also when you update your PRL you have to completely power down, and then reboot the device for the PRL update to take effect I know it says update successful but that don't mean it has been applied to the device. If you go back to NC5 from NAB again your have update your PRL example : I updated to 4.4.4 today to check and see if Nh7 has a flash counter, which it does, so I went back to 4.4.2 NC5, after about 3 flashes I finally got NC5 back to official status, and than tried to download an app from Google Play it said no connection retry so I updated my PRL and rebooted the device, and my 4G LTE started working again. Where were you when it quit working ? Where you on the road out town ? If you leave town you should update your PRL it is supposed to do it automatically, but doesn't always happen.
Well I was at work and no issues got home and I got a text when I tried to reply it would not send.. I could only receive . So my 1st thought was towers since I had issues with tower close to my house several times.. after asking sprint said network was good my gf. Gs3 had no issues either .. so then tried prl and profile updates that would make my text work but my data would drop.. after a restart text would fail but data worked.. after talking to sprint and google.. ( they blamed it on rooted since they can see what apps u buy) titanium... but after going back to NAB all issues gone.. I am currently back on NC5 did a full un root version and will see. Guessing it's a NC5 issue or hardware
kosmo42o said:
Well I was at work and no issues got home and I got a text when I tried to reply it would not send.. I could only receive . So my 1st thought was towers since I had issues with tower close to my house several times.. after asking sprint said network was good my gf. Gs3 had no issues either .. so then tried prl and profile updates that would make my text work but my data would drop.. after a restart text would fail but data worked.. after talking to sprint and google.. ( they blamed it on rooted since they can see what apps u buy) titanium... but after going back to NAB all issues gone.. I am currently back on NC5 did a full un root version and will see. Guessing it's a NC5 issue or hardware
Click to expand...
Click to collapse
Ok, sounds like software, here is what I would do. Go to micmars here is the link http://forum.xda-developers.com/showthread.php?t=2712205 and get his NC5. Now back up all your data i.e. pics, music, etc. to a ext sd card or PC desktop. Go ahead to do a factory reset. Next with odin on your PC flash a fresh copy of NC5. Now this is the IMPORTANT PART check your download mode screen should look like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Both lines at official status, sometimes you end up custom and official, so if not boot into your stock recovery, and use the device keys and do a factory reset again. Then odin flash a fresh copy of NC5 again. I know it seems like a lot of B.S. but I call it taking out the trash, you need to get back to stock square one. Boot it up see if the issues are gone, if so odin flash a recovery here is the link for Philz CWM 6.12.9 hltespr its bulletproof https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ then root your device here is the link for SupSu v 1.94 http://download.chainfire.eu/396/SuperSU/ Now if everything is working with no issues, make a backup so you can always restore back to a working OS. Let me know how it goes ?
Will rather stay on NAB or NC5 for little bit more.. warranty runs out in a week if new or old issues happen will root and break Knox to get custom rom.. only reason staying on stock was my warranty.. I was just curious to see if anyone had encounter issues like me.. also upgrading to note 4 in few weeks
kosmo42o said:
Will rather stay on NAB or NC5 for little bit more.. warranty runs out in a week if new or old issues happen will root and break Knox to get custom rom.. only reason staying on stock was my warranty.. I was just curious to see if anyone had encounter issues like me.. also upgrading to note 4 in few weeks
Click to expand...
Click to collapse
Cool, been thinking about an LG G3 myself. Definitely not as many features as Note 4, but more of a pure android OS. The main features of the G3 is no KNOX, little to no bloatware, will run under water, and a removable battery.
Yea wish Samsung would make the bloatware optional.. and Knox also LG3 does look sweet also