Related
On Nougat, doing fastboot boot twrp.img would work as expected. Now, on Android O DP3, TWRP goes into a bootloop. It flashes the bootup screen and then going to black in an infinite loop. Anyone know how to solve this issue?
O doesn't work with twrp. I never got it too even if you downgrade for twrp to work you have to flash N on both partitions just to get it to temp boot
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
O doesn't work with twrp. I never got it too even if you downgrade for twrp to work you have to flash N on both partitions just to get it to temp boot
Click to expand...
Click to collapse
Not true in every case. I used flash all to upgrade to O beta. Then I used flash all to go back to N. I've done this multiple times. I'm able to boot twrp fine after using flash all to get back to N. I don't need to flash it to both slots. I know of a few other people that use the same exact method as me. I think where people are running into issues is when they take the OTA to upgrade to the O beta. Taking an OTA swaps the current boot slot. I haven't tried taking an OTA for the O beta to test this out though.
toknitup420 said:
Not true in every case. I used flash all to upgrade to O beta. Then I used flash all to go back to N. I've done this multiple times. I'm able to boot twrp fine after using flash all to get back to N. I don't need to flash it to both slots. I know of a few other people that use the same exact method as me. I think where people are running into issues is when they take the OTA to upgrade to the O beta. Taking an OTA swaps the current boot slot. I haven't tried taking an OTA for the O beta to test this out though.
Click to expand...
Click to collapse
Weird maybe I just go overkill I never knew what exact step I did that got it to work but all I know is when I do that it works fine lol
TWRP just gets stuck on the boot screen after reflashing Nougat. I don't know how to switch slots in fastboot, because it looks like the required command is removed.
EDIT: It turns out the fastboot and adb from apt aren't up to date, so now I can swap the boot slot once updating it.
khang06 said:
TWRP just gets stuck on the boot screen after reflashing Nougat. I don't know how to switch slots in fastboot, because it looks like the required command is removed.
EDIT: It turns out the fastboot and adb from apt aren't up to date, so now I can swap the boot slot once updating it.
Click to expand...
Click to collapse
I don't really understand the dual slots yet. How does switching slots help you avoid a boot loop when installing TWRP?
No idea, I flashed Nougat on one slot and TWRP bootlooped, but after flashing it to both slots, it worked perfectly.
khang06 said:
No idea, I flashed Nougat on one slot and TWRP bootlooped, but after flashing it to both slots, it worked perfectly.
Click to expand...
Click to collapse
That's good to know if I ever get the courage to flash on this phone. Thanks.
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
kismetmookz said:
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks, I have been using this and used it as I was wring the article, I'm just trying to see how we flash the ROMs on this puppy.
i use to do these steps
wipe caches
install rom
install twrp.zip for taimen
reboot
setup phone
if you want root then reboot on recovery again then install magisk.
I do these steps and have no failure when flashing; after I wipe the Caches, I flash the ROM and then the TWRP partition flasher and reboot the system. I've waited 15 minutes to have the device boot with no luck and I don't want to risk any longer due to the Pixel 2/ XL having burn-in issues.
thowersome said:
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
Click to expand...
Click to collapse
Probably because there's not a full OS on the slot your flashing to. If you know your fastboot, it's relatively easy going forward. The Dueces scrip it's great tool for sure to help out. If you want to do it manually, fastboot the factory image to both slots with the -w removed from the flash-all.bat file.
Once that's done, go back to fastboot, and boot into twrp. Then do a twrp factory reset with the swipe bar. Flash the rom, then the twrp.zip and let it boot up. Once in the OS, keep lock screen set to swipe, and do a minimal setup. Then go back to twrp and flash your custom kernel(optional) then flash magisk. And that should do it :good:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
thowersome said:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
Click to expand...
Click to collapse
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Badger50 said:
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Click to expand...
Click to collapse
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
thowersome said:
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
Click to expand...
Click to collapse
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend! ??
Badger50 said:
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend!
Click to expand...
Click to collapse
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
thowersome said:
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
Click to expand...
Click to collapse
Outstanding! Well done :good::good:
Hey all! So I'm still way back in the Stone age on my Nexus 6 shamu. I'm thinking of getting a new pixel device but the things that have changed seem so daunting to me.
Quick questions:
1) when you install a rom, does it go into both system partitions? How does that work? Devices before this dual partition stuff we're straight forward.
2) Is it even worth it to flash stock images with hand typed commands? Or is the flash all script the life saver here?
3) the recovery is now merged with the boot partition, is there any more of quirks like this with a pixel?
4) Does encryption follow suit from the older Nexus devices where it's forced by the boot?
Thanks guys! I'm really thinking of moving on to the new way of using Android on a new flagship device [emoji41]
H4X0R46 said:
Hey all! So I'm still way back in the Stone age on my Nexus 6 shamu. I'm thinking of getting a new pixel device but the things that have changed seem so daunting to me.
Quick questions:
1) when you install a rom, does it go into both system partitions? How does that work? Devices before this dual partition stuff we're straight forward.
2) Is it even worth it to flash stock images with hand typed commands? Or is the flash all script the life saver here?
3) the recovery is now merged with the boot partition, is there any more of quirks like this with a pixel?
4) Does encryption follow suit from the older Nexus devices where it's forced by the boot?
Thanks guys! I'm really thinking of moving on to the new way of using Android on a new flagship device [emoji41]
Click to expand...
Click to collapse
1. If you flash a ROM zip in TWRP, assuming you are on "partition" or slot 'A', the ROM will be flashed to slot 'B'. You don't need to do anything yourself, it just happens on its own. You do need to flash the TWRP zip file again if you were wanting to keep TWRP recovery on your device.
2. Don't know what you mean by hand-typed commands, but I simply run the flash-all file to both slots whenever I want a clean upgrade. Most people get away with flashing it to one slot though.
3. Yes the recovery now resides in boot. You just have to flash the TWRP zip, a custom kernel and Magisk for root in that order to get things working properly!
4. Not too sure about this one, sorry!
rickysidhu_ said:
1. If you flash a ROM zip in TWRP, assuming you are on "partition" or slot 'A', the ROM will be flashed to slot 'B'. You don't need to do anything yourself, it just happens on its own. You do need to flash the TWRP zip file again if you were wanting to keep TWRP recovery on your device.
2. Don't know what you mean by hand-typed commands, but I simply run the flash-all file to both slots whenever I want a clean upgrade. Most people get away with flashing it to one slot though.
3. Yes the recovery now resides in boot. You just have to flash the TWRP zip, a custom kernel and Magisk for root in that order to get things working properly!
4. Not too sure about this one, sorry!
Click to expand...
Click to collapse
Cool thanks! So the device chooses which slot it's gonna boot from by itself then? I'd imagine the bootloader controls that yeah? Does this mean the slot switches for every flashed file or only if it's a full rom package?
H4X0R46 said:
Cool thanks! So the device chooses which slot it's gonna boot from by itself then? I'd imagine the bootloader controls that yeah? Does this mean the slot switches for every flashed file or only if it's a full rom package?
Click to expand...
Click to collapse
As far as I know, it's only for ROM flashes or taking OTA updates when on stock. I'm pretty sure the bootloader does it but I've never manually switched slots unless I wanted a super clean/fresh upgrade. Other than that no manual switching; it's not really hard at all once you get the hang of it!
2) If you mean what I think you mean -- manually inputting fastboot commands for every/all .img files -- Deuces script actually does this! You can even look (or edit, if you are unaware) at the "code" and see 20+ fastboot flash commands. It's a really great modified version of the flash-all script and has helped a whole bunch of users.
3) there aren't many "quirks" I would say, but it does cause a bit of misunderstanding with users coming from other devices onto the Pixels. When coming from root and custom recovery (mostly for OTA updating), they get confused as to resetting it back to stock believing there is a recovery partition to flash and not really bothering with the boot image/partition. I came from the Galaxy S5, so I never got used to that type of thing and am now knowledge-based that recovery goes with the boot image/partition.
4) I'm going to go out on a limb here and attempt to answer this; hopefully I'm understanding it correctly. I believe the device does encrypt from boot. At the very least TWRP (custom recovery) MUST load in any security method you employ to decrypt and properly read the contents of the phone's file system. I can't imagine there being a "process" or "state" that's after turning on the device but before the boot and/or recovery is evoked (other than the "unlocked bootloader" warning, of course).
These are just my assumptions -- if anyone knows better or "righter":silly:, please feel free to correct me -- but in any case, I hope this helps....
Since the oneplus 7T has two slot a and b. Is it possible to load another rom onto slot b? Depending on which slot is active could we boot into the rom in that slot? Thanks for your reply.
tknguyencsu said:
Since the oneplus 7T has two slot a and b. Is it possible to load another rom onto slot b? Depending on which slot is active could we boot into the rom in that slot? Thanks for your reply.
Click to expand...
Click to collapse
Possible if decrypted, but it's very likely you run into issues and mess your /data partition up.
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
p51d007 said:
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
Click to expand...
Click to collapse
This has been the case for Android for a few years now. The system is installed on either A or B.
p51d007 said:
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
Click to expand...
Click to collapse
I think you are right. When I mess up the 7T in version 10.0.9 and it get stuck in fastboot mode. I tried to boot into twrp.img hopefully to flash the stock rom again, instead the phone some how reboot itself into the previous version 10.0.8 and I need to update it to version 10.0.9.
tknguyencsu said:
I think you are right. When I mess up the 7T in version 10.0.9 and it get stuck in fastboot mode. I tried to boot into twrp.img hopefully to flash the stock rom again, instead the phone some how reboot itself into the previous version 10.0.8 and I need to update it to version 10.0.9.
Click to expand...
Click to collapse
Why would you even use TWRP? It's not working and has nothing do to with what he mentioned.
Sent from my OnePlus7TPro using XDA Labs
---------- Post added at 03:26 PM ---------- Previous post was at 03:12 PM ----------
The system still resides on the super partition, and its read only which means you cannot flash it. One of, if not the main reason why TWRP is not here.
It would be very risky and hard to do it without a working TWRP.
Sent from my OnePlus7TPro using XDA Labs
To answer the OP's question: if you were to be able to stay decrypted, you could flash two ROMs via fastboot. Once the first is flashed, you could switch to the B partition via "fastboot --set-active=", reboot to the bootloader and then flash the second fastboot ROM.
However, it is not recommended, might not work and I'm not sure whether an available custom ROM is decrypted by default. Also not sure if you can decrypt properly as there is no no-verity.zip flashable right now.
Macusercom said:
To answer the OP's question: if you were to be able to stay decrypted, you could flash two ROMs via fastboot. Once the first is flashed, you could switch to the B partition via "fastboot --set-active=", reboot to the bootloader and then flash the second fastboot ROM.
However, it is not recommended, might not work and I'm not sure whether an available custom ROM is decrypted by default. Also not sure if you can decrypt properly as there is no no-verity.zip flashable right now.
Click to expand...
Click to collapse
I don't think that's possible. The super (read only) handles the slots internally and it's the OTA that takes care of 'filling' the other slot up dynamically, meaning you can only flash the slot a system, not slot b.
In order to dual boot, you would need some risky repartitioning and could mess your device up.
(Not an expert of course, so I might be wrong)
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
I don't think that's possible. The super (read only) handles the slots internally and it's the OTA that takes care of 'filling' the other slot up dynamically, meaning you can only flash the slot a system, not slot b.
In order to dual boot, you would need some risky repartitioning and could mess your device up.
(Not an expert of course, so I might be wrong)
Click to expand...
Click to collapse
If you use fastboot to flash the ROM you can flash it to a particular slot. You can then flash different .img files to A or B. But if they would boot is another question, yes. So in general I do not consider it working.
Lossyx said:
Why would you even use TWRP? It's not working and has nothing do to with what he mentioned.
Sent from my OnePlus7TPro using XDA Labs
---------- Post added at 03:26 PM ---------- Previous post was at 03:12 PM ----------
The system still resides on the super partition, and its read only which means you cannot flash it. One of, if not the main reason why TWRP is not here.
It would be very risky and hard to do it without a working TWRP.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I boot into TWRP to change slot, even though you can do it through fastboot. The point I would like to make is that when I mess up my stock rom version 10.0.9 in slot A and when I boot into TWRP it somehow get me boot into slot B with the stock rom is still in version 10.0.8. I later tried to load two different roms into two slots A and B using fastboot command to flash all the necessary images. You need to make sure you are in fastbootd (I used the recovery image from the MSM extended rom that clearly tell whether you are in fastboot or fastbootd). It turned out that I can boot into different rom in each slot. However each time I need to format the data partition again for it to boot. It was not worth the trouble unless you want to try two different roms. Now I have the stock rom in slot B and the AOSiP rom in slot A. I am now in slot B with stock rom 10.0.9.
tknguyencsu said:
I boot into TWRP to change slot, even though you can do it through fastboot. The point I would like to make is that when I mess up my stock rom version 10.0.9 in slot A and when I boot into TWRP it somehow get me boot into slot B with the stock rom is still in version 10.0.8. I later tried to load two different roms into two slots A and B using fastboot command to flash all the necessary images. You need to make sure you are in fastbootd (I used the recovery image from the MSM extended rom that clearly tell whether you are in fastboot or fastbootd). It turned out that I can boot into different rom in each slot. However each time I need to format the data partition again for it to boot. It was not worth the trouble unless you want to try two different roms. Now I have the stock rom in slot B and the AOSiP rom in slot A. I am now in slot B with stock rom 10.0.9.
Click to expand...
Click to collapse
Oh, so you're having two different ROMs installed?
Then Macusercom is right, if we're able to decrypt then we should be able to boot into the other ROM without formating?
Sorry if I'm confused btw, I'm still also new to this whole thing.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Oh, so you're having two different ROMs installed?
Then Macusercom is right, if we're able to decrypt then we should be able to boot into the other ROM without formating?
Sorry if I'm confused btw, I'm still also new to this whole thing.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Even if we 're able to decrypt I still think we need to format the data since the two different roms will not have the same apks in them. The two slots A and B share the same data partition (even though they have their own recovery) so we cannot have two independent roms.
interesting topic!
I was on Global 10.0.7 on my HD1900... was able to boot into my HydrogenOS on the other partition...
After updated to 10.0.9, I can't boot into the other paertition anymore... I got boot loop. ?
Silly me... suppose go update the HydrogenOS first... now 10.0.9 refused to let me update to the other partition of HydrogenOS 10.0.8.
Fun to have 2 systems... maybe moving forward it's impossible.
Hi everyone!
Is there somebody out there who can share a kernel backup img for 11.2.2.2 BA for flashing in fastboot? Need it to awake my bricked OP9P. Unfortunately there is still no MSM tool to bring it back to life. Which fastboot command should I use? Thanks in advance.
corneo said:
Hi everyone!
Is there somebody out there who can share a kernel backup img for 11.2.2.2 BA for flashing in fastboot? Need it to awake my bricked OP9P. Unfortunately there is still no MSM tool to bring it back to life. Which fastboot command should I use? Thanks in advance.
Click to expand...
Click to collapse
fastboot flash boot <filename>
stock boot img (BA)
patched boot img (BA)
zoman7663 said:
fastboot flash boot <filename>
stock boot img (BA)
patched boot img (BA)
Click to expand...
Click to collapse
Ok, it didn't work. So something else must have happened. So now I have to wait for an MSM tool. Hopefully one will come soon. Thank you anyway
corneo said:
Ok, it didn't work. So something else must have happened. So now I have to wait for an MSM tool. Hopefully one will come soon. Thank you anyway
Click to expand...
Click to collapse
No problem. What happened? Did you try to change slots on fastboot?
zoman7663 said:
No problem. What happened? Did you try to change slots on fastboot?
Click to expand...
Click to collapse
Yes, I tried that. Changing the slot also works. But then I don't get any further. The device always ends up in fastboot. I was a little curious and tried to undervolt gpu a bit on max frequency with KonaBess. The backed up stock image cannot be restored and that is the result. It doesn't work with the extracted boot.img from the official package either. Only the MSM tool seems to help. I do not know how to continue
corneo said:
Yes, I tried that. Changing the slot also works. But then I don't get any further. The device always ends up in fastboot. I was a little curious and tried to undervolt gpu a bit on max frequency with KonaBess. The backed up stock image cannot be restored and that is the result. It doesn't work with the extracted boot.img from the official package either. Only the MSM tool seems to help. I do not know how to continue
Click to expand...
Click to collapse
Gotcha, I tried messing with that also and couldn't get it to work. Changed slots and had to reflash full update package to restore slot to functioning again. I think it has something to do with the vendor_boot.img. But even with that pulled from the update zip I couldn't successfully fastboot flash that either and just reflashed the ROM.
zoman7663 said:
Gotcha, I tried messing with that also and couldn't get it to work. Changed slots and had to reflash full update package to restore slot to functioning again. I think it has something to do with the vendor_boot.img. But even with that pulled from the update zip I couldn't successfully fastboot flash that either and just reflashed the ROM.
Click to expand...
Click to collapse
Can I maybe ask for instructions? I just want to get the device working. Could you maybe write a short how-to please?
corneo said:
Can I maybe ask for instructions? I just want to get the device working. Could you maybe write a short how-to please?
Click to expand...
Click to collapse
I understand your pain, but if you already switched slots in fastboot and the device doesn't boot from either slot unfortunately I don't have any suggestions. I'm pretty sure without TWRP or the device booted into the OS there isn't a way to flash the ROM zip, until a fastboot flashable ROM is made or MSM tool is available.
Edit: I guess you could fastboot flash the various partitions from a payload dump of the ROM. But honestly I'm not sure what partitions are actually compromised from the KonaBess attempts. My guess is the vendor_boot.img (which is what gets backed up when you choose that in the app), but I couldn't get it to flash in fastboot, I kept getting a no such partition error. Which is funny cause it's in the ROM zip.
Maybe you can try fastboot flash boot_a\b, vendor_boot_a\b [file-path]. Try at your owm risk.
Ok, it worked. I flashed vendor_boot partition again (without a/b) and it boots now. Thanks for the quick and friendly help.
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
I incorrectly assumed vendor_boot and boot would be the same .img and now i cannot leave fastboot mode.
It can I flash the European version over global?
I was basically fine changing the voltage but after getting a stable UV I got greedy for a higher clock frequency.
deadzombieseverywhere said:
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
I incorrectly assumed vendor_boot and boot would be the same .img and now i cannot leave fastboot mode.
It can I flash the European version over global?
I was basically fine changing the voltage but after getting a stable UV I got greedy for a higher clock frequency.
Click to expand...
Click to collapse
Yes. EU version was tested by other members and will work. You can at the very least use it as a temporary measure.
deadzombieseverywhere said:
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
(...)
Click to expand...
Click to collapse
Use the payload dumper to unpack payload.bin in the full OTA. In the output folder you will then find the vendor_boot.img. You then flash this via adb with the command "fastboot flash vendor_boot vendor_boot.img". Has worked for me
I want to thank everyone in the thread, firstly. I never thought I'd be tiptoeing into Python to get a phone working again. At the moment I'm fighting with Microsoft Visual distributions, but at least there's a path to follow.
Update: got it running and was able to dump the payload but come time to flash it says partition size unknown so I tried formatting and it wouldn't.
Time to wait for MSM I guess..
deadzombieseverywhere said:
[...]
Update: got it running and was able to dump the payload but come time to flash it says partition size unknown so I tried formatting and it wouldn't.
Time to wait for MSM I guess..
Click to expand...
Click to collapse
Have you already tried to change the slots? I switched from A to B and then flashed the vendor_boot image. Maybe try again, it could work ...
corneo said:
Have you already tried to change the slots? I switched from A to B and then flashed the vendor_boot image. Maybe try again, it could work ...
Click to expand...
Click to collapse
Yeah I tried switching slots. I tinkered with it a bit more, made sure I had the latest platform tools, tried different variations and slots. Wiped it in fastboot. Might try a different computer/usb cord tonight. But overall, I think I'm out of luck.
I finally got it running again. Had to use the AA which released today.