I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
KingAroan said:
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
Click to expand...
Click to collapse
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
mac796 said:
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
Click to expand...
Click to collapse
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
KingAroan said:
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
Click to expand...
Click to collapse
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
mac796 said:
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
Click to expand...
Click to collapse
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
No there the same. You can put whatever on either one. There for normal use. seamless updates they call it I believe.
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
robocuff said:
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
Click to expand...
Click to collapse
Holy ****, i didnt know that part, i just thought it flashed it to your current slot and when you rebooted into system, the slot didnt change.....brb but first a quick titanium backup
UPDATE: SOLVED! Flash snoke R10 kernel in TWRP, reboot back into TWRP, flash Magisk 15.2 zip. Had to do this as manually attempting to patch system.img wasn't working.
I was successfully unlocked and rooted on the November 8.0 factory image. I have a Pixel 2 directly from Google and using it on Verizon.
I just wiped and went clean to the latest Jan 2018 factory image.
I grabbed the latest Magisk, 5.5.2, and installed the apk. So far so good.
Magisk opens fine, and I've tried changing the update stream to Beta. I have the system.img to patch on my sdcard. Whenever I tell Magisk to patch the image, it looks like it processes for a bit. But then Magisk crashes. I've repeated this several times and have even tried rebooting. No go.
Any ideas? My understanding is that you don't *need* snoke kernel. I'm not sure if with the latest images you must do this in TWRP. For the November update I didn't need to go into TWRP at all. You'd simply patch system.img, boot into fastboot and fastboot flash boot <image_name>
You may try to install Magisk without having a manual patch and let it do everything on it's own. I updated to the Jan patch, reflashed TWRP, custom kernel, booted normally. Uninstalled old Magisk Manager, reinstall magisk manager (latest) and allow it to do whatever it needs with the automatic methods and I didn't have any issues after that.
Update. I got it working. Flashed Snoke 10 kernel in TWRP. Then rebooted back into TWRP and flashed the Magisk 15.2 zip. All good
For anyone who get boot loop, missing wifi, root lost after January boot image patch, here solution for that.
I did the following steps and did not find any problems with my MI A1 until now.
- You must reflashing rom again with xiaomi flash tools, and must choice clean flashing and lock, remember your data will be wipe.
here's link download N2G47H.7.12.29 (Android O) 1084 MB (28 Desember 2017 Patch) ;
http://bigota.d.miui.com/7.12.29/tis...c9a6ea979b.tgz Update : Miui was delete this rom
- After flash finished, wait to update January security patch from OTA, then update until finish and restart your device.
you must see your firmware now is OPR1.170623.026.8.1.10 with 01 Jan 2018 security patch
- Install latest version of magisk manager , you can get it at official magisk page, if finished reboot your device to fastboot mode.
- Now you can unlock you device and root with patched_boot.img as explained earlier in this thread :
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
- After restart, open magisk manager, install with direct install then reboot your device.
Now you have root and to prove root is not lost after reboot, you can try to reboot your devices several times.
Ok so I was on oxygen 5.1.6 and I downloaded the update for 5.1.7. I booted into twrp flashed it booted up and was in 5.1.7. I boooted back to twrp and made a backup. I booted after backup and phone went back to 5.1.3. WTF?! I had to reflash the update, reinstall the twrp installer zip and root once again. I also noticed that If u change slots you will boot into the unrooted version of your rom and the other is the rooted version. What's the deal with the two slots in twrp. I can see where in the future this will have advantages but it's kind of confusing at the moment. Does anyone know why my phone went back to 5.1.3 after a backup and can anyone explain why there is two slots now and the sole purpose of them within twrp.
I thought twrp and magisk flashed both slots?
a/b partition is just for /system iirc
a/b partition exists for all the partitions as seen in /dev/block/platform/soc/1d84000.ufshc/by-name. When you updated from 5.1.3 (let's say slot a) to 5.1.6, it updated 5.1.6 to slot b and set it as the active slot. When you updated 5.1.7 via twrp, I think it just writes over your current active slot (which is also b), so my guess is you updated slot b to 5.1.7 and slot a is still 5.1.3. Not sure how your active slot switched after booting into 5.1.7, but that's my best guess as to what happened.
If you take the OTA normally, the phone will write to the inactive slot and overwrite boot.img as well as all the other partitions, then set the active partition to the new slot
So I got my new Pixel 3 the other day and I'm trying to root it
I unlocked the bootloader
I downloaded the latest version of Magisk Manager, got the boot.img for my device and android version (can confirm it works as i've flashed it to boot and it works fine)
I patched the boot.img with Magisk Manager
Then I flashed magisk_patched.img to boot in boot slot b (so i can still use a while troubleshooting, as i daily drive this phone now)
It flashed ok, but when I boot from slot b it gets as far as the G logo with the progress bar under it, and gets no further, it just stays there until i force shutdown the phone
Slot a still boots perfectly fine but theres ofc no root
I've looked everywhere and i can't figure out what's wrong