Low Volume on Call - OnePlus 3 Questions & Answers

I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?

romaolp said:
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
Click to expand...
Click to collapse
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

sakarya1980 said:
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.

romaolp said:
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
Click to expand...
Click to collapse
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?

pulsorock said:
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
Click to expand...
Click to collapse
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.

tnsmani said:
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
Click to expand...
Click to collapse
Thank you @tnsmani. Yes, I just remembered that. I don't recall unlocking the bootloader on this device before.
So, can anyone using OxygenOS with Oreo 8.0 confirm if this patch works, I could go ahead and try it. It would suck going to the steps and wiping everything for it not to resolve the low volume issue.
Thanks!

Low volume in custom roms using nos

i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy

davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!

Does it give you any error during flash of the zip?

pulsorock said:
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Click to expand...
Click to collapse
After flashing twrp.. Reboot into recovery and root your phone
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Is there a similar file for low loudpeaker volume fix?

davide136 said:
Does it give you any error during flash of the zip?
Click to expand...
Click to collapse
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
drfox96 said:
After flashing twrp.. Reboot into recovery and root your phone
Click to expand...
Click to collapse
So rooting is required to avoid twrp being replaced by stock recovery again?

pulsorock said:
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
So rooting is required to avoid twrp being replaced by stock recovery again?
Click to expand...
Click to collapse
Yes

davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?

phrozenwire said:
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
Click to expand...
Click to collapse
I can tell you that i tested with my phone and this never happened, considering that's not touching any file but this "/system/vendor/etc/mixer_paths_tasha.xml", I think it's something else causing what happened to your phone. Did you flash something else? Otherwise i'll take it down

amg_driver said:
i took a look in this file/fix.
my advice: dont flash this. imo the values are set too high and this fix could damage the hardware. as davide136 said "almost broke my ear"...
Encloused my fix created for latest NOS (Oreo).
But should work on other roms as well (if path to mixer_paths_tasha.xml is /system/vendor/etc/)
Try "88-fix". If it's a bit too low for you than flash "90-fix" - as filename suggets, its 2db louder.
Click to expand...
Click to collapse
Is it Oneplus 3T compatible?
Thank you for your work!

Hello everyone, i want to clarify something, it was never a software issue.it's just DUST, believe me.
After trying all the mods and flashable zips and increasing the values, it only increase the volume but it becomes like a walkie talkie and not clear at all. So i decided to open the phone and it's very simple you can watch a video, nothing very dagerous.
Remove the 2 screws and the sim tray, carefully try to rise the screen with a credit card from the lower part of the phone.
Disconnect the battery, remove the 8 screws and remember their placement( there is one hidden screw middle left under the white stick)
Remove the signal cable and screen and extentions ones, and carefully unclip the motherboard from the top middle and try to rise it, slowly
I advice to put some ductape on the camera lenses so no dust can go in
Remove your speaker
You'll find it clean and be surprised, but the remove the black mesh a'd then you'll be shocked.
Clean the black one with alcohol and then use alcohol+toothbrush to clean the speaker grill on the phone
Clean it till you can see light through it and when you blow on it air can pass through
Reassemble your phone and connect the battery at lassst you dont provoke a shortcut when you screw or something and VOILAAA

Related

Downgrade from CAN-L11C432B320 (EMUI5/7.0) to CAN-L11C432B100 (EMUI4.1/6.0)

hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
I think we need to flash first the EMUI 4.1 recovery.img
Houamei said:
I think we need to flash first the EMUI 4.1 recovery.img
Click to expand...
Click to collapse
i've flash erecovery.img and recovery.img extracted from the update.app --> reboots too on 5%
extracted 4.1 Recovery: mega.nz/#!1MdXmART!Bbd3COTNnCsOB4iVMwQ0vOQhdEvzWDaWVnRhMwFMg08
xCite86 said:
hey community
I've tested CAN-L11C432B320 a while and miss the equalizer-app, also have an extreme powersaving device (...) but if i'm running runtastic they will turn off gps after 30 seconds display-off-time, background-services like whatsapp, pushbullet, etc.. will close after a few hours "inactivity", bad fingerprint-performace, some xposed-plugins have massive battery-drain and wont work....
so on.. i still search a while if its possible to get my stock emui 4.1 back...
...and yesterday i found this post:
h**p://w*w.htcmania.com/showthread.php?p=24388723
it looks like there was a full CAN-L11C432B100 and CAN-L01C432B100 firmware but i could not install them
i put the update.app in SDCARD:\dload and tried to install them with original EMUI5-recovery and the extracted EMUI4.1-recovery - everytime it hangs up at 5% and reboots after ~5 minutes.
i'm clueless.. maybe someone will also downgrade and found a solution how to get them work...
sorry from my bad english and the link-modification but i'm new here
Click to expand...
Click to collapse
There is a link for a rollback update, but i'm not home. When I get there, I send it. About battery, try to use greenify to help it to last long.
You can't just try to use a full package because of versioning scheme they use.
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Same problem here, still drops at 5% even with the new file
I just wana know the best way to revert to stock
---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------
and sorry I don't have an SD Card
Vinnom said:
Here http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v72696/f1/full/update.zip
Click to expand...
Click to collapse
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
can we extract all from the ota update zip and install via flash? can this work?
xCite86 said:
thanks for the file but it won't work for me too..
the install process stops at 5% "Installing update" and reboots after a few minutes
Click to expand...
Click to collapse
Hmmm, sorry, I thought it would help. In fact, the package is listed as a rollback to M, but it is for CAN-L11. The rollback for CAN-L01, I didn't find. As there isn't many differences between those models, I thought it would work
EDIT: now that I read the op again, I noticed that your model is CAN-L11. I wonder why it didn't work
Houamei said:
can we extract all from the ota update zip and install via flash? can this work?
Click to expand...
Click to collapse
No, it won't.
The reason behind this is because system partition get smaller (because nougat way of update) after updating it to emui 5. So the old system.img won't fit the new partition
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
So you downgraded?
Mikey94 said:
My phone only hangs up at 5% when the usb cable is connected. When i open the download mode without connected usb cable, it works.
Click to expand...
Click to collapse
did you downgrade your nougat successfully with the files above??
edit: i tried it without a connected usb cable and got "software install failed!" after short time
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
i think this should work if you or someone else share a backup i could try..
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
no, in my opinion the nougat bootloader want work with mm.
I would flash the firmeware of mm and after that flash twrp and restore the backup after that [emoji106]
It will work. There is a backup within twrp thread, from bluesmothie.
Vinnom said:
It will work. There is a backup within twrp thread, from bluesmothie.
Click to expand...
Click to collapse
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Michiel0912 said:
Is a restore of a CAN-L11 backup from Android 6 in TWRP not possible?
Click to expand...
Click to collapse
Yeah, thanks Vinnom...
xCite86 said:
found it...
https://forum.xda-developers.com/showpost.php?p=70259615&postcount=2
re-unlocked bootloader
flashed twrp with fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
copied all the dropbox files to /external_sd/TWRP/BACKUPS/FPFDU16930014596/1970-03-18--16-40-58_CANC432B100/...
wipe all partitions except sd-card
recover the complete backup
so @Vinnom many thanks for your help. i got my phone back to life (after fomatted data partition) and got downgraded to CANC432B100 now.
Click to expand...
Click to collapse
Did the same thing, but first TWRP didn't find the backup. So i did a small backup just of the boot partition, so that TWRP makes a new backupfolder "FPF4C16A07000014"". Now i renamed the " FPFDU16930014596" to the new "FPF4C16A07000014" and TWRP found the backup and i was able to restore :highfive::highfive:
Small Addition:
It was a freaking fight to get my bootloader unlocked again, cause i lost the unlock code.
The websites (english and asian) are freaking BS. Was not able to get to the page where you get the code, so i downloaded DC-Tool and payed 4 dollars for the damn code.
Now the code is saved in my owncloud, dropbox, google drive, on a sheet of paper and google notes. No way to lose it again
B100 firmware is much smoother than B320 but has a lack of comfort, like i'm missing the new quick settings with double pull down and the touch responsibility of slide bars (like the volume bars) is not very good in B100... But i won't upgrade to 320 again, because of the following points that make it a no go for daily driver:
- Camera is very slow and hangs up
- Video playback is very slow and buggy (no matter if it's in the galery or youtube, ect.)
- Fingerprint is too slow
- Whole system gets very slw if you dont clean up the app history
Will upgrade again when there is a new version out
please am having same issue here. tried restore but still not booting.
problem is cust. what do i do about it.
HELP ME

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

lenovo zuk z2 plus goes into bootloop after opening the camera

hey everyone
so i flashed lineage os 7.1 on my zuk z2 and everything was working perfect
after that i tried aicp 13.1 nightly and it was also working flawlessly but problem arrived as i used the gcam port for hdr+ in snapdragon 820 devices, initially the camera worked fine and everything was working normal but suddenly after some time whenever i opened gcam my phone hanged and then went into fastboot mode itself(the notification light is on ) and after i rebooted the phone it went into bootloop.
then after doing too many reboots finally my phone started and i changed the rom as i thought it might be a rom problem but in every rom whenever i tried to use gcam or even whatsapp default camera my phone suffered the same problem every time so i reflashed the stock zui firmware but the problem still persists as whenever i uses my stock cam or any other camera my phone goes into bootloop
when i searched the web i wasn't able to find a single thread related to my problem
really worried
please help
any help would be appreciated
*sorry i'm a noob to all this flashing etc*
also the bootloop occurs only after using the camera otherwise everything works fine
!!!!!!!!!!!!!!!!!!!!PLEASE HELP URGENTLY!!!!!!!!!!!!!!!!!!!!!!
Very strange issue. Dont know why that happens to you.
Which camera are you using? Try BSG port, v1a. Im using it and it works great. https://drive.google.com/file/d/1ubVpPrrZRkvVPH9qT7XzlttwcCVPxUcM/view?usp=sharing
Also try this, which i did also. Flash with qfil ZUI Oreo 243 version, you have thread for this, Jintu jose is OP.
It didnt lock my bootloader, and it didnt encrypt my phone memory.
Flash TWRP
Flash latest AEX Oreo
Flash GZR gapps
Magisk (you have to do it two times, once when u install rom, let it boot, than again flash in recovery)
Install google camera i posted and try.
This setup is working great for me.
I've tried every possible version of gcam but it happens always
Now the main problem is that I can't even use my stock camera app as whenever camera opens it goes into bootloop
I've flashed the stock ROM using qpst tool
But the problem persisted
Can anyone please tell me what should I do?
Is this a problem with my kernel?????
What should I do?
I am currently using aex latest version ?
Thanks for the reply but please help
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
@vuckovic_stefan please help!!!!
avi badak said:
@vuckovic_stefan please help!!!!
Click to expand...
Click to collapse
You said in previous post that you flashed stock rom via qfil
Tell me is camera working fine with stock rom?
@vuckovic_stefan no the problem remained same even with the stock camera of my phone
avi badak said:
@vuckovic_stefan no the problem remained same even with the stock camera of my phone
Click to expand...
Click to collapse
Than I would say it is hardware problem man
If you have warranty, flash stock rom, I think 1.9 lock bootloader, and reclaim warranty
I say this because I never had this problem, ever, on any custom rom nor stock
Can I reclaim the warranty after locking the bootloader
avi badak said:
Can I reclaim the warranty after locking the bootloader
Click to expand...
Click to collapse
Yes you can, just make sure there are no traces of any type of modifications.
Can you tell me the steps so that there are no traces left
avi badak said:
Can you tell me the steps so that there are no traces left
Click to expand...
Click to collapse
Flash zui 1.9 by qfil method.
Everything should be stock.
Fir step by step guide, search on xda discussion section.
There are several guides
Thanks for the help
Will let everyone know about the problem if I found one
the same thing that happen with mi zuk z2 but changing the rom to a another witch no uses the lineage os kernel solve the problem
I have the same problem the camera only works on the stock Android 6, maybe someone will find a solution for the guarantee it's impossible to hand over the phone purchased with AliExpress.
Hi, i have a similar issue with my ZUK, i have changed ROM, and after flashing it went to constant bootloop. i thought it might have been an issue with the rom, so i flashed again, but the problem stayed. Phone started and gapps were installed ok. It worked well for a bit and then it went to bootloop again (last time was when i switched from camera to video). I have formated data, to start clean, flashed rom again, but this time it got stuck on the ''android'' logo and doesnt seem to go further. Phone is recognisable by my PC and i have access to internal memory.
I have same problem now ...nothing working for me ..please help
avi badak said:
Thanks for the help
Will let everyone know about the problem if I found one
Click to expand...
Click to collapse
Sir one I've the same problem.
Did you find any solution?
Please share if you did.
---------- Post added at 09:45 PM ---------- Previous post was at 09:45 PM ----------
Rufjan said:
Hi, i have a similar issue with my ZUK, i have changed ROM, and after flashing it went to constant bootloop. i thought it might have been an issue with the rom, so i flashed again, but the problem stayed. Phone started and gapps were installed ok. It worked well for a bit and then it went to bootloop again (last time was when i switched from camera to video). I have formated data, to start clean, flashed rom again, but this time it got stuck on the ''android'' logo and doesnt seem to go further. Phone is recognisable by my PC and i have access to internal memory.
Click to expand...
Click to collapse
I've the same problem.
Did you find any solution?
MohdAhmed said:
Sir one I've the same problem.
Did you find any solution?
Please share if you did.
---------- Post added at 09:45 PM ---------- Previous post was at 09:45 PM ----------
I've the same problem.
Did you find any solution?
Click to expand...
Click to collapse
Yes, unfortunately it turned out that the battery has been damaged and that was just nit enough voltage to startup the phone, I have replaced the battery myself for cost of approx 15 usd. It is very easy to open the phone ad replace it, as all tools are included with battery, you just need a hairdryer to melt the acrylic tape holding the glass back of the phone.
Rufjan said:
Yes, unfortunately it turned out that the battery has been damaged and that was just nit enough voltage to startup the phone, I have replaced the battery myself for cost of approx 15 usd. It is very easy to open the phone ad replace it, as all tools are included with battery, you just need a hairdryer to melt the acrylic tape holding the glass back of the phone.
Click to expand...
Click to collapse
Sir but in my case I can go to twrp recovery easily, without any issues.
After your battery replacement the phone was back to normal self, i.e the room you previously installed was working without any issues?
Or did you had to use qfil and start from stock 2.5 zui and then re unlock bootloader and install twrp and custom ROM?

oneplus 3 having very rare issue

i have oneplus 3 which is working on oos 4.0.2 but no sounds
it worked fine on oos 3.1.2 only once & no mic speaker error but now restarting on oos 3.1.2
i tried mega unbrick thread
all guides regarding bootloop & dm veriety guides too
if do dirty update through adb or through OTA i m facing mic & speaker error issue
with clean update mobile again start restarting problem at welcome screen & automatically boots into recovery
tried custom firmwares too & having mic speaker issue
can someone help me to solve my problem
wbr
Mobile Smoker
Have you tried any custom rom? I had same problem on my older device Lenovo p2 and custom rom helped me to solve the problem but I reinstalled different roms 1000 times and it fixed my problem. Even on stock rom
Tried custom roms too but on custom roms facing mic & speaker error u can say no sound at all
Hello..I recently flashed havoc is on my OP3.I am having issue with screen wake up..when I double tap still it won't wake up and even while pressing the power button..just capacitive button lights appear. After pressing power button for 4-5 times it sometimes wakes up..please anyone suggest me the problem.
Is there no expert here who can guide me?
..::Mobile Smoker::.. said:
Is there no expert here who can guide me?
Click to expand...
Click to collapse
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
tnsmani said:
WARNING: I am no expert but since you threw a challenge, I can not resist.
Install TWRP latest official, wipe system, data (if possible internal storage also), Dalvic and cache. Flash OOS 5.0.6, no Magisk or any other apps. Boot and check. You would have lost TWRP but if everything is ok, it can be flashed later.
Click to expand...
Click to collapse
Really appreciated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
..::Mobile Smoker::.. said:
Really appropriated that someone finally offered a different try
Give me 10 minutes i m gonna be back with result
Btw
Thanks in advance
Click to expand...
Click to collapse
Click the thanks button.
Am waiting for your report.
After erase all partitions via twrp
I installed full OOS & rebooted system
On setup screen phone showed factory resetting & restarts in recovery mode automatically
Same thing happened when i tried to format all three options inside official recovery
I dont have any personal data in it i just wanted to boot my mobile in working condition with working speaker & mic
tnsmani said:
Click the thanks button.
Am waiting for your report.
Click to expand...
Click to collapse
Anyother solution bro?
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
..::Mobile Smoker::.. said:
Anyother solution bro?
Click to expand...
Click to collapse
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
emuandco said:
Do not wipe system image, only system! Or just use the Factory reset option in TWRP instead of selecting any partitons manually.
Click to expand...
Click to collapse
I did as u said but on first boot showed
Factory Data Reset
Restarting
tnsmani said:
Use the Mega Unbrick Guide Method 2. Follow the instructions meticulously, don't skip any step. Boot into OOS 3.x.x and check. If everything is working, don't upgrade or flash any other ROM including OOS immediately. Hopefully, your issue should be solved.
Click to expand...
Click to collapse
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
..::Mobile Smoker::.. said:
After unbrick full zip
I am having same factory data reset Restarting
Issue
Ryt now only 4.0.2 oos can boot up my OP3 A3003 fully ( But having mic & speaker error)
If you can fix audio problem on oos 4.0.2 OOS will be ok with me i dont want oreo or anything
I just want my mobile back in working condition
Thanx in advance
Click to expand...
Click to collapse
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
tnsmani said:
After booting up in 4.0.2, connect ear/head phones and check whether they work. If they do, then it is not a ROM/software problem. By speaker do you mean the earpiece or the regular speaker of the phone?
Have you checked the mic and speaker ports for possible blocks?
I am running out of ideas.
Click to expand...
Click to collapse
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
..::Mobile Smoker::.. said:
Non of any audio working checked my attached pics these are failed test of mic & speakers
I installed magisk audio modules too but no audio
& ryt now my OP3 is on 4.0.2 & working without audio
I m gonna be crazy
Click to expand...
Click to collapse
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
tnsmani said:
Final attempt: check the headphone/earphone port since normally when you plug them in, the built-in mic and speaker connections are disabled. Your device's port may be stuck in that position.
Click to expand...
Click to collapse
I tried with headphone no change
Even with bluetooth no audio at all
..::Mobile Smoker::.. said:
I tried with headphone no change
Even with bluetooth no audio at all
Click to expand...
Click to collapse
In that case, most likely a replacement of the daughter board is required ie. hardware error.
tnsmani said:
In that case, most likely a replacement of the daughter board is required ie. hardware error.
Click to expand...
Click to collapse
One my op3 booted in OOS 3.1.2 & audio was perfect
So i dont think so it has hardware problem

OP3 phone is un-usable please help!

Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart

Categories

Resources