Hi there,
January Security Patch is not here yet so that's why I wanted to ask you guys:
Recently, I reflashed system.img and boot.img on slot B with the stock ones and locked the bootloader but I've modified the slot A before locking.
So I'm currently with a locked bootloader, using 100% stock slot B and I have a modified slot A. Will that modified inactive slot make any problems with updates (bootloops, etc.)?
Yes you will have problems, when you get a OTA you will get an error because slot A is modified, so the update won't apply.
To install OTA's you'll need to have your inactive partitions unmodified because the OTA will apply to that one (the active partition can be modified)
Modified slot A and bootloader still locks. Can anyone elaborate on this one.
So, how can I fix it WITHOUT FULL REFLASH USING MI TOOL PLEASE?
Do I just flash stock Oreo boot.img and system.img on slot A too? That will make slot A the same use the stock ROM as slot B.
Hmm?
nicolasmart said:
So, how can I fix it WITHOUT FULL REFLASH USING MI TOOL PLEASE?
Do I just flash stock Oreo boot.img and system.img on slot A too? That will make slot A the same use the stock ROM as slot B.
Click to expand...
Click to collapse
Yes flash stock on both slots. Then there won't be any trouble in getting ota.
I would recommend flash all.
alkesh95 said:
Yes flash stock on both slots. Then there won't be any trouble in getting ota.
I would recommend flash all.
Click to expand...
Click to collapse
Will flashing work without unlocking bootloader again?
Related
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
Question: If I install a full stock zip, does it overwrite:
Boot stack? <- Yes if from stock recovery / ? if from TWRP
Fastboot? <- Yes if from stock recovery / No if from TWRP
Recovery? <- Yes if from stock recovery / Yes if from TWRP
I've flashed a full stock zip and fastboot. just want to make sure I don't need to also flash stock bootstack for RMA purposes.
witchcraftz said:
Question: If I install a full stock zip, does it overwrite:
Boot stack? <- ?
Fastboot? <- No
Recovery? <- Yes
I've flashed a full stock zip and fastboot. just want to make sure I don't need to also flash stock bootstack for RMA purposes.
Click to expand...
Click to collapse
If you want to RMA your phone, flash an official zip through the official recovery. Those overwrite the bootstack, the recovery and the bootloader. Or use MiFlash. But I wouldn't risk locking the bootloader with not everything fully stock...
After flashing the official zip use axon7toolkit to relock.
I followed this process and I locked my phone.
https://forum.xda-developers.com/showpost.php?p=73576556&postcount=47
I'll download the latest Official Zip form ZTE and flash it officially just to make sure.
https://www.zteusa.com/axon-7#support
Thanks
I have been able to download OTAs and update this way.
But when I try to flash a Stock update.zip either from SD card or internal storage it gives me an error about not being able to mount the SD card.
Will the OTA updates also overwrite to boot stack?
Choose an username... said:
If you want to RMA your phone, flash an official zip through the official recovery. Those overwrite the bootstack, the recovery and the bootloader.
Click to expand...
Click to collapse
The phone downloaded the OTA for B19 and was able to run the update. How does ZTE check for a phone having been modified? Are there some steps or commands that can be run to check before sending it in? Should I just reflash the B19 full stock from Miflash to be sure everything is back to stock?
witchcraftz said:
The phone downloaded the OTA for B19 and was able to run the update. How does ZTE check for a phone having been modified? Are there some steps or commands that can be run to check before sending it in? Should I just reflash the B19 full stock from Miflash to be sure everything is back to stock?
Click to expand...
Click to collapse
We don't really know if they check it at all. Someone said he sent it unlocked and they disn't even notice.
Just be sure that the 5 second screen doesn't show up when you turn it on. Should be enough
Choose an username... said:
We don't really know if they check it at all. Someone said he sent it unlocked and they disn't even notice.
Just be sure that the 5 second screen doesn't show up when you turn it on. Should be enough
Click to expand...
Click to collapse
Update: My device was accepted by RMA and I have just received a replacement. Success!
I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Sent from my [device_name] using XDA-Developers Legacy app
gregg0829 said:
I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Click to expand...
Click to collapse
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Sent from my [device_name] using XDA-Developers Legacy app
gregg0829 said:
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Click to expand...
Click to collapse
Either way will get the job done. I flashed vendors all the time with twrp in my rom hopping days without issue. Strictly your call my friend :good:
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
Huh? I've never had to flash the vendor in TWRP more than once.
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.
SlimSnoopOS said:
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.
Click to expand...
Click to collapse
Hope you've been good my friend. I don't have a link for the commands, many I have just learned over time. I'm sure google search could help you out, and, you can always type...fastboot help...while in fastboot mode that will show a list of commands :good:
another way to update the vendor is to download the full factory image, then open it in a file explorer. open the zip inside the zip and find vendor.img. extract that somewhere and flash it. this is how ive done it. cuz i never have a computer handy when i want to update.
I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?
You already took the November OTA or are you still on October?
ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November
Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.
I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks
Yes.... fastboot flash boot boot.img
ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?
TWRP doesn't work with Q. Just use stock recovery to sideload.
ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.
The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk
Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
thanks for this.. i was looking everywhere for boot extraction tools
Hi. I am looking for some method to flash a recovery or rooted boot for Razer 2 since the USB port on it is messed up.
Not sure if it is the software or the hardware, but the only way I can charge it at all (slowly) if I use an USB A to C cable and the device is off (well, not really since it flashes the logo, vibrates, and now complains about the unlocked boot-loader)
The stock recovery has the option "apply update from SD card" Are there any signed images in update.zip form I could just throw on the sd card?
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.
There isn't one. Once booted you can use ADB over WiFi. But Fastboot only works with USB.
You're far better off updating to the newest firmware and patching via magisk than ever using downloaded pre-patched boot images
That would be true if we could get Magisk to patch a un-rooted phone. All I've done here is extract the latest stock firmware and patch it with Magisk so others can flash it. I believe the first time you boot after, it askes you to updated to the latest version.
hackthis02 said:
Here is the patched Magisk boot.img and the stock one incase you need to flash back. No TWRP, just root.
Click to expand...
Click to collapse
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
kylster said:
Do you have a recommended guide on how to use these? I have RP2 and not sure where to begin since it's stock.
Click to expand...
Click to collapse
Take the patched one and flash it like you would any boot.img
Flash w/ Fastboot
pensive said:
By the way, where can I get a link to
P-SMR7-RC003-RZR 210107.3225 images? The official factory image page does not have it.
Click to expand...
Click to collapse
not sure if i can paste here, but here we go...
Spoiler
https://www.reddit.com/r/razerphone/comments/iyb47z
im not sure why in razer webpage is incorrect, but is the same server AWS
P-SMR7-RC003-RZR 210107.3225Security Maintenance Release / Over The Air (OTA) UpgradeGlobal (Aura)9.0 Pie2021 February 05
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3225-user-full.zip
Hey I recognize that post