As the title says is it possible to root, install modifications to stock ROM and is there a fast way to revert everything is something go wrong? I'm asking because support for 5X has ended, and I can't permanently unlock bootloader. I don't want to hard brick this phone by mistake and also I don't want just look how this device is being wasted.
So here's some probably noob questions that I want to ask:
1. Can I install TWRP on NO RPMB bootloader and boot it without issues? If so, how?
2. What recovery version should I install 4-core or regular 6-core?
3. Can I root device and hide it with magisk?
4. If an security update appear how to install it since stock recovery is replaced with TWRP?
5. If something go wrong like 2nd death loop how to revert everything? Can I simply flash stock system image in TWRP to "fix" device?
Thanks in advance.
You might try the solution the user in this thread suggested, https://forum.xda-developers.com/nexus-5x/help/rpmb-bootloader-locked-t3481906/page2
So I have to unlock bootloader, then flash TWRP, Super SU, compatible Magisk in one attempt, then I'm ready to go? Will TWRP boot and work like nothing happened?
Sent from my Nexus 5X using XDA Labs
I haven't tried it but based on the steps I would think it should work. It won't hurt anything. It also won't stop the bootloader from locking upon a reboot. But as long as you can unlock it prior to flashing any of the partitions as the reddit thread suggests you could be ok.
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Banan PL said:
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Click to expand...
Click to collapse
I'm running custom kernels just fine with locked bootloader.
CazeW said:
I'm running custom kernels just fine with locked bootloader.
Click to expand...
Click to collapse
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Haven't tried Jolla's multiboot or drivedroid. As long as you can get into fastboot, you can just unlock it again and flash stock (though you will obviously lose everything that's on the device). Haven't tried flashing custom ROMs but as custom kernels are working, I don't see why custom ROMs wouldn't.
negusp said:
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Click to expand...
Click to collapse
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't own a device without RPMB (I got a fairly new refurb), but I've used TWRP/flashed ROMs and kernels successfully with the bootloader locked and TWRP installed.
Alright I'll flash TWRP take nandroid and hopefully device will boot. Can someone give me link to 4-core TWRP, I can't find it?
Sent from my Nexus 5X using XDA Labs
Google 4 core twrp 5x xda. It's in that thread. https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Banan PL said:
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Click to expand...
Click to collapse
Did you unlock and then without rebooting flash the TWRP?
CazeW said:
Did you unlock and then without rebooting flash the TWRP?
Click to expand...
Click to collapse
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Banan PL said:
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Click to expand...
Click to collapse
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
CazeW said:
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
Click to expand...
Click to collapse
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Banan PL said:
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Click to expand...
Click to collapse
So you are not actually getting into recovery at all. Try with different TWRP image.
CazeW said:
So you are not actually getting into recovery at all. Try with different TWRP image.
Click to expand...
Click to collapse
I tried with regular TWRP 4-core modded TWRP and with Multiboot TWRP. Same result.
Sent from my Nexus 5X using XDA Labs
Related
i just picked this up today rooted it in like 15 minutes whole 9 yards well when it boots it has a dumb little lock symbol under the word GOOGLE i was wanting to know how to get it rid of it i used triangle away for the samsung devices is there anything similar to that or is this something that im stuck with ( it looks tacky )
Unroot and relock the boot loader and you won't see that anymore.
someolddude said:
Unroot and relock the boot loader and you won't see that anymore.
Click to expand...
Click to collapse
i don't want to unroot so pretty much im stuck with it
Its not so much unrooting, but locking the bootlaoder. The little lock signifies an unlocked bootloader.
sent from my nex7 flo
mugzylol said:
Its not so much unrooting, but locking the bootlaoder. The little lock signifies an unlocked bootloader.
sent from my nex7 flo
Click to expand...
Click to collapse
so what will happen in regards to locking the bootloader will i be able to use recovery and have root
I don't think you will be able to use recovery but since superuser has already been flashed I think it would stay but I'm really not sure.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I think that re-locking may wipe your device just like unlocking does; in which case you'll use root... or not?
mugzylol said:
Its not so much unrooting, but locking the bootlaoder. The little lock signifies an unlocked bootloader.
sent from my nex7 flo
Click to expand...
Click to collapse
Exactly right!
soldier1184 said:
so what will happen in regards to locking the bootloader will i be able to use recovery and have root
Click to expand...
Click to collapse
Yes.
mugzylol said:
I don't think you will be able to use recovery but since superuser has already been flashed I think it would stay but I'm really not sure.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you lock the bootloader whatever recovery that you have installed will stay regardless if you are rooted or not and you would still be able to use that recovery.
schermvlieger said:
I think that re-locking may wipe your device just like unlocking does; in which case you'll use root... or not?
Click to expand...
Click to collapse
No. Relocking the bootloader does NOT wipe your device. A locked bootloader will prevent you from being able to fastboot flash ANY images which includes the factory image or parts thereof (system, boot, recovery, bootloader). Using the command fastboot oem unlock will always wipe your device!
If you are unlocked, rooted and use a custom recovery like TWRP you can lock (or unlock) the bootloader with BootUnlocker and still use your custom recovery. And that will also get rid of the unlocked icon. I've used BootUnlocker and it works great. After locking the bootloader and you are still rooted you might even be able to use Flashify to install a new/updated recovery or boot image, I haven't tried that so I'm not sure. I don't have BootUnlocker installed now because I have no problem with my bootloader always being unlocked and I have no idea if it will continue to work after future android updates.
Update: With a locked bootloader I just used Flashify to flash TWRP and it worked fine.
I have a new M8 and, for the moment, I want to keep it stock, but rooted. Is it possible to fastboot boot TWRP, flash SuperSU for root, and still be capable of receiving OTA updates, since TWRP isn't actually installed? I'm coming from a N4 and N10 where I didn't care so much about official OTAs, so I've never tried this.
Also, do I still have to unlock the bootloader first in order to use fastboot at all? And does having an unlocked bootloader prevent OTAs?
Sent from my Nexus 10 using XDA Free mobile app
No, you can't root with a locked bootloader. That's the whole point (well, mostly) of a locked bootloader.
Also, its my strong opinion that OTAs have no place on a modded/rooted device. It won't work anyway, the OTA will check for root and fail to install. Or even if it did install, it would unroot the phone.
If you want to root, just do the whole deal, unlock bootloader, install custom recovery, etc. You can flash anything you want, including the awesome array of custom ROMs, or stock rooted ROMs for other carrier versions (which usually get released soon after the OTAs anyway).
Totally makes sense. Knowing me, it won't be long before I feel constricted with a locked bootloader (especially if I can't root}, but just wanted to see how "virgin" I can't keep the phone while I break it in. Plus I read a recommendation to use fastboot to boot into TWRP as an alternative to flashing it. But if I have to have an unlocked bootloader to do even that, I suppose I should just install TWRP and be done with it, like I'm used to.
Sent from my Nexus 10 using XDA Free mobile app
bruce7373 said:
Plus I read a recommendation to use fastboot to boot into TWRP as an alternative to flashing it. But if I have to have an unlocked bootloader to do even that, I suppose I should just install TWRP and be done with it, like I'm used to.
Click to expand...
Click to collapse
Not sure what will happen if you try to boot TWRP with a locked bootloader. Maybe only one way to find out
But that would be purely academic. You can't flash SU or SuperSU, since you need write access to the system partition to do so (and therefore an unlocked bootloader), regardless of whether you can boot TWRP or not.
redpoint73 said:
Not sure what will happen if you try to boot TWRP with a locked bootloader. Maybe only one way to find out
But that would be purely academic. You can't flash SU or SuperSU, since you need write access to the system partition to do so (and therefore an unlocked bootloader), regardless of whether you can boot TWRP or not.
Click to expand...
Click to collapse
Great, that's exactly what I needed to know. I'll just wait a week or two, see if I'm happy with the phone and, if I am, just do it all. Thanks a lot.
Sent from my Nexus 10 using XDA Free mobile app
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
You should install stock recovery if you want to get OTA . If you're rooted, you will lose root and need to flash Magisk again (with nexus root toolkit).
Locked or unlocked bootloader, it not affect the updating process. The custom recovery will not flash OTAs . Flash fire is the solution if you have custom recovery . Bootloader and radio can only flash with fastboot. But lately with the latest updates on flash fire, it reboot and screen stay black and need to perform force reboot.
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
mika91 said:
What I wanted to do:
1 - Factory reset (I received my 5x yesterday, no data to backup)
2 - Revert to stock (stock rom + stock recovery)
3 - Install Magisk Manager
4 - Patch stock boot image in Magisk Manager
5 - Flash the patched boot image
After these few steps, I should have a stock rom with magisk.
When OTA is available, I have to restore stock boot image, then apply the OTA, and finally perform steps 3 to 5 right?
Click to expand...
Click to collapse
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
mika91 said:
Ok, thanks for the tips.
It's easier sure, but it works only if you have a computer near to you
Click to expand...
Click to collapse
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well.. You have to have a stock recovery for OTA, you can't flash it via TWRP.
_mysiak_ said:
Well, unless I missed something, in your steps you need computer to flash patched boot.img as well..
Click to expand...
Click to collapse
oups, you're right!
so definitively you're method is the way I'll go
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
_mysiak_ said:
I find this easier/faster:
1. stock rom + stock recovery
2. "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3
Click to expand...
Click to collapse
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
nigga99 said:
bug
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
How did you suceed to boot twrp with locked bootloader? I'm trying to make as you wrote, but when I try it fails:
downloading 'boot . img'...
OKAY [ 0.429s]
booting...
FAILED (remote: unlock device to use this command)
I neither want to unlock my bootloader.
Click to expand...
Click to collapse
_mysiak_ said:
You can't use fastboot commands with locked bootloader, the only way is to unlock the bootloader. Unlocking bootloader on Nexus 5x is also a "safety" preparation for a future HW bootloop, you might be able to use one of the existing (temporary) fixes to boot the phone with problematic CPU cores disabled.
Click to expand...
Click to collapse
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
nigga99 said:
Thank you much. So I'll unlock the bootloader then, I didn't know that it is possible to OTA with unlocked bootloader..
Click to expand...
Click to collapse
As long as you keep stock recovery and unmodified system, you can apply OTA. It doesn't check bootloader status or systemless modifications (Magisk, Supersu,..). Just please keep in mind that bootloader unlocking will wipe all your data.
Here is a guide how to install the OTA without computer and keep magisk:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
mika91 said:
Hi,
With the new version of Magisk v14.0, it seems that neither root neither custom recovery are necessary!
So if I just unlock the bootloader and install Magisk, my device should reveice the OTA right?
Anyone tried and succeeded?
I'm currently using PureNexus, but i'd prefer to go back on stock with OTA. (and edit /etc/host with magisk)
Thanks
Click to expand...
Click to collapse
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
tomsonmathewv said:
Dear Sir,
I have nexus 5x and it has bootloop issue. " https://www.youtube.com/watch?v=VyebEZMwVsQ " With the help of this video i repaired my phone. Thanks for one who created the Patched boot image.
I am not able to install any custom Kernel to my phone, if i install it wont boot up. Then i need to repatch the Patched boot image. Is there any soluction for this? I got any update to 8.1.0. Is it possible to update without any problem?
Click to expand...
Click to collapse
You're asking in a dead and wrong thread. However, this post has everything you need. You can also check out https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926.
So I have small problem. I have to restore device to factory state (flash stock image), but I have TWRP instead stock recovery. If I unlock bootloader while I have TWRP will something bad happened?
Should I flash stock recovery first and then unlock bootloader? Or I can simply do it with TWRP?
It shouldn't matter if you have twrp. But unlocking the bootloader will wipe your device so backup anything you want first. I'm not sure if you mean you want to unlock the bootloader with twrp? That you can't do, use fastboot. But, if you have twrp haven't you already unlocked the bootloader?
Sent from my SM-T820 using XDA-Developers Legacy app
jd1639 said:
It shouldn't matter if you have twrp. But unlocking the bootloader will wipe your device so backup anything you want first. I'm not sure if you mean you want to unlock the bootloader with twrp? That you can't do, use fastboot. But, if you have twrp haven't you already unlocked the bootloader?
Click to expand...
Click to collapse
Bootloader will lock itself on next boot, but that's different story.
So nothing bad will happen? I need to get rid of "device is corrupt" if I want to send device to LG for screen replacement.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Bootloader will lock itself on next boot, but that's different story.
So nothing bad will happen? I need to get rid of "device is corrupt" if I want to send device to LG for screen replacement.
Click to expand...
Click to collapse
Do you mean the "device is corrupt" screen on boot up. I guess I haven't specificaly tried it on my 5x, but I don't believe that will ever go away once you've unlocked the bootloader the first time. Even if you flash the stock firmware and Mick the bootloader with the device. But it's a Google device so LG still do the screen replacement.