Related
Hi all,
Finally received my nexus 4 after suuuch a long wait.
I went the nexus root as I'd really like to learn all the ins and outs of android. I'm working as a web dev now (nothing with java).
This is my first android device and I will soon want to unlock, root and try manually amend system files.
I have some questions though:
1. Can I unlock the phone through the terminal manually and without toolkit? I want to do everything myself.
2. Are there any tutorials on manually rooting a nexus 4 (I saw a gnex). I don't want to use a tool kit for now.
3. I'd like to try start amending (very basic) some System files. Will it be easy to transfer over the code when updates come?
Thanks!
Check the sticky in the general forum. Great stuff by efrant. http://forum.xda-developers.com/showthread.php?t=2010312
nm3th said:
Check the sticky in the general forum. Great stuff by efrant. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Thanks for the link but I have already read that. What I want to do is manually perform the tasks he mentions. When he says to download a toolkit , I want to skip that and manually do what the toolkit does to have a better understanding of the OS.
Did you actually read it? He gives a step by step from unlocking the bootloader, to installing the drivers needed to run adb/fastboot, root, etc. No toolkit; exactly what you're asking for.
nm3th said:
Did you actually read it?
Click to expand...
Click to collapse
Yes I have. I guess I must of misunderstood what platform tools are.
Why do I need those? The android development bridge cannot work without that?
Platform-tools-v16 contains the files needed to run adb and fastboot. Adb (android debug bridge) allows you to communicate with your device from your pc. Fastboot allows you to update the flash file system. You will need this if you don't already have the sdk installed. Just follow the instructions and it'll be a good learning experience. Good luck.
**edit** I'm not on my system with the sdk, so I can't check, but I don't think fastboot is included with the sdk anymore, only adb is.
monkeying. around said:
Hi all,
Finally received my nexus 4 after suuuch a long wait.
I went the nexus root as I'd really like to learn all the ins and outs of android. I'm working as a web dev now (nothing with java).
This is my first android device and I will soon want to unlock, root and try manually amend system files.
I have some questions though:
1. Can I unlock the phone through the terminal manually and without toolkit? I want to do everything myself.
2. Are there any tutorials on manually rooting a nexus 4 (I saw a gnex). I don't want to use a tool kit for now.
3. I'd like to try start amending (very basic) some System files. Will it be easy to transfer over the code when updates come?
Thanks!
Click to expand...
Click to collapse
its the same as on the gnex, exactly. its the same on all nexus devices. fastboot oem unlock, fastboot a custom recovery, flash either a custom rom or the su binaries in that new recovery, then reboot and profit
nm3th said:
You will need this if you don't already have the sdk installed. Just follow the instructions and it'll be a good learning experience. Good luck.
Click to expand...
Click to collapse
OK thanks that clears another point up. I'm not really after learning how to flash etc but more about the OS as a whole. Would also like to slowly attempt to amend some changes in the system files but I'll go ahead and do that guide.
simms22 said:
its the same as on the gnex, exactly. its the same on all nexus devices. fastboot oem unlock, fastboot a custom recovery, flash either a custom rom or the su binaries in that new recovery, then reboot and profit
Click to expand...
Click to collapse
OK thanks will try tackle it this weekend.
Can you guys answe my other question? What about people who amend the files how so they go about updating the system where. Updates are released?
monkeying. around said:
Can you guys answe my other question? What about people who amend the files how so they go about updating the system where. Updates are released?
Click to expand...
Click to collapse
Make a backup of whatever file you are modifying and when there is an update, revert back to the old file and you should be able to flash the OTA. Or just flash the stock image using the instructions from my first reply, then flash the OTA.
Androidrootz.com has tutorials for manual or tool kits rooting via windows or Mac. I did the Mac version and it was a piece of cake and I am no pc expert. They have info for unrooting and flashing clockwork mod recovery.
Good luck,
Ian B
nm3th said:
Make a backup of whatever file you are modifying and when there is an update, revert back to the old file and you should be able to flash the OTA. Or just flash the stock image using the instructions from my first reply, then flash the OTA.
Click to expand...
Click to collapse
Ok that should sort out the updating but after updated what do I do with the backup/modified file. I will have to remodify everything again correct?
Mr Ian B said:
Androidrootz.com has tutorials for manual or tool kits rooting via windows or Mac. I did the Mac version and it was a piece of cake and I am no pc expert. They have info for unrooting and flashing clockwork mod recovery.
Good luck,
Ian B
Click to expand...
Click to collapse
Thanks I saw this tutorial and video although I found a better one. Like I said before I thought this was the plug n
Play version. Any will root the traditional way I guess.
there's another guide in this forum, maybe you like that one
http://forum.xda-developers.com/showthread.php?t=2018179
OK guys just backed up all my data to my computer. I've downloaded the platform tools but there seems to be a contradiction here.
Do I have to download the .IMG file that is 300+ mb?
cause some tutorials say I don't.
The IMG file is for just in case you goof up and need to get your phone back up and running.
nm3th said:
The IMG file is for just in case you goof up and need to get your phone back up and running.
Click to expand...
Click to collapse
OK thanks. Now I get it.
Regarding the updates, if I am unlocked and have root access with no other changes, I can successfully install the update correct?
Only thing I will lose is root access?
What will happen if I do a factory data reset on a unlocked + rooted device?
monkeying. around said:
What will happen if I do a factory data reset on a unlocked + rooted device?
Click to expand...
Click to collapse
You lose installed apps and data but maintain root
Sent from my Nexus 4 using Tapatalk 2
What about if I've flashed cwm recovery? To the boot loader. Would that get overwritten
Or is that not affected since its in the bootloader...before you get to the os.
monkeying. around said:
What about if I've flashed cwm recovery? To the boot loader. Would that get overwritten
Or is that not affected since its in the bootloader...before you get to the os.
Click to expand...
Click to collapse
It will not erase that as you said unless you flash back to the stock recovery image as the boot and recovery is separate. You can wipe data and reflash all day long if you want.
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
you will need to unlock to flash custom zip, but u can relock after
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
playya said:
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
Click to expand...
Click to collapse
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
gjjh25 said:
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
Click to expand...
Click to collapse
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
playya said:
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
Click to expand...
Click to collapse
Thanks, what do you recommend for the easiest way to unlock and root then?
gjjh25 said:
Thanks, what do you recommend for the easiest way to unlock and root then?
Click to expand...
Click to collapse
I used a toolkit but honestly you can unlock manually by just booting into bootloader mode. Go into development and try Wugs Toolkit.... Rooting the phone is easy and all methods are relatively the same.
I do not see anything wrong with giving CM a try as well
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
I recommend you to stick to your original plan, its your phone, do what you like, you don't need to flash custom roms if you don't want to. I am using stock kernel and stock KitKat right now and the performance is excellent.
Follow these instructions to unlock bootloader, install latest kitkat factory image, install custom TWRP recovery, and root. http://forum.xda-developers.com/showthread.php?t=2010312
The links to fastboot package and driver required is in my signature.
Link to download factory image: https://developers.google.com/android/nexus/images
Link for latest TWRP: TWRP recovery
Link for latest SuperSU package: SuperSU package
After you do all that, in bootloader menu, you can flash back the stock recovery (recovery.img), which is location in the "image-occam-******.zip" of the factory image. (fastboot flash recovery recovery.img)
Then lock your bootloader by "fastboot oem lock". You can also use BootUnlocker to lock and unlock your bootloader on the fly while in the phone, without losing your data, since everytime you do fastboot oem unlock, it will wipe the entire device.
By using stock rom, stock recovery, stock kernel and temporarily unroot (SuperSU) or hide root (SuperSU paid version), it allows you to receive future OTA updates from Google. If you want to modify your phones more while staying with stock, read up on Xposed Framework and its module Gravity Box, which is not yet compatible with Android 4.4 but will be eventually.
Just remember if you don't have custom recovery, once something goes wrong and your phone can't boot, its very hard to save the data inside. Once you have custom recovery like TWRP, you can make a backup of your stock image (which also backup your stock kernel) and try out other custom roms and easily go back to stock, then you can flash stock recovery again to receive OTA updates.
Thanks for advice everyone.
I rooted and unlocked with Wugfresh over the weekend. A lot easier than I thought it would be
Hey XDA,
My Nexus ha been a dream. Though I've hit a few bumps, I don't expect to waste money on other flagships again.
I don't need to be able to right this instant, but wiping cache is one of my regular troubleshooting tools. Upon troubleshooting an MMS issue I was having, I discovered my recovery wasn't working properly. Though I fixed the MMS issue by resetting APN settings, the recovery thing has been bothering me.
I am running stock and locked. I have done nothing to this phone to warrant it being my fault. The problem is simple (and a Google search indicated, common). When you get to Recovery, you get a droid on its back, a red exclamation mark and "NO COMMAND". Doesn't matter if you hold up and power, tap up, or get there from the bootloader. The recovery software is seemingly missing completely.
I have an extended warranty through the retailer I bought from, but the phone is otherwise fine, so this is a last resort.
My dilemma is that I want to use Android pay. My understanding is that even unlocking the bootloader breaks Android pay. Is this correct? If so, can one reliably reset the phones security trips to allow Android pay after flashing the recovery back on?
Thanks for the help.
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
celsian said:
No, unlocking the boot loader does not block Android Pay.
There is a systemless root method for the Nexus that allows you to use Android Pay while rooted, there are also a couple of ROMS that have it working currently as well.
Click to expand...
Click to collapse
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Does this mean that I can't flash at least a stock recovery?
Download your system image, unzip it, unlock your bootloader and flash only the recovery.IMG in fastboot, then relock your bootloader again. Android Pay will work fine and your warranty won't be affected so long as you relock your bootloader
Arcaed said:
Does this mean that I can't flash at least a stock recovery?
Click to expand...
Click to collapse
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
The Stig 04 said:
Sorry, but are you saying if I wanted to install twrp I would need a modified stock boot img?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Yes. Myself I would flash full image and start over fresh. But you can go with just recovery if you want. Also do not forget to check allow oem unlock in dev settings before attempting to unlock. If you want twrp you will need modified stock boot image with DM verity removed. Or else it won't boot. I can link you to one from the newest image if you'd like. But if you only want stock recovery you don't need anything other than stock Google image.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
In that case, where do I get a full system flash?
Arcaed said:
In that case, where do I get a full system flash?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Sent from my Nexus 6P using Tapatalk
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
You beat me to it with #3. Unfortunately I'm at work and couldn't come back to this thread quickly enough.
toknitup420 said:
Android pay already patched systemless root. If you want Android pay don't root. You can unlock though. That will not affect Android pay.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Arcaed said:
Quite so? Can you provide links to the root method and mayhaps the roms? Does this mean I could slap TWRP on here with no consequence?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65188325
Heisenberg said:
There are quite a few errors in the information given in this thread.
1. Unlocking the bootloader does not break Android Pay.
2. Android Pay has been patched so you can't have root with Android Pay, even systemless.
3. TWRP recovery does not require a modified boot.img.
4. Flashing any recovery (Stock or TWRP) will not affect Android Pay at all.
If you need directions on unlocking or flashing check my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
I've always been under the impression that the device will not boot with twrp installed unless you have DM verity checks removed. Has something changed with that.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It isn't necessary. I'm on my eighth Nexus 6P and I haven't flashed any modified boot.img prior to flashing TWRP.
83097markcynt said:
Actually AP now works with systemless root again. I have AP working (yes actually making purchases), currently running the latest Chroma Rom with Supersu 2.61
Found the workaround in this thread.
I'm sure Google will patch it again though.
Click to expand...
Click to collapse
I can second this. I have systemless root, and AP working, confirmed with purchases. Just a note, if you can successfully add a card, that means it has to contact your bank for approval, therefore it should confirm AP is working.
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg said:
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.[/b]
Click to expand...
Click to collapse
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
tsuttie99 said:
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
Click to expand...
Click to collapse
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Heisenberg said:
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Click to expand...
Click to collapse
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
tsuttie99 said:
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
Click to expand...
Click to collapse
Well, welcome to XDA then! Here's the thread in case you need it:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
EvanVanVan said:
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
Click to expand...
Click to collapse
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
+1 Flashfire
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
EvanVanVan said:
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
Click to expand...
Click to collapse
The other issue with TWRP was backing up and restoring the EFS partition, it seemed that 3.0.2-1 corrupted it on restore which would be a problem. They did have a work around. They suggested using -0 would be fine. I have -2 and did a N to N restore with no issue, but I did not restore EFS. I'm always extra careful with new versions, I tend to backup my data and backups off-phone just in case.
dratsablive said:
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
Click to expand...
Click to collapse
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
smallvan said:
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
Click to expand...
Click to collapse
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
dratsablive said:
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
Click to expand...
Click to collapse
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
smallvan said:
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
Click to expand...
Click to collapse
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
dratsablive said:
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
Click to expand...
Click to collapse
I believe I am looking for a suitable way to upgrade my 6p from MM to N that I have explicitly stated at my wrong thread post. This is absolutely not my intention to return my 6p back to stock of MM. And there is every reason to upgrade to N, thus, vendor.img is no doubt a must for an amateur like me.
Nevertheless, thanks for dratsablive kind suggestions.