/Vendor - Nexus 6P Q&A, Help & Troubleshooting

OK guys. Before you bite my head off, I'm an experienced ROM flasher and a junior ROM developer....I've been rooting every phone/tablet I get, I know how to use adb/fastboot and even made a personal stock ROM....like I said....junior not an expert lol....I currently have a nexus 5,6,7(2013). Now, I will be getting my new nexus 6p gold 32gig tomorrow (Tuesday). I have read about the new /vendor partition. Since I ha e never had to deal with that, I need your help. Any info about it before I root it tomorrow would be much appreciated!!!

From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.

dl200010 said:
From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.
Click to expand...
Click to collapse
So, flashing ROMs and such....I don't have to mess with vendor?

Just if there is a newer version out. I think now u can flash the vendor. Img via twrp 3.0 if I'm not wrong

jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).

Heisenberg said:
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).
Click to expand...
Click to collapse
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet

pa.pn2 said:
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet
Click to expand...
Click to collapse
From what I've seen posted, yes. I haven't tried it myself though.

Heisenberg said:
From what I've seen posted, yes. I haven't tried it myself though.
Click to expand...
Click to collapse
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)

jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Only time I flash the vendor is when updating to the latest of the ROM I use. Also going to the latest vendor factory img from google in the process. And like the other guy said when going from a layers ROM to anything else.

mocsab said:
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)
Click to expand...
Click to collapse
Yes that's right.

as of 3.0.0-0 you can flash vendor and system images in twrp

Related

[Q] Simple CM based ROM?

Can anyone recommend a basic CM based ROM that has the Google Apps installed already?
Thanks
What do you mean by Simple CM based ROM? Why not just use CM?
Also it'll be tough to find a rom with gapps included as they are not a part of AOSP, and are proprietary apps so you're technically not allowed to include them in a rom. Whats wrong with flashing a seperate gapps package?
Chromium_ said:
What do you mean by Simple CM based ROM? Why not just use CM?
Also it'll be tough to find a rom with gapps included as they are not a part of AOSP, and are proprietary apps so you're technically not allowed to include them in a rom. Whats wrong with flashing a seperate gapps package?
Click to expand...
Click to collapse
Ah OK. I guess things have moved on since I was last flashing on my HTC Sensation... all the ROMs I used back then had GApps baked in.
jomtones said:
Ah OK. I guess things have moved on since I was last flashing on my HTC Sensation... all the ROMs I used back then had GApps baked in.
Click to expand...
Click to collapse
no gapps in any nexus roms except stock based. yes, any kind of nexus. in other devices there could be, but nexus devices dont need any hacking, and developers generally follow the rules. where hacking is needed to get roms running, most developers dont follow rules, hense hacking.
simms22 said:
no gapps in any nexus roms except stock based. yes, any kind of nexus. in other devices there could be, but nexus devices dont need any hacking, and developers generally follow the rules. where hacking is needed to get roms running, most developers dont follow rules, hense hacking.
Click to expand...
Click to collapse
OK, understood. So rooting these devices is easier? There's no firmware arms race going on?
jomtones said:
OK, understood. So rooting these devices is easier? There's no firmware arms race going on?
Click to expand...
Click to collapse
Of course. Rooting a nexus is not some sort of hack fest.
Its a simple process that makes sense, and is quite easy to understand. You just unlock the bootloader (fastboot oem unlock), flash a custom recovery (fastboot flash recovery recovery.img), and from there you can basically do whatever you want. Flash a custom rom (that is pre rooted), or simply flash a supersu binary zip that will root your stock rom.
Its a nice clean process. No using bootleg third party crap or anything like that...all official Google stuff like fastboot and adb.
jomtones said:
OK, understood. So rooting these devices is easier? There's no firmware arms race going on?
Click to expand...
Click to collapse
rooting any nexus device in a nutshell..
1. via fastboot.. fastboot oem devices(a code that google enabled to unlock the bootloader).
2. fastboot flash a custom recovery.
3. flash either the su binaries or any custom rom via your new custom recovery.
4. reboot and profit.
yes, its that easy. and these directions work on any nexus device. no firmware arms races going on.
---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------
Chromium_ said:
Of course. Rooting a nexus is not some sort of hack fest.
Its a simple process that makes sense, and is quite easy to understand. You just unlock the bootloader (fastboot oem unlock), flash a custom recovery (fastboot flash recovery recovery.img), and from there you can basically do whatever you want. Flash a custom rom (that is pre rooted), or simply flash a supersu binary zip that will root your stock rom.
Its a nice clean process. No using bootleg third party crap or anything like that...all official Google stuff like fastboot and adb.
Click to expand...
Click to collapse
damn, i must be getting old! you beat me to it
simms22 said:
damn, i must be getting old! you beat me to it
Click to expand...
Click to collapse
Haha, by a few seconds
Hah, thanks guys. Rooted using a toolkit so I wasn't aware how simple it was. Why don't they just supply the phones unlocked?
jomtones said:
Hah, thanks guys. Rooted using a toolkit so I wasn't aware how simple it was. Why don't they just supply the phones unlocked?
Click to expand...
Click to collapse
Shouldnt have used a toolkit. Supplying them unlocked would be a big security issue.
Chromium_ said:
Shouldnt have used a toolkit. Supplying them unlocked would be a big security issue.
Click to expand...
Click to collapse
Ah - cos when you root it wipes device?

[FIRMWARE][WIP] OnePlus X Firmware

Disclaimer:
Your warranty may be void
I by no means take responsibility if you brick your device. I have not tested my methodology nor am I sure of the firmware differences between releases.
I noticed that when flashing Oxygen 2.2.0 new firmware was released. Some people may have need for it if they are on a custom ROM and don't feel like flashing stock and then restoring from a backup.
THIS IS NOT FLASHABLE!!!
INSTALLATION
1. Extract the archive
2. Copy the firmware folder to the highest directory (/)
3. Replace the files
4. Reboot
5. Pray
Immediate feedback is appreciated from those still using the firmware from older versions. Uploading firmware from previous versions is appreciated as well. In the future I will try to make a flashable image.
Download:
https://drive.google.com/file/d/0B7CLqaEGT92ATWVBbllvakh5eHM/view?usp=docslist_api
Reserved
I don't know what are you trying to do, confused.
http://forum.xda-developers.com/oneplus-x/general/rom-mirrors-official-oxygen-os-rom-ota-t3301797
ChavitoArg said:
I don't know what are you trying to do, confused.
http://forum.xda-developers.com/oneplus-x/general/rom-mirrors-official-oxygen-os-rom-ota-t3301797
Click to expand...
Click to collapse
I'm providing new firmware in place of the entire ROM. People may not want to download the entire ROM.
RJDTWO said:
I'm providing new firmware in place of the entire ROM. People may not want to download the entire ROM.
Click to expand...
Click to collapse
What do you mean with firmware? Isn't the ROM the firmware?
sydeu said:
What do you mean with firmware? Isn't the ROM the firmware?
Click to expand...
Click to collapse
Firmware is the basis from where hardware can interact with software. The entire ROM isn't in and of itself firmware as it includes an operating system (in the case of Oxygen, Android). Essentially I'm providing the libraries from /firmware which are specific to the device itself.
RJDTWO said:
Firmware is the basis from where hardware can interact with software. The entire ROM isn't in and of itself firmware as it includes an operating system (in the case of Oxygen, Android). Essentially I'm providing the libraries from /firmware which are specific to the device itself.
Click to expand...
Click to collapse
Is this useful if you are on cm12.1 /cm13?
sydeu said:
Is this useful if you are on cm12.1 /cm13?
Click to expand...
Click to collapse
That's the thing; I'm not entirely sure. I believe the only updated binaries were for the the camera. If you've flashed 2.2.0 you should already have them. I wouldn't attempt it unless you're familiar with fastboot and reflashing the stock ROM as a whole that way. It should help with the camera, but no guarantees.
RJDTWO said:
That's the thing; I'm not entirely sure. I believe the only updated binaries were for the the camera. If you've flashed 2.2.0 you should already have them. I wouldn't attempt it unless you're familiar with fastboot and reflashing the stock ROM as a whole that way. It should help with the camera, but no guarantees.
Click to expand...
Click to collapse
Haven't flashed 2.2.0. Doesn't have access to my pc for 10 days so I'll have to wait u til then before I play around too much.
I think cm has updated with the oos 2.2.0 things though.
sydeu said:
Haven't flashed 2.2.0. Doesn't have access to my pc for 10 days so I'll have to wait u til then before I play around too much.
I think cm has updated with the oos 2.2.0 things though.
Click to expand...
Click to collapse
Good to know. So in short, don't attempt this unless your ROM has yet to include it.
I did just test it though and it works. There's a definitive difference between the camera firmware used
...and that was on CM 13

Int'l ROMs?

I found a *****en ROM named Nameless in the f/g variants of the Note 4. Was all psyched to flash it and play with it only to realize there's data issues. Is there any body who knows how to fix the data issue or maybe properly port this to our device?
http://forum.xda-developers.com/showthread.php?t=3220738 there ya be sir
Sent from my SM-N910W8 using Tapatalk
kkeith said:
http://forum.xda-developers.com/showthread.php?t=3220738 there ya be sir
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
I tried that and was unable to get it to get data. It really stumped me
Edit: Oh damn. I realized I flashed the wrong kernel and tried again. after flashing the data fix I got data for a second before the phone rebooted. I wiped everything but data when I flashed from my stock rom
Naturesretard said:
I tried that and was unable to get it to get data. It really stumped me
Edit: Oh damn. I realized I flashed the wrong kernel and tried again. after flashing the data fix I got data for a second before the phone rebooted. I wiped everything but data when I flashed from my stock rom
Click to expand...
Click to collapse
I have managed to get the rom up and running.....for the most part. Only downside so far is I can't get Netflix to work. It just loads forever
Naturesretard said:
I have managed to get the rom up and running.....for the most part. Only downside so far is I can't get Netflix to work. It just loads forever
Click to expand...
Click to collapse
Google will be your friend on that one, i cant remember off the top of my head but there is a file you need to delete
Sent from my SM-N910W8 using Tapatalk
kkeith said:
Google will be your friend on that one, i cant remember off the top of my head but there is a file you need to delete
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
T_T I'm not sure of what to search for. For branded roms it's relatively easy, but as an INT'L ROM I'm not sure if my process would work. So it's just some obscure file? I was thinking it may be because I flashed something wrong. No chance you can remember where you think you may have seen it? Like xda or another site?
Naturesretard said:
T_T I'm not sure of what to search for. For branded roms it's relatively easy, but as an INT'L ROM I'm not sure if my process would work. So it's just some obscure file? I was thinking it may be because I flashed something wrong. No chance you can remember where you think you may have seen it? Like xda or another site?
Click to expand...
Click to collapse
I went back to the beanstalk forum and just so happened across the fix just now haha
Go to system/vendor/lib and delete liboemcrypto.so and reboot
Sent from my SM-N910W8 using Tapatalk
kkeith said:
I went back to the beanstalk forum and just so happened across the fix just now haha
Go to system/vendor/lib and delete liboemcrypto.so and reboot
Sent from my SM-N910W8 using Tapatalk
Click to expand...
Click to collapse
OMG You're a lifesaver. It worked! Thanks!
Now to create some more threads or posts in the Nameless ROM section; Upon reflashing my backup to perform this fix, I now have random system information on my lockscreen and notification bar. Oh well.
Thanks again!
Naturesretard said:
OMG You're a lifesaver. It worked! Thanks!
Now to create some more threads or posts in the Nameless ROM section; Upon reflashing my backup to perform this fix, I now have random system information on my lockscreen and notification bar. Oh well.
Thanks again!
Click to expand...
Click to collapse
I have been trying my hardest, asking on every forum i can find, to find out how to get the beta release of emotion kernel R24 for N910T. Not one single response.....but anyway. It is my understanding that the latest release of Emotion Revolution rom has r24 kernel as an option in aroma. My question is this; would it be possible to unzip the R23 kernel zip for N910T and replace only the R24 boot image from the emotion rom and leave all the other system files. Or would that be a really bad idea? Ha. I just want the kernel on Tekhds URv7. I know this is possible a really stupid question but I'm just now beginning to learn all the technical details of these things. And I will say ahead of time that any answer will be beneficial because I don't know much about how a N910T kernel differs from international as far as data is concerned or what the fix actually fixes when you flash it. But if it has any relwvance my phone is carrier unlocked and i dont even use tmobile. My goal is to learn something new everyday without hard bricking my baby like I did my N900A. I'm not by any means new to rooting but am very new to having a device that I can actually play with. Thanks in advance and us noobies appreciate everybodys patience.

TWRP Sources

Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
user7743 said:
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
Click to expand...
Click to collapse
Use whichever you like, both work
Just be careful about the version, versions lower than 3.1.0 are dangerous and backing up stuff can wreck your phone
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
user7743 said:
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
Click to expand...
Click to collapse
Maybe it is a mirror... can't test but you could compare md5
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
user7743 said:
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
Click to expand...
Click to collapse
well there are more than one TWRP versions out there it seems. For example when you flash the universal bootloader TWRP displays 3.1.0-N while on stock 7.1 it shows 3 1.0-0
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
fastjohnson said:
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
Click to expand...
Click to collapse
The problem I think is data partition.
Every time I swich rom to oficial I have to format data, wipe dont work. Maybe before restore format data in f2fs or ext4 for oficial rom
Enviado desde mi ZTE A2017G mediante Tapatalk
May sound strange but it was because I flashed the ROM and gapps from my USB c style flash drive so I just decided to do the phone over fresh. It's working 100% all fresh install. Thanks for your help but no matter what I did it wasn't going to install those restores.

How to flash to another custom kernel.

I'm using a custom kernel on my rooted device and want to try out another. Do I need to flash back to the stock kernel before flashing to the other kernel or I can just flash it on top of my custom kernel?
If I have to flash back to stock kernel is there a place I could download the stock kernel?
Using EXKM and rom is 10.5.8.IN11AA
Sorry for the noob question I am completely new to this.
Although you can get by prolly by flashing another, I've always gone by flashing stock, and THEN the new kernel, and what I recommend. Believe others would do. As far as the stock kernel, I wanna say there's a thread somewhere that has them posted, but you may have to search.
Truant_Luce said:
Although you can get by prolly by flashing another, I've always gone by flashing stock, and THEN the new kernel, and what I recommend. Believe others would do. As far as the stock kernel, I wanna say there's a thread somewhere that has them posted, but you may have to search.
Click to expand...
Click to collapse
I did try to search but I read a lot of people try to extract it from the stock rom or something like that. I'm not sure how to do that though.
If somebody could post a link on the stock kernel file that would be great
matchankh said:
I did try to search but I read a lot of people try to extract it from the stock rom or something like that. I'm not sure how to do that though.
If somebody could post a link on the stock kernel file that would be great
Click to expand...
Click to collapse
Go here, download the 10.5.8 2023 BA variant for your device, confirm hash. Go to settings, syatem updates, cog wheel, local upgrade, select package. I THINK it'll let you flash it like an upgrade, but don't quote me, I am not to familiar with the device yet, or oneplus in general. Just flash magisk to other boot slot after if it says your device will no longer be rooted stuff, you know. The typical.
I'ma go to bed, but if that doesn't work, you can see about opening the .zip up, extract the payload and search google for a method that'll extract the kernel for you. Best of luck.
Oh, and in case it wasn't reiterated, back up persist partition too. Just in case, always. In case it wasn't obvious.
Truant_Luce said:
Go here, download the 10.5.8 2023 BA variant for your device, confirm hash. Go to settings, syatem updates, cog wheel, local upgrade, select package. I THINK it'll let you flash it like an upgrade, but don't quote me, I am not to familiar with the device yet, or oneplus in general. Just flash magisk to other boot slot after if it says your device will no longer be rooted stuff, you know. The typical.
I'ma go to bed, but if that doesn't work, you can see about opening the .zip up, extract the payload and search google for a method that'll extract the kernel for you. Best of luck.
Oh, and in case it wasn't reiterated, back up persist partition too. Just in case, always. In case it wasn't obvious.
Click to expand...
Click to collapse
Is there a specific reason that I would flash to BA not AA?
So I would lose root and have to reinstall magisk is that correct?
PS I also have nolimit rom installed.
matchankh said:
I did try to search but I read a lot of people try to extract it from the stock rom or something like that. I'm not sure how to do that though.
If somebody could post a link on the stock kernel file that would be great
Click to expand...
Click to collapse
matchankh said:
Is there a specific reason that I would flash to BA not AA?
So I would lose root and have to reinstall magisk is that correct?
PS I also have nolimit rom installed.
Click to expand...
Click to collapse
My apologies, I thought I saw you said IN11BA, not IN11AA. Do the AA. Caught me right before I fell asleep. But putting phone on charger. Good night.
---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------
matchankh said:
Is there a specific reason that I would flash to BA not AA?
So I would lose root and have to reinstall magisk is that correct?
PS I also have nolimit rom installed.
Click to expand...
Click to collapse
And magisk.... Open magisk up and flash to other slot after you do the system update. Tada. Recommended to disable modules first.
Truant_Luce said:
My apologies, I thought I saw you said IN11BA, not IN11AA. Do the AA. Caught me right before I fell asleep. But putting phone on charger. Good night.
---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------
And magisk.... Open magisk up and flash to other slot after you do the system update. Tada. Recommended to disable modules first.
Click to expand...
Click to collapse
If mine is the Chinese version which was flashed to global rom, will it be stuck in bootloop again if I update it from OTA again?
It was stuck the first time round and I had to wipe cache and setting.
matchankh said:
Is there a specific reason that I would flash to BA not AA?
So I would lose root and have to reinstall magisk is that correct?
PS I also have nolimit rom installed.
Click to expand...
Click to collapse
matchankh said:
If mine is the Chinese version which was flashed to global rom, will it be stuck in bootloop again if I update it from OTA again?
It was stuck the first time round and I had to wipe cache and setting.
Click to expand...
Click to collapse
It SHOULDN'T but I also provide no guarantee, as not specifically certain. But I do highly doubt it would be stuck in bootloop again, it's just the first time around.
Truant_Luce said:
It SHOULDN'T but I also provide no guarantee, as not specifically certain. But I do highly doubt it would be stuck in bootloop again, it's just the first time around.
Click to expand...
Click to collapse
Ok I'll give it shot. Really appreciate your help!
Btw do you have any kernel you recommend for battery life.Using ElementalX at the moment but don't see much difference between stock.
matchankh said:
Ok I'll give it shot. Really appreciate your help!
Btw do you have any kernel you recommend for battery life.Using ElementalX at the moment but don't see much difference between stock.
Click to expand...
Click to collapse
Using elementalX myself atm. Although I'm always interested in what others bring, too.
matchankh said:
Ok I'll give it shot. Really appreciate your help!
Btw do you have any kernel you recommend for battery life.Using ElementalX at the moment but don't see much difference between stock.
Click to expand...
Click to collapse
Omega

Categories

Resources