Related
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
Hi,
I really like my HTC 10. The only thing I'm missing is the option to put my phone to sleep via a soft button or something like that.
I read that it's possible to install a new kernel and get the function to double tap the fingerprintsensor to lock the screen.
What do I have to do to add a similar function? Only flash a new kernel?
best regards
tom
edit: "only" flash a new kernel - I have no clue how to do it. And to root my phone is a bit complicated, because I want still be able to play PokémonGO.
Hi,
here is my way.
1. install "Screen Off & Lock" https://play.google.com/store/apps/details?id=com.katecca.screenofflock
2. activate Screen off & Lock in devices administrator
3. long press home button
4. choose "Screen Off"
regards
starbase64
Thank you for your answer.
I tested this app, because it sounds really promising.
I can't unlock my phone with the fingerprintsensor. It always want the PIN if I locked it with the app.
The "double tap on fingerprintsensor to sleep" thing sounds really good. Could someone provide some noob-friendly explanations? For example: Can I flash a kernel without flashing another ROM?
Use Tasker with "run shell" command "input keyevent 26".
Sent from my HTC 10 using Tapatalk
muhhh351 said:
Hi,
I really like my HTC 10. The only thing I'm missing is the option to put my phone to sleep via a soft button or something like that.
I read that it's possible to install a new kernel and get the function to double tap the fingerprintsensor to lock the screen.
What do I have to do to add a similar function? Only flash a new kernel?
best regards
tom
edit: "only" flash a new kernel - I have no clue how to do it. And to root my phone is a bit complicated, because I want still be able to play PokémonGO.
Click to expand...
Click to collapse
Try this. Root is not required, and it's free.....
https://play.google.com/store/apps/...ar2&pcampaignid=APPU_1_lDG8WOu6C6S7jwTBjZjIAg
comstockload said:
Try this.
Click to expand...
Click to collapse
Thank you for your suggestion. Unfortunately it's not what I'm looking for.
Maybe someone could answer if I can flash a kernel with staying at the stock ROM?
muhhh351 said:
Thank you for your suggestion. Unfortunately it's not what I'm looking for.
Maybe someone could answer if I can flash a kernel with staying at the stock ROM?
Click to expand...
Click to collapse
Clean slate kernel I think. Let us know as I'm in the same position as you [emoji2]
---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------
muhhh351 said:
Thank you for your suggestion. Unfortunately it's not what I'm looking for.
Maybe someone could answer if I can flash a kernel with staying at the stock ROM?
Click to expand...
Click to collapse
Clean slate kernel does I think, let me know if this works as I'm thinking of trying it for the same reason
timbohobbs said:
Clean slate kernel does I think
Click to expand...
Click to collapse
Thank you! Finally!
That was the keyword I needed!
I will read a bit about these things (I'm a noob - only rooted my OneX+) and try it.
As I understand it for now:
I unlock my phone with htcdev site
I install TWRP (don't know how - I will read about it in the threads)
Then I can flash the CleanSlate Kernel
No root necessary (so I can play PokémonGO without problems)
No settings app or something like that necessary. All features (double tap to sleep, some LED changes) are included.
But my phone will be cleaned (data and apps will be deleted).
EDIT:
- Adrenoboost version 2.2 - smooth gaming, battery friendly, fixing GPU handling of stock HTC kernel -- battery friendly conservative governor. Three levels (1 is the most battery friendly), and off state. ICE configurator / LeeDroid settings should handle it soon (thanks @flar2 for the original idea)
Click to expand...
Click to collapse
This feature maybe helps to play PoGO (drains battery really fast). So I will read about the ICE configurator, too... Much to learn
muhhh351 said:
Thank you! Finally!
That was the keyword I needed!
I will read a bit about these things (I'm a noob - only rooted my OneX+) and try it.
As I understand it for now:
I unlock my phone with htcdev site
I install TWRP (don't know how - I will read about it in the threads)
Then I can flash the CleanSlate Kernel
No root necessary (so I can play PokémonGO without problems)
No settings app or something like that necessary. All features (double tap to sleep, some LED changes) are included.
But my phone will be cleaned (data and apps will be deleted).
EDIT: This feature maybe helps to play PoGO (drains battery really fast). So I will read about the ICE configurator, too... Much to learn
Click to expand...
Click to collapse
Sounds like you know what you're doing, reading is always the most important thing. Make sure you use unofficial twrp after reading the op and FAQ on twrp perfume thread.
I'm running stock rooted currently and, same as you am missing the screen off button from my m8. My procedure was slightly different in that I used sunshine to S off, then took all Ota's to nougat, then flashed twrp. That way there is no need for HTC Dev to unlock bootloader so no data loss. I then rooted with supersu, but of course I can't use PoGo or banking apps. You could also flash leedroid rom which uses clean slate kernel, this has loads of tweaks and can be ran without root to enable PoGo etc.
muhhh351 said:
Thank you! Finally!
That was the keyword I needed!
I will read a bit about these things (I'm a noob - only rooted my OneX+) and try it.
As I understand it for now:
I unlock my phone with htcdev site
I install TWRP (don't know how - I will read about it in the threads)
Then I can flash the CleanSlate Kernel
No root necessary (so I can play PokémonGO without problems)
No settings app or something like that necessary. All features (double tap to sleep, some LED changes) are included.
But my phone will be cleaned (data and apps will be deleted).
EDIT: This feature maybe helps to play PoGO (drains battery really fast). So I will read about the ICE configurator, too... Much to learn
Click to expand...
Click to collapse
Hi there, got updated to 7.0 early last week, everything was fine except similar to you that fingerprint was down. Every time i tried record my fingerprint, i was asked to enter either PIN or pattern repeatedly.
Can anyone help?
muhhh351 said:
Thank you for your answer.
I tested this app, because it sounds really promising.
I can't unlock my phone with the fingerprintsensor. It always want the PIN if I locked it with the app.
The "double tap on fingerprintsensor to sleep" thing sounds really good. Could someone provide some noob-friendly explanations? For example: Can I flash a kernel without flashing another ROM?
Click to expand...
Click to collapse
This Mod uses your fingerprint to lock your device. Longer presses will take you to the reboot menu.
:good: Download in my rom section or this quicklink.
https://forum.xda-developers.com/devdb/project/dl/?id=29427
How can i remove it from my phone?
nemanco said:
How can i remove it from my phone?
Click to expand...
Click to collapse
Unfortunately I had to reinstall my rom. :x
The problem was that the FP sensor is way too sensitive after installing the mod.
I couldn't hold the phone in the hand without instantly triggering the FP sensor.
Foremost the FP sensor doesn't react not only to saved FP's.
You should definitely look into that, Jerome.
Or at least offer a patch to uninstall the mod.
Besides that it's a very good idea, but it needs fine tuning.
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
nemanco said:
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
Click to expand...
Click to collapse
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment restore-fingerprint.zip
SubwayChamp said:
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment 4505426
Click to expand...
Click to collapse
Worked as a charm, thanks! !!!
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
mavid26 said:
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
Click to expand...
Click to collapse
Almost any rom would need a proper remover/replacer zip, last was for miui roms so try this, read the post #5 and apply to this zip before flashing it. I hope it works
View attachment restore-fingerprint-aex71.zip
I installed the lineage os 15.1 on my xiaomi redmi 5 plus, but the fingerprint settings are not there and I do not know how to put them.
Are there any mods? How can I do?
thank you
Thanks for your amazing mod it's working prefect on my miui but now i installed pixel experience rom and the mod not work. Please update it for costume roms.
Tested on MIUI 10 RN5 Global (AI) and it broke both power button and fingerprint button.
EDIT: the fix provided did not work for me. Copied the folder as requested to the zip but even after flash the buttons are still broken (had to flash the ROM, just a system restore could not fix it too.)
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
sfnemis said:
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
Click to expand...
Click to collapse
Which version firmware are you using?
lock unlock fingerpriner
does it exist for redmi note 7?
Way to fix...
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
king.com said:
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
Click to expand...
Click to collapse
Hi, Is there a code you know for the mi A1 (tissot) is needed to lock the screen.
or there may be a hint on where to find it, thanks :victory:
Hello,everybody,since no developers working on custom rom for P20,we have to flash a treble rom,or,like you see here,flash a P20pro rom.
After several days trying,I finally suggest you to flash the lineage15.1 rom ported to P20 pro from Luk.
Now,it's time to escape from Huawei EMUI，out of the limit(like more apps background running).
What's the good thing?
Fingerprint yes! Fast charge yes! Full screen apps yes! Even stock camera(from Androlark).
Any bugs?
NFC(not working at all) ,wifi-hotspot(you can use USB tethering instead).
Here is a guide for flashing:
Before you go,make sure a unlocked bootloader,and twrp for installing gapps/migisk/stock camera.And you must do a full factory reset,it's very important ,otherwise the rom can't boot.
A flashable system.img link(extract from Luk's P20 pro rom)
One-click ADB
Flash it using ADB tool.
Type the following line:
Code:
fastboot erase system
Code:
fastboot -u flash system p20-lineage15.1-system.img
Then reboot.
If you want to flash gapps,after boot worked,turn the "Developer options"-"Advanced restart",then reboot to twrp,wipe data cache dalvik again(it's necessary,if not ,you will see the apps forceclosing again and again)
Cheers:highfive:
Thanks @LuK1337 again
Reserved for Q&A.
Thanks for the thread man !
But with the upcoming update of Pie, i will wait a little bit before jumping on a new rom than the EMUI, otherwise i would already installed it.
maxime4611 said:
Thanks for the thread man !
But with the upcoming update of Pie, i will wait a little bit before jumping on a new rom than the EMUI, otherwise i would already installed it.
Click to expand...
Click to collapse
I can't wait,so I flash the rom. Apart from that,I also like original Android,with much more freedom
qisu2011 said:
I can't wait,so I flash the rom. Apart from that,I also like original Android,with much more freedom
Click to expand...
Click to collapse
Finally able to boot on the rom.
If you have trouble for install : try a different version of adb, and after a full factory reset, go to twrp and wipe dalvik, cache and internal storage again then flash.
How come hotspot is broken here but not on the official Treble Lineage 15.1 ?
maxime4611 said:
Finally able to boot on the rom.
If you have trouble for install : try a different version of adb, and after a full factory reset, go to twrp and wipe dalvik, cache and internal storage again then flash.
Click to expand...
Click to collapse
That's right bro,sorry I didn't help you in time yesterday,I'm in China,there's a time difference between us.
Upload an ADB tool I'm using,for those who need it.
One-click ADB
Thanks for the tool
- Fingerprint working
- Root & magisk supported.
- Stock Camera mod also works
- Always on display (but i really don't like it and no stock setting to disable it completely, only hide it when you turn off the screen)
So far the bugs i encounter are:
- No notch support (but icons are spread between the edge of the status bar, so only the speed meter is hidden in my case)
- The home button only works for fingerprint sensor if you have virtual button enabled.
-NFC ? (i don't use it)
Here's some screenshots to show the notification system's behavior (yes, they are expandable from the notification drawer and lockscreen :good: )
I attach a link for a simple script tool that I have used which is very useful for creating flashable system images from system.new.dat.br and system.transfer.list files.
Extractor 3.5
I have attached this so that people can make their own system image files when the Linage OS rom is updated rather than wait for someone to upload their own image files.
Instructions
1. Extract Extractor folder from attached zip.
2. Extract system.new.bat.br and system.transfer.list from rom zip file.
3. Place files in folder labelled "place_for_supported_files_here".
4. Run Extraktor_EN.cmd
5. Select option 9.
6. Use the system.new.img and flash using fastboot as detailed in the original post.
maxime4611 said:
Thanks for the tool
- Fingerprint working
- Root & magisk supported.
- Stock Camera mod also works
- Always on display (but i really don't like it and no stock setting to disable it completely, only hide it when you turn off the screen)
So far the bugs i encounter are:
- No notch support (but icons are spread between the edge of the status bar, so only the speed meter is hidden in my case)
- The home button only works for fingerprint sensor if you have virtual button enabled.
-NFC ? (i don't use it)
Here's some screenshots to show the notification system's behavior (yes, they are expandable from the notification drawer and lockscreen :good: )
Click to expand...
Click to collapse
There are options in system settings bro.
Display-advanced
At first thanks for your work :good:
Which one of Luk's builds you took?
The new (25.09.2018) or the old (28.08.2018) one ?
Schubi97 said:
At first thanks for your work :good:
Which one of Luk's builds you took?
The new (25.09.2018) or the old (28.08.2018) one ?
Click to expand...
Click to collapse
new
Man, I really want Lineage 16 instead... I've had no luck finding any Pie based rom for the P20.
qisu2011 said:
There are options in system settings bro.
Display-advanced
Click to expand...
Click to collapse
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...
Muscar said:
Man, I really want Lineage 16 instead... I've had no luck finding any Pie based rom for the P20.
Click to expand...
Click to collapse
That's the problem,no pie rom for p20 can boot except emui9 beta at the moment. I tried all I could find, including aosp pie for Honor v10,which is based on emui8.1 vendor,can boot on p20 pro.
USB C headphones doesn't work
Theo1218 said:
USB C headphones doesn't work
Click to expand...
Click to collapse
No they dont, adapter works..
maxime4611 said:
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...
Click to expand...
Click to collapse
I have tested for days bro,it's normal on my phone.
I flashed the rom based EMUI version 167sp1(for CN EML-AL00). Maybe this is the point?
maxime4611 said:
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...
Click to expand...
Click to collapse
I have tested for days bro,it's normal on my phone.
I flash the rom based EMUI version 167sp1(for EML-AL00),could this be the point?
Anyone tried this on their P20 yet?
https://forum.xda-developers.com/hu...r-forget-emui-9-install-aosp-android-t3855930
Hey all
I very recently made the mistake of upgrading my phone, not realising that it was a complete overhaul from 8.0 to 9.0. I absolutely hate it. There are a dozen downsides and, as far as I have noticed, not a single benefit to this upgrade. I have gotten frustrated many times already due to the stupid little changes and have spent a good portion of my day attempting to figure out how to reverse it.
Now I'm not that tech-savvy, and the only method to get back the phone I knew and loved is to 'flash' it (?) using a software which I have acquired. I must also apparently make sure to back up my data because downgrading in this manner apparently does not ensure any of your personal data is protected.
So my question here is twofold:
1. Does anybody have the UK version for the latest 47.1.A.16.20 firmware as an appropriate file (FTF?) for me to get back the phone I paid for as opposed to this crap?
2. What would be an appropriate method of backing up my phone such that I can recover it all post-flash with all of my settings and user data intact?
Thank you all so very much for your help!
PCBearington said:
Thank you all so very much for your help!
Click to expand...
Click to collapse
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Here is a copy of 47.1.A.16.20, It's not the UK version, but that makes no difference
Download Newflasher and put it in the same folder as the firmware you downloaded
Delete persist*.sin to avoid losing android attest key.
Turn phone off completely. Then start newflasher.exe and follow instrctions. Plug the phone into the pc whilst holding volume up(+), then no & no in the newfalsher dialog box, then you should be away.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, you can't keep your data when you downgrade, so this would be the easiest way of keeping the important stuff. Back up onto your sdcard, then restore once the flash has completed.
Didgesteve said:
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Here is a copy of 47.1.A.16.20, It's not the UK version, but that makes no difference
Download Newflasher and put it in the same folder as the firmware you downloaded
Delete persist*.sin to avoid losing android attest key.
Turn phone off completely. Then start newflasher.exe and follow instrctions. Plug the phone into the pc whilst holding volume up(+), then no & no in the newfalsher dialog box, then you should be away.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, you can't keep your data when you downgrade, so this would be the easiest way of keeping the important stuff. Back up onto your sdcard, then restore once the flash has completed.
Click to expand...
Click to collapse
Hi Steve, I accidentally installed the update today and I wish to revert too. Apparently the Xperia XZ1c has DRM keys for things like the camera and video processing which if custom firmware is flashed will be lost. Is this an issue when flashing an older version of a stock xperia rom like you are suggesting? Thanks
Joecalone said:
Hi Steve, I accidentally installed the update today and I wish to revert too. Apparently the Xperia XZ1c has DRM keys for things like the camera and video processing which if custom firmware is flashed will be lost. Is this an issue when flashing an older version of a stock xperia rom like you are suggesting? Thanks
Click to expand...
Click to collapse
No unlocking the bootloader is an entirely seperate procces and can't be done accidently flashing firmwares. You have to get an unlock code from Sony and do some ADB magic.
There is another tools called Flashtool, that does the same thing as Newflasher, but has the power to delete your DRM, if driven improperly, so I don't recomend that.
Newflasher is safe to use and won't damage your TA partition (DRM keys), just note the persistxx.sin removal, that stops damage to one of the partitions.
You can't keep you data when retro-grading, you must wipe the phone to factory, there isn't any other way.
Didgesteve said:
No unlocking the bootloader is an entirely seperate procces and can't be done accidently flashing firmwares. You have to get an unlock code from Sony and do some ADB magic.
There is another tools called Flashtool, that does the same thing as Newflasher, but has the power to delete your DRM, if driven improperly, so I don't recomend that.
Newflasher is safe to use and won't damage your TA partition (DRM keys), just note the persistxx.sin removal, that stops damage to one of the partitions.
You can't keep you data when retro-grading, you must wipe the phone to factory, there isn't any other way.
Click to expand...
Click to collapse
Thanks for the quick response! I'm backing up my phone right now. You mentioned the persistxx.sin removal, sorry if the answer is obvious but I'm a bit new to all this, does Newflasher do this automatically or do I need to do it myself? If so, how does one go about removing it?
Joecalone said:
Thanks for the quick response! I'm backing up my phone right now. You mentioned the persistxx.sin removal, sorry if the answer is obvious but I'm a bit new to all this, does Newflasher do this automatically or do I need to do it myself? If so, how does one go about removing it?
Click to expand...
Click to collapse
It'll be in the firmware folder that download
Didgesteve said:
It'll be in the firmware folder that download
Click to expand...
Click to collapse
Ah right I think I understand you, I opened the ftf file with 7zip and deleted the file named "persist.sin". I'll be flashing it tomorrow so I'll let you know how it went. Really appreciate the tips
PCBearington said:
I absolutely hate it. There are a dozen downsides and, as far as I have noticed, not a single benefit to this upgrade.
Click to expand...
Click to collapse
Hey PCB! Could you tell me more about all those downsides? I'd like to know more before/if I (ever) decide to upgrade.
I know that clock on the left-hand side would irritate me. Also, volume buttons defaulting to media is something I don't like.
But you mentioned "a dozen" so I'm curious.
Tnx!
komer said:
Hey PCB! Could you tell me more about all those downsides? I'd like to know more before/if I (ever) decide to upgrade.
I know that clock on the left-hand side would irritate me. Also, volume buttons defaulting to media is something I don't like.
But you mentioned "a dozen" so I'm curious.
Tnx!
Click to expand...
Click to collapse
Hey man! I wrote up a few reasons on a Reddit post earlier so I'm just going to paste that if that's okay!
Volume button now always does media volume instead of a sliding scale for normal stuff ie ringtone
Lots of irritatingly unnecessary changes such as the time now being in the top right so my muscle memory has me checking the time and I'm momentarily confused.
They've changed the overall aesthetic to be more Apple-y resulting in a really weird look, making the text in most places look larger than usual (especially the notifications).
The pull-down-from-the-top menu now shows two rows of enlarged buttons instead of three like before.
The WiFi and Bluetooth drop down menus have gone, so now if you want to quickly switch between two networks instead of being able to do it all in one screen you have to go to the settings page for WiFi and Bluetooth.
(this one is very minor) the colour of the keyboard has gone from black and orange (which I liked) to black and blue.
I know it sounds like I'm being awfully nitpicky but honestly the few bits of functionality that were removed were things I relied on a lot; I just don't appreciate such ****ty unnecessary changes for no apparent reason.
As far as I can see, there are absolutely no improvements or upgrades or anything at all that I can point to and go "yeah that's worth it."
I've been using this update for only a little while and I'm sure that there are other things which'll pop out at me over time as well!
Hope this helps mate
PCBearington said:
The pull-down-from-the-top menu now shows two rows of enlarged buttons instead of three like before.
The WiFi and Bluetooth drop down menus have gone, so now if you want to quickly switch between two networks instead of being able to do it all in one screen you have to go to the settings page for WiFi and Bluetooth.
Click to expand...
Click to collapse
These two are absolutely unacceptable. An update should never remove features or make previous things harder to do, this update is an absolute joke. Now once again I have to go through the arduous process of factory resetting my phone to downgrade simply because Sony couldn't put out a competent update to save their lives.
Thanks mate! I agree with you 100%. The phone is "perfect" just the way it is and some changes, that Google and Sony made, should totally have been optional. I would upgrade it just for curiosity.... but I don't wanna regret it later.
Cheers!
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
I've just updated and am I wrong or the recent app switcher and the navigation bar are still the same and not the Pie version?
Dark Emotion said:
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
Click to expand...
Click to collapse
I can only have two rows shown at a time on mine! I looked in the settings as well, any other buttons now have to be swiped across to access because of how ludicrously large they made them.
bexem said:
I've just updated and am I wrong or the recent app switcher and the navigation bar are still the same and not the Pie version?
Click to expand...
Click to collapse
You're not wrong. It's the same. Sony removed Google's gesture navigation.
PCBearington said:
I can only have two rows shown at a time on mine! I looked in the settings as well, any other buttons now have to be swiped across to access because of how ludicrously large they made them.
Click to expand...
Click to collapse
Sorry man, I forgot that I changed dpi in settings. Take a look at the screenshot I attached.
Didgesteve said:
It'll be in the firmware folder that download
Click to expand...
Click to collapse
Hi, me again :laugh:
I tried flashing the phone today with newflasher but to no avail. I downloaded those xperia drivers, added them using device manager, and the hardware wizard gave the following message
"The following hardware was installed:
Sony sa0117 ADB Interface Driver
The software for this device is now installed but may not work correctly.
This device cannot start (Code 10)"
I tried flashing anyway after the phone had been put into debug mode but newflasher simply prompts whether or not I need GordonGate flash driver. If I type "n" to skip, it throws the error
"No usb device with vid:0x0fce pid:0xb00b !"
Joecalone said:
Hi, me again :laugh:
I tried flashing the phone today with newflasher but to no avail. I downloaded those xperia drivers, added them using device manager, and the hardware wizard gave the following message
"The following hardware was installed:
Sony sa0117 ADB Interface Driver
The software for this device is now installed but may not work correctly.
This device cannot start (Code 10)"
I tried flashing anyway after the phone had been put into debug mode but newflasher simply prompts whether or not I need GordonGate flash driver. If I type "n" to skip, it throws the error
"No usb device with vid:0x0fce pid:0xb00b !"
Click to expand...
Click to collapse
If you're using Windows 10 it would have completly failed to install your driver and didn't bother telling you. Restart Windows 10 in safe mode and look for 'driver signing disabled', then try again.
Edit: or click 'Yes' to first question in Newflasher and it will prodice a zip file of the drivers you need, then apply as above.
Didgesteve said:
If you're using Windows 10 it would have completly failed to install your driver and didn't bother telling you. Restart Windows 10 in safe mode and look for 'driver signing disabled', then try again.
Edit: or click 'Yes' to first question in Newflasher and it will prodice a zip file of the drivers you need, then apply as above.
Click to expand...
Click to collapse
No luck with either of these unfortunately. I'll try doing it on my Windows 7 PC at home, hopefully I'll get better results with that :fingers-crossed:
Dark Emotion said:
Are we talking about toggles? You do know that you can add a third row? For WiFi and Bluetooth just do the long press and go to settings.
Click to expand...
Click to collapse
Dark Emotion said:
Sorry man, I forgot that I changed dpi in settings. Take a look at the screenshot I attached.
Click to expand...
Click to collapse
Would you mind telling me how you did that? I trawled through the settings briefly but couldn't see anything applicable!
Would really appreciate it!