Hi all! I am sorry if this has been asked before but I couldn't find a definitive answer in here.
I bought OnePlus 8 Pro from the official website in April and I feel it's time to flash a custom kernel. I've been modding my phones since 2011 using Xperia Neo back then.
1. If I unlock my bootloader will I still be able to receive official updates?
2. How exactly do you flash a custom kernel? At the moment I have no intentions on rooting the phone.
3. Is the procedure for flashing a custom ROM the same as the kernel?
4. Does unlocking my bootloader delete everything from the phone?
A lot has changed since Android 8 and 9 so I feel like a complete noob.
Thank you for the help in advance!
1. Yes as long as your boot partition is stock/aka not rooted or using custom kernel, you can take regular otas.
2. If rooted you can use ex kernel manager... If not you'd boot to bootloader and use fastboot commands to modify the boot image.. Note after this you wouldn't be able to take otas until you flash back stock boot img.
3. Yes very similar, you'd flash different partitions in bootloader using fastboot commands.
4. Yes, same as relocking.
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Lossyx said:
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Click to expand...
Click to collapse
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
kokope28 said:
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
Click to expand...
Click to collapse
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Lossyx said:
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Click to expand...
Click to collapse
I haven't tried a lot of kernels but in my experience coming from other phones like pixels.... When boot.img gets modified it will fail ota updates...I tried it with this phone with a rooted boot.img and it failed so I assumed a kernel modified boot.img would be the same. Much apologies if I'm incorrect... But that's my reasoning for writing my post.
Updating isn't an issue.
My guide for doing just that amongst other things.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Personal I use ex kernel manager. Hasn't failed me yet.
Auth apps have worked for me, as does gpay so you should be ok.
Titanium / swift might do it but the OS won't be the same so the apps could notice that.
Just set them back up, the more you do it the easier it is.
Probably best to deactivate first so it's easier to enrol on your new OS
Related
Successfully installed twrp, now I am just curious: must any rom we flash be loki'd to work? not really an issue but wanna know my limits... we arent gonna be ablec o just flash canadian roms then, right? (until they are loki'd)
t2abousa said:
Successfully installed twrp, now I am just curious: must any rom we flash be loki'd to work? not really an issue but wanna know my limits... we arent gonna be ablec o just flash canadian roms then, right? (until they are loki'd)
Click to expand...
Click to collapse
This is going to become a huge problem if people don't start reading about what it is they are doing to their phones...
http://forum.xda-developers.com/showthread.php?t=2292157
"I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
"
scott14719 said:
This is going to become a huge problem if people don't start reading about what it is they are doing to their phones...
http://forum.xda-developers.com/showthread.php?t=2292157
"I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
"
Click to expand...
Click to collapse
As always a good answer from the king.
Hello guys, I tried to flash Dirty Unicorns ROM
I have a brand new nexus 6p
At first I went through this tutorial:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
First stuck was when I tried fastboot devices in cmd, those USB drivers from sdk manager didn't seem to work, so I downloaded some other driver, which seemed to work
Now I am stuck here:
How To Install A Custom Recovery On Your Device
fastboot flash recovery <filename>.img
So in my CMD I did this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16932 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.827s
and after fastboot reboot, the device is still the same, still the same bootloader, when I hit "recovery mode", there is just the green android robot lying on his back with red ! and after a while the device just starts like normal
also when I start I see "your device software cant be checked for corruption. Please lock the bootloader......" etc and Google logo with unlocked lock in the bottom, but I guess it's normal
any advice please?
solved, /thread
bejek said:
solved, /thread
Click to expand...
Click to collapse
Please post how you solved your issue so it's here for someone searching for an answer in future.
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
bejek said:
well I found some other guide how to unlock, flash twrp, root etc...
in this guide there is completely missing one step, where you must download some modified boot image and flash it before flashing twrp
so after I performed this:
fastboot flash boot boot.img
I was able to flash twrp recovery...
Click to expand...
Click to collapse
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Heisenberg said:
You don't need a modified boot.img for TWRP unless:
A) You're running extremely old firmware
B) You've flashed an extremely old version of TWRP
C) You're running Android N
What version of TWRP did you flash? Were you previously using Android N?
Click to expand...
Click to collapse
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Jammol said:
You did enable OEM Unlock under developer options right? That's very odd you found a guide that said to flash a modified boot.img. Can you post a link to the guide?
Click to expand...
Click to collapse
Ofc I did.
I am not sure where did I see it for the first time, but this step was definitely in more guides than just this one.
for example here:
https://devs-lab.com/root-install-twrp-in-nexus-6p.html
and this is the step I am talking about:
Prerequisites:
Unlocked Nexus 6P bootloader.
ADB USB Drivers
Minimal ADB Package
TWRP Recovery: Nexus 6P.
SuperSU (For Root): Download.
Modified Boot.img: Download.
Installing TWRP Recovery in Nexus 6P:
1. Launch command.bat file & type:
fastboot flash boot boot.img
bejek said:
Hello Heisenberg,
it was a brand new Nexus 6p, just put out of the box.
I believe there was some stock Android 6.0.0 installed.
I tried to flash TWRP 3.0.2 obviously.
I still wanna thank you for your awesome guide, but without this step with flashing some modified boot.img first I really wasn't able to flash TWRP...
Click to expand...
Click to collapse
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Heisenberg said:
A modified boot.img hasn't been required for quite some time, and still isn't required. I can see from the link you gave that the modified boot.img is for MDB08K, which is a very old build. This means that guide, and any guide that instructs you to flash a modified boot.img, is outdated unless you're on quite an old build. What build are you actually on?
Click to expand...
Click to collapse
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
bejek said:
Well I know it's outdated, but without it I wasn't able to flash TWRP - and trust me, I tried every guide here at XDA and went through a big bunch of threads, I was really desperate.
I have no idea what build was originally in my 6p, some 6.0.0.
Now I am on newest stock, MTC20F
Click to expand...
Click to collapse
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Instead try out,
fastboot boot twrp_src_name.img
(Where twrp_src_name is your TWRP file name)
That should directly boot you to the TWRP. Else try custom TWRP builds like the one with MultiROM.
Heisenberg said:
You really just needed to update to the latest build before unlocking/rooting (standard procedure), then any current guide would have been fine. Either way you got it done though, so happy days.
The fact that you have no idea what build you were on previously is a little worrisome though, it's one of those basic things you should know before you start messing with your phone. But you're new to this so it's a learning curve I guess.
Click to expand...
Click to collapse
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
bejek said:
Yeah, you are obviously right. I didn't even let it update to the latest stock build and went straight to flashing new rom, so I guess there was the problem with TWRP.
Click to expand...
Click to collapse
If you don't boot into recovery right after flashing it, the standard recovery will overwrite it. If you want to prevent this, after flashing TWRP, boot directly into TWRP. Flash latest SU to root it (This will prevent the system from overwriting twrp on reboot.)
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.
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is there is a way i get info or download link for the stock kernel. Is it possible that i can just flash the kernel. Will my camera app stops again if i do that?
Please reply
Stifmeister11 said:
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is there is a way i get info or download link for the stock kernel. Is it possible that i can just flash the kernel. Will my camera app stops again if i do that?
Please reply
Click to expand...
Click to collapse
Flash boot.img from your stock ROM using fastboot, just like you flash stock but this time only flash the file boot.img
Thanks for the prompt reply
Before trying the Fastboot method, do a backup of everything in case of a bootloop , after flashing the stock kernel, do a backup with Flashify
Broloff said:
Before trying the Fastboot method, do a backup of everything in case of a bootloop , after flashing the stock kernel, do a backup with Flashify
Click to expand...
Click to collapse
Or by temp-booting TWRP from fastboot
Bro another noob question can i flash the stock rom with twrp rather than going with fastboot method. I dont own a PC and new to this rooting and flashing stuff. Is there a way?
Stifmeister11 said:
Bro another noob question can i flash the stock rom with twrp rather than going with fastboot method. I dont own a PC and new to this rooting and flashing stuff. Is there a way?
Click to expand...
Click to collapse
The fastboot ROM can't be flashed with TWRP, we have a separate TWRP flashable stock ROM builds that are used specifically with TWRP and other custom recoveries (if available).
So to make it clear, you can't flash the fastboot ROM via TWRP, you need to download stock ROM from the below thread.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Keep in mind to flash only the firmware that matches your device or the last update version you were on and never downgrade to a lower version than your device had when you stepped into the world of custom ROMs, root and etc otherwise you'll end up bricking your device.
Oh wow you just solved my problem i was really worried but this will do it... Yes i go through the instructions and flash the correct one... Thanks again
It's available via OTA
JDBarlow said:
It's available via OTA
Click to expand...
Click to collapse
Are you able to use arter kernel with this update?
kountry83 said:
Are you able to use arter kernel with this update?
Click to expand...
Click to collapse
should be able to, I don't see why it wouldn't work
Arter works fine with it. I updated this morning.
Do you have to have stock recovery + locked bootloader to install?
BeardKing said:
Do you have to have stock recovery + locked bootloader to install?
Click to expand...
Click to collapse
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
chris5s said:
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
Click to expand...
Click to collapse
What do you mean by flash the system update? Sorry I'm new here, but what exact steps did you do? I am currently on a rooted MR2 with Arter 's kernel.
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
finixs said:
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
Click to expand...
Click to collapse
compared to MR2, we probably will need to wait for months until razer puts the factory images on their dev-page...
I really can't understand what takes so long for that last step. Just upload that crap and you're done, razer
Can the update be flashed in TWRP without disturbing Magisk or Arter's kernel? I've grabbed the update zip via a link I found by generating a bug report in the developer options and searching for "System_Update". I'm just wondering if it's safe to flash over everything.
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Monopod said:
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Click to expand...
Click to collapse
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
chris5s said:
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
Click to expand...
Click to collapse
Arter97 R12 Kernel with Twrp and magisk root.
Monopod said:
Arter97 R12 Kernel with Twrp and magisk root.
Click to expand...
Click to collapse
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
chris5s said:
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
Click to expand...
Click to collapse
No mods not even F2fs and Vold, for the stock boot image I simply fastboot flash it.
I flashed f2fs, wondering if that's why I can't flash update even after flashing stock kernel? ?
Peace
https://github.com/RadekBledowski/Razer_Phone_mods/blob/master/magisk_patched.img?raw=true
here's magisk patched version
to flash arter kernel you have to flash it via zip not fastboot so flash it first via fastboot and flash it again but in twrp as zip
So what I see is you can update without reloacking your bootloader by... (I'm asking if this is right)
1. Fastboot flash stock boot.img
2. Update normally
3. Reflash magisk, your custom kernel and what not.
Correct?
I've tried flashing back to stock kernel but it didn't work for me.
I usually perform the "reset to factory" task from the razer images (properly commenting the line that erases userdata)
After that you just are with original stock and you can update via OTA as usual.