yashsingh1/xdaforums huggingface dataset:
[XDA Assist] Partyking125:
As title says, cant exit screen where it says

recovery booting (in blue)

recovery is not seandroid enforcing (red)

set warranty bit : recovery (yellow)

i try to boot it into recovery mode and just goes straight back to this screen no matter what i do, pretty sure there is no way to flash a rom because i cant get to download mode... please help i just brought this phone recently and really don't have the money to buy another phone again :crying:

used the first method that came up when searching root gs5, from tomshardware, is the 900i verson
[XDA Assist] xanthrax:
Hi !

This tutorial is for a different s5 variant but it should work and you must chose the correct firmware for your asian variant

https://xdaforums.com/showthread.php?t=2785185

Read properly before proceeding and don`t jump into first website you see on internet , with this smartphones there is no "one click solution" , lot of reading is required if you don`t want to throw money in the wind

Good luck !
[Google Pixel XL Questions & Answers] YellowSnowman23:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.

Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???

I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.

Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?

* Yes my platform-tools are up to date.

* Yes I watch it flash everything till the end with out fail.
[Google Pixel XL Questions & Answers] cntryby429:
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
[Google Pixel XL Questions & Answers] V40:
then you saw that flash-all.bat flashed both slots :o
[Google Pixel XL Questions & Answers] canemaxx:
Doesn't flash to both slots on mine
[Google Pixel XL Questions & Answers] DaveHTC200:
I believe it flashes to one slot and deletes the data on the other as standard
[Google Pixel XL Questions & Answers] Golf c:
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.

One data slot shared by A + B

Slot A & B have separate partitions for

-Vendor

-Bootloader

-Radio

-Modem

-Boot

-System

Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.

Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
[Google Pixel XL Questions & Answers] TonikJDK:
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
[Google Pixel XL Questions & Answers] 5.1:
Hello,

This makes me think:

With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.

So there will be two different bootloader anyway, no? :)

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
[Google Pixel XL Questions & Answers] 5.1:
Hey,

I started fresh before Pure Nexus and flashed NHG47K to both slots.

Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.

Switched a to b and booted stock. Switch back on a and back to PN...

Of course i'm no expert or developer either.

Where I agree is that custom could create problems I don't know either.

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Maybe I'm doing it the wrong way then :P

Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.

Check this: https://postimg.org/gallery/2muhcz91o/

Slot a is PN, slot b is stock NHG47K.

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

If I do it, i sincerely don't know how or when...

By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.

Well, I guess I'll have to install my phone over again...

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
Delete

---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------

Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

I did it just to show something to someone earlier. I don't need dual boot either...

One ROM is enough in my opinion.

Ok, time to hit the bed. See you later...

Cheers...
[Google Pixel XL Questions & Answers] TonikJDK:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.

This is a fancy update system, just like Chromebooks and iPhones.
[Google Pixel XL Questions & Answers] Golf c:
And I don't even use it because I have never taken an OTA. lol!
[Google Pixel XL Questions & Answers] canemaxx:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
[Google Pixel XL Questions & Answers] TonikJDK:
No need since it ia working but you get into Fastboot mode then

Fastboot set_active a

Flash L, flash April bootloadee.
[Google Pixel XL Questions & Answers] xocomaox:
Just an FYI... The chances people are flashing custom firmwares with TWRP to the same slot constantly is highly unlikely.

The reason being is that when you flash a firmware with TWRP, it ALWAYS flashes to the inactive slot, then changes that slot to the active one. So if you are running slot B and decided to do a factory reset wipe and flash another firmware, you'll then be on slot A. Switching slots in TWRP is pretty easy, but requires you to reboot into recovery after you do it. This is why you sometimes have to flash the updated vendor image after flashing custom firmware and rebooting because it's already changed slots on you...
[Google Pixel XL Questions & Answers] Golf c:
Several people are claiming to be doing just that. Everytime they flash a rom, they switch slots first, then flash rom and twrp. So they are always running in the same active slot. I think it's a recipe for disaster if they have old bootloaders in the inactive slot. I myself keep both slots identical at all times, this way I always know what is in both slots. I constantly switch slots when flashing custom roms with maybe flashing different vendors as needed.
[Google Pixel XL Questions & Answers] 5.1:
Hello,

I have to disagree here...

I flashed both a/b NHG47K before Pure Nexus. And I can assure you each time i install a new iteration of Pure Nexus, it does it on the same slot...

I still have stock NHG47K on the other slot. And I swear i installed Pure Nexus more than once since.

Check the attached screenshots. I did those yesterday to show someone the same thing... But I guess you must have seen it if you have read the previous posts: https://postimg.org/gallery/2muhcz91o/

My setup: Pure Nexus, TWRP rc1 installed, EX Kernel, SuperSU.

Every time I update, i clean install. Wipe everything, except internal storage. And reinstall directly... The only thing I do is reboot TWRP in case I need to install a new vendor image.

Cheers...
[Google Pixel XL Questions & Answers] xocomaox:
I'm not sure what these screenshots are supposed to show. Looks like you have the same vendor image for each... The only thing that appears to be different is the kernel and the baseband..?

I noticed you're still using the older version of TWRP. That might be the big difference as everyone is using RC2 now.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

The only difference is the white shots are stock NHG47K firmware on one slot.

The black themed one is Pure Nexus on the other slot.

It doesn't "look like" I have the same vendor. As I said I first flashed both slots stock NHG47K...

Maybe TWRP RC1 is the culprit as you say. I'm gonna retry with RC2 and report back. :good:

Cheers...
[Google Pixel XL Questions & Answers] pcriz:
I have always had an older bootloader in my inactive slot. In fact right now my bootloader is from the 7.1.1 March update in that slot. The only issue I am having is that if I boot OS on that said data is all wonky which is normal.

I don't see how it could brick the device if both bootloaders work from the start, they operate independently of one another so me booting up the march BL because I switched slots has little to do with the other slot with the may bootloader.
[Google Pixel XL Questions & Answers] Golf c:
From my point of view, for me it's best practices to flash both slots identically so I know exactly what I have. I noticed people are doing it a few different ways. To each his own. Whatever works. I don't follow hard bricks to closely but I remember some taking OTA'S and switching slots and somehow corrupting the bootloader. It just seems to me alot of folks haven't a clue what's in their slots.
[Google Pixel XL Questions & Answers] pcriz:
If both slots are flashed successfully I don't see how one BL could corrupt another. That defeats the purpose of partitions. The few bricks (don't like saying hard or soft, a soft brick ain't a brick) I have seen were caused by issues during the flash that corrupted or screwed up the current bootloader so fastboot couldn't be used to switch slots to the good one or flash factory data.

Ultimately do what makes you comfy but for clarity some less seasoned users will take "mismatch bootloaders cause bricks" as gospel when until it's substantiated it may not be true.

Nevermind that most people, given how the factory images load will be flopping between slot a and b and thus flopping between two bootloaders if they flash ROMs and don't manually flip slots.
[Google Pixel XL Questions & Answers] canemaxx:
I get a message when flashing image that says Remote: partition can not be determined. What is that all about?
[Google Pixel XL Questions & Answers] pcriz:
That's weird. I'd say make sure adb fastboot is updated. I'll try to research it. I saw your pm but my xda labs fcs when I try to open messages.
[Google Pixel XL Questions & Answers] canemaxx:
No worries. Any info would be appreciated
[Google Pixel XL Questions & Answers] xocomaox:
How are you flashing the firmware?

Typically this is when you are trying to flash something to a partition that doesn't exist (usually older ADB drivers will reference partitions that are not valid). Give us some more of what is spitting out in the log so we can determine what actually failed right before that message.
[Google Pixel XL Questions & Answers] Glsoto:
So, if you want the stock image in both slots, you need to Run the flash.bat command in both of them (a + b), How do you switch slots,
[Google Pixel XL Questions & Answers] pcriz:
fastboot --set-active=_a (or _b)
[Google Pixel XL Questions & Answers] Glsoto:
Thank you. :o
[Google Pixel XL Questions & Answers] admiralspeedy:
For the record, when you use flash-all it flashes blank images to the second slot. I tested it by trying to flash both, first a, then b and if I switched back to a, the phone simply booted into the RAM dump thing over and over.
[Google Pixel XL Questions & Answers] Golf c:
The only thing that's flashed to the inactive slot is System_other.img in the system slot. Im not sure what this is for but in my one attempt, it would not boot. The rest of the inactive slot partitions would contain whatever was there when it was last active. Radio, vendor, modem etc...
[Google Pixel XL Questions & Answers] pcriz:
There is nothing bootable there because its not being used until the device gets an update at which time then it installs and once the install is complete it swaps to that slot on the next reboot.

Imagine if we could fully utilize the seamless update process, we could install updates to roms without ever leaving the OS. Just follow up with a reboot.
[Google Pixel XL Questions & Answers] admiralspeedy:
If you watch the script output, yes it flashes what I am assuming is a blank system image or something to the opposite slot, so if you try to boot on that slot it just goes to the RAM dump thing. Realistically, it shouldn't matter what other images are there but I would try to make sure they are same, so I flashed the newest factory image over both slots, then re-flashed the April bootloader on both slots manually, and then I wiped the slot that had the actual system image on it, switched slots and flashed my custom ROM so that it was in the wiped slot.
[Google Pixel XL Questions & Answers] Golf c:
So its really like a place holder. When a OTA installs, it wipes that System_other.img and replaces it with the new system.img. Then the inactive system slot get another placeholder system_other.img.
[Google Pixel XL Questions & Answers] pcriz:
Without looking at an OTA zip at the moment I assume that is exactly what happens.
[Google Pixel XL Questions & Answers] Golf c:
I think so, its similar in that regard to flashing the factory image.
[Google Pixel XL Questions & Answers] pcriz:
That also explains why users running stock rooted still took updates. The OTA runs a hash check on system but I think it's the inactive slot so if the check passes (because its that blank system image) it will allow the OTA to load, switch slots and the user ends up on a newer version without twrp and root, where as in the past updates would fail
[Google Pixel XL Questions & Answers] canemaxx:
That could be the issue, do you have a link to the latest drivers?
[Google Pixel XL Questions & Answers] 5.1:
Hello,

Google?

https://www.google.fr/search?q=plat...70j0j4&sourceid=chrome-mobile&ie=UTF-8#xxri=0

First link by the way...

Cheers...
[Google Pixel XL Questions & Answers] canemaxx:
Thank you ....and for just for the record I did Google it and I had the March version which in my search said it was the latest. Again thank you I will update and see if that fixes it
[Google Pixel XL Questions & Answers] 5.1:
Hey,

I'm not blaming you. Sometimes i also search things i don't find.

Hopefully this one fixes your issue... :)

Cheers...
[Google Pixel XL Questions & Answers] Glsoto:
To flash the factory image to both slots, did you run the flashall.bat command in both slots..??? first in slot A and the did you use fastboot commands to change active slots, and then flash the stock image in the other slot.???
[Google Pixel XL Questions & Answers] pcriz:
But if it flashes a blank system img to the other slot doesn't that kind of defeat the purpose?
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Then what happens if he accepts an incremental OTA with modified partitions on the inactive slot? Just in case?

Also, I already flashed both and booted both. So I'm not sure it really flashed a blank system.img. I guess the system_other is a different partition.

Edit: I'm going to build PN this weekend and do some testing with factory images. Trying to understand exactly what is going on under the hood.

Cheers...
[Google Pixel XL Questions & Answers] admiralspeedy:
I would assume the OTA wipes the other slot before it does anything, so it shouldn't matter.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Wipes what? The incremental is usually a small piece of software. How maybe a 200mb OTA would fulfill a 1gb system partition? Or I misunderstand you..?

Cheers...
[Google Pixel XL Questions & Answers] pcriz:
It may fail I can only assume if it does run a hash on that partition but I am only guessing.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Yeah, hopefully. For safety purpose, i would flash both though. It cost me five minutes and I don't have to fear further issues. But that's just me.

Could be unnecessary. But until i fully understand how it works, my OCD orders me to do it! :angel:

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
I don't know how the OTA exactly works, but when you flash the factory image to both slots your filling your a&b partitions with identical images on both slots.

-Radio

-Boot

-Bootloader

-Modem

-Vendor

The system image is different. It gets flashed to the current active system partition and the system_other.img gets flashed to the current inactive system partition. So when you flip slots in fastboot, the the system.img and system_other.img just flip. Then all other a&b partitions are identical. See above. I haven't seen an explanation as to what the system_other.img function is? Just seems to be a non-bootable placeholder till you switch slots and install a bootable system.img
[Google Pixel XL Questions & Answers] 5.1:
Hey,

As far as I understood a/b was done the way if a slot gets corrupted, after a few attempts, it would boot on the other slot.

But how could it boot on the slot b if for example system on slot a is corrupted and the system was just flipped onto b?

The more i think about it, the more i get lost... :eek:

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
I don't know, all I can say is I tried booting system_other.img and it wouldn't boot.

Edit: I haven't tried to boot that in 5 months, I believe it just kicked me back to the active slot with the real system image. Thats the way Google designed it I believe. Somebody correct me if my memory failed? What your doing with both slots is what I do only manually. I know exactly whats in both slots at all times.

---------- Post added at 11:51 PM ---------- Previous post was at 11:23 PM ----------

@5.1

I just thought of something else. Lol. In your scenario it won't matter. It will be a soft brick. If your bootloader isn't corrupted just boot into bootloader, unlock if locked, flash factory image. I hope we're all unlocked and stay unlocked? Other than that, if your bootloader is corrupted, Google hard brick.
[Google Pixel XL Questions & Answers] 5.1:
Hey,

Of course, I left my bootloader unlocked as long as i own a Google phone I don't see any reason not to. I leave OEM unlocking disabled though, so FRP works...

I'm going to search a bit again this weekend and play with the same factory image on a/b. Modify a few things on system partitionon and see if it applies to the other slot.

Cheers...
[Google Pixel XL Questions & Answers] Golf c:
Let us know if you come up with anything profound?
[Google Pixel XL Questions & Answers] Glsoto:
Yes , please let us know. I returned to stock (May factory image) , after a lot of trial and errors. in slot A, then I switch to slot B, and everything went OK. But now I am scared to installed a custom ROM again, or TWRP. I do not get this slot Stuff at all...Thank you
[Google Pixel XL Questions & Answers] 5.1:
Hello,

So i flashed latest May N2G47O on slots a/b. Booted twrp on b, installed SuperSu 2.79 SR3, used Chaifire boot signer v2 and booted system. Went back to recovery, deleted Chrome folder from /system/app/ with twrp file manager and rebooted to be sure it is gone for good.

Rebooted in bootloader, switched to slot a. Rebooted system... Ram dump :P

Finally, i booted twrp while in slot a and got into /system/app/ with twrp file manager

And this is what i got:

/system/app and /system/priv-app have usual apps folders only filled with odex files.

While being in slot b (the one i flashed factory imge in second position) i had this:

Which is the system i got used to when flashing a stock firmware on previous Nexus devices... /system/system/app and /system/system/priv-app are filled with apps APKs only...

Noticed the difference in file directories?

/system/ <-- on what appears to be system_other or inactive slot

/system/system/ on active slot

So, i think i previously got fooled thinking i had two proper system partitions when i booted PN on one slot and stock on the other one. I flashed NHG47K on a/b. I think i just installed Pure Nexus on the slot that contained the empty /system (system_other) as seen on the first screenshot. This way, the other slot still had a full stock firmware and proper /system/system partition installed, allowing me to boot both.

So, [MENTION=6302926]Golf c[/MENTION], you were kind of right when you said (i guess) that system partition switches during OTA. At least a part of it.. What happens in the background during the OTA, what moves and where, is out of my scope. Sorry, i'm not a computer engineer or tech either...

It was fun, but now i have to clean flash this mess again :)

Cheers...
[Google Pixel XL Questions & Answers] pcriz:
That's part of the reason they switched to this file structure because it allows for the seamless updates. I think we lose perspective because most of us aren't taking OTAs but it only makes sense it would download and make the changes to the inactive partition so it doesn't affect your user experience.
[Google Pixel XL Questions & Answers] Glsoto:
Thank you for sharing with us !!, so it does not make any sense to install stock images. on both slots..??, one deletes the other... So if you are in Slot b and installs a custom ROM, that ROM installed in Slot A..? and Slot B leaves a stock Rom intact..???. Also how do you manage to install TWRP with May factory image.?? Dis you fast boot April boot loader.??

Thank you for your Help..