Database Users

Unable to update MX4 Pro and several other issues

Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.

Audio drivers went missing during update

I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736

The problem with the phone is it makes no sounds?

gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms

Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?

Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.

It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.

So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1

Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.

Zenfone 5 LTE (T00P) Erroneous Behaviour

Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.

Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....

Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.

Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.

Install firmware in Asus Zenpad 10 (P00C)

Hello everyone!
I have a big issue with this tablet: after the new update to 7.0 I notice the system is consuming a lot of internal space and the system is not stable like it should be.
What I would like to do is to revert to the previous firmware/version or try to install any other bootloader wich now is beeing very difficult because I dont know how to do and the steps that I read to do it are very complicated.
Does anyone can help me to install the firmware on this tablet?
I have everything, the tools, the firmwares, cables, the pc... everything.
Then other thing is when I try to go to bootloader, I mean, is in chinese!!! Is not even simple and looks I cant solv my problem at all.
Please, anyone can give me a hand?
Thanks in advance for all your help and sorry about my bad english.
I will give a party with those who can help me and I will offer beers to everyone!
Thanks!

Where did you get the firmware ?

I have exactly the same problems. I managed to get the Z300M software from the ASUS website but not the P00C. Would like to roll back to software from May or before.

same EXACT problem... looks like audio_dump .wav files are the culprit but cannot delete them. used fastboot to factory reset after 7.0 update and problem came back 3 days later! can't find any older updates for the p00c online either

Somebody posted a possible solution in another thread. Can you see if it works for you?
diplomatic said:
Hey guys, see if this works:
Install Engineer Mode MTK shortcut
Turn on developer options
Start Engineer Mode. Go to Hardware Testing -> Audio -> Audio Logger
Uncheck any boxes that are checked
Profit (and maybe reboot)
All in all, I don't understand why some tablets have the logging enabled and other don't, if this is indeed the issue. I've never seen it enabled, even after a factory reset.
If you have the audio logging issue on either the Z380M or the Z300M, please post:
Your firmware SKU
Your region code given by the property ro.config.versatility (may need a terminal app to read that via getprop)
The firmware version you were on when you reset your tablet
Click to expand...
Click to collapse

Killed P9 Lite instead of getting back to live, maybe there is a last chance?

Hello, short Story before. I got a full Hand of non working mobile phones because being full of a hell of viruses.
5pcs. younger ones.
2 Huaweis and 3 Samsungs.
Well so far 4 PCs. are saved.
Getting into the phone wasn´t possible anymore. Data not important so I resettet over the Buttons to original Status. -> Worked fine.
But one Piece which is a Huawei P9 Lite guess it is a single sim? was the button method not possible cause it wanted a Software update and Installation of WLAN failed (EMUI)
Getting into the phone for any informations was also not possible because of all the viruses and not working right ahead anymore.
Well ok -> will use High Suite for stock Firmware -> this mobile phone is not supported and also couldn´t activate MTP as I am not in the phone. So far.
Next Idea -> ok. will take the C900B300 and go back to Marshmallow. From original HUAWEI site.
Took the European Version in German. Did it over EMUI (hold 3 Buttons) and worked so far but when I turned on I was stucking on the WIFI+. Even pressing the button -> further nothing anymore. So I thought -> maybe another stockfirmware useful.
Again C900B300 and then I think I did the big mistake. Took out the sdcard during it was rebooting (HUAWEI was already visible) and now it is big crap. Stucks at HUAWEI. Turning off not possible. This EMUI is not possible anymore. Just with a trick I am able to get into fastboot. Yeah. But what then? Reading TRWP which I know from Samsungs but putting it on with ODIN. ODIN doesn´t work with Huawei. Do I Need TRWP to get it back to normal Firmware? Mobile phone was never customized or anyhting else. just normal stock was on it and is the wish to get a clean back. Resetting to factory was not possible anymore.
So my questions, even I know it is my fault. Any rescue possible?
What could be the best stock Firmware. I Guess it is a single sim from Austria unlocked and unbranded. Would also take Nougat again. Just wanted to get it back to normal working and now I guess I have a big letter holder. Model from the backside is VNS-L31. More I don´t have.
Thanks a lot for any help for my being an idiot. Samsungs are much more easier than HUAWEIs.

Blimey mate,
This really just boil down to what partitions were damaged in your case- Most likely your system and data,
however since you are still Technically running unmodified emui you could manage to sort of salvage it.
The logic is this:
Most custom roms for the p9 lite build on top of emui (patching the system image) rather than replacing it (like the way samsung smartphones do)- so you could flash the rom, it would wipe your phone clean of viruses in the process and then proceed to do a hard restore back to emui.
1.) get your phone into fastboot and flash this twrp http://www.meticulus.co.vu/p/forum.html#nabble-td27
2.) Then flash this rom : http://www.meticulus.co.vu/p/ressurection-remix-for-hi6250-devices.html MAKE SURE YOU FOLLOW THE INSTRUCTIONS ON THIS SITE VERY CAREFULLY
3.)Follow this guide to do a hard restore https://forum.xda-developers.com/huawei-p9lite/how-to/tips-revert-custom-rom-to-official-t3668413
good luck!!! if you have any questions hit me up!

Hi
Hi Exiatron00,
thanks a lot for your maybe solution way. Will do it this evening after work and come back.
Hopefully it works cause as mentioned in other threads -> don´t think that the original owner opened the Debugging so that I can work over a tool. FRP locked is in fastboot. This was already mentioned in other posts which I have read here in the forums.
Thanks for your step by step explanation. Will do it. Hopefully it works. I am really pissed of my own that i was unpatient with the sdcard. That´s a mistake which shouldn´t happen. Anyway it did. So i will try to do everything to get back working again. I am from IT so I am not such a DAU but newbie with HUAWEIs. Most are Samsungs.
Will give Feedback.
CU

If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.

Hi,
well adb for flashing not working as device not found. Hi Suite installed. Guess that the USB Debugging is not enabled. hrmpf.
There is a similar thread of somebody with no enabled USB Debugging.
https://forum.xda-developers.com/nexus-4/help/fastboot-recovery-remotely-enable-usb-t2177440
He writes an solution how to enable in fast boot mode with using N4 toolkit.
Search for a p9 lite toolkit and found this
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
may could work?
Big **** -> as Long as USB Debugging is not enabled as Long I am not able to Flash TWRP over adb.
If I connect to PC Hi Suite opens automatically. So driver should be fine as pc recognize the phone.
hm?

Got it working somehow
Exiatron00 said:
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Click to expand...
Click to collapse
Hi Exiatron00,
got it working somehow!!!!
Bought a 3 day licence for DC Phoenix where you are able to put Firmware even in fastboot with FRB lock and no USB Debugging on.
So I got the IMEI and Fitting Version which is a L11.
Downloaded it original from Huawei as I still want a original stock Rom not customized which was
HUAWEI P9 Lite Firmware (VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU) only wokring one.
BUT the big Problem is that the apk Android System Web View is missing in the ROM. A known Problem by HUAWEI. Yeah now I am stucking in the Setup wizard like this guy who mentioned also the solution whell the reason of this Problem.
https://forum.xda-developers.com/hu...stuck-initial-setup-upgrade-to-t3498097/page2
So my question now. How do I get the apk on the phone still no USB Debugging? Does anyone have this Version original incl. this apk? Maybe an img. from a running working System?
Only way I am able to put the Firmware on is DC-Phoenix. It is valid still two days. Maybe someone can help me? Please?
So an Image of VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU incl. Android System Web View, so that I can go ahead and use the phone again please?
Thanks a lot.
Kind Regards.