Related
I'm running Marshmallow 6.0 through the Bad Boyz v.2 Rom and I just got a 2.2 MB system update... Has anyone else recieved this update, any clue what this is?
I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.
I received it also, not sure what it is
artjef said:
I received it also, not sure what it is
Click to expand...
Click to collapse
I'm afraid... hold me.
It fixed the netflix video freezing issue.
fasthair said:
I just had it pop up for me a few minutes ago. I'm rooted so I can't flash it yet because I'm not near aPC.
Click to expand...
Click to collapse
I've just had this too. Can I ask how you flash an update like this on a rooted device? I usually wait for the full image and then just flash that.
I got it too just now. it's 10/27/2015 1:27 AM
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
the update is 2.2 megs. The original MM6 image was manually installed on my device when it came out and this update just got installed normally as usual. Maybe you should get the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh original MM6 installed .....
Cold this morning in Québec hey ?
zigonneux said:
the update is 2.2 megs. The original MM6 image was previously installed manually when it came out and this update just got installed normally as usual. The device told me that an update was available and if i wanted to install it.... that's it that's all. Maybe you should wipe and flash the stock MM6 image from google and let things work by themselves. I don't see why i would change anything on my nexus 7 2013 with a fresh stock MM6 installed .....
Cold this morning in Québec hey ?
Click to expand...
Click to collapse
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
And yes it was -4°C this morning
Magister54 said:
I installed the 6.0 image last week as explained in a post, with TWRP and the modified kernel. How do I install this update now?
Click to expand...
Click to collapse
Magister54 said:
Problem is it reboots in TWRP, I cannot install it manually from here, it fails :-/
Click to expand...
Click to collapse
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
you can use " Nexus tool rootkit " to wipe and reinstall the original stuff. As the man said up here, you need a stock recovery to install the update... if you re-install this modified kernel, you might have the same problem at the next update.
does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....
airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
Just wondering if the version and or the build numbers changed?
Thanks
^As it says on the factory image page, it's still 6.0.0. MRA58U.
quazimodem said:
does anyone have a flashable zip for this update? I really don't wanna reload just to install this update....
Click to expand...
Click to collapse
You don't need to.
Download the system image and fastboot flash boot.img and system.img.
That's is. Doesn't wipe anything. Takes two minutes.
airberger said:
You need stock recovery to install the update. I'm not sure about the modified kernel, I flashed the stock boot.img just to be safe.
After sideloading the update (or I guess you can just update it normally if your device has automatically downloaded the update) and rebooting, I re-flashed TWRP and then used it to install the modified kernel and SuperSU. Everything is peachy now.
Click to expand...
Click to collapse
I rebooted in bootloader, flashboot recovery and boot from official image, but recovery boots in the dead android robot :-/. I reflashed TWRP and rooted kernel to get back on feet.
yosmokinman said:
^As it says on the factory image page, it's still 6.0.0. MRA58U.
Click to expand...
Click to collapse
Thanks... I should have looked there first.
Is it somehow possible to flash the OTA on a rooted MM 6.0 with still stock recovery on it? I never flash but temperary boot TWRP to flash things. Would hate to reflash firmware for every OTA.
Thanks.
You can download the whole archive of MRA58U, extract system.img, reboot in bootloader and use flashboot to flash system.img (and boot.img if you do not need the rooted kernel)
bad modified boot image?
Hi there,
I am upgrading to MRA58U, factory image upgrade just works fine (skipped wiping as usual), but the modified boot image (from razor-mra58u-boot.zip) won't load.
Code:
> fastboot flash bootloader boot.img
sending 'bootloader' (7448 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
The very same procedure worked fine for mra58k.
What am I doing wrong?
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.
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
So op 5t released a new update, whenever i open the update screen it says root detected, i would lose my root privileges if I update the phone.
I wanted to know whether i would only lose my root, or entire thing of bootloader getting locked etc?
After updating will I be able to just boot into recovery and flash root file? Or whole process I would have to do again
Thanks
Updates reinstall the stock recovery. You have to flash twrp then root.
virusshah1997 said:
So op 5t released a new update, whenever i open the update screen it says root detected, i would lose my root privileges if I update the phone.
I wanted to know whether i would only lose my root, or entire thing of bootloader getting locked etc?
After updating will I be able to just boot into recovery and flash root file? Or whole process I would have to do again
Thanks
Click to expand...
Click to collapse
When you install an OTA it will NOT relock your bootloader, it will reinstall the stock recovery since that is included in the OTA zip and is forced installed to be sure the update installs correctly.
You will lose the root temporarily until you flash a custom recovery again and your root of choice.
Misanful said:
When you install an OTA it will NOT relock your bootloader, it will reinstall the stock recovery since that is included in the OTA zip and is forced installed to be sure the update installs correctly.
You will lose the root temporarily until you flash a custom recovery again and your root of choice.
Click to expand...
Click to collapse
I have to flash TWRP again?
virusshah1997 said:
I have to flash TWRP again?
Click to expand...
Click to collapse
yes.
Misanful said:
yes.
Click to expand...
Click to collapse
Wait, really? https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips doesn't say anything about having to flash twrp again...
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse
Or does "100% stock images" mean the stock bootloader = flash twrp again?
Just to clearify, updating my phone by an OTA does not lock the bootloader but I'd have to flash twrp and magisk again..?
Yakumichan said:
Wait, really? https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips doesn't say anything about having to flash twrp again...
Or does "100% stock images" mean the stock bootloader = flash twrp again?
Just to clearify, updating my phone by an OTA does not lock the bootloader but I'd have to flash twrp and magisk again..?
Click to expand...
Click to collapse
yee, but after you have used the OTA you will need to flash twrp again since the OTA flashes the stock recovery, or modify your boot image but that is a pain in the ass. :silly:
Misanful said:
yee, but after you have used the OTA you will need to flash twrp again since the OTA flashes the stock recovery, or modify your boot image but that is a pain in the ass. :silly:
Click to expand...
Click to collapse
Means if I'd like to unroot my phone by doing nothing, this is probably the easiest way?
Currently running Oreo 8.1 with magisk root and TWRP installed. I have access to no other devices other than my pixel XL.
Is there a way to update to Stock 9.00 in this situation without losing TWRP or the ability to root with magisk?
Flash ota with twrp.
Then flash twrp and magisk and reboot.
Probably will want to wipe and start 9.0 clean.
Sent from my Pixel XL using Tapatalk
lafester said:
Flash ota with twrp.
Then flash twrp and magisk and reboot.
Probably will want to wipe and start 9.0 clean.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I am being dense, but how would he flash TWRP (after flashing the OTA with TWRP the 1st time) without a computer to then fastboot boot the twrp.img? The OTA will revert recovery to stock, so he won't be able to flash the twrp.zip and magisk.zip.
You are still in twrp, so just flash the zip.
Sent from my Pixel XL using Tapatalk
lafester said:
You are still in twrp, so just flash the zip.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I said I might be dense. I haven't flashed anything in TWRP without rebooting immediately in a long time since I remember folks having issues flashing Magisk after the TWRP.zip (or flashing anything after an OTA) without a reboot. Good call though. It's worth a try.
sliding_billy said:
Maybe I am being dense, but how would he flash TWRP (after flashing the OTA with TWRP the 1st time) without a computer to then fastboot boot the twrp.img? The OTA will revert recovery to stock, so he won't be able to flash the twrp.zip and magisk.zip.
Click to expand...
Click to collapse
he first would have to download Full OTA from google, not the incremental ota that he receives in the phone. He also could download the incremental ota, but that he would need to capture that incremental ota url. So, it's much easier to download the full ota because the links are publicly shared by google.
onesolo said:
he first would have to download Full OTA from google, not the incremental ota that he receives in the phone. He also could download the incremental ota, but that he would need to capture that incremental ota url. So, it's much easier to download the full ota because the links are publicly shared by google.
Click to expand...
Click to collapse
Gotcha. I have done the full OTA through TWRP (mostly just to see if it worked), but it has been well over a year since using OTA through TWRP quit working for at least one TWRP build. When that happened, I quit playing with it at all and have used nothing but the flash-all (minus the -w of course) since then. I just remember there being a bunch of errors if you continued to install in TWRP without doing a reboot device after an OTA (and even other zip installs).