I tap the icon in settings to turn on Blue tooth and it stays off! Help! This is after doing the JellyBean update today. I am not rooted but have an unlocked
Bootloader I think. (padlock is unlocked) Anyone else have this issue? Help please!
I tried a factory reset and bluetooth still does not work.
laserbiz said:
I tap the icon in settings to turn on Blue tooth and it stays off! Help! This is after doing the JellyBean update today. I am not rooted but have an unlocked
Bootloader I think. (padlock is unlocked) Anyone else have this issue? Help please!
I tried a factory reset and bluetooth still does not work.
Click to expand...
Click to collapse
I have not seen such issue over here.What kind of phone do you use? Do You use stock Rom?
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
Samsung Galaxy Nexus Stock frim Verizon
Have you tried a factory reset?
Sent from my Galaxy Nexus
Try reflashing the system.img via fastboot. Also, there is a thread suggesting a permissions repair may do the trick.
laserbiz said:
I tap the icon in settings to turn on Blue tooth and it stays off! Help! This is after doing the JellyBean update today. I am not rooted but have an unlocked
Bootloader I think. (padlock is unlocked) Anyone else have this issue? Help please!
I tried a factory reset and bluetooth still does not work.
Click to expand...
Click to collapse
Had the same issue, over the weekend. I was stock rom, unlocked and rooted. I reset the phone a total of 6 times, with different combinations of radios, firmwares, locked/unlocked, etc. Tried the changing of permissions too. NEVER got BT to work. I installed a custom rom, based off the official 4.2.2 (mwalt version) and now it works as its supposed to.
http://forum.xda-developers.com/showthread.php?t=2204707
Came into work and the coworker next to me has the exact issue on his verizon gnex. Big issue here for Verizon users who updated factory phones.
pdiggitydogg said:
Had the same issue, over the weekend. I was stock rom, unlocked and rooted. I reset the phone a total of 6 times, with different combinations of radios, firmwares, locked/unlocked, etc. Tried the changing of permissions too. NEVER got BT to work. I installed a custom rom, based off the official 4.2.2 (mwalt version) and now it works as its supposed to.
http://forum.xda-developers.com/showthread.php?t=2204707
Came into work and the coworker next to me has the exact issue on his verizon gnex. Big issue here for Verizon users who updated factory phones.
Click to expand...
Click to collapse
I am having the same issue with my Verizon GNex. I'd rather not do a custom ROM, but it sounds like I'll have to.
I have the same problem with my stock Verizon, unlocked, rooted phone.
The other day I was looking for a solution to my (toroplus) deep sleep issues. I found http://forum.cyanogenmod.org/topic/57724-cm10-discussion-of-nightlies/page__st__1000
Sent from my Galaxy Nexus using Tapatalk 2
Ok, this fix I found over on Reddit worked for me:
Permissions need to be changed for /system/vendor/lib/libbt-vendor.so.
They were rw-------, change them to rw-r--r--.
Once the change is made, reboot your phone.
This change can be made with a file explorer on your phone, provided it has root access and you can mount the /system read-writeable. Alternatively, you can use the ADB shell and chmod 644 libbt-vendor.so to do it too. Remember to mount /system read-writeable though!
Rooted, unlocked Verizon Galaxy Nexus 4.2.2 (stock ROM installed via OTA).
merkidemis said:
Ok, this fix I found over on Reddit worked for me:
Permissions need to be changed for /system/vendor/lib/libbt-vendor.so.
They were rw-------, change them to rw-r--r--.
Once the change is made, reboot your phone.
This change can be made with a file explorer on your phone, provided it has root access and you can mount the /system read-writeable. Alternatively, you can use the ADB shell and chmod 644 libbt-vendor.so to do it too. Remember to mount /system read-writeable though!
Rooted, unlocked Verizon Galaxy Nexus 4.2.2 (stock ROM installed via OTA).
Click to expand...
Click to collapse
I got my OTA update for 4.2.2 yesterday on my rooted Samsung Galaxy Nexus. My bluetooth would no longer turn on aferwards. I used root explorer to change the file permissions as described above and rebooted. Works fine now. Thanks for the post.
DonDallas71 said:
I got my OTA update for 4.2.2 yesterday on my rooted Samsung Galaxy Nexus. My bluetooth would no longer turn on aferwards. I used root explorer to change the file permissions as described above and rebooted. Works fine now. Thanks for the post.
Click to expand...
Click to collapse
Worked for me, too. Awesome!
Worked for me too. Thanks
azj said:
Worked for me too. Thanks
Click to expand...
Click to collapse
after searching for an hour or so i came across this fix and worked perfect!!! awsome fix thanks alot!!
merkidemis said:
Ok, this fix I found over on Reddit worked for me:
Permissions need to be changed for /system/vendor/lib/libbt-vendor.so.
They were rw-------, change them to rw-r--r--.
Once the change is made, reboot your phone.
This change can be made with a file explorer on your phone, provided it has root access and you can mount the /system read-writeable. Alternatively, you can use the ADB shell and chmod 644 libbt-vendor.so to do it too. Remember to mount /system read-writeable though!
Rooted, unlocked Verizon Galaxy Nexus 4.2.2 (stock ROM installed via OTA).
Click to expand...
Click to collapse
What if your permissions are already rw-r--r-- and it still doesn't work? This is on a Note, but I'm sure it's about the same.
merkidemis said:
Ok, this fix I found over on Reddit worked for me:
Permissions need to be changed for /system/vendor/lib/libbt-vendor.so.
They were rw-------, change them to rw-r--r--.
Once the change is made, reboot your phone.
This change can be made with a file explorer on your phone, provided it has root access and you can mount the /system read-writeable. Alternatively, you can use the ADB shell and chmod 644 libbt-vendor.so to do it too. Remember to mount /system read-writeable though!
Rooted, unlocked Verizon Galaxy Nexus 4.2.2 (stock ROM installed via OTA).
Click to expand...
Click to collapse
I have 2 "VENDOR" folders:
/system/vendor/lib/libbt-vendor.so
/vendor/lib/libbt-vendor.so
Is it correct ?
Should I do it with the both files ?
Related
Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.
Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.
has anyone fixed this issue where wifi stops working?
wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.
Ok, i changed up my soft keys a few times... as per this thread...
http://forum.xda-developers.com/showthread.php?t=1413582
Here is my problem... I changed them a few times with no problem. I even made my own and it worked fine... then after I changed it maybe a 6th time, the keys just vanished all together. I'm not talking that they are just blacked out, I mean the screen has streached out the full 4.65" and there is no slot for the keys. I have no way to navigate around.
I followed the "Easy Breezy Method - Using MetaMorph". I worked every time, except the last one. I have tried reapplying ones i knew worked, but no joy.
ANY ideas???
GinoSylum said:
Ok, i changed up my soft keys a few times... as per this thread...
http://forum.xda-developers.com/showthread.php?t=1413582
Here is my problem... I changed them a few times with no problem. I even made my own and it worked fine... then after I changed it maybe a 6th time, the keys just vanished all together. I'm not talking that they are just blacked out, I mean the screen has streached out the full 4.65" and there is no slot for the keys. I have no way to navigate around.
I followed the "Easy Breezy Method - Using MetaMorph". I worked every time, except the last one. I have tried reapplying ones i knew worked, but no joy.
ANY ideas???
Click to expand...
Click to collapse
Restore your last nandroid backup? If you didn't make one, then I'd run an adb backup and flash your ROM again:
Code:
adb backup -apk -nosystem -all -f /backup/backup.ab
Using -nosystem means your SystemUI.apk (which is probably hosed) won't be backed up (although I doubt it would back that up anyway). Then, restore using:
Code:
adb restore /backup/backup.ab
Curious, what was the last one you flashed?
I didn't make a backup because i'm running stock... stupid me..
The one i flashed that killed it was "grungetext"
I'm going to try flashing with the "Automatic Method - Images using Softkey Modder" ... that one doesn't require much from the phone itself... lets see what happens..
ok.. well doing the "Automatic Method - Images using Softkey Modder " didn't work.. i think i broke it...
Just noticed i don't have a notification bar either...
Your SystemUI.apk is borked. Find a stock one from whichever build you are on and push it to /system/app directory.
Metamorph has been very sketchy as it is kind of outdated and is not %100. ALWAYS just push images into apks manually. Its safer and you learn how to theme properly. Takes less time than Metamorph anyways.
Sent from my Galaxy Nexus using XDA App
Just install stock images through fastboot or a new rom..
Sent from my Galaxy Nexus using xda premium
mb02 said:
Your SystemUI.apk is borked. Find a stock one from whichever build you are on and push it to /system/app directory.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I'm just using the stock 4.0.2 on the Verizon LTE version... can you direct me to where i can find a clean SystemUI.apk and where to put it?
aside from not having a working UI, my phone is exactly the way i want it, i would rather avoid just flashing a new rom and wiping everything out.........
GinoSylum said:
I'm just using the stock 4.0.2 on the Verizon LTE version... can you direct me to where i can find a clean SystemUI.apk and where to put it?
aside from not having a working UI, my phone is exactly the way i want it, i would rather avoid just flashing a new rom and wiping everything out.........
Click to expand...
Click to collapse
I posted my 4.0.2 and 4.0.3 unmodified SystemUI.apk files here yesterday. Let me know if it works for you.
copkay said:
I posted my 4.0.2 and 4.0.3 unmodified SystemUI.apk files here yesterday. Let me know if it works for you.
Click to expand...
Click to collapse
THANK YOU THANK YOU!!
Yes, that worked... all back to normal.. now to get back to messing it up again
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
ik4evr said:
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
Click to expand...
Click to collapse
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
THEDEVIOUS1 said:
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
ik4evr said:
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
Click to expand...
Click to collapse
If that didnt work then it might be your updater-script...once again just copy the one from a known working deice with an exynos cpu & 4.4.2 (N9000 MAYBE?) then u should be ok. Also...did u swap the daemonsu file in xbin as well? Another thing...delete the su located in "bin" & make sure its in "xbin". The last thing i can think of...did u unpack the boot.img & change the value in the dfault.prop to make it non-secure?
edit: I was just thinking...i noticed u said "supersu" but every guide ive seen added "superuser" instead so swap that too. U should be able to include either but mine didnt work either until i switched them although it could have been coincidence since i also made all of the rest of the alterations around the same time...if u notice in my thread i told users to go download supersu AFTER they flash just to be safe but now that i have it working i'll probably try changing apps again for the next version to eliminate a step
where do I dl twrp for tab pro 10.1 wifi?
I only see 10.1 tab pro lte ...not wifi?
Thanks
Hello,
My Wifi won't turn on after upgrading to lollipop, it just says error.
What can cause this, I know before I updated something as I had a custom ROM which would allow the wifi to work, what controls the wifi? Is it the Radio?
My Radio is. 1.25.214500021.06G
Hboot is: 3.19.0.0000
Thanks in advance.
Mcyates said:
Hello,
My Wifi won't turn on after upgrading to lollipop, it just says error.
What can cause this, I know before I updated something as I had a custom ROM which would allow the wifi to work, what controls the wifi? Is it the Radio?
My Radio is. 1.25.214500021.06G
Hboot is: 3.19.0.0000
Thanks in advance.
Click to expand...
Click to collapse
i would first do a clean install and see if that helps then i would check the firmware version you are using, making sure your updated to the newest lollipop sense firmware, hope this helps.
Done a factory reset and everything seems to be working now!
Strange!
Same problem here. Came from Stock + root + xposed. Not got wifi working again yet.
Mcyates said:
Done a factory reset and everything seems to be working now!
Strange!
Click to expand...
Click to collapse
Update your Firmware. Xposed don't work on Lollipop.
/ Sent from my phone /
jkolner said:
Update your Firmware. Xposed don't work on Lollipop.
/ Sent from my phone /
Click to expand...
Click to collapse
'firmware' you mean system partition, or what specifically? Uninstalling Xposed before applying the OTA didn't help. Trying to uninstall xposed after the original OTA gave me a soft-brick
tshoulihane said:
'firmware' you mean system partition, or what specifically? Uninstalling Xposed before applying the OTA didn't help. Trying to uninstall xposed after the original OTA gave me a soft-brick
Click to expand...
Click to collapse
Xposed don't work at all on Lillipop at all, no matter what you do.
You can read about updating Firmware here:
Did we have the same WiFi problems with the developer edition firmware? Or is it just the WWE firmware with the problem? Plus before anybody comes back with a "did you upgrade your firmware" answer, yes I did 401.10 the latest.
Sent from my HTC Space Banana
I wasn't able to get the firmware replace to work (maybe because I'm S-ON?) but it seems factory reset fixed it and restoring data from nandroid broke it again.
edit: Titanium won't backup wifi access points - it just gets stuck waiting there after running overnight.
Solution (for me) was to delete (using root and adb) /data/misc/wifi directory. There is clearly some permissions issue which presumably ought to be patched up by the OTA (so a pre-post lolipop data partition can't be restored, which is no great surprise).
After reboot, that directory gets re-created (without any previous saved passwords) and all is good.
tshoulihane said:
Solution (for me) was to delete (using root and adb) /data/misc/wifi directory. There is clearly some permissions issue which presumably ought to be patched up by the OTA (so a pre-post lolipop data partition can't be restored, which is no great surprise).
After reboot, that directory gets re-created (without any previous saved passwords) and all is good.
Click to expand...
Click to collapse
can you elaborate on how to do that?
I think I can't update the firmware since it requires S-OFF and I can't do that now since firewater is gone :/
Shiverfire said:
can you elaborate on how to do that?
I think I can't update the firmware since it requires S-OFF and I can't do that now since firewater is gone :/
Click to expand...
Click to collapse
If this doesn't work, tell me what you have got working.
Upgrade to Lollipop, Philz (or TWRP) bootloader, Backup, Super-SU, then:
Code:
adb shell
su
cd /data/misc
rm -r wifi
exit
adb reboot
Fixed?
tshoulihane said:
If this doesn't work, tell me what you have got working.
Upgrade to Lollipop, Philz (or TWRP) bootloader, Backup, Super-SU, then:
Code:
adb shell
su
cd /data/misc
rm -r wifi
exit
adb reboot
Fixed?
Click to expand...
Click to collapse
I removed the folder in root explorer and rebooted but still having problem with WiFi keeping a connection when I goes into deep sleep.
Sent from my HTC Space Banana
DROITURK182 said:
I removed the folder in root explorer and rebooted but still having problem with WiFi keeping a connection when I goes into deep sleep.
Sent from my HTC Space Banana
Click to expand...
Click to collapse
Diffetnet problem. For me, wifi didn't even turn on.
Thanks guys, I was suffering from the same problem.
I did restore from Nandroid a couple of times, only the wifi of the non stock rom worked. I did a reflash of the firmware, It didnt help in any way. I did a factory reset from CWM no change in WIFI.
The way that i tried and worked was the factory reset from the bootloader with original recovery.
sir i have upgraded to lolipop sm-n9005 but know wifi is just gone grey
n9005 somesh121 said:
sir i have upgraded to lolipop sm-n9005 but know wifi is just gone grey
Click to expand...
Click to collapse
You should post your issue to the forum section specific to your device (looks like the Note 3?).
This section is for the HTC One (M8) and the causes and fixes for these types of issues are often very device specific. Trying a fix meant for another device may even damage your phone.
Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris
Works for me. Thanks!
Sent from my Nexus 9 using Tapatalk
Works on http://forum.xda-developers.com/showthread.php?t=3129778
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Have you flashed the stock vendor.img with fastboot?
wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Hey wfyjay,
sorry to hear about your nexus. Well, my fix only creates a property-file which stores version-information in /vendor and should have nothing to do with your touchscreen problem. However, as fleischbanane said, have you tried flashing the vendor image which is included in Google's factory image?
fleischbanane said:
Have you flashed the stock vendor.img with fastboot?
Click to expand...
Click to collapse
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk
wfujay said:
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Factory images are located here: https://developers.google.com/android/nexus/images
gladiac said:
Factory images are located here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk
wfujay said:
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Well, that's odd. If you flashed back to stock then the vendor-partition (as well as all the other important partitions) must be in their original state. I'm afraid your touchscreen problem is unrelated to my fix. You could post a logcat (adb logcat) on the forum and someone might be able to figure something out or relock the bootloader and send your nexus in for warranty. I'm not sure if I can help you any further.
What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip
mgiusto said:
What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip
Click to expand...
Click to collapse
Hi, this file is supposed to be flashed via the recovery (TWRP, CWM, ...) just as you would do with a normal rom.
Worked for me, running Broken 2.4
Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk
Cuzz1369 said:
Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Hey there,
well, the error occures as soon as the values in /vendor/build.prop do not match those in /system/build.prop. Most roms only flash /system - leaving /vendor completely untouched. And since most roms change /system/build.prop in every release which in the end causes the error message to appear. At the end of the day, there is no mechanism that ensures that the values of those two files actually match. In an ideal world, roms should provide /vendor as well. In a less ideal world, roms should patch /vendor/build.prop themselves. In _this_ world, roms just don't care so I created this update-zip.
Hope that clears things up,
cheers gladiac
gladiac said:
Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris
Click to expand...
Click to collapse
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.
Anubis22666 said:
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.
Click to expand...
Click to collapse
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers
gladiac said:
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers
Click to expand...
Click to collapse
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually plz? Or direct me to a guide
Anubis22666 said:
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor file/folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually perhaps? Or direct me to a guide
Click to expand...
Click to collapse
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.
gladiac said:
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.
Click to expand...
Click to collapse
Thank U so much for Ur kind help.
I checked, this /vendor folder doesn't have the 'build.prop' file in it,it has just three folders. Although /system folder does have the 'build.prop' file. See attachments, please