Related
Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
$> su
#> alsa_amixer
It throws some error but It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
nice catch man...anybody with f240 already tested this?
will try to download cm11 roms and definitely going to try this one...
Thank you!
notohp said:
Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
prompt> alsa_amixer
It throws some error about module not found or something. It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
Click to expand...
Click to collapse
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
esaintor said:
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
Click to expand...
Click to collapse
Yes just that. You can flash it right after flashing roms. :good:
no luck.
notohp said:
Yes just that. You can flash it right after flashing roms. :good:
Click to expand...
Click to collapse
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
esaintor said:
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
Click to expand...
Click to collapse
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Still...
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I tried on omni but no success
I executed this command didn't restart still no sound
esaintor said:
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
Click to expand...
Click to collapse
Okay I will test it with omni rom once I am back home. Could you point me to the link?
here is the link
notohp said:
Okay I will test it with omni rom once I am back home. Could you point me to the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2562998
GOT IT!!!
esaintor said:
http://forum.xda-developers.com/showthread.php?t=2562998
Click to expand...
Click to collapse
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
esaintor said:
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
Click to expand...
Click to collapse
Glad you got it worked...may be this line ..."I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine," had a brief mention but anyway...I will edit the OP...:good:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
nguyenthienqui said:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
Click to expand...
Click to collapse
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
esaintor said:
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
Click to expand...
Click to collapse
i had same problem with my f240k Android OS drained alot of battery so I switched to Mokee 4.4.2, its AOSP so like 99% CM
battery problem is fixed so is sound....get around 4 hours of SOT
try it if you like:
http://forum.xda-developers.com/showthread.php?t=2639469
Tested of F240L
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
mudu8 said:
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
Click to expand...
Click to collapse
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
notohp said:
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
Click to expand...
Click to collapse
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
mudu8 said:
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
Click to expand...
Click to collapse
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
notohp said:
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
Click to expand...
Click to collapse
I'm not very conversant with the methods of kernel extraction etc.
I reckon you could compare the chinese CM11 Kernel to the stock CM11 one and see which files need manipulating in order to get it working and also what differences exist between the E98X and F240x models.
No pressure though it just my opinion.
It seems F240 models get little support around here, so if we could figure this out it would be great.
Here's a flashable zip, if you flash international rom and wants wifi calling.
I flash it on Sense 7, working great.
wonder with the nexus getting lollipop - will the rom makers be able to take wifi calling out of it and place into an asop rom.
Will this only work on sense ROM'S im just wondering as I use sense ROM'S with t mobile Wi-Fi calling but would like to try it on any ROM I choose to use. Thanks for your answer in advance.
What a great idea - thanks for this. Now I am free to tray any rom.
Thanks man
Has anyone used this recently and does anyone know if it works on ASOP ROMs? There a few M8 roms with Wifi Calling but they all seem to be Sense based.
Alec2435 said:
Has anyone used this recently and does anyone know if it works on ASOP ROMs? There a few M8 roms with Wifi Calling but they all seem to be Sense based.
Click to expand...
Click to collapse
It won't work-- wifi calling depends on Sense
can not be flash. it shows "remote: signature verify fail". any solution? thanks!
jlove1111 said:
can not be flash. it shows "remote: signature verify fail". any solution? thanks!
Click to expand...
Click to collapse
Hello, if you are using TWRP please make sure that ZIP file signature verification is not checked. It will appear when you have the ZIP file selected to flash
Htc M8 with sense 6
Jewman said:
Hello, if you are using TWRP please make sure that ZIP file signature verification is not checked. It will appear when you have the ZIP file selected to flash
Click to expand...
Click to collapse
I took my at&t unlocked phone to a cell phone guy to jail break and flash this zip. He rooted the phone and it was working fine. I gave this zip to him and he flashed the zip and phone stopped working. All the google apps are not closing and not able to reach setting or other apps.
He tried to restore phone and after repeated trials he gave up saying he cannot fix it. I not having much knowledge on this could not do anything. Can you please advise and help me out here...to restore the phone to factory settingss or remove this tmobile rom
Does it work?
Has anyone made this work? If so, how?
Hi guys, sorry for my english, I hope understand me, I have trouble with my phone this no sound or mic during calls only music and phone sound is OK, I restored it to default many times, I try some customs roms, I try 4.3 modem, I do a rework on the logic board in the Audio IC, but nothing works for me, I need help with my phone I dont have more phones, I hope somebody can help me :crying:
Note: Apps like Skype, Messenger or Whatsapp works perfectly on calls
Do a double flash of the stock oh3 complete firmware via odin. This means unchecking the reboot in odin, flash the stock firmware. No reboot. Pull battery. Hold keys to boot back to download mode immediately upon battery reinsertion. Flash firmware again.
Then reboot normally and set up phone for test with 100 % stock software.
PS: do a complete wipe before the Double Flash.
Frankenscript said:
Do a double flash of the stock oh3 complete firmware via odin. This means unchecking the reboot in odin, flash the stock firmware. No reboot. Pull battery. Hold keys to boot back to download mode immediately upon battery reinsertion. Flash firmware again.
Then reboot normally and set up phone for test with 100 % stock software.
PS: do a complete wipe before the Double Flash.
Click to expand...
Click to collapse
Ok, let me try it, but where can I get the stock OH3 firmware for M919, can you tell me ? I have one link of rapidgator, but I never get finish the download, the servers are awful
Sammobile works but is slow. Or see threads in General where others have posted Mega links.
See beginning of this thread:
http://forum.xda-developers.com/showthread.php?t=2816508
Frankenscript said:
See beginning of this thread:
http://forum.xda-developers.com/showthread.php?t=2816508
Click to expand...
Click to collapse
Hi, I dont have good news for me, I try your suggestion the double flash of the stock OH3 complete firmware via odin but, dont works , only can listen sometimes a weird noise in the another celphone or telephone, help me friend!!!
If double flash of stock doesn't work, there is a hardware problem of some sort. I briefly had an ATT S4 i337 model with wired audio issues. Required factory repair.
Frankenscript said:
If double flash of stock doesn't work, there is a hardware problem of some sort. I briefly had an ATT S4 i337 model with wired audio issues. Required factory repair.
Click to expand...
Click to collapse
Ok the last question, Can I change the logic board for an logic board of another model of S4 ?
Nope. Only M919 I believe.
Frankenscript said:
Nope. Only M919 I believe.
Click to expand...
Click to collapse
Hi, I discover that the audio works if I use Bluetooth headset
This worked for me
I installed Android Terminal Emulator from the Play store - granted it SuperSU access - and proceeded to type the following command(s):
su [enter]
pm disable com.sec.knox.seandroid
*NOTE - the above to lines require you to go to a new line after typing "su", the [enter] is only a reminder, DO NOT type [enter] after su
Frankenscript said:
Nope. Only M919 I believe.
Click to expand...
Click to collapse
If I record the call, at the end of the call everything is recorded despite no sound on call
JayTheSavage said:
I installed Android Terminal Emulator from the Play store - granted it SuperSU access - and proceeded to type the following command(s):
su [enter]
pm disable com.sec.knox.seandroid
*NOTE - the above to lines require you to go to a new line after typing "su", the [enter] is only a reminder, DO NOT type [enter] after su
Click to expand...
Click to collapse
Thank, I tried but donts works for me
I got same issue.. .I tried Many things, many custom ROM installed but didn't get success.
Sometime if I clear cache from firmware mode then, sound and mic everything works perfect untill phone reboot.
But after reboot, issue is happened again..
I don't understand Is this OS issue or Hardware issue???
Local repairer says that Its OS issue and I can resolve it.
At last now I am giving to repairer...
I hope its working..
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Have you tried flashing back to stock and seeing if that fixed these issues?
Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...
DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2
Thanks alot... ?
Just received this
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Oh no, seems like I have to stuck in version 10.0.10.0 forever ... :crying:
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Hopefully we will get it back with Android 10. I'm using superior os 10 till we get it.. so far it works pretty nicely.
Also got the update. The size looks ok for a simple security patch and minor fixes so nothing major.
Phone starts ok, no problems so far.
This is the first update that no one is complaining about yet... so it's a change in the right direction for the Xiaomi OTAs.
Xiaomi Mi A2 users (they got it 3 days earlier) said that it even works fine with Magisk.
I had 2 odd things happen as a result of installing this OTA.
1) USB Debugging was turned off. No other developer things seem to have changed, just that toggle was off.
2) My timezone was changed. Almost like the phone temporarily forgot I didn't want to use network-provided timezone (it often picks the neighbouring state, which has a 1-hour offset from here).
I've never had this happen with previous OTAs.
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
My dad didn't have this issue. Make sure it isn't your network provider having this problem
If you don't enroll your fingerprint before updating to v 10.0.16 ,you can't do it after the update
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
Hello, if someone is experiencing the same problem, I resolved it flashing the official stock rom with Miflash tool. Cheers
This update has definitely done something to the signal mine is falling onto 2G a lot, before that I was steady on 4G. Once it hits 2G it stays on it regardless of the signal strength until you restart the phone. It is very annoying.
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
downloadonlyaccount said:
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
Click to expand...
Click to collapse
This sounds like the known issue with new/fast cards. There's a thread where it was discussed.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
That's a problem that sometimes occurs since Pie came out. Restarting the mobile should fix it.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
My multitasking seems to be very bad after the update...
Hello,
I have Mi A2 lite with magisk installed, and I am unable to perform the november OTA update.
here is what I do:
1. In magisk : Uninstall > restore images
After doing this, magisk still looks the same:
2. Launch the OTA update.
I first have this screen:
red message translation: "Install will resume when the phone is not active. Click on resume to finish installation now"
3. Clicking on resume will start the installation, but it fails after some moment:
4. After that, I go back to Magisk: Install > Direst install to avoid having Magisk uninstalled after reboot. When doing this, here is the screen:
I don't understand why my OTA is refused...
Is there something to setup in magisk hide ? In order to hide magisk from the OTA updater ? or anything else ?
/system could have been modified, you can try flashing only that partition to solve the issue
nehuy said:
/system could have been modified, you can try flashing only that partition to solve the issue
Click to expand...
Click to collapse
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
takhama said:
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
Click to expand...
Click to collapse
The upgrade tool writes a log to logcat. It says which partition it does not like.
adb logcat | grep update_engine
There have been no fastboot image released for 10.0.15.0. I have backups of both system and vendor (since they both seem to be modified every OTA for me). If you can confirm that either of these is needed I can try to upload it somewhere. Note that these are very large partitions.
Alternatively, you could use the 10.0.13.0 fastboot and OTA from there. Make sure to backup data before doing this.