Related
Can someone help me with this? I found that if you remove sprintandroidextension.apk it goes away but it didnt. I also found that by removing SprintOMADMConnMOPlugin.apk it goes away, but i cant find it on my Galaxy note 2. Any ideas? Thanks in advance.
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
digitallogik said:
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Click to expand...
Click to collapse
I tried doing that many times but it never worked, it just gave me an error.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
Thank you! it worked
interesting. found this thread buried, and there still seem to be many people with this issue... seemingly related to the chameleon FCs some are getting, somehow possibly related to the LK8 update and/or a return to an earlier stock version...
digitallogik said:
If you let it go all the way through HFA once it won't return.
Click to expand...
Click to collapse
I've let it complete (personally) aprox 20+ times, so no go.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
could the "fix" really be this simple? (at work, can't test this right now.)
kingdazy said:
could the "fix" really be this simple? (at work, can't test this right now.)
Click to expand...
Click to collapse
yes, and you can delete the activation.apk as well to stop it
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
thanks, stopped the HFA, still have the chameleon errors to deal with...
t3project said:
yes, and you can delete the activation.apk as well to stop it
Click to expand...
Click to collapse
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
kingdazy said:
thanks, stopped the HFA, still have the chameleon errors to deal with...
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
Click to expand...
Click to collapse
your solution is to thoroughly wipe and reflash whatever rom you are running.
t3project said:
your solution is to thoroughly wipe and reflash whatever rom you are running.
Click to expand...
Click to collapse
I would have thought so too. As I've been advised by other as well. But...
I have, at least five times, run a return to stock, both through ODIN and OneClicks.
I still have the issue. Baffles the mind. Makes little sense. But there it is. And I'm not the only one.
(Just so it's noted, and before you accuse me otherwise, I am not new at this, and I follow directions fastidiously. I've never once had a problem that I didn't cause myself, and I've always been able to fix them by further reading/researching.)
Just for SnG's I'll quote myself and others from a few other posts in other threads:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kingdazy said:
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
And this morning, I tried the following:
Installed TWRP with GooManage, restored a nandroid from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
Click to expand...
Click to collapse
Itchiee said:
I'm having similar issues, I was on the release before LK8, then updated to LK8 but wanted to start over again.
Once i downgraded to LJ1? the hands free bug kept popping up every reboot, until I moved onto to LJC then LK8 update file which is fine.
I'm trying to figure out myself how to go back to the original firmware (pre any updates) without the issues... /subscribed.
Wonder if this is tied into it somehow...
I dunno, my head is exploding reading all these posts, replies.... 5 different versions of restore.
Click to expand...
Click to collapse
evilgenyus said:
I have tried the one click restores back to ljc and the original tar, and I still have the hands free activation issue and the chameleon error. And when I update to lk8 I get no wifi. I have tried returning to stock about 4 times and then updated to lk8 with the same results. I always go back to ljc bc I need wifi.
Click to expand...
Click to collapse
kingdazy said:
interestingly, even using a stock oneclick full restore (and even using a TAR in Odin), still have the handsfree repetition and chameleon FCs. (lol, I'm not complaining really, it's early in the dev life for this device I suppose. )
Also, I've been reading that re-flashing the LK8 update.zip (via sxtp?) while it seems to fix the HFA and ChameleonFC, it kills the wifi? (it killed my wifi after aprox 2 days use, when I orig updated...)
Click to expand...
Click to collapse
garwynn said:
I'm starting to wonder if the move to 4.1.2 changed something that isn't handled properly by older versions. Without a gn2 will be hard to confirm... but I may be resolving that soon as well!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It would apear that something in the LK8 changes ... something. Permanently?
So, any new advice would be welcome...?
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
smooth703 said:
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
fine question, but without knowing what the chameleon apk does, i'm reluctant to f**k with it.
anyone know? (a goog search gave me nothing...except this XDA rom w/ a fix...? I'm going to try n PM him...)
and again, my concern is the issue seems to be more significant, seeing as a Full Wipe to Stock doesn't fix it.
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
sxtp site said:
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
Click to expand...
Click to collapse
kingdazy said:
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
Click to expand...
Click to collapse
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
shiftr182 said:
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
Click to expand...
Click to collapse
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
kingdazy said:
it would seem that the factors that all of us with this issue have in common are: a) rooting w/ ToolKit ver2 b) flashing LK8 update zip c) trying to return to stock LJC/LJ1 because of a wifi problem... please chime in if you have the issue, but not one of those factors?
After everything, I just returned to stock LJC w/ Flash Counter @ 0 (no) w/ the errors still present, took it into Sprint store said, 'hey guys, this is weird, i've got a persistent error, won't go away after resetting my phone." (IE, acted dumb enough to not have rooted/flashed unofficial shtuff/etc, but smart enough to know that it's a real issue), they looked at it, asked a few obvious questions, replaced it, because obviously something was wrong in a permanent way. I want to a corp store, not a "repair center". I think it was a good thing that these guys were not super techie.
I told them as little as possible, that I had a "wifi issue after an update, tried full reset (through the android settings menu, of course), and the problem didn't go away, no matter what". Once they heard that I had done a full factory reset, and saw the problem/error happen, it was a no-brainer to swap out.
I'll be avoiding the LK8 leak for now, and frankly gun-shy about the toolkit.
Click to expand...
Click to collapse
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
kingdazy said:
ok, to get back to stock, first use this OneClick to get to Stock+Root, it will wipe ALL internal memory except SD card:
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Instructions are here:
http://www.sxtpdevelopers.com/showt...-TAR-SPH-L900-LJC-(LJC-Modem-Kernel-ROM-Stock)
then use TriangleAway, this will set your counter at 0 (reads as "no" in download mode). it should also say "Official" And "Samsung Official"
Then, if you want to get Total Stock unrooted, for returns to Sprint, or any other reason, use Odin (not mobile) to flash this:
http://www.androidfilehost.com/?fid=9390214368362234120
Instructions for flashing that are here:
http://www.sxtpdevelopers.com/showthread.php?76-TAR-STOCK-Full-L900VPALJC-quot-Back-to-Stock-quot
After I did those things, I was stock unrooted, no flash count.
Click to expand...
Click to collapse
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Yeah, I have to give it up to garwynn, he hooked me up with the pit file for our phone. Good people.
ProjectROM 2.1
Did a clean install and I get this as well =/
RussellAlan said:
Did a clean install and I get this as well =/
Click to expand...
Click to collapse
a clean install, coming from what? And what did you use to get back to stock? (Just asking so people will have a clear history of what is causing this. In case a dev wants to look closer at the problem, have clear ideas where to start)
Sent from my SPH-L900 using xda premium
ceabbott2 said:
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1
Sent from my galaxy note 2....
kingdazy said:
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Click to expand...
Click to collapse
I try that method but mine still show 1 on the counter. Is there a way to get rid of that?
I have had a sprint gs 3 and everythhog worked fine except they suck net speed wise.
Anyway I am on the tombile gs 3 now. I love this program called LBE security but in order to get it to work you have to reboot into recovery and fix permissions. This is where my issue starts.
On my sprint version it took a while to fix permissions but on me and my wife's s3 it says it completed but completes almost instantly which makes me think something isn't right. There are no programs for an alternate that I know of.
I used the same flash file I used with the sprint version which was clockwork mod and I even updated it to the touch...same thing..downloaded .tried team win recovery same thing.
Anyone have any ideas here? Rooted running different roms and same thing happens.
Sorry for the typos. Its hard to do this from my phone. I still use a t9 keypad app
Stock kernel i think running tesm infamous newest version
Josh McGrath said:
I have had a sprint gs 3 and everythhog worked fine except they suck net speed wise.
Anyway I am on the tombile gs 3 now. I love this program called LBE security but in order to get it to work you have to reboot into recovery and fix permissions. This is where my issue starts.
On my sprint version it took a while to fix permissions but on me and my wife's s3 it says it completed but completes almost instantly which makes me think something isn't right. There are no programs for an alternate that I know of.
I used the same flash file I used with the sprint version which was clockwork mod and I even updated it to the touch...same thing..downloaded .tried team win recovery same thing.
Anyone have any ideas here? Rooted running different roms and same thing happens.
Sorry for the typos. Its hard to do this from my phone. I still use a t9 keypad app
Stock kernel i think running tesm infamous newest version
Click to expand...
Click to collapse
I use the ROM Manager app for fixing permissions. You can watch it run, then it will prompt you to reboot. It creates a file on your sd card. I have used this app for awhile and it seems to do the job. I was also like you when using recovery to fix permissions and it's over in a second. I don't use ROM manager for anything else though. I use twrp for recovery. Good luck.
Sent from my AT100 using xda premium
Thanks. I will try that. I tried it before and got the failed to fix permissions error. Anything else anyone can think of it could be.
Fixing permissions is pointless anyway. I haven't used it since the original Galaxy.
Sent from my SGH-T999 using Tapatalk 2
When you do it with CWM, it creates a log file. Don't remember where it goes, but it's easy to find. Called fix_permissions.log
Fixing permissions is the only way the lbe program I wanted to use would work since jellybean. Its apparently been abandoned on the market but I found a rough newer version but don't really like or trust is since chinese made and probably has a backdoor as zte and huwei supposedly have
Sent from my SGH-T999 using xda app-developers app
It's probably not safe to trust.
I only fix permissions after i flashed a bunch of **** and my phine starts acting funny. After that it seems to fix it. Other than that I don't bother with it
Sent from Flip's S3
elflip88 said:
I only fix permissions after i flashed a bunch of **** and my phine starts acting funny. After that it seems to fix it. Other than that I don't bother with it
Sent from Flip's S3
Click to expand...
Click to collapse
That's what I do with mine. The lbe will cause reboots over and over until the permission fix is run.
Sent from my SGH-T999 using xda app-developers app
2 days ago I installed 4.2.2 factory rom on my gnex because I wanted to do a clean installation of a new ROM, like I did many times, but when I try to copy files from the PC the gnex goes vinto bootloop and i have to install the stock rom another time. I've tried several 4.2.2 roms and i also went back to 4.1.2 but i have the same problem. From ubuntu 13.04 i can't copy any file. Any solution?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Frank_9.5 said:
2 days ago I installed 4.2.2 factory rom on my gnex because I wanted to do a clean installation of a new ROM, like I did many times, but when I try to copy files from the PC the gnex goes vinto bootloop and i have to install the stock rom another time. I've tried several 4.2.2 roms and i also went back to 4.1.2 but i have the same problem. From ubuntu 13.04 i can't copy any file. Any solution?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
use ADB and udev, simple.
beekay201 said:
use ADB and udev, simple.
Click to expand...
Click to collapse
Unfortunately the problem is not only this because I noticed that the phone random reboots even when I'm using it and I can't understand the reason! But as I said I've tried to do many resets and the problem is still there...
Inviato dal mio Galaxy Nexus con Tapatalk 2
Frank_9.5 said:
Unfortunately the problem is not only this because I noticed that the phone random reboots even when I'm using it and I can't understand the reason! But as I said I've tried to do many resets and the problem is still there...
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
Use a otg cable and flash from the USB?
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Use a otg cable and flash from the USB?
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
His problem is he can't copy files from/to sdcard. Through MTP or whatever its called I assumed, so I suggested adb. If he only posted some logs, if we would see input/output errors, then it would mean something's wrong with eMMC. Its rather strange he's even able to flash anything, I would be scared if my device reboots randomly and I was to flash anything to it. So it maybe an issue with a damn app, idk.
a manta wrote this.
mrgnex said:
Use a otg cable and flash from the USB?
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Ehm sorry I don't understand!
beekay201 said:
His problem is he can't copy files from/to sdcard. Through MTP or whatever its called I assumed, so I suggested adb. If he only posted some logs, if we would see input/output errors, then it would mean something's wrong with eMMC. Its rather strange he's even able to flash anything, I would be scared if my device reboots randomly and I was to flash anything to it. So it maybe an issue with a damn app, idk.
a manta wrote this.
Click to expand...
Click to collapse
Well, the main problem is that the phone random reboots 4-5 times a day and it's really annoying. I tried to pass only a part of files every time, something like 300 mb every time, and it worked until I tried to copy DCIM folder (5 gb). It rebooted. How and when should I create a log? (I'm feeling so noob now lol)
First, did you try pulling/pushing files through adb? I don't really trust mtp.
a maguro wrote this.
beekay201 said:
First, did you try pulling/pushing files through adb? I don't really trust mtp.
a maguro wrote this.
Click to expand...
Click to collapse
Yep, I've tried, and the phone reboots...
Fixing permissions?
a maguro wrote this.
beekay201 said:
Fixing permissions?
a maguro wrote this.
Click to expand...
Click to collapse
i've got a similar problem, my rooted gnex with stock rom was almost perfect for months.. then yesterday begin to randomly reboot....
i try cyanogen 10.1 but no luck, i got the same problem!
today i switch back to factory... it downloaded all my apps... but then i got another reboot!!!!
the only thing... on stock rom i was using the app notification toggle, after a reboot i removed it... and now seems ok... no more reboot!!!
maybe when we have a bad flash memory block that crash the phone when accessed/written???
beekay201 said:
Fixing permissions?
a maguro wrote this.
Click to expand...
Click to collapse
I wanted to try this, but I had to reset the phone because it was stuck in a bootloop and I couldn't boot to android! Now I installed slim bean 4.2.2 and I have no issues so far, for 5-6 hours. I only downloaded the apps without copying the files from pc to phone, so I have the memory clear.
icecuber said:
i've got a similar problem, my rooted gnex with stock rom was almost perfect for months.. then yesterday begin to randomly reboot....
i try cyanogen 10.1 but no luck, i got the same problem!
today i switch back to factory... it downloaded all my apps... but then i got another reboot!!!!
the only thing... on stock rom i was using the app notification toggle, after a reboot i removed it... and now seems ok... no more reboot!!!
maybe when we have a bad flash memory block that crash the phone when accessed/written???
Click to expand...
Click to collapse
In fact I was thinking about something like this... some kind of problem with the memory, because the phone starts rebooting only when I try to push files to devies, with mtp or even adb, anyway I had this problem even in safe mode when third part apps are disabled so the problem is the phone itself!
I thought you were trying to get a backup.
Anyways, don't restore app backups, re-install them from the play store. IF you're installing apps from outside Play Store (and even from it), you need to be careful with what you install, you're always doing it at your own risk. Don't let the Play store restore your saved data, only the apps themselves.
And the problem it's not the phone, or everybodies phone.. I also have a maguro, like many in here, and there are a lot of us who never did have such an issue.
beekay201 said:
I thought you were trying to get a backup.
Anyways, don't restore app backups, re-install them from the play store. IF you're installing apps from outside Play Store (and even from it), you need to be careful with what you install, you're always doing it at your own risk. Don't let the Play store restore your saved data, only the apps themselves.
And the problem it's not the phone, or everybodies phone.. I also have a maguro, like many in here, and there are a lot of us who never did have such an issue.
Click to expand...
Click to collapse
I'm not restoring app backups, I only downloaded all them manually from the store, and I don't use any app installed outside the store, I use the same apps I have always used on my phone with no problems. In fact now phone is working well but without all my data on it. I didn't say that the problem is the phone as gnex, I mean maybe it's my phone that has an hardware issue but it seems too strange. My model is a C9 and I heard that these models could potentially have more issues than the others.
Inviato dal mio Galaxy Nexus con Tapatalk 2
Frank_9.5 said:
I'm not restoring app backups, I only downloaded all them manually from the store, and I don't use any app installed outside the store, I use the same apps I have always used on my phone with no problems. In fact now phone is working well but without all my data on it. I didn't say that the problem is the phone as gnex, I mean maybe it's my phone that has an hardware issue but it seems too strange. My model is a C9 and I heard that these models could potentially have more issues than the others.
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
Leave at least 2 or 3 GB free space.
a manta wrote this.
beekay201 said:
Leave at least 2 or 3 GB free space.
a manta wrote this.
Click to expand...
Click to collapse
I had 8 gb of free space, I was copying 700 mb of files and the phone rebooted.
Have you tried trimming your emmc?
a maguro wrote this.
beekay201 said:
Have you tried trimming your emmc?
a maguro wrote this.
Click to expand...
Click to collapse
I've tried using the app lagfix (free), it says: TRIM is not supported on the following partitions: /system, /data, /cache. This is either hardware or kernel issue and can not be worked around.
Frank_9.5 said:
I've tried using the app lagfix (free), it says: TRIM is not supported on the following partitions: /system, /data, /cache. This is either hardware or kernel issue and can not be worked around.
Click to expand...
Click to collapse
Unfortunately, I agree. I was only trying to get every troubleshooting out of the way, although these type of situations are normally hardware issues.
beekay201 said:
Unfortunately, I agree. I was only trying to get every troubleshooting out of the way, although these type of situations are normally hardware issues.
Click to expand...
Click to collapse
Yes, unfortunately... my phone is still in warranty but I read of many people who sent it for repair and they were without their phones for a long time, 1-2 months, and at the end the phone came back with the same problem... anyway it's the only solution. Thanks for the help
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.
reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r
cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.
Thank you.
It's sadly still doing it.
cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.
Factory Reset
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