So, I got the May OTA yesterday before I unlocked my bootloader this morning to begin the process of possibly switching to a custom ROM (or just rooting, not sure yet). I unlocked it and everything is fine, but I read that the new bootloader included in the OTA breaks root and that I should flash the April one, so I did and works fine but I noticed that fastboot says that it flashed the bootloader to slot a, as if there are multiple bootloader slots.
Is there multiple bootloader slots? Should I be concerned that if I flash a ROM and it switched to slot B that I will have no bootloader, or would the April one be there from the OTA I did when I got the phone? Also, is there a way to flash into the second slot manually with fastboot, if it exists?
admiralspeedy said:
So, I got the May OTA yesterday before I unlocked my bootloader this morning to begin the process of possibly switching to a custom ROM (or just rooting, not sure yet). I unlocked it and everything is fine, but I read that the new bootloader included in the OTA breaks root and that I should flash the April one, so I did and works fine but I noticed that fastboot says that it flashed the bootloader to slot a, as if there are multiple bootloader slots.
Is there multiple bootloader slots? Should I be concerned that if I flash a ROM and it switched to slot B that I will have no bootloader, or would the April one be there from the OTA I did when I got the phone? Also, is there a way to flash into the second slot manually with fastboot, if it exists?
Click to expand...
Click to collapse
Hello, there is a bootloader on both slots... This is the purpose of seamless update. And, in case one slot fails, it will boot the other one...
Check this: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
You can flash the same factory image to both slots...
Flash your current slot with flash-all method. After the phone reboot, reboot once again to bootloader and issue:
fastboot --set-active=b (if your current active slot is a)
fastboot --set-active=a (if your current slot is b)
fastboot reboot-bootloader
Flash-all on the second slot, done...
I don't really see the point though, if you don't have issues.
Flashing custom ROM on a Pixel is a little bit different than older Nexus devices.
Check this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I wrote a little guide for someone today who wanted to install Pure Nexus, SuperSU and TWRP: https://forum.xda-developers.com/showpost.php?p=72128419&postcount=2
You can use it as a base...
Good luck...
5.1 said:
Hello, there is a bootloader on both slots... This is the purpose of seamless update. And, in case one slot fails, it will boot the other one...
Check this: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
You can flash the same factory image to both slots...
Flash your current slot with flash-all method. After the phone reboot, reboot once again to bootloader and issue:
fastboot --set-active=b (if your current active slot is a)
fastboot --set-active=a (if your current slot is b)
fastboot reboot-bootloader
Flash-all on the second slot, done...
I don't really see the point though, if you don't have issues.
Flashing custom ROM on a Pixel is a little bit different than older Nexus devices.
Check this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I wrote a little guide for someone today who wanted to install Pure Nexus, SuperSU and TWRP: https://forum.xda-developers.com/showpost.php?p=72128419&postcount=2
You can use it as a base...
Good luck...
Click to expand...
Click to collapse
Ok, thanks for the info.
admiralspeedy said:
Ok, thanks for the info.
Click to expand...
Click to collapse
Just a question....wouldn't it be smart to have the same image on both slots in case one slot fails for some reason or another? And isn't there a way to flash to both slots simultaneously? @ admiralspeedy
canemaxx said:
Just a question....wouldn't it be smart to have the same image on both slots in case one slot fails for some reason or another? And isn't there a way to flash to both slots simultaneously? @ admiralspeedy
Click to expand...
Click to collapse
Hello,
I doubt you can flash simultaneously both...
Wait for confirmation, but I have seen people flashing boot img on slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Guess this command can be used to flash bootloader as well...
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
I haven't tested it myself. You're on your own here...
Cheers...
Related
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
New official TWRP build 3.0.0.1 released: https://dl.twrp.me/bullhead/
bmbm said:
Since we have working TWRP for MHC19J build - HERE , I have one question about flashing MHC19J to my Nexus 5x.
Every month I'm flashing security updates this way:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Reboot to recovery
Flash the latest SuperSU
but in MHC19J build there is also a new bootloader - bootloader-bullhead-bhz10m.img and a new radio - radio-bullhead-m8994f-2.6.31.1.09.img . Do I need to flash this new bootloader and radio too? I assume yes, but I prefer ask first before RMA
Click to expand...
Click to collapse
Yes. You need to flash the bootloader and radio because they have changed. When in doubt, flash all of them except for user data. I follow Heisenberg's directions (below).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Rozalina340 said:
Or you can type in "flash-all.bat" , yes this is less safe , but I have been doing this method since the day I got my Nexus 5X and I have never encountered any issue ever since ! This is the method recommended by google so ... And by the way thank you for posting the link to the new TWRP , I needed this
Click to expand...
Click to collapse
Won't flash-all also write user data, thereby deleting everything? There's likely a reason that the experts on this forum have never recommended to use flash-all. If you follow Heisenberg's directions, everything will be fine, and you won't lose any data.
Edit: here's something stating that flash-all will erase data unless you modify the command.
http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I didn't know Heisenberg's method doesn't erase user's data. My bad then ^^
Sent from my Nexus 5X using Tapatalk
I've flashed the last two updates using flashfire from chainfire. It injects root during the process so twrp is easily installed using flashify. All without using PC (root is of course required for using flashfire)
Skickat från min Nexus 5X via Tapatalk
Bought my Z Play used and have been really enjoying it! Phone came with TWRP + Root. After the November update came out, I flashed everything except baseband and modem, since I didn't want to lose my imei and couldn't find factory images for my device. I'd really like to flash back to 100% stock so I can relock my bootloader, use Android pay, and accept the upcoming nougat update once it arrives.
Looked through all of the factory images I could find on XDA and did a lot of googling, no luck.
Same situation as you are. I can't find that specific ROM.
Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1
Really_Rekt said:
Lenovo have not released signed images that you can flash and lock your bootloader with. Your device will always have the software flag : modified in the bootloader. Your best option for Android pay is for Alberto97 to include the SafetyNet kernel flag in LOS 14.1
Click to expand...
Click to collapse
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!
xxBrun0xx said:
Really, I care more about being able to take the upcoming nougat OTA, but this is good info, thank you!
Click to expand...
Click to collapse
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.
luciddreamin92 said:
If I'm not mistaken, you should still be able to take upcoming OTA's even with an unlocked bootloader.
As long as you have stock recovery + un-root, you should be good in theory.
Click to expand...
Click to collapse
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.
xxBrun0xx said:
True, but my baseband currently doesn't match anything else. To get to the November update, I flashed everything except modem from the latest USA factory ROM. Guess I can just do the same thing once someone posts images for nougat.
Click to expand...
Click to collapse
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!
W3ND31 said:
Hey guys, to prevent the loss of your precious data (apks, settings and etc), and "enable" ota on your devices, go to Twrp, wipe System, cache and dalvik cache.
After this, flash the firmware of your device via fastboot with the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
After that, your phone should be able to install ota's.
Cheers!
Click to expand...
Click to collapse
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)
xxBrun0xx said:
Only if there is a factory image available for your device. Otherwise the OTA is going to brick your phone (OTA updates bootloader and modem, wrong modem will break radios, not sure if bootloader is region specific? If so, taking out of region OTA would hard brick you.)
Click to expand...
Click to collapse
Nice addon!
Thx!
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I would avoid at all cost flashing any modem, bootloader or baseband related bin file. You can freely flash the sparse chunks and boot.img to your heart's content.
Sent from my XT1635-02 using XDA-Developers Legacy app
xxBrun0xx said:
Update to this: spoke with a Level 2 Motorola Representative over the weekend. He did not seem to know anything about fastboot or TWRP or bootloader unlock vs sim unlock. I was pretty disappointed, Moto support has been excellent in past experience. He looked up the device by IMEI and told me it was unlocked US version, but had no idea what I was asking after almost an hour of explanation. The Level 1 tech I spoke to spoke pretty broken english. It's possible the baseband for RETUS is ROW_CUST, but I'm not brave enough to try flashing modem and boot.img.
If you're in the same boat, I'd recommend waiting until someone with a RETUS can confirm their baseband.
Click to expand...
Click to collapse
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.
dandrumheller said:
I'm on RETUS. Baseband is Addison_RETUS_Cust. No ROW.
Click to expand...
Click to collapse
The plot thickens
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.
Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.
Then you didn't flash it but just boot it
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
I'm waiting for this as well
have you tried changing your active slot to the other one and see if you can boot?
use fastboot to see which slot you are on, then set it as the other and reboot
this will get your current slot
Code:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.034s
set your active slot opposite of what you are currently on (slot b)
Code:
fastboot set_active a
if you are on b, set it to a
if you are on a, set it to b
give that a try and see if you can boot. you can revert it back it it doesnt help. worth a shot though.
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
H4X0R46 said:
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
Click to expand...
Click to collapse
I was very careful not to do that.
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Both slots need to be flashed the init_boot read my post
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Somehow you screwed up the boot partition that's why it won't boot
str8str said:
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
Click to expand...
Click to collapse
I assure you I did not flash to boot. I am the type that reads instructions 100 times. I know I must have did something wrong but it wasn't that.
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
AkayamiShurui said:
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
Click to expand...
Click to collapse
I forgot to mention this does work on bricked devices
Anybody with a corrupt boot.img that needs a factory one...
Does this one work ?
I would think it would work?
as it's a generic kernel image.
https://dl.google.com/android/gki/gki-certified-boot-android13-5.15-2023-02_r1.zip
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
Well if you trying to update to A.08 don't try flashing the boot.img I, I tried everything too and almost bricked my phone twice. if rooted you can't update with incremental updates in the USA ROM you only can do that with the EU ROM because they get a full ROM every time.
So I downloaded the EU ROM using oxygen updater App from play store then I used the OPLocalUpdate_For_Android12 App to force the update locally. The EU ROM looks the same to me so far but when we get a full ROM update in USA will switch back. Hope that helps