Hi! I have a problem with my phone that the mic only work when I record videos but not oin audios in whatsapp or calls. Someone know a solution? I have tried factory reset and changing the room but nothing work.
Thanks
This has been a theme on some devices for years, with no reported solution. I still have my N6 and have never had any problems so I can't speak from experience. If you are willing to try something, I would try using a Full OTA and see if it helps.
If you have TWRP, you can just treat the OTA zip as a ROM and use the install feature. In this case, TWRP will be replaced with the stock recovery. If you first do a backup in TWRP of only the recovery partition, then go straight to wipe data, cache and davlik (clean install), then install the OTA, don't reboot yet, install the recovery backup you just made and finally, go back to the main menu -> reboot and reboot recovery. Once back in recovery (it should be TWRP), you can reboot to system and see if things have improved.
There is some risk that you will loose TWRP in this process so be prepared to use [TOOL]Minimal ADB and Fastboot [2-9-18] to restore TWRP if needed. If you use v1.3 - v1.4 that is the same era as this device.
IMHO, it would be best to ensure you can communicate between your phone and PC before starting any of this. It would make me sad if you loss TWRP and couldn't restore it.
ktmom said:
This has been a theme on some devices for years, with no reported solution. I still have my N6 and have never had any problems so I can't speak from experience. If you are willing to try something, I would try using a Full OTA and see if it helps.
If you have TWRP, you can just treat the OTA zip as a ROM and use the install feature. In this case, TWRP will be replaced with the stock recovery. If you first do a backup in TWRP of only the recovery partition, then go straight to wipe data, cache and davlik (clean install), then install the OTA, don't reboot yet, install the recovery backup you just made and finally, go back to the main menu -> reboot and reboot recovery. Once back in recovery (it should be TWRP), you can reboot to system and see if things have improved.
There is some risk that you will loose TWRP in this process so be prepared to use [TOOL]Minimal ADB and Fastboot [2-9-18] to restore TWRP if needed. If you use v1.3 - v1.4 that is the same era as this device.
IMHO, it would be best to ensure you can communicate between your phone and PC before starting any of this. It would make me sad if you loss TWRP and couldn't restore it.
Click to expand...
Click to collapse
Thank you, but that does not work. I have found that the Mic works on Havoc rom on the camera, but no in stock, in stock it sounds like noise background. I think that if I could understand wich is the "name" of the mics in the mixer_patch, I could change them in each setting and put them as default. But I do not how to read mixer patch.xml
I attached the mixer patch file of Havoc, can someone figure out wich is the name uses in the camera app to record? And how can i put it as default for apps like whatsapp or call phone?
Thank u
Related
I was trying to install CM12 on my VS980 LG G2, and in order to do that I installed TWRP 2.8 because that was what they recommended to use with that version. It worked, and I installed it by using the flashable zip from http://blastagator.ddns.net/twrp/2-8-3-1.php
I used this recovery to install the latest build of CM12 from here: http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269 after wiping my data using advanced wipe as the TWRP thread says to. I wiped Dalvik, system, and cache, and then flashed the ROM, GApps, and SU.
When I rebooted, I was bootlooping. Not too abnormal for flashing things on this phone, so I went back into recovery to restore the backup I had made, to find that the backups file list is completely blank. No (Up a folder) or anything. So I panic, and think I wiped more than I have to, so in order to reset everything and start over, I did a format. It says it completes, so I reboot and get back into recovery, and push a new rom to /data/media/0.
Now, when I try to install that zip, it's not there. Nothing gets placed in there. Installing a zip from anywhere else results in bootloops because it can't boot anything, somehow. It's like there's two partitions and it's trying to boot from the one with nothing on it, and that's the same one I'm shown when I go into the restore menu. There are folders like /data/, /sdcard/, etc still visible if I try the install option, but they do not show up when I try to use the file manager in TWRP.
I'm not sure what to do, can I fix the partitions that TWRP is looking at somehow, or is that not even the issue here? I would like my phone to be usable and I feel that having the recovery it shouldn't be this hard to get it back to booting order.
Thanks
I have close to the same issue on my vs980. Except I have twrp 2.7 and I can't flash it 2.8.4 it always fails. But cm12 and gapps were successful on 2.7 version of twrp except it out me in a bootloop. Which my backup and everything was still there for me to restore. Do you have an issues with random reboots after you put twrp on your phone too?
this is what i've done.
lenovo k3 note with twrp 2.8.7.2_K3_CUOCO92 and rom K3_LOLLIPOP_5.0_ROW_v1.12
i wanted to install one of the latest nougat rom. so i downloaded a twrp 3.1.1.1 made for the k3 note. i flashed the image from my old twrp and replaced choosing the RECOVERY partition.
Flashed ok, i tested a rom, AospExtended-v4.4-aio_otfp-20170708-1051- i flashed it and it worked.
OK BUT.............. i did not wipe the data partition because i received AN ERROR. the new nougat rom was ok but it was a superdirty flash with all the old apps that were crashing. what to do?
i enter into twrp, i REMEMBER that i had the data partition ENCRYPTED so i format it and after doing this i was able to do every wipe i want, included data.
OH PERFECT...... THIS IS WHAT I THOUGHT. i made a full wipe of the rom wiping 4 thinkg : data , internal storage, cache and dalvik cache.
reboot and BOOM. black screen. i press 3 or times the power button and the creen goes on... i am into twrp. from this moment i never returned to see my SYSTEM!
i tested other roms, same problem. i thought it was a twrp problem.... so i installed from the twrp an IMAGE of other twrp... i tested 2 or 3 other twrps specific for my phone k3 note.
I HAD LITTLE BENEFITS with another one.... just because when i press to reboot into system... the phone reboots into twrp AND I CAN SEE IT because the screen is ON, whilst with the "latest" twrp i found...... despites the flashing procedure was ALL CORRECT without errors, at the reboot i always entered into twrp...... BUT INTO A BLACK SCREEN MODE, like if the screen was on...touch enabled, but OFF backligt, and the only way to revive it it is to press power 2 or 3 times, to see the home of the twrp.
i've also found that on MOUNT.......... i always see SYSTEM unflagged, ok i flag it, reboot into system, actually reboot into twrp and system is UNflagged, i try the same thing ALSO flagging READ ONLY...... , idem reboot, twrp.
SEEMS THAT i cannot boot to system anymore. but..... if the twrp was fault, why for the first time let me flash the phone? i really entered into the nougat rom! i found all my old apps and files, but of course it was a DIRTY FLASH, i just wanted to make some wipes.....re flashi the rom.... but oddly i missed the possibility to return anymore to the system.
what could i do at the moment?
how to flash a original image? how to see if this recovery is ok? i donkt 'know where to find my answers......
ah last thing, while into the recovery i was always able to transfer files from pc to phone, but from minutes i am NO MORE ABLE to see the internal memory of the phone.
my computer does not see anything!!! so i am fukked i think....... i did not make anything different.
i only made a lot of wipes... a lot of flashing a lot of testin into recovery. i was able to see it from my pc and put new files through pc. now NO.
solved. i flashed with flash tools an old original firmware android 5.0, then i flased latest twrp with flashtool.... and then flashed the zip of a custom rom.
BL
if u have backup then restore ur stock version or reeboot??
Summary:
1. Flash factory image onto phone successfully
2. Install twrp and make a backup
3. Restore backup after reboot and I'm stuck in a bootloop
I have a new fi Moto x4 running Android 8.1 that I'm attempting to set up. I've reset this phone a bunch of times so here is the standards process:
1. Flash factory firmware as shown in this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I'm using: PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2. After flashing, start up the phone and it works fine.
3. Reboot into the bootloader and boot to twrp using: fastboot boot twrp-3.2.3-1-payton.img
4. Copy in the twrp install file using: adb push twrp-installer-payton-3.2.3-1.zip /sdcard
5. Install the zip via the twrp Install function
6. Reboot the phone into the bootloader then start recovery
7. Use the twrp Backup function to create a backup of the Boot, Data and System partitions on Internal Storage (plenty of space).
8. Reboot the phone into the bootloader then start recover
9. Use the twrp Restore function to restore the backup. Finishes fine.
10. Reboot phone to system but the load won't finish. Phone just alternates between the Android One and the Motorola splash screens. Left it for an hour at one point just to be sure. No love.
Things I have tried:
1. Using twrp via fastboot boot and a hard install
2. Making backups to the internal and external memory cards
3. Changing the partitions in the backup
4. Wiping everything except the external sim card before performing a restore
If anyone has any thoughts I would love to here them.
Thank you!
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
I have the same problem as you are. After I finished install all applications, I made a backup with twrp-3.2.3-1-payton. Then next day I restore it from the backup, after finished backup, it goes to bootloop forever. My version is OPWS28.46.21.12, I download stock rom OPW28.46-13 but afraid to flash this rom since it is the lower version might be break the phone if not backward compatible. Then I search the web and found your message and follow this side fund a higher version of the stock rom OPWS28.46-21-14. I download it and flash it. After flashing complete and boot up, it saying new OTA update available, I don't want to update the rom since I want my phone rom version is same as the stock rom I have downloaded into my PC just in case in the future I accidentally doing something wrong I can flash back the stock rom without worrying the backward compatibility problem.
t-bob said:
I'm having a similar problem and found this old thread. I am on stock pie rooted and made a twrp backup this morning so that I could try flashing some custom ROMs. After successfully installing a custom ROM I attempted to restore the backup and return to stock but just get bootloop. I am able to get back to to twrp and the phone will boot after a factory reset, but even if I just restore data I get bootloop. I'm wondering what I am doing wrong with restoring the backup. Any thoughts? Thanks.
Click to expand...
Click to collapse
I'm a bit slow on the response - but my first thought is manually flash stock rom over your restore without wiping data
I'm able flash the latest stock rom of FI_9.0_PPWS29.69-26-4 and reinstall twrp-3.2.3-1-payton. Then I restore data only that backup from previous rom, I get bootloop again after restore the data only from TWRP. The I reflash FI_9.0_PPWS29.69-26-4 again, install twrp and root it with Magisk. Restore data from cloud google drive automatically. And this time is successfully without bootloop.
Think i have rally buggered up and update, was going to try out the havoc rom, when i went to flash it i was told i needed to update vendor to v12 so i flashed the official miui vendor v12 rom, rebooted and now im stuck in a fastboot loop. i think my mistake was following the instructions on the havoc rom and wiping system, data, dalvik and cache without the havoc rom flashed.
this worked for me:
from https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
Full credits to @ SivSomRao (telegram handle, since no xda)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery[/QUOTE]
I was OverJoyed when this worked. However, every time I entered recovery, I was met with the fastboot logo again, Therefore, I just repeated the process I did when I first unlocked my bootloader via twrp in the tutorial above, which was, I went to manage partitions and formatted my data, wiped my rom, and did the same steps as in the tutorial when I first got my orange fox.
Now use twrp interface, copy orangefox.zip to my phone via PC, then flash that zip. Then go to settings > manage partitions > data > format data > type 'yes'. Then quickly flash a vendor, then a flash ROM (normal clean flash, tutorial given above) and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right so I tried LR-twrp (it's in Chinese, but I can change the language to English) . PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did. .
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.
Robbo.5000 said:
The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.
Click to expand...
Click to collapse
Thank you for this type of answer. I was trying use all the instructions to wipe, but all the time I got brick (fastboot loop) in my Mi 9 SE. Not problem when usign the first page of the wipe.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.