Develop Bugs

[Theme] Modified InversionUI Vendor.img

Mods please close.

Thank you soooooo much! The lack of a custom recovery and root has been killing me. This will definitely help tide me over until then. Inversion ui is the best, too.

Absolutely ^, thanks for throwing this together

any updates to this or will this vendor img work for the newest ota?

ZiggSVO said:
any updates to this or will this vendor img work for the newest ota?
Click to expand...
Click to collapse
Didn't really expect people to be using this at this point.
But when I get a chance I'll happily update this for the latest OTA
Sent from my iPhone using Tapatalk

ZiggSVO said:
any updates to this or will this vendor img work for the newest ota?
Click to expand...
Click to collapse
You can root your Pixel C now. There is no need to use this anymore. Just root and then install Layers Manager + Inversion UI.

oRAirwolf said:
You can root your Pixel C now. There is no need to use this anymore. Just root and then install Layers Manager + Inversion UI.
Click to expand...
Click to collapse
Layers no longer working, even with Root. I like this vendor.img.
Sent from my Pixel C using Tapatalk
---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------
superchilpil said:
Didn't really expect people to be using this at this point.
But when I get a chance I'll happily update this for the latest OTA
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
For some reason I can't get layers working on Android N Preview 5. They did work on previews 2-4.
I therefore dl and flashed the Vendor.img file. Looks real nice, even on Preview 5. If you can update it or customize the Vendor.img so that other layers can be used, it would be nice. Thanks in advance.
Sent from my Pixel C using Tapatalk

Well the point of this was since root was a bit wonky at first I threw this together because I had root working on mine.
All I did was installed layers and pulled the vendor image.
Probably not what you want to hear but if you roll back to preview 4 then install layers and update everything but your vendor image you can keep layers.
I just don't have the time anymore.
Sent from my Nexus 6P using Tapatalk

superchilpil said:
Well the point of this was since root was a bit wonky at first I threw this together because I had root working on mine.
All I did was installed layers and pulled the vendor image.
Probably not what you want to hear but if you roll back to preview 4 then install layers and update everything but your vendor image you can keep layers.
I just don't have the time anymore.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, that's good advice, but instead I can flash the vendor image from my Preview 4 Nandroid. Do you have any idea why layers is not working on DP5? I couldn't restore my layers backup and could not even create a file called "Overlays" in the System/Vendor even though I had root explorer set to R/W.
I did what you suggested, but got the exact same Google System error message when booting up that I got with your Vendor.img file. Google was not fooled by the Vendor.img from DP4. The vendor image works fine and I can flash whatever layers that work with N. Only thing I had an issue with was that in the Settings/About tablet a small window opens up and then when I press Check for Updates it crashes. I think that it is because of Inversions.UI or because I have a DP4 System Image and I'm checking for updates to DP5.
Got rid of the error message by copying the Build.prop from the Vendor.image file in DP5 and pasting it back into the DP4 Build.prop. No more Google warning! However, Settings/About tablet/Check System Updates still crashes.
Haven't' figured that one out yet.
Thanks,
Sent from my Pixel C using Tapatalk

Alxoom33 said:
No, that's good advice, but instead I can flash the vendor image from my Preview 4 Nandroid. Do you have any idea why layers is not working on DP5? I couldn't restore my layers backup and could not even create a file called "Overlays" in the System/Vendor even though I had root explorer set to R/W.
I did what you suggested, but got the exact same Google System error message when booting up that I got with your Vendor.img file. Google was not fooled by the Vendor.img from DP4. The vendor image works fine and I can flash whatever layers that work with N. Only thing I had an issue with was that in the Settings/About tablet a small window opens up and then when I press Check for Updates it crashes. I think that it is because of Inversions.UI or because I have a DP4 System Image and I'm checking for updates to DP5.
Got rid of the error message by copying the Build.prop from the Vendor.image file in DP5 and pasting it back into the DP4 Build.prop. No more Google warning! However, Settings/About tablet/Check System Updates still crashes.
Haven't' figured that one out yet.
Thanks,
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Found out it seems to be a problem with the Inversion UI layers themselves. At some point I may have to use another dark theme like Timberwolve.
Sent from my Pixel C using Tapatalk

update to 7.0 Ota from rooted rom?

Do I download update Ota then install on rooted rom, or flash Back to stock and update

pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
You should flash back to stock and update. Cannot install OTA over a rooted rom I believe.
However, I came from Paranoid Android and followed the advice here, and it worked perfectly. Was able to keep root and TWRP.
http://forum.xda-developers.com/showpost.php?p=68314164&postcount=69

oeusr said:
You should flash back to stock and update. Cannot install OTA over a rooted rom I believe.
However, I came from Paranoid Android and followed the advice here, and it worked perfectly. Was able to keep root and TWRP.
http://forum.xda-developers.com/showpost.php?p=68314164&postcount=69
Click to expand...
Click to collapse
currently on CM13.1 nightly I'm going to follow what you did. Hope it will work

I was rooted I use this post, and the is a link in that thread to the actual zip your will need, and also you must have the updated TWRP as well. All the information is in that thread. but that is literally it.
Download update zip
Download Flashfire
download new TWRP
Back up you crap ( will not wipe SD card unless you tell it to )
Run FlashFire, set setting correctly
run it, you will already be rooted when done
set dev mode
re-flash new TWRP
PROFIT

Did you get the option "Restore boot and recovery images" when setting Flash OTA zip? I just got Auto mount and Mount /system read/write.

pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
You can use Flashfire to flash OTA file

i don't get the option to restore boot and recovery images. is that ok ?

pdolo5784 said:
Do I download update Ota then install on rooted rom, or flash Back to stock and update
Click to expand...
Click to collapse
If you have Xposed just get Android N-ify and it's just like having 7.0

Anyone updated from DP5 / systemless root / TWRP?
And flashed zip for adaway to work.
What are the steps to update with ota zip?

Yes and everything is ok. Follow the steps carm01 suggests some post above. Its easy and at least for me everything worked. After fisrt boot you can go to TWRP and flash everything else you need.

blackra1n said:
If you have Xposed just get Android N-ify and it's just like having 7.0
Click to expand...
Click to collapse
Not really other then a couple of options.
Sent from my Nexus 5X using Tapatalk

milan187 said:
Not really other then a couple of options.
Click to expand...
Click to collapse
You can get the same experience without going through the trouble of upgrading and then having to root again etc. I personally like it but we all have opinions

blackra1n said:
You can get the same experience without going through the trouble of upgrading and then having to root again etc. I personally like it but we all have opinions
Click to expand...
Click to collapse
I used it months ago so there could be a lot of changes to it since then?
I don't believe the new notifications are there? Quick pull down? It's also nice that it takes up a GB less for system as well.
What rom are you on?
Sent from my Nexus 5X using Tapatalk

milan187 said:
I used it months ago so there could be a lot of changes to it since then?
I don't believe the new notifications are there? Quick pull down? It's also nice that it takes up a GB less for system as well.
What rom are you on?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The notifications are definitely there, so is quick pull down It's updated frequently so I'm sure the experience is the same
I'm running Dirty Unicorns 6.0.1 with ElementalX kernel

blackra1n said:
The notifications are definitely there, so is quick pull down It's updated frequently so I'm sure the experience is the same
I'm running Dirty Unicorns 6.0.1 with ElementalX kernel
Click to expand...
Click to collapse
I just looked at N-Fy, pretty impressive. Good for them.
Sent from my Nexus 5X using Tapatalk

milan187 said:
I just looked at N-Fy, pretty impressive. Good for them.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
They've definitely done a great job

No working recovery for Oos 4.0 and I'm softbricked :(

Hi
I updated to Oos 4.0. Then flashed TWRP. It boots into recovery but I can't see any files when I attempt to flash anything. I need to decrypt and from what I've read, that requires a data format. I tried that and now my system won't boot.
So as it stands, I have an unlocked bootloader, I can access TWRP but without being able to see the files and I can't boot up my phone.
Please help.
Edit: Latest TWRP (3.0.4) worked with Nougat and problem solved. Thanks everyone.

Use a different TWRP.. The latest one should support encrypted. Keep in mind booting on encrypted in twrp can take a long time so do not panic!
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999

LeighR said:
Hi
I updated to Oos 4.0. Then flashed TWRP. It boots into recovery but I can't see any files when I attempt to flash anything. I need to decrypt and from what I've read, that requires a data format. I tried that and now my system won't boot.
So as it stands, I have an unlocked bootloader, I can access TWRP but without being able to see the files and I can't boot up my phone.
Please help.
Click to expand...
Click to collapse
Follow this guide:
https://www.youtube.com/watch?v=m3E-WYwk1QM&t=56s

you need the latest unreleased beta twrp. I would flash a full OOS as well to make sure everything is clean. I had the same problem and its a 10 min fix with the right twrp
Sent from my ONEPLUS A3000 using Tapatalk

Puddi_Puddin said:
Use a different TWRP.. The latest one should support encrypted. Keep in mind booting on encrypted in twrp can take a long time so do not panic!
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
Click to expand...
Click to collapse
I should have said, I'm using the OnePlus 3T. I just tried this file and it wouldn't work, then read not to try on the 3T. Thanks anyway
uudruid74 said:
you need the latest unreleased beta twrp. I would flash a full OOS as well to make sure everything is clean. I had the same problem and its a 10 min fix with the right twrp
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Do you know where I might find it for the 3T? I'm looking but can't find it. Thanks.

LeighR said:
I should have said, I'm using the OnePlus 3T. I just tried this file and it wouldn't work, then read not to try on the 3T. Thanks anyway
Do you know where I might find it for the 3T? I'm looking but can't find it. Thanks.
Click to expand...
Click to collapse
3 and 3T are now combined. See thread
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
Sent from my ONEPLUS A3000 using Tapatalk

LeighR said:
I should have said, I'm using the OnePlus 3T. I just tried this file and it wouldn't work, then read not to try on the 3T. Thanks anyway
Do you know where I might find it for the 3T? I'm looking but can't find it. Thanks.
Click to expand...
Click to collapse
My fault, here https://forum.xda-developers.com/devdb/project/?id=15934#downloads look for this file: "twrp-3.0.3-x_blu_spark_v20-op3_op3t.img". This should 100% work!

v3.0.4-1 should work.

Thanks everyone, I used a newer TWRP and it worked

Planning to Rollback to MM

Whats the latest last stable build of CyanogenMod 13?
Planning to downgrade due to some xposed modules i miss anyone can help me link the rom . Thank you ?
Sent from my Nexus 5X using Tapatalk

This should be latest Snapshot.

neth15 said:
This should be latest Snapshot.
Click to expand...
Click to collapse
Thanks sir, from where thread did you get this one? ? Thanks for the link
Sent from my Nexus 5X using Tapatalk

And what vendor image should i use?
Sent from my Nexus 5X using Tapatalk

paul222008 said:
And what vendor image should i use?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
According to HERE the last image for MM was MTC20K.
You can even download the full image from there, and extract the vendor.img if you can't find it elsewhere.
I would also try downloading the newest N4F26T 7.1.1 just for extracting the radio.img out of it, and flashing that. Radio.img is independent of OS version, and may offer some improvement.

Flash latest MM factory image and then install cm13 I linked.
I found it a while ago, when I was testing Sailfish OS which requires installing CM13 first But it's standard CM, don't worry

crazyates said:
According to HERE the last image for MM was MTC20K.
You can even download the full image from there, and extract the vendor.img if you can't find it elsewhere.
I would also try downloading the newest N4F26T 7.1.1 just for extracting the radio.img out of it, and flashing that. Radio.img is independent of OS version, and may offer some improvement.
Click to expand...
Click to collapse
Is it safe to downgrade? It's just some modules in xposed i would like to used again
neth15 said:
Flash latest MM factory image and then install cm13 I linked.
I found it a while ago, when I was testing Sailfish OS which requires installing CM13 first But it's standard CM, don't worry
Click to expand...
Click to collapse
Sailfish OS is MM right?
Sent from my Nexus 5X using Tapatalk

paul222008 said:
Is it safe to downgrade? It's just some modules in xposed i would like to used again
Click to expand...
Click to collapse
Yes, just keep in mind doing factory reset before flashing older system image and you'll be good to go.

przemcio510 said:
Yes, just keep in mind doing factory reset before flashing older system image and you'll be good to go.
Click to expand...
Click to collapse
+1 I would wipe everything, and start over from scratch. WIth an unlocked bootloader, you could theoretically boot anything you wanted, as long as it's made for bullhead.

Downgrade from Android P DP5 to DP3?

Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk

Bromsoket said:
Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Flash the factory image, but you shouldn't need to wipe data.
Use a text editor (I use Notepad++) to open the flash-all.bat file and remove the "-w " near the end of the script. Then it won't wipe your phone.

But to do that I need to unlock bootloader?
Then the phone will be wiped?
xunholyx said:
Flash the factory image, but you shouldn't need to wipe data.
Use a text editor (I use Notepad++) to open the flash-all.bat file and remove the "-w " near the end of the script. Then it won't wipe your phone.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Bromsoket said:
But to do that I need to unlock bootloader?
Then the phone will be wiped?
Click to expand...
Click to collapse
Yep

Ok.
Not possible to just sideload DP3 OTA image I guess?
TonikJDK said:
Yep
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Yeah, think I will go back to DP4 from DP5 myself, since I can't get TWRP to load temp recovery.

Bromsoket said:
Ok.
Not possible to just sideload DP3 OTA image I guess?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You can always just relock your bootloader. It's not hard to do.

Bromsoket said:
Hello xda,
Is it possible to downgrade from Android P DP5 to DP3 by just flashing the DP3 OTA image or is a full factory image required wiping all data?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
May I ask why are you down grading?
If it's because TWRP not allowing you to boot into recovery, I found a work around for that issue.

Yes I know, done this before, I just want to avoid getting the phone wiped (Backup/restore takes ages..)
xunholyx said:
You can always just relock your bootloader. It's not hard to do.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Sure
DP4 and 5 don't save exif data in photos taken using portrait mode and during summer I am taking loads of pictures and since the exif data is missing I can't organize them in a efficient way..
I didn't have any problem with my phone since DP3 so going back to is not really a "downgrade" for me and I don't root my phone, just stock.
3rd party camera might be a workaround but I find the stock cam better.
dallas90733 said:
May I ask why are you down grading?
If it's because TWRP not allowing you to boot into recovery, I found a work around for that issue.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Need some help here...
Tried to downgrade from Android P DP5 to DP3 but it fails with this message:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'vendor.sig'
archive does not contain 'system.sig'
Bootloader is unlocked and i tried many times but always fails with the same message...
(It worked before when i upgraded from 8.1 to DP2)
Any ideas?
Thanks.

Bromsoket said:
Need some help here...
Tried to downgrade from Android P DP5 to DP3 but it fails with this message:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'vendor.sig'
archive does not contain 'system.sig'
Bootloader is unlocked and i tried many times but always fails with the same message...
(It worked before when i upgraded from 8.1 to DP2)
Any ideas?
Thanks.
Click to expand...
Click to collapse
Have you tried using Android SDK "platform tool?"
I download it, went into the platform tool folder and added the file I wanted to flash, and it ran super fast and easy without any error. I was getting multiple errors as well, when I try to use ADB.

Thanks,
Will try that, hopefully it works better.
dallas90733 said:
Have you tried using Android SDK "platform tool?"
I download it, went into the platform tool folder and added the file I wanted to flash, and it ran super fast and easy without any error. I was getting multiple errors as well, when I try to use ADB.
Click to expand...
Click to collapse

Bromsoket said:
DP4 and 5 don't save exif data in photos taken using portrait mode
Click to expand...
Click to collapse
Really? I'm not seeing that problem. All the pics I've taken since getting DP5 are still tagged with info like GPS coords, etc.

drwtsn32x said:
Really? I'm not seeing that problem. All the pics I've taken since getting DP5 are still tagged with info like GPS coords, etc.
Click to expand...
Click to collapse
Photos taken using portrait mode?
Normal mode is working, the problem is in
portrait mode.
Sent from my Pixel 2 XL using Tapatalk

Bromsoket said:
Photos taken using portrait mode?
Normal mode is working, the problem is in
portrait mode
Click to expand...
Click to collapse
Yep. Works in either orientation for me.

Ok.
Did you update to DP5 OTA or clean flash?
Thinking about trying a clean DP5 install.
Sent from my Pixel 2 XL using Tapatalk

It's not the orientation that's the issue. It's the Portrait Mode (Bokeh Effect). For me, sometimes EXIF information is there and sometimes it's not.
drwtsn32x said:
Yep. Works in either orientation for me.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

drwtsn32x said:
Yep. Works in either orientation for me.
Click to expand...
Click to collapse
Portrait mode as in the camera portrait mode (bokeh effect), not as in portrait orientation.

uicnren said:
Portrait mode as in the camera portrait mode (bokeh effect), not as in portrait orientation.
Click to expand...
Click to collapse
Oh, I see what you mean now. Yes confirmed - that mode doesn't store GPS coords.