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 !
Related
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!
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
facuarmo said:
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
Click to expand...
Click to collapse
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Elite.101 said:
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
Click to expand...
Click to collapse
Okay, please let me know what happened when you're done.
lecorbusier said:
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Click to expand...
Click to collapse
For a better stability, you must flash it. For example, running this ROM without this patch, the RIL keeps crashing, taking in mind that Movistar and Tuenti (a lesser know Argentina provider, a recently started provider), are not being detected.
I'll wait for the next build. Then probably use it as a Wireless AP, as there are huge problems resulting from the small data partition and Ram. I still hope that MMs z-buffer feature provides some solution. This whole mess started about half a year ago and getting worse, on the L9 and a similarly featured tablet with CM11, so it's not the rom's fault. The tablet has plenty of space on the data partition, however, but ram and SoC face similar problems.
My current wireless AP is an Iphone 4s with only 0,5GB Ram. And it's is still working reliably, no apps freezing and fcing, and I can access websites which will make Firefox on the L9 and said tablet quit every time.
All the affected apps seem to deal with HTML code and are supposed to use the system webview engine. Updating the Google webview engine is possible with CM12.1 and 13, but to no avail, only taking space on the data partition.
facuarmo said:
Okay, please let me know what happened when you're done.
Click to expand...
Click to collapse
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Codeplex said:
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Click to expand...
Click to collapse
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
facuarmo said:
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Click to expand...
Click to collapse
I currently Have the LG-P769. T-Mobile variant
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
Alright. Ill try this right now.Ima do a backup first.
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
im still having problems. i just finished setting up and now i have a kernel panic.......reverting now
Elite.101 said:
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
I currently Have the LG-P769. T-Mobile variant
Click to expand...
Click to collapse
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
facuarmo said:
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
Click to expand...
Click to collapse
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Elite.101 said:
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Click to expand...
Click to collapse
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
facuarmo said:
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
Click to expand...
Click to collapse
True.one thing I want fixed is the headphones problem where sound goes to speaker
Elite.101 said:
True.one thing I want fixed is the headphones problem where sound goes to speaker
Click to expand...
Click to collapse
That's quite strange, seems like a bad kernel. For me, using the P760 (in the P778g, Argentina, LATAM) works fine, both speakers (front and rear) and headphones.
When the headphone amp starts to clip/overdrive, this is accompanied by an unplugging event for the headphones. Artas' CM11 and CM12.1 are affected, too, but I could get my P760 to work with decent and stable sound output. While in Rammar's PA sound volume was even lower than with the stock rom(too low for even bothering to take the headphones with me) , CM12.1 is loudest. In order to not accidentially trip clipping and unplugging events, which will also reset volume to safety level, requiring to turn it up and clip again etc etc, Ilimited max volume to 80% in the Headset Button Controller app,which allows to control volume via headset mic button.
Hello friends,
In a moment of a severe mental handicap, I appear to have flashed a Mi4(cancro) ROM in EDL mode when I was trying to unlock my bootloader.
(The reason was that the guide I was using had a broken download link, so I searched for the filename and downloaded from one of the mirrors I found. I did not realize I was now downloading a file with a different device prefix (cancro instead of kenzo.).
So after the unavoidable brick, I was able to recover by flashing a proper Kenzo MIUI rom with disabled device checks (Since the phone now thought it was a Mi4, I guess).
MIUI is booting, but most of the functions are broken:
- No camera
- No SIM/Service
- Can't adjust brightness
- No rotation
Maybe there's more stuff broken, but I did not check every corner.
I moved on to try CM13, but that won't boot up at all (just sits there at the boot animation).
So far everything I've tried to get the phone back into a working state has failed, but I'm still getting used to this phone's specifics, so I may have missed something.
Please tell me there is something I can do.
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Abd121 said:
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Click to expand...
Click to collapse
Thank you. I can indeed get to recovery, but I always end up without sim card and camera when I flash an official rom.
I just tried to go back to the shop rom from geekbuying, that at least made brightness and rotation work, but still no signal/camera. I feel there's some firmware missing or was overwritten by my stupid action and now there does not seem to be a simple way to get it back up.
EDIT: So I just found out that my IMEI is gone. I will try to use a guide to re-set it. Hopefully, that will get mobile service running again. Dunno about camera, though
Coming from an MM eXistenZ installation (not sure what exact version, i think it was 5.6.5 final) I wanted to upgrade to O or at least N.
I have tried RR-O builds 20180316 and 20180213, RR-N 20171020 Final, CR-O 20180316, CR-N 20170918, but the result is always the same.
I get a smoothly running installation with only one obvious quirk: Whenever there are no apps running and the screen is off, after some amount of time (sometimes instantly, sometimes after 10 minutes or more) i can either not turn the screen on again and my phone reboots, or it reboots by itself without me interacting.
The only way I can reliably prevent my phone from crashing is playing music (via Spotify), even when muting media sound. While charging the phone will not reboot as well, until it reaches 100%
I tried different performance modes, with high performance resulting in (subjectively) worse results, i.e. reboots after a shorter amount of time, and almost thought energy saving mode would have fixed the problem as it worked for about 20 minutes, but then it began to reboot again.
I am using TWRP 3.2.1-1 and tried with/without Magisk (16.0) and flashing MarrowKernel (O-0.6, N-0.6/0.5).
Before flashing I performed a full wipe and also replaced the SD card
Logs from RR-N-v5.8.5-20171020-sirius-Final with Magisk 16.0 and MarrowKernel 0.6
dmesg: https:// cloud [DOT] haggi [DOT] me/index.php/s/C969nUuKTWMuJ1g
logcat: https:// cloud [DOT] haggi [DOT] me/index.php/s/as0qMPNYpGh4YKD
Sorry for the ugly links, but the logs are too long for a post, I cannot find an attachment option and as a new user may not post outgoing links yet
Please reflash Stock firmware via sony emma tool
This should help
Do not use existenz rom before switching to any custom rom reflash Always last stock and then update it to custom rom
Thank you, flashing stock firmware did the trick. Didn't work on the first try and my phone got stuck on the Sony bootscreen, but flashing the ROM a second time fixed the problem.
Running on RR-O now without any noticeable problems except for AudioFX crashing when sound starts/stops playing, but this should be fixed easily.
haggi94 said:
Thank you, flashing stock firmware did the trick. Didn't work on the first try and my phone got stuck on the Sony bootscreen, but flashing the ROM a second time fixed the problem.
Running on RR-O now without any noticeable problems except for AudioFX crashing when sound starts/stops playing, but this should be fixed easily.
Click to expand...
Click to collapse
Hi, did you root after flashing stock firmware ? or proceeded already to installation instructions ?
---------- Post added at 09:35 AM ---------- Previous post was at 08:46 AM ----------
rcstar6696 said:
Please reflash Stock firmware via sony emma tool
This should help
Do not use existenz rom before switching to any custom rom reflash Always last stock and then update it to custom rom
Click to expand...
Click to collapse
Hi Guru,
Do you recommend using Sony Emma Tool over Flashtool for flashing stock FTF ?
I would also like to try your ROMS, but I'm completely new on this device and not sure what to do when your installation instructions is to flash first stock ftf.
I wanna ask about Emma, does you recommend Emma for updating bootloader? I read in somewhere that if updating bootloader you cannot use stock ftf or restor TA backup cause it will kill the device. Is that true?
19iceman32 said:
Hi, did you root after flashing stock firmware ? or proceeded already to installation instructions ?
Click to expand...
Click to collapse
I have not rooted my phone after flashing stock FW
darknessmc said:
I wanna ask about Emma, does you recommend Emma for updating bootloader? I read in somewhere that if updating bootloader you cannot use stock ftf or restor TA backup cause it will kill the device. Is that true?
Click to expand...
Click to collapse
Sorry, I can't tell you as I continued flashing RR without having booted my phone in between and my TA partition is already lost since flashing the first custom ROM because I didn't know of it
Hey, I am using a redmi note 4 Snapdragon version,and I installed custom rom on my device,the installation was successful but hardware components are not accessible to me now.Like, wifi,bluetooth is not turning on, camera app is not present and even flashlight icon in notification shade is blurred out.
I installed resurrection remix and aex ROMs,I know they are fine cause i have installed them before(same versions) in the same phone,but now they are showing problems.And gapps are not installing either twrp recovery shows corrupt file even though its not for sure.
I think i messed up while wiping data ,I wiped the internal storage and formatted the phone too, that is the only thing i did that was different this time.
Please help if there is a link to any thing that i deleted and need to replace please provide that,
Thank You
Sounds like a firmware problem, get latest firmware here, and flash it from recovery.
RogueMoon said:
Sounds like a firmware problem, get latest firmware here, and flash it from recovery.
Click to expand...
Click to collapse
It worked!, Thank you man.
Also I have a problem with the same device that it charges in recovery or switch off mode but it does not charge while in system.Thinking of starting a new thread but if you can answer ,no need to do that.Again Thanks.
Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!
RogueMoon said:
Weird. First I would make sure that the device indeed doesn't charge in system (install Ampere app, or use a USB power meter if you have one) - otherwise it might be a UI problem. Other than that, if that's indeed the case I would do a clean reflash, starting with flashing a latest stable MIUI in fastboot, then recovery again, factory reset (DONT format system) and ROM (which one are you using?) again. Maybe others could chime in. Good luck!
Click to expand...
Click to collapse
Thanks i will try that.?