Related
Hi,
I am currently running the latest XEU UK firmware KI4
Firstly when i go into the gallery for the first time since reboot it say "loading..." for about 5 - 10 secs (Very slow) I have about 2 pictures on my sd card and have just purchased a new samsung 32gb card as i thought the old card was the problem but it appears not
Next when i reply to a text message I have to tap the message box a few times before the keyboard eventually pops up
Can anyone else confirm??
Thanks
Well I'm not 100% sure, but it may is software related. Yesterday I flashed a stock ROM and had similar problems.
Is it rooted? If yes, I'd do a backup with ClockWorkMod and flash another ROM to check if the problem is there too.
Sent from my GT-I9100 using XDA App
Its not rooted, completely stock rom, ill just wait for the next update i suppose
thanks
You could check the background programs and see what's loaded...
Since its stock it might be bloatware problem, so I will say software for sure.
Backup data and factory reset is always the first solution .
jje
hi guys
i just installed the new 4.0.3 firmware (I9100XXLP2_I9100OXALP2_OXA from sammobile.com) and after one time restarting my phone when im pressing the power button the phone immediately shutting down and no menu for choosing
i reinstalled the rom and no change
used full wipe , *2767*3855# , recovery mode wipes, reset factory and also installing 4.0.1 and same problem
(after installing ICS roms the welcome screen isnt appears like new rom )
and the phone dosnt have slide or any kind of unlocking method (i tried to change to FC, pattern or key but no changes at all)
but when i using stable 2.3.5 its doing fine
any hope to fix this problem guys??
Same problem on this thread.
http://forum.xda-developers.com/showthread.php?t=1445144
ICS ROMs are still unstable.
in first
i flashed 5 GSII with this rom and no one has same problem and i should say mine was fine at first so whats difference between GSIIs ?
In case you do not understand this is a leaked test beta rom not for public use buggy is the name of the game . Why so many noobs want to install a not yet finished buggy test rom baffles me .
jje
JJEgan said:
In case you do not understand this is a leaked test beta rom not for public use buggy is the name of the game . Why so many noobs want to install a not yet finished buggy test rom baffles me .
jje
Click to expand...
Click to collapse
Mr jj i know thats beta and also buggy but if there is a bug it should be for all and i checked it with the same series of GSII, so if im asking for help i need to know is there any problem with my GSII or what?!!
hiddenstar said:
Mr jj i know thats beta and also buggy but if there is a bug it should be for all and i checked it with the same series of GSII, so if im asking for help i need to know is there any problem with my GSII or what?!!
Click to expand...
Click to collapse
No the bugs appear to be more random than for everyone .Possibly compounded by lemming like newbies flashing these test rom s .
You can only tell if something is wrong by testing a stock rom .
However its your choice .
jje
JJEgan said:
No the bugs appear to be more random than for everyone .Possibly compounded by lemming like newbies flashing these test rom s .
You can only tell if something is wrong by testing a stock rom .
However its your choice .
jje
Click to expand...
Click to collapse
u think this blaming going to help?
at least be positive and gimme a way to reset my phone like it was in package
The thing is its a test ROM at the moment and has random bugs.These random bugs can and will appear "randomly" on any phone for anyone.The link I provided you proves that your not the only one.You may have flashed it successfully 5 times before but unfortunatly this time you have been hit by the "random bugs".Its not your fault its just the way non completed ROMs are.Until they are finished these things will happen.
thanks cooza for useful information
what i couldnt understand is: i accepted ur idea about random bug but my phone was doing fine at first so why when i reset the phone that is not going to be the same?
One thing you could try is reinstall the again but on a clean device.This will mean a wipe but not just wipe/factory reset.You could format you phone of all data and therefore just maybe have a chance to get it running properly cos sometimes old ROM data left behind can cause performance problems with new ROMs as they are not always compatable.A full system wipe/install will need you to do the following.First do a titanium backup of your apps and a nandroid just in case.
1.Pass your ROM to your internal-SD
2.boot to recovery and wipe cache partition.Then go to advanced and wipe battery stats and dalvik cache.
3.go to mounts and storage and format data,system and cache.
4.factory reset.
Now your phone is completely clean of all previous data.Now install your new ROM then do a cache partition wipe.I normally do another factory reset before rebooting to avoid bootloops but thats up to you.If you get one you can pull the battery or re-enter recovery and do one.Hopefully this will help avoid the bugs in the ROM.
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
Hi everyone,
I ran into some trouble by upgrading Cyanogenmod 7.1.0 to the latest ICS 4.0.3
Alpha Relase from codeworkx (Build 02122012; http://forum.xda-developers.com/showthread.php?t=1410400).
After upgrading, I noticed the menu and back button are not receiptive to
touch any more and dont work. The background light of the two buttons still
shines. But when I hit either of them nothing happens. The home butten works
though.
While upgrading to ICS 4.0.3 I also upgraded the modem version to XXLPB
Modem (just in case, it matters).
To fix the issue, I tried to go back to Cyanogenmod 7 again, but strangely, here
the buttons dont work now anymore either. I am lost.
Does anyone have a clue, what happend? Its really hard to use Android without
any menu and back button (I installed the virtual button app to have at least
on screen buttons).
Robert
Try to make a clean install of a custom rom through recovery(no AOSP)... If this doesn't help, try to flash an official gingerbread firmware using ODIN....
Sent from my Galaxy S II powered by CheckROM
If your home button doesn't work after ICS ugrade..
If your home button doesn't work after ICS ugrade..
please do it.
1) You must do rooting.
2) install "Root Explorer" application.
3) run "Root Explorer"
4) go to "/efs/imei".
5) you have to make "keystr" file
6) just write down it "ON"
- please use capital "ON" ... not "on"
7) save and rebooting
8) enjoy
I installed several official Firmware ROMs via Odin. Since I got my phone from Vodafone, I used the official Vodafone ROMs. Unforunately without success. The update process went fine (although some ROMs produced bootloops after update), the menu and back button still dont work.
It kind of seems they are physically broken. But how, I cannot explain. Or could it still be a software issue?
eogns119 said:
If your home button doesn't work after ICS ugrade..
Click to expand...
Click to collapse
Well, the home button does work. Its the menu and back button who dont.
I had a look at the keystr file anyway. Its there and it already contains "ON". Still no function...
Try to root and install a custom rom after a full wipe..
Sent from my Galaxy S II powered by CheckROM
hughfollett said:
Try to root and install a custom rom after a full wipe..
Click to expand...
Click to collapse
Shouldn't full wipe and installation of an official rom be sufficient? How would rooting and installing a custom rom again be of additional use to make the buttons work?
l05443 said:
Shouldn't full wipe and installation of an official rom be sufficient? How would rooting and installing a custom rom again be of additional use to make the buttons work?
Click to expand...
Click to collapse
Your basic problem is you have installed Alpha and Beta roms and have lost buttons .
Probability is its software not hardware .Custom roms are of no use .
You need to wipe the lot and determine if its hardware or firmware .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
If nothing is left to do yet with the possibility of Odin rootet firmware.
Of course, the best 3 piece set ...
I guess I am out of luck and have to send the phone to repair.
All the phone wipes and re-flashes with various custom and official roms (tried 1 part and 3 part roms; also with re-partitioning in odin) didnt fix the buttons.
I guess the phone really is broken.
Thanks for your replies.
i have the similiar problem but my home button works but my back button doesnt. it has actually switched and my home button has been doing the functions of the back button and the back button does nothing. it lights up to touch but no haptic feedback or functions. i tried the steps listed above with writing the script to ON and rebooted and still same issue. worked fine until i flashed the rootbox aokp ics rom. only thing i havent done to try to fix it is to factory reset and re-install rom. any suggestions on another alternative?
any updates on this issue?
Did you fix this problem?
Thanks
InfantryMarc said:
i have the similiar problem but my home button works but my back button doesnt. it has actually switched and my home button has been doing the functions of the back button and the back button does nothing. it lights up to touch but no haptic feedback or functions. i tried the steps listed above with writing the script to ON and rebooted and still same issue. worked fine until i flashed the rootbox aokp ics rom. only thing i havent done to try to fix it is to factory reset and re-install rom. any suggestions on another alternative?
Click to expand...
Click to collapse
Yes it looks like your already have, but go to the AT&T Galaxy S II (SGH-I777) forum to get ROMs and such. This is the forum for the GT-I9100. A different model phone.
The two phones are very close, but there are differences, such as the i777 having 4 capacitive buttons, and the i9100 having only 2 with 1 hardware button.
numediaweb said:
any updates on this issue?
Did you fix this problem?
Thanks
Click to expand...
Click to collapse
Who are you asking?
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Do you wipe before/after you've flashed it/them? Also, I would probably have flashed an older FTF just to check that it's a software issue and not a hardware one (not that any hardware issue would do these things), but just to be sure. If the same issue happens on a lower firmware, then it's a little harder to determine what the issue might be.
Also, try to flash an FTF from your region or one that's fairly close. I flashed a Saudi Arabian .368 FTF the first time, and I had major issues with battery and other smaller bugs, but when I flashed one from my region (Europe), it solved itself. I just think you're having some bad luck, and it sounds like some software issues. Don't forget to wipe the system before or after you've flashed it.
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Shigeur said:
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Click to expand...
Click to collapse
Do you have the C6833? Or the C6802?
Klaos3000 said:
Do you have the C6833? Or the C6802?
Click to expand...
Click to collapse
i have the C6802
Shigeur said:
i have the C6802
Click to expand...
Click to collapse
Okay, I'm going to make an Indonesian C6802 FTF for you, so just hang tight for a little while and I'll have it for you soon (20-30 min).
Here you go: https://drive.google.com/file/d/0B_VjBcIjyoZDX3BFQ0hpeHJHbHM/view?usp=sharing
thanks, ill try, i hope its working...
Hello, im upping this thread...
its still not working, the sound still have same bug...
it seem something weird around bootloader stuff, i find my phone is unlocked bootloader.
is anyone know that unlocking bootloader can make sony xperia z ultra no sound bug like this ?
anywork around ?
i already try installing custom rom, but all my custom rom i try is stuck at bootloop, or just wont stick ( it detected as no OS and just keep on SONY logo )
any recommendation of custom rom that i should try ?
and im really newbie here, all recovery that i install is gone after i flash custom rom, so its really hard to flash rom, root, install recovery and install custom rom which is a dead end ( bootloop )
*its really weird bug...
sometime sony camera app also wont open ( app crash ) + no sound
after rebooting 2-3x its fix both of them, after screen go to sleep
sound is gone, and the camera still works fine until i reboot or no battery ( repeat reboot and it fix the camera and sound ( temporary )
>> relock bootloader, and restore with official software ( pc companion ) still not fix this bug.
You use Google play "soundabout" app .workaround. will restore sound
rockky said:
You use Google play "soundabout" app .workaround. will restore sound
Click to expand...
Click to collapse
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Shigeur said:
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Click to expand...
Click to collapse
it still cant, it seem something wrong with audio engine / system files. when i press 'play' button on walkman it didnt changed.
all sound app didnt work and saying something wrong
as for camera, i cant use sony default camera, but i can use other camera app, such as google camera. but as the audio all 3rd party app not working either directly crash or just stay still play button can be pressed.
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
E90 Commie said:
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
Click to expand...
Click to collapse
ill try, and will post the update, but maybe next month, i hope this work.
a bit busy this month preparing other stuff... thanks for helping
Shigeur said:
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Click to expand...
Click to collapse
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Shigeur said:
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
Click to expand...
Click to collapse
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
RealityFails said:
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
Click to expand...
Click to collapse
how to create a new mixer path ? just delete the old one ?
Shigeur said:
how to create a new mixer path ? just delete the old one ?
Click to expand...
Click to collapse
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
RealityFails said:
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
Click to expand...
Click to collapse
or it seem a hardware issue... just realised after doing a lot of fix..
if it shaked or pressed in some kind area of the screen the sound will gone for a while...
it seem the component are a bit loose inside.
you can see in video below
https://www.youtube.com/watch?v=kO8zN-v9b_w&feature=youtu.be
if someone can confirm this hardware issue, this thread can be closed, thanks a lot for those who help me
Merry Christmas !