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 !
This is not a formal release, because i dont have the phone and anything posted here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same for the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
pchatzop said:
This is not a formal release, because i dont have the phone and anything tested here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same fro the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
Click to expand...
Click to collapse
The bad thing about this phone, is that it has no qfil rom to flash, if it bricks
Enviado do meu LeTv 1 Pro através de Tapatalk
It has a working twrp to take a full backup, and i think there is the nx506j updater that can restore it if something goes wrong.
I will try this weekend maybe
Enviado do meu LeTv 1 Pro através de Tapatalk
pchatzop said:
This is not a formal release, because i dont have the phone and anything tested here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same fro the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
Click to expand...
Click to collapse
i have bricked my smarthphone, nothing comes up, not even serial port
dont ask if i have the drivers, i do
any help
Try using the nx506j updater from here: http://www.androidiani.com/forum/mo...-z7-nx506j-stock-lollipop-lang-pack-bb72.html . The power+volup+voldown trick for some seconds might help.
I want to know exactly what you did, in order to be able to help you, i will search the nx506j board schematics later to find a testpoint, for jumpstarting the board in download mode.
I also removed the rom from mega, i am building one that does not flash the baseband.
pchatzop said:
I also removed the rom from mega, i am building one that does not flash the baseband.
Click to expand...
Click to collapse
have you found anything to help me?
Nubia ToolStudio
twd123 said:
have you found anything to help me?
Click to expand...
Click to collapse
Sorry about your phone
Can you put it in the recovery mode?
Try NubiaToolStudio or QPST you find references here
Since dear user @komplot confirmed that the build is booting and mostly working, i decided to take a further look, and i will have a new build up in the mega folder a few hours, for anyone with the device willing to test. Bugs mentioned was audio and orientation, and i did a lot of work on them, hope they are squashed. If my recovery is not working, try this one: https://mega.nz/#!ctkxlabD!rPlcL4mrCz8oNwZ_JqmR1Or2XXYThAQcX-38D_ABNa0 (found it at androidiani forum)
@twd123 please tell me what steps you took to lead to this outcome for the phone(if you still have it), and its current state, to try and think of a way to unbrick it. Unfortunately, i can not find schematics for the nx506j board online, to find the download mode testpoints, but removing the battery and using the combination volup+voldown+power while the phone is connected to the computer could be of help. The guides for lg g3 might also be of help(if you use toolstudio once you get to download mode), the points used are kinda similar.
Nubia Z7 nx506j RR Experimental
Thank you Pchatzop for your effort! I am glad you reply on my comments.
So, to be more specific about topic, I have try to flash your custom ROM a few times from I left the comment here. I try to use TWRP 3.0.2-0 to flash the latest RR (....2016115), however this build doesnt boot at all even when I try to use previous chinese TWRP based on TWRP 2.8... It looks the chinese TWRP works better than 3.0.2 because I have found the 3.0.2 doesnt flash even RR build 20160925, which previously works with errors I have described in my comment.
So, the resume is: I have found working only ResurrectionRemix-M-v5.7.4-20160925-nx506j.zip flashed by chinese TWRP.
Thank you, and I will test your build as soon as you publish it.
Have a nice day.
Try using the kernel from the 0925 release with the new release. Like replacing with boot.img from the 1105 release with the one from 0925. If it boots, i will know what to fix next.
Experimental RR nx506j
pchatzop said:
Try using the kernel from the 0925 release with the new release. Like replacing with boot.img from the 1105 release with the one from 0925. If it boots, i will know what to fix next.
Click to expand...
Click to collapse
Hi, I try to use boot.img from 0925 with 1115 release as you advice, and it works. That means, I can boot, the problem with gyroscope senzor (or with switching from portrait to landscape) dissapear. However the mic and speakers are still def, even if I overwrite the file "mixer_paths.xml" with the version you provide me. There are trouble with camer as well. Start camera ends with message "Cant connect to camera". I have used TWRP 3.0.2 which I have found at the forum. I have boot from build 0925, wipe dalvik and etc... There are some minor things as the diode of aside virtual butons arround middle button doesnt light. The knock wakeup doesnt works, but as i mention, those things are only minor. I have try as well to go back to version 3.88, but it ends with complete mess and even recovery doesnt works. So I wouldnt like to use stock ROM with lots of bloatware any more.
Would the provided information helps? Please feel free to ask me to check something else. As soon as possible with as many effort what I could, I will help.
Thank you.
Thanks for the feedback, now i know this is a kernel issue i have to fix(hopefully i can get you a bootable build soon without patches). The camera issue was there on the 0925 release? Because i used the drivers from 3.88 release on the 1115 build, and they could cause some problems with camera(had problems making them working on z7 max and mini). If camera works on the 0925 build(which contains 3.86 drivers), let me know. The audio problem is probably from the ak4961 dac chip on the z7 that the max and the mini are missing. I have send 2 emails to zte requesting the lollipop source for the z7, no response yet, hope they get back to me, as that is the key to getting this audio chip working. Please get me some logcats when you try to playback music, and try to use the nubia camera apps i have in the mega folder, could make a difference with the camera.
After the other tests, you can try this boot.img(with the last release), hope the kernel is fixed and booting now.
pchatzop said:
After the other tests, you can try this boot.img(with the last release), hope the kernel is fixed and booting now.
Click to expand...
Click to collapse
Hi.
I try camera functionality from 0925 build and it works flawlessly. The camera apk, you provide me from 3.88 drivers, doesnt work at all. It just blink after start, nothing happens, no error message.
I cant provide you with a log about mic and speakers functionality. After start to play music file or youtube everything looks OK, except there is no sound. No error messages. Have I missed something?
Tell me please what to check and I will dig it.
Thanks.
So camera works with the 3.86 blobs, that is really great to know. I have a new build, 3.88 blobs, hope you can try it and report what works and what does not. Camera is pretty easy to fix(by rolling back the blobs) so dont fret if it does not work with the latest build. I think the audio chip is working correctly, just the audio path was wrong in the kernel(i attempted to fix that in the latest build) and did not lead the decoded audio to the speaker or headset. Please try the last build without any patch and report back. Hopefully we will have a pretty much working build, with only minor bugs.
pchatzop said:
So camera works with the 3.86 blobs, that is really great to know. I have a new build, 3.88 blobs, hope you can try it and report what works and what does not. Camera is pretty easy to fix(by rolling back the blobs) so dont fret if it does not work with the latest build. I think the audio chip is working correctly, just the audio path was wrong in the kernel(i attempted to fix that in the latest build) and did not lead the decoded audio to the speaker or headset. Please try the last build without any patch and report back. Hopefully we will have a pretty much working build, with only minor bugs.
Click to expand...
Click to collapse
I have try 1119 build (3.88 blobs) you provide me. Many thanks. I flash it by TWRP (doing standard wipe before), everything seems right, no error messages or something suspicious. However after re-boting to system, the screen looks strange. Display was black, but turned on, no message of life after 5 mins I turned it on/off, after that, phone starts, but situation was strange again. After first show of logo, sreeen is fade out to 5 white strips left on. No signs of life again. I have seen very similar situation when I try update to official 3.88 drivers, but at that time a half of screen stay in wide blue strip turned on. After restart, the phone was not possible even to start in to recovery mode. I solve the situation "accidentaly" when I try to use the Nubia emergency tool. It was not a big time, because the phone could not connect to PC because of some trouble with snapdragon USB drivers... After few trays the phone was possible start at least to recovery. Any idea?
Thank you.
Im sorry it got you to that big trouble. Can you please try replacing the boot.img from the last release with the one from the yesterdays post and report back? Thank you for testing!
I created a new boot.img, this one is based on the booting and working configuration of 0925 builds, with only my attempted audio fixes included, hope you can try it with the last release. If you still get problems, i will roll back the blobs to 3.86 as well, seems the new 3.88 update caused many problems for many users of the nubia z7. Our priority is getting a working custom rom for the z7, and it doesnt matter much if the 3.86 or the 3.88 blobs are used.
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
Hey guys,
Newbie here. I am very excited about my new yet to be received phone - X829 using EUI 5.8.016S (Stable).
I care about call quality, camera quality, sound quality using the CDLA technology headphones (in this order).
I don't consider myself a heavy user - I talk maybe 30 mins per day maximum, light web browsing, no gaming...
Should I stick to the stock rom supplied EUI 5.8.016S or is it worth upgrading to something else? Like, will a custom ROM yield better call quality, camera quality and sound quality than the stock rom?
Thanks!
Andrei
Hi, i am also a X829 user and i would suggest you to try recently released EUI 6.0.030s, which has great battery life and network receiving, of course quite stable.Camera quality is also good.
This one is the same rom modified by CrisBallGreece that includes system adblocker by default and preinstalled magisk manager, removed unnecessary leeco apps and chinese garbage apps.
Here is the link:https://drive.google.com/file/d/17dVqqd_kRZol6ORhvs_Ubri7xNldRLvw/view
Google apps : https://drive.google.com/file/d/1bcmKY1yaoVAnLViL0aSabAdpjK6jpn9x/view
Hi,
Thanks for the reply. How do I get the 'cleaned-up' version installed? Not familiar with either super su or magisk. What is the easiest way to go about doing this? The threads I found make reference to super su but can't download it from the official website. Sorry if this was already addressed in a different thread...
Thanks a lot!
Follow this link :
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
First of all, you should unlock your bootloader and flash twrp (a custom recovery mode, allows you flash rom).
Download rom and gapps then put them to your device, backup your data.Reboot to recovery mode.Press wipe - wipe data, go back and press install - find the rom you copied and flash it.Once the phone booted, go back to recovery and flash gapps in the same way then reboot.That's it.
This is the only way to flash any type of rom.
Btw, magisk is a root manager like the supersu, gives you root access of the system.
Hi,
Thanks for the very informative post. I got my phone yesterday and started to play with it As expected, I had some hard time installing the EUI 6 CBG version. I think it's because I installed a very recent (if not the most recent) version of TWRP...From memory, the one I installed is 3.2.2...Anyhow, EUI seemed to install fine and I got the success message displayed in TWRP along with the note 'phone will reboot in 5 seconds' or something like that - which never happened.
I then installed Lineage OS 15 Oreo because I didn't know how to downgrade TWRP.
So do you think that the problem I had was because of the TWRP version I used? how does one downgrade that?
Also, I installed the Gapps (https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577) but Google services gives an error message...'Google stopped working'. Is there a workaround for that?
Thanks!
Andrei
Hi mate,
Right after that " phone will reboot ..." note, you should have rebooted the device by pressing and holding the power button for 8-9 secs and it would be fine.
No, latest twrp version works fine and is compatible with this firmware.
Hmm, you can try to delete the app data of google play services.Have you flashed the los 15 with full wipe ?
Btw los 15 is not mature enough.It still has some battery consumption problems and the battery life lasts not as long as EUI's. + I don't know if it has CDLA sound mod but it doesn't contain dolby digital sound.
Hi,
I believe I did a full wipe (dalvik, cache, system, data).
I will try again to flash EUI 6 by CBG tonight.
The workaround for gapps was to flash them at the same time with LOS 15. Previously I flashed LOS 15, rebooted into the system, went back to recovery twrp and then flashed the gapps.
Thanks!
Yeah, flashing the gapps with rom in a row is not a workaround, its a must-to-do.Unfortunately i forgot to mention this to you.Apologises..
Great, thanks a lot! it worked. I'm getting used to it right now. Will play with this ROM for a couple of weeks and then try something else...I was thinking SLIM7...any thoughts on it? have you tried it? any red flags?
Thanks!
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Drollach Gûntar said:
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Click to expand...
Click to collapse
Not sure if it supports CDLA...I tried this rom briefly the other day and I had a hard time with the camera...battery seemed to deplete quite fast, but I'm sure it can improved with different settings, greenify, etc...try it and let me know if you like it.
Which other roms have you tried?
Thanks!
Most non-eui roms will have slightly worse battery life making greenify an absolute must.
But if you want a non-eui rom (like me, I just hate eui) I recommend lineage 15.1 or du12 by infrag(my current rom).
Hi man, after a long time, I had a change to try different rom, named mokee 7.1.2 (nougat).Well, it's not bad, performance is excellent, not a single lag at all. Also the battery backup is good, not perfect as EUI but acceptable.
Pros of this rom are, it's being updated in a nightly period and Android security patch is dated as august 5 2018 !
You may check it out if you are interested..
Regards.
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Milanche78 said:
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Click to expand...
Click to collapse
Try Aex Treble Pie, you will be satisfied.