Greetings,
I have a brand new Nexus One and I am eager to void the warranty.
I have downloaded the Android Eclair source (v2.1r2) and built the system image (system.img) and it works great on the Android emulator. I am hoping this forum will tell me two things:
1. What do I do differently to build a system image for the Nexus one? I'm pretty sure I'm going to need different drivers and libraries - how do I get them and how do I insert them into my build process?
2. How do I get (flash) the system image onto the Nexus one phone? I'm guessing I use this command: fastboot flash system system.img, but I'm not sure.
Thanks. I apologize in advance if this is the wrong forum for these questions.
-Sam
Hello all, this is a request for a build.prop file. I recently got the Android L OTA update on my Nexus 7 2013 WiFi. The update downloaded as normal, however when it tries to install I get the message:
Verifying current system...
"/system/build.prop" has unexpected contents.
My tablet is rooted, however I have never (intentionally, at least) modified my build.prop, and so I have no backup of it. Please could someone help me out and give me a copy of their build.prop.
I'm from the UK (IDK if that makes a difference). The Build Number is KTU84P.
Thanks,
Milo Pig
- you are in the wrong subforum. this is the Nexus 7 2012 section. you want to ask your request in the 2013 section here: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa
- if you don't get the file there here's a suggestion:
download the stock KTU84P 4.4.4 firmware for your Nexus 7 2013 (razor) from Google: https://developers.google.com/android/nexus/images
extract the files. inside you'll find the stock system.img file. get your N7 in bootloader mode, then flash the stock system.img
this will restore your system partition to stock and should allow you to take the OTA. you'll lose root but you're gonna lose that anyway when you update to Lollipop, and you can easily get it back afterwards.
I assume you know the steps needed for all this. if not you can look through the general or help sections of the 2013 subforum I'm sure there are guide threads there.
Hi guys,
I've seen this question asked a few times, but no one ever answers it. I tried looking around on other sites, but can't seem to find an answer.
I just came over from a Galaxy S5, and I don't think we ever used those. Is there anybody who'd be willing to point me in the direction of knowing?
It holds proprietary binaries for the Nexus 5x, 6p and 9, from what I've read.
Hey OP, did you find out what a vendor.img is yet? Have also come to Nexus from Samsung. Flashing my first rom, and don't know what this vendor file is. Or if I even need it. Like you, have found threads where people ask, but no definitive answers...
I've been curious about this, too.
Also wondering how the Vendor partition differs from System. What do the data/functions in the Vendor partition do?
EFS partition seems to be specific to the individual device (unique IMEI). Is Vendor specific to each phone too, or do all Nexus 6Ps have the same thing in the Vendor partition (assuming they're on the same build of Android)?
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
OK cool, so the vendor file is Nexus specific. And the OS won't operate properly without it? So I assume it's not possible to bake the vendor file straight into a custom rom? Just flashed pure nexus vendor.img along with the rom. Still not exactly sure what it does, but hey, if I need it, I'll flash it if I change roms.
Gorgtech said:
The vendor.img is important to this device if you upgrade your OS. You might have to flash it with every update too or your camera won´t work. This IMG is indeed strange if you´re used to older devices which are not as complicated.
Click to expand...
Click to collapse
Supplemental information about Vendor from a former member of the Android team
SlimSnoopOS said:
Supplemental information about Vendor from a former member of the Android team
Click to expand...
Click to collapse
Thanks for the link. So from my understanding, all the proprietary nexus files are stored on it's own 'vendor' partition, separate from the OS. And is updatable with it's own .img. Which is different to touchwiz (for eg.), which merges it's own files with android into the one partition.
Edit: FYI, just found this in PureNexus FAQ's:
Q: What is the vendor.img/vendor.zip? (5X and 6P only)
A: The vendor partition is new to Nexus phones with the 5X and 6P. Previous devices had the vendor files (proprietary binaries and drivers) within the system partition (/system/vendor); on these devices, they now have it in their own partition (/vendor). If this is not up to date, you will get an error message and need to flash the latest one so your phone continues to work properly. Beans has made this a TWRP flashable file available in the OP of the 5X and 6P threads (also linked below) so you do not have to fastboot it.
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
So, with this partition for drivers ROMs can keep the same camera quality as stock?
Llaver said:
I'm a bit late on this one, but does anyone know if updating OTA (stock android updater) updates the vendor partition as well or do you specifically have to flash it?
Click to expand...
Click to collapse
No, the vendor.img does not need to be flashed independently of the OTA update.
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
jameeldroid said:
I have seen it in many phones other than mentioned in the thread, it is even in infinix phones. what i think is it contains apps from google like maps, drive, gmail, photos, and also some apps from the manufacturer of the phone. why i think this is the case? here is the my guess.
yesterday when i tried to remove google bloatware and manufacturer bloatware with root permissions etc. it didn't work.
i have magisk root, i had set selinux permissive as someone told me it would help BUT i was still unable to remove bloatware. they were removed for now but whenever i rebooted my phone, they were reinstalled and i think this vendor file does that.
as per google's android documents here is the difinitoin.
vendor: The vendor partition contains any binary that is not distributable to the Android open source project.
means, google apps are never distributed with AOSP but manufacturers does that via vendor.img to make it non-removable? i guess.
Click to expand...
Click to collapse
????? This is a nexus, it contains no bloat because its a google device, its not a Motorola , lg, samjunk etc. Those devices contain "bloat" there are zero applications installed from the mfg, its stock android.
Not sure why you can't remove system apps, sounds like user error. I have never had an issue removing something with root and titanium backup.
The vendor contains what it says it does the binarys, blobs and other interworking's of the device that are needed for it to operate.
Hello. I'm a new to Android world. I have a Moto G4 (XT1622) and I install AOSiP-8.1-Derp-athene-20180501/Android Open Source Illusion Project ROM (arm64).
I see 'your vendor image does not match the system' message on every boot with a prompt to flash npjs25.93-14-13.
I download latest Nougat ROMs (arm32) (both adb and twrp flashable). Try both methods of flashing with success.
Then I install custom ROM again (with TWRP, clean) and see the same message again.
I search regarding this problem and everything ends with flashing Stock ROM and perform installing custom one again, what I done and mention of vendor.img file.
I try to find such file but no luck, my device has only vendor folder.
So my question is: how to remove this message in the custom ROM?
I post it here because ROM's thread is closed
Thanks.
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Read this first: http://forum.xda-developers.com/showpost.php?p=64399854
Then read this: http://forum.xda-developers.com/showpost.php?p=65102741&postcount=7741
The answers to your question are both in those links, which you should ALWAYS read. You'll thank me later for making you read those.
Danzilla79 said:
Hello everyone. So I'm brand new to not only xda but rooting and the likes all together. Yesterday I rooted my nexus 6p without issue and I will now list what I used. Twrp 3.0.0 -1-angler, BETA-SuperSU-v2.67-20160121175247. My phone build was MMB29P. then I flashed on pure_nexus_angler-6.0.1-20160315-CMTE and PureNexus_Dynamic_GApps_6.x.x_3-15-16.zip. Now my phone is saying its build MHC19J. I don't know if that is normal, but now I'm confused. When I boot up I get an Android System message saying " It appears your vendor image may be out of date. Please flash the latest vendor image for your device. " So followed the link to the vendor images and I see the list of vendor images however I don't see my build MHC19J.. or am I to get MMB29P? also once I do get it downloaded and load up twrp I see the option to click image and there's several boxes there to check/uncheck.. Do i just check vendor? So put as short as possible I need to know which vendor image i should get and how to flash it from twrp. Thanks for reading and your help will be greatly appreciated.
Also I almost forgot.. Will i need to flash a raido file or anything like that??
Click to expand...
Click to collapse
The vendor version you need is MHC19I which you can download following the link on the first post on the pure nexus ROM. Flash it via TWRP by hitting the flash img button and then selecting the vendor partition (duh). It's also good to make sure you are running the latest bootloader and radio (the bootloader should be on version 3.51 and the radio on 3.61).
Moved to:
https://forum.xda-developers.com/showthread.php?t=3609358
Hello
This is a place holder for the Device tree I'm about to submit for our device.
Currently, I'm in the middle of testing restore, but I totally did a cannibal install of 3.1.1 straight to my recovery partition, while I had Rootkernel 5.23 Boot.img TWRP 3.0.2 installed... and I had dual boot.
So I'm fairly confident, I have and can get the other versions of Android working for the E5823.
You all should just be able to pull the specific device branch, download the TWRP source, and then build using your prebuilt binary that Sony supplies, or use Flashtool to extract the ELF of the FOTA-Kernel.
I'll update this as the project progresses
Adios.
https://github.com/NeoBeum/XpeRicoverE5823
EDIT: Yep, just did a full restore. I will test encryption this week. I can go back and forth from the other boot image too. DRM Keys intact too, if you have your DK.ftf.
I'll get it working with Rootkernel & Magisk next.
Test Passed:
Complete Backup & Restore
Restore TA Partition to revert lost DRM Keys on Bootloader Unlock
Current issues:
Install from Zip/Image Permissions - 16/5/2017
Enlighten me please, what is this? Source code for recovery or rom?
MakeHav0 said:
Enlighten me please, what is this? Source code for recovery or rom?
Click to expand...
Click to collapse
TWRP Recovery Source for vanilla Sony AOSP. So no need for CM or Omnirom.
Team Win says they should be able to review the build in about a fortnight