Open devel2ew opened 5 years ago
It can be fixed like Xiaomi Redmi 6.
su mount -o rw,remount /vendor cd vendor echo "ro.audio.ignore_effects=true" >> build.prop cd / reboot
Do it in /system rather, it's safer
it returns that the system is only read only
but this in return disables the sound effects and i can't run the Viper Driver i have installed.. Any more permanent fix
Seems like this isn't only an issue for A20, but also for the BV9500. The same workaround for build.prop fixes this issue. Logcat matches up with OP's descriptions.
Hey guys, I seem to be getting this same error however it's been going on for the last 12 Hours. All i get is a totally black lit up screen for like 7-10 seconds and it goes of for like 15 seconds. Doesn't seem to be coming on, nor can I connect it to anything. Any idea's?
is ur ram below 2gb... if yes enable the optimize bit in ur build.prop
this wud drastically reduce the memory overhead and features but the rom will run
Not that i know of it's been in a boot loop the whole day now, it's the bv9500, it won't even show a screen, the screen lights up and turns off in a loot, when connected to the PC it connects and disconnects, no access to anything, i can't even shut it down. I guess it'll keep going like this till the battery dies.
Just fixed this by re flashing the stock recovery and files using sp flash, booting to it and clearing the user data and re-flashing the image via ADB. Managed to connect the phone while clicking volume down and connecting the power.
Good :-)
Hello
I am trying to flash a BV9500 pro following wiki instructions and am stuck at boot.
I tried arm64 vanilla AOSP 9 aonly and get stuck at "android" inscription I also tried another ROM based on one of your aosp 11 releases and get stuck at the same point with the ROM name in place of "android". Install method is fastboot from my linux laptop. I would like to try the solution proposed here however have no idea how to edit build.prop file. Could you point me a diection?
Now I might have managed to install TWRP and use the terminal inside to add the given line in /system/build.prop even though I do not know how to read this file in the terminal and therefore cannot confirm it had effectively been added.
I then tried to flash your latest AONLY release I could find which is aosp 11 because my device is aonly and it appears to stay stuck after boot on a comic strip image of a duck driving a car with his three duck children the meaning of which is unclear to me
Problem solved for AOSP 9 of course I had to edit build.prop again after flashing system and could finally boot. For last AOSP11 release it does not solve the problem I could still not boot
Problem solved for AOSP 9 of course I had to edit build.prop again after flashing system and could finally boot. For last AOSP11 release it does not solve the problem I could still not boot
I don't know if it's the same with AOSP, but I was able to boot LineageOS 18.1 (Android 11), sort of. After doing the change in build.prop on the system partition, it booted up until it said "Factory data reset. Restarting...". Then it requires the stock recovery to wipe the phone (the TWRP ported to the BV9500 can't do it. It doesn't take OS requests I guess). I do it, restart, and then the same message appears on the screen, which then requires the recovery, and loops forever. From what I read, there was a change in partitions with Android 11 and a newer recovery may be needed. Thought I'd say this, in case you had not got to this point.
Boot after 40 minutes.
In logcat it is related Sound Effects.