Related
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 !
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
1. Must backup your data. You are gonna wipe it
2. Use flashtool and downgrade to a rootkitXperia rootable firmware. I used 26.1.A.1.112 but other rootable should be the same. (wipe data may not be necesary in this step but i did it just in case)
3. When flashing done, root the device with rootkit, and install TWRP
4. Use xperifirm to download the 3.111 FW then create the prerooted with its system.ext4 and kernel.elf
5. Flash the zip via TWRP, wipe dalvik, then start the phone and check that you have superuser, and go about phone to make sure everything went well and your in 3.111 with its kernel also.
6. Use flashtool again to flash 26.1.A.3.111 but you this time you must EXCLUDE SYSTEM and KERNEL to keep the root, in other words your gonna flash everything but kernel and system so be sure you ticked them, also should wipe data so you can start fresh and avoid possible incompatible things.
7. Let the phone starts, mine took around 10 - 15 min. You should now be in 26.1.A.3.111 with root and no random reboots. So far im using it since 12 days and no reboots nor system hangs, ive updated all apps via playstore, and even downloaded several 500Mb+ games and its working really fine
Click to expand...
Click to collapse
Sorry for this guide that isnt noob friendly, im doing it quite hurry because im too busy with work but i wanted to share what worked for me with everyone. If this works for you too and someone wants to do a better noob friendly guide with links and such go ahead it is ok.
[NOTE]Random reboots seems to happen when there are diferent modem versions. Special thanks to @sergioslk who discovered this.
Of course, all credits to the respective developers who worked really hard on this tools for us. Thanks devs.
Hey, thanks. I had 26.1.A.2.167 rooted, so I just installed 3.111 with data wipe through prerooted zip on top of 2.167, and then reflashed everything except for kernel and system (also data wipe here) like you wrote in your post. So far so good - almost 30h without reboot, which is far better than before.
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
fpghost84 said:
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
Click to expand...
Click to collapse
Did you first flashed via TWRP the prerooted zip you created with system.ext4 and kernel.elf extracted from 3.111 FW? did you wiped data after completing flash? which version of FW you had just before flash 3.111?
Yeah, I did as you say. My phone orig had 2.167, but it upgraded itself recently to 3.111, then I downgraded to 1.128 to root, before using the prerooted TWRP zip (with system.ext4 and kernel.elf extracted from 3.111 ftf) to upgrade back to 3.111.
EDIT: I think something went wrong when I created the ftf bundle from the files downloaded from xperifirm. I repeated the whole process and now I'm not seeing the random reboots (at least for an hour with quite a few apps installed and updated) ....So yeah in summary many thanks for this ...It would be nice if it was mentioned on the main how to thread.
thewailer said:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
Click to expand...
Click to collapse
Thanks so much for posting this. I had thought of doing this myself but quickly ruled it out because I thought it was a dumb idea (no offense) and wouldn't work, but after hearing of your success I thought I'd give it a try anyways and I've been powering through a ton of app installs/updates and haven't had a single reboot so far. It sounds to me like this is the key.
I'll post an edit after a few days to let you guys know how it holds to my personal test of time.
Thanks again!
Update:
Well, it's been nearly a week now and I've yet to experience a random reboot. This is definitely the fix we've all been waiting for! I hope this knowledge can be spread to all who have been plagued with this issue!
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Hey @sergioslk,
Thanks so much for your contribution. I found your post about this problem but it was kind of hard to read whereas the original poster here went into a bit more detail. Sometimes that's all people need, is a little more information. I'm sure you've made other contributions to the community that have been extremely valuable.
To reitterate, this is definitely the fix to the problem we've all been facing when it comes to using the pre-rooted zip to get root on the latest version. I had suspected this to be the problem awhile ago but couldn't really figure out how to fix it.
Thanks everyone for all your hard work!
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Oh dude many thanks for this contribution, i havent readed your post before, but now i can say theres a know reason why the random reboots occurs. Im not an expert in android, i just tried this as a last hope, ive tried everithing, no google account, no wifi, no moibile data, no sdcard, deleting all bloatware, untouching bloatware, a lot of wipes..... and this last one for some reason worked but i wasnt sure why untill now. Thanks again!
I just bought my first Chinese phone at Bangood. I noticed that a lot of people are having problems with some of their units so I was wondering what are the first things that I should check when I receive mine. Thanks
First, try to turn on after fully charged :=)
check if your phone is rebooting after some time, I think that is most/biggest issue. Search through threads to find more.
You may try to "boot" twrp and backup all incuding current original recovery prior "flash". So via "fastboot boot recovery.img" you can
boot without overwrite it. Try Multirom so you can have multiple roms to compare without flash new over current one.
Check for:
- random reboots
- fingerprint scanner working
- random flashing on the screen
make a backup of your delivered x829 original rom and radio, i did it not, now i am searching for it
easymik said:
make a backup of your delivered x829 original rom and radio, i did it not, now i am searching for it
Click to expand...
Click to collapse
How to make backup of radio? What part to backup for it?
I have X829, got it last week , with 16s vendor rom, then I flash 19S Indian rom.
there is no issue in the phone, it is amazing and only 170 euro by banggood
also fingerprint sensor work fine.
mame76 said:
First, try to turn on after fully charged :=)
check if your phone is rebooting after some time, I think that is most/biggest issue. Search through threads to find more.
You may try to "boot" twrp and backup all incuding current original recovery prior "flash". So via "fastboot boot recovery.img" you can
boot without overwrite it. Try Multirom so you can have multiple roms to compare without flash new over current one.
Click to expand...
Click to collapse
Wouldn't rooting void my warranty? And also, do you recommend updating it to the latest official update?
Thanks for all the tips guys! A lot of people will find this thread very useful
ShiroNek0 said:
Wouldn't rooting void my warranty? And also, do you recommend updating it to the latest official update?
Thanks for all the tips guys! A lot of people will find this thread very useful
Click to expand...
Click to collapse
Where did I wrote to root it?
Further more - which warranty? Is there any seller giving warranty?
BTW: rebooting issue was caused by sim card with data within second slot - dual sim issue. Works nice switching sims now.
mame76 said:
How to make backup of radio? What part to backup for it?
Click to expand...
Click to collapse
There should be System image in the internal storage I think it would be the original system of the phone. I have not try to restore it though. I also got X829 everything work fine but FP was dead after 2-3 days I got it.
---------- Post added at 04:08 AM ---------- Previous post was at 04:02 AM ----------
For the phone, FP is the problem hope it keep working for you. Other than that just install TWRP and root it (there is guide in this forum) so you can update/flash custom rom.
Link [COMPLETE GUIDE] usb driver, adb, fastboot, recovery(without flashing), backup, flash
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
Check it's turn on/off, can make phone call, sound, camera etc just normal stuff usually there no problem I think.
What I've done (got mine this week):
- tested wifi
- tested 4g/lte
- tested ir (le control)
- tested fingerprint
- tested the sound
Booted the second most recent version of twrp (the last one hasn't worked properly), backed up everything, copied it to my PC/Cloud storage.
Flashed twrp and Chinese 23s (stock rom) to check all the built-in features and how they are supposed to work.
Then I intend to move to some custom.
Regards ?
Sent from my Le X820 using Tapatalk
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
cyberwytch said:
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
Click to expand...
Click to collapse
I'd love to try it, but unlocking bootloader plus installing a new one (clockwork or the other one), plus the mix up between my non-standard edition E8305 and most current release not being any guides up-to date. Its daunting for a newcomer like me.
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
sky.walker said:
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
Click to expand...
Click to collapse
Clean install is your best bet in fixing most issues
Factory reset helped at first but after a week of using it it became slow again
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
cyberwytch said:
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
Click to expand...
Click to collapse
Any chance you can help me revert to 6 or 7.0?
JeansenVaars said:
Any chance you can help me revert to 6 or 7.0?
Click to expand...
Click to collapse
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
try disable Movie Creator app
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks. Im back to 5.1.1 and running smooth. Not sure how long to wait before giving Last version another shot
JeansenVaars said:
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
mceyhan4 said:
try disable Movie Creator app
Click to expand...
Click to collapse
sky.walker said:
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
Click to expand...
Click to collapse
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
what was firmware just prior to 32.4.A.0.160 (7.1.1) ???
Hello could you kind folks please guide me what was official (not rooted) Sony Z5C firmware prior to the above monster? I want to go back but don't know which one it was? Please link me to official version just before this latest ( 32.4.A.0.160 (7.1.1)) NASTY update! Many Thanks.
JeansenVaars said:
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
Click to expand...
Click to collapse
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
BlackFriar said:
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
Click to expand...
Click to collapse
What about the issue with browser page reloading every time you switch to a different app and then back again to the browser? OP reported this issue, and I've been having it, too. Did that get resolved for you with the disabled Movie Creator crap?
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Sent from my E5823 using Tapatalk
Superrman said:
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
Click to expand...
Click to collapse
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Kiers said:
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Click to expand...
Click to collapse
Google "Flashtool" - it's literally the first result there. Also, Flashtool has XperiFirm, which can download almost all firmwares for Xperias and pack them into ftf format automatically.
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Tomixxon said:
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Click to expand...
Click to collapse
Yes, just flash an older version with Flashtool, it's how we got TA backup to be possible
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.