Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
What carrier/rom/update/etc?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Edit: then realized your replied a minute before I Uzephi haha.
Uzephi said:
What carrier/rom/update/etc?
Click to expand...
Click to collapse
Spring stock rom on the original August update
Sent from my Moto Z (2) Force using XDA Labs
Acoustichayes said:
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Click to expand...
Click to collapse
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
Spring stock rom on the original August update
Click to expand...
Click to collapse
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
Have to ask this general base question of course lol. are you trying to dirty flash or did you do a full clean install?
But in general, what Uzephi said, as this is his project. I'll let him go ahead and take over. Goodluck
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Click to expand...
Click to collapse
You using stock kernel? To get crypto changes in 4.4.101-103 added, it breaks encryption on our phones and will cause a boot loop due to Motorola's dirty code. Hopefully when Oreo ROM drops (since Google is kinda telling oems to stay upstreamed) it will fix those issues in our stock ROMs.
Uzephi said:
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
Click to expand...
Click to collapse
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Click to expand...
Click to collapse
Hard to say. Those of us that have tried hard bricked the device. Not readable via USB and wouldn't boot anything after the flash.
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Acoustichayes said:
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Click to expand...
Click to collapse
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Uzephi said:
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Click to expand...
Click to collapse
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Acoustichayes said:
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Click to expand...
Click to collapse
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Uzephi said:
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Click to expand...
Click to collapse
I know there are few devs out there working on making it work on non treble phones. Repartitioning and adding a vendor partiion wouldn't be the issue with making it work. Rather trying to get the vendor source for drivers to add to it, and if they need to be reworked to add support. I've been off for a few months with health issues so I'm still getting back into things with oreo, but that seems to be the biggest issue at the moment that I could find.
When my health is back to 100 percent within a couple weeks I will dive into work with you and aid in any way possible for this. To me, trying to get driver source and make it work sounds fun. but we are far off topic now for this post so I'll leave this here haha.
Hi all
I come from the Oneplus one where flashing has been pretty straight forward. Now I am in the possession of a Pixel 2 XL and I would like to flash some roms on it. I have read many threads on flashing on the Pixel 2 xl and it always seems to have some caveats involved. I have tried to search the internet for a good tutorial but I have not discovered one yet. In advance, I am sorry if I missed some good resource on this.
So, here is my situation: I am currently on the latest patch (February 2019) and let's assume I would want to flash HavocOS. My bootloader is unlocked and I know thaf I either have to flash TWRP or only temporarily boot into TWRP. Usually, here I would flash the Rom, gapps, and magisk. For updates I would simply dirtyflash the newest rom version. As far as I have gathered, flashing the Pixel is not that straightforward.
Does TWRP flash automatically both A and B?
Do I need to flash the rom twice? Once A and once B? Or simply flash it once?
Do I need to extract things such as vendor, radio, bootloader etc and flash that once/twice? Only for the first time or for every (dirty)flash?
I would love to learn the standard procedure on flashing the Pixel 2 XL.
Again, I am sorry if I missed some good resource on this.
Thank you for your time and your help!
Welcome to the 2 XL family.
The 2 XL is a fickle beast, which you will soon find out
There is a link for upgrading/updating the 2XL in my sig, but as usual there are many ways to skin the proverbial cat.
As far as slots; I have never manually selected a slot for ANYTHING. Not TWRP, not cust Roms, not stock Roms, not kernels, not Magisk.
Whenever I flash something, the slots are always automatically chosen by whatever I'm flashing.
I know that you CAN manually select slots, but in all the time and the hundreds of Roms, kernels, Magisk versions I've flashed, I have never manually selected a slot.
Again, there are many ways to do nearly everything related to the 2 XL, and my way certainly is not the only or absolute best method, but the step by step in my sig has always, without fail, been successfully followed by myself and many other for flashing cust kernels, cust Roms, updating stock images, rooting, fastbooting, etc.
If you ever get into a sticky situation, hit up some of the 2 XL regulars who have a wealth of knowledge individually and can fix anything collectively.
@Badger50, @clothednblack, @Pkt_Lnt, @post_mortem, @simplepinoi177, @TonikJDK just to name a few.
Thank you for your insightful comment! Very helpful!
I went through your signature and got a lot of good information.
However, I still have some questions regarding about vendor, boot, radio etc.
I found this comment in the Havoc ROM thread: https://forum.xda-developers.com/showpost.php?p=78842872&postcount=1800
Are you usually dirty flashing that way?
Thank you so much for your help!
hascherpur said:
Hi all
I come from the Oneplus one where flashing has been pretty straight forward. Now I am in the possession of a Pixel 2 XL and I would like to flash some roms on it. I have read many threads on flashing on the Pixel 2 xl and it always seems to have some caveats involved. I have tried to search the internet for a good tutorial but I have not discovered one yet. In advance, I am sorry if I missed some good resource on this.
So, here is my situation: I am currently on the latest patch (February 2019) and let's assume I would want to flash HavocOS. My bootloader is unlocked and I know thaf I either have to flash TWRP or only temporarily boot into TWRP. Usually, here I would flash the Rom, gapps, and magisk. For updates I would simply dirtyflash the newest rom version. As far as I have gathered, flashing the Pixel is not that straightforward.
Does TWRP flash automatically both A and B?
Do I need to flash the rom twice? Once A and once B? Or simply flash it once?
Do I need to extract things such as vendor, radio, bootloader etc and flash that once/twice? Only for the first time or for every (dirty)flash?
I would love to learn the standard procedure on flashing the Pixel 2 XL.
Again, I am sorry if I missed some good resource on this.
Thank you for your time and your help!
Click to expand...
Click to collapse
Thank you @Az Biker! You are the best! You don't know how flattered I am that you even kept me in mind, let alone be among that great list...I am truly humbled...
So, hascherpur, I'll answer a bit of your questions, then I'll offer you some general advice when starting up with this Pixel 2 XL (taimen) as well as some dire tips if/when you get yourself in trouble (as Az Biker had alluded, it seems with this device, it is rather "inevitable" :good: )...
TWRP (and most other flashing installation files/process [ROMs, Magisk, etc.]) actually consider and keep in mind the multi-slot possbility and have made it that, if it's called for, it will automatically patch/boot/load either/both/individual slot. You'll see many and mmaannyy others go about manually/forcibly "set[ting]" and choosing specific slots, but I, like Az Biker, in my (roughly) 16 months of using this device have never, ever found a reason to -- and, for better or worse, I've broken my taimen and my gf's walleye countless times and managed to save/recover it but completely got it bricked twice.
The time you need to extract those (bootloader, radio, vendor, etc.) is when you're updating or reparing/recovering your device. A note about that though: if you wish to manually update our device (monthly; for the security updates), the absolute best way to go about it is to download the Full Factory image direct from the Google Developer's website, and extract the files within the .zip (usually these bootloader, radio, vendor, and others totalling usually 9-ish files) into the folder that has adb.exe and fastboot.exe, modify/edit the "flash-all.bat" file/script (flash-all.sh depending on your OS) and remove the "-w" (unless you wish to "w"ipe your internal), and then run that flash-all file. Because this manner of updating essentially re-installs the /system and /vendor folders and partitions, this would actually be more of a "clean" flashing than the other methods; downloading the OTA (not Full Factory) image and manually (via adb) updating and/or modifying your device so it will take an OTA update -- which is it's own hairpulling and (imo) unnecessary process -- these methods should be considered "dirty" flashing/updating, if anything.
I'm unsure how HavocOS ROM updates and if it needs to be done within its own environment or in the recovery, but I imagine much of what I just said would still apply, at least in some manner.
Okay, some general info you would find helpful and would (hopefully) keep you from falling into some of the "pitfalls" that we've all run into and have told ourselves "...if I had only known beforehand...". There is the fact that, for all Pixels -- and I'm pretty sure any multi-slot device -- there is no more recovery partition! It now resides in & with the boot partition/image. This has thrown so many new users of Pixel phones for a loop...they're usually attempting to "flash to recovery" for 24 hours before finding this out :silly:. Then there is ALL the issues you'll run into with adb, fastboot, and platform-tools in general; When you get issues when using adb and/or fastboot, you're initial instincts is going to lead you into thinking something is wrong with the image, device, and/or commands -- and with this/our phone, many times that is not the case (believe it or not, it'll put up a flashing-type error, but it's actually the USB cord?!)! Az Biker has the best troubleshooting guide in his signature, and it holds advice that usually gets things working 90% after having issues -- some general tips to keep in mind is make sure you UPDATE the platform tools and sometimes, for some reason, you have to run the same commands/process 4-5+ times before it "...works all of a sudden, this time...!" But, basically (as Google is genius in this), as long as you have access to Bootloader Mode, then there's always hope! I've gone as far as re-formatting partitions, changing the partition type, changing the size of the partition, and even manually flashing 12+ image files after forcing the partition size to change for those image files, and I've been able to come back from it because of being able to have access via Bootloader Mode.
Now, being able to unlock the bootloader and have a custom recovery, especially considering you plan on flashing custom ROMs and/or kernels and such, IT IS BEST THAT YOU MAKE A BACKUP (NANDROID IS BEST)! I know that this isn't exclusive advice for the Pixel 2 XL, but it still bears reminding; but here's some taimen specific advice -- keep in mind that many backup processes (TWRP specifically) does not (normally*) backup the data in your /internalsd (which includes your Download, Music, Photos folders)! (*i say "normally" because there is a convoluted method I've found that actually does backup the internal sd which I do every month, which I could walk you through if you are interested...). But I believe it's the best backup method because it at least backs up the system, boot, and data partitions -- note: you don't have to replace and install the custom recovery in order to utilize it; there is always temporarily booting the twrp "image" and running it off that -- but there is also TB and the other myriad ways to backup as you see fit (I'm completely unfamiliar with HavocOS, but there might even be a backup method via its environment). The key thing is: that you make backups!
And, lastly, some specific advice for when you run into issues... Re-installing/Re-flashing the Full Factory image is always a great way to fix a lot of the issues out there -- I still remember the days of my Galaxy S5 and Motorola Droids where "flashing" would wreck and wipe all data and customizations, so I love how Google made it so that's not the case with the Pixels -- but if you find that it hasn't resolved the issue, using Deuce's script (that can be found HERE) has saved countless many in repairing and recovering our devices. One of the greatest things about it is that it manually and individually flashes each and every image file to BOTH slots! Thereby covering a lot of "little bases" that a standard flash-all script doesn't do -- the only caveat is that you'll have to additionally extract all 15+ image files from the image .zip file (that resides within the Full Factory .zip file). One last recovery bit of advice, running the command "fastboot getvar all" will provide a great deal of pertinent information about the device, to say the least! It'll be good if you wish to check and to include when requesting help...
My deepest apologies for making this as long as it is; for those who know me, sometimes I can't help myself. Well, there's really that many crazy things that would be so helpful to know at the beginning with this device as well as I type very fast and fluently (kind of as fast as I talk), so I get away from myself...In any case, thanks for reading this far, if anything, and my sincerest apologies...
Again, I'm very happy to help and so glad the Great Az Biker had thought of me to include. This is a wonderful, great device and I don't want any other! But, as with all great things and loves, it will also have its "hair-pulling" headaches...so, just take your time and read and re-read, keep some of these things in mind, and good luck to ya!
Well @simplepinoi177: How am I even supposed to answer to your post? This is an incredible resource (maybe even warrants a sticky somewhere) and I am very grateful for all the details you just shared. Thank you so much. I did not expect such a warm welcome!
I have one last question: as it turns out, I was using a Taimen before (for a few months), but did not really bother using roms. In the end this proved to be really helpful as my USB port broke. I could still charge the phone, but I was unable to access the phone through cable (no bootloader, no adb, nothing). Luckily the RMA process gave me a completely new phone.
Now I wonder: if my phone's USB port breaks, I then need to RMA it and it has a rom on it, how could I restore it to a stock-like situation? I got a new device even though the bootloader was unlocked. I guess I could flash the stock image through TWRP somehow. How would I remove TWRP without a cable though?
simplepinoi177 said:
.....
.
.
.....But, as with all great things and loves, it will also have its "hair-pulling" headaches...so, just take your time and read and re-read, keep some of these things in mind, and good luck to ya!
Click to expand...
Click to collapse
Tons of solid advice, willingness to help, and a lot of experience.
^^^^^This is why I included you in the list of great resources!
hascherpur said:
Well @simplepinoi177: How am I even supposed to answer to your post? This is an incredible resource (maybe even warrants a sticky somewhere) and I am very grateful for all the details you just shared. Thank you so much. I did not expect such a warm welcome!
I have one last question: as it turns out, I was using a Taimen before (for a few months), but did not really bother using roms. In the end this proved to be really helpful as my USB port broke. I could still charge the phone, but I was unable to access the phone through cable (no bootloader, no adb, nothing). Luckily the RMA process gave me a completely new phone.
Now I wonder: if my phone's USB port breaks, I then need to RMA it and it has a rom on it, how could I restore it to a stock-like situation? I got a new device even though the bootloader was unlocked. I guess I could flash the stock image through TWRP somehow. How would I remove TWRP without a cable though?
Click to expand...
Click to collapse
Thank you hascherpur, I appreciate the sentiment. But, as I mentioned, as much as it helps you, it helps the helpers here as well. Anyone whose worked on our taimen and walleye can attest to those few things that would save soooooo many people if they just knew these small insignificant-seeming tidbits...
I am actually in this particular situation currently myself. Me (and this other fellow) got our devices (my gf's walleye to be exact) bricked where fastboot does not recognize and detect the USB plug, even though it is charging and just because of this fact, there's nothing that can be done and only a RMA is in order... But the key difference is that my custom recovery also somehow broke. That's why, at it's base purpose, a custom recovery is meant to replace and enhance your repair/recovery options -- so you can have it in dire situations and boot it up and utilize it if needed. If my TWRP was still accessible, I would more than have a chance to repair the device.
But to answer your specific question, I imagine a data wipe/erase from either stock or custom recovery would be in order. And, depending on how particularly broken the USB port is, you might still consider and try a USB-C flash drive and attempt the OTG enabled feature. If that could still work, then I've gotten the idea that attempting to install the system via OTA update installation .zip might be able to help -- but I would have my doubts because, like I kind of stated in my last post, that's more of a "dirty flash" and I wonder how well an not-so-complete OTA update can work and establish itself when its base /system and /data partition is wiped and essentially just empty space...But, also, if even a flash drive can be read, then you should be able to use adb to move essential flashing files to the device and utilize fastboot to make repairs and re-flash (i'm unsure if fastboot can manage this off of a flash drive; i'm not even sure it has OTG capabilities...). If, at that situation, the one resource I mentioned, Deuce's script, would be great as it will flash all pertinent and important stuff if, for some reason, the flash-all can't get passed flashing certain portions like bootloader or vendor.
So that's the ideas that come to my mind as possibilities that might work...hope this helps...
simplepinoi177 said:
Thank you hascherpur, I appreciate the sentiment. But, as I mentioned, as much as it helps you, it helps the helpers here as well. Anyone whose worked on our taimen and walleye can attest to those few things that would save soooooo many people if they just knew these small insignificant-seeming tidbits...
I am actually in this particular situation currently myself. Me (and this other fellow) got our devices (my gf's walleye to be exact) bricked where fastboot does not recognize and detect the USB plug, even though it is charging and just because of this fact, there's nothing that can be done and only a RMA is in order... But the key difference is that my custom recovery also somehow broke. That's why, at it's base purpose, a custom recovery is meant to replace and enhance your repair/recovery options -- so you can have it in dire situations and boot it up and utilize it if needed. If my TWRP was still accessible, I would more than have a chance to repair the device.
But to answer your specific question, I imagine a data wipe/erase from either stock or custom recovery would be in order. And, depending on how particularly broken the USB port is, you might still consider and try a USB-C flash drive and attempt the OTG enabled feature. If that could still work, then I've gotten the idea that attempting to install the system via OTA update installation .zip might be able to help -- but I would have my doubts because, like I kind of stated in my last post, that's more of a "dirty flash" and I wonder how well an not-so-complete OTA update can work and establish itself when its base /system and /data partition is wiped and essentially just empty space...But, also, if even a flash drive can be read, then you should be able to use adb to move essential flashing files to the device and utilize fastboot to make repairs and re-flash (i'm unsure if fastboot can manage this off of a flash drive; i'm not even sure it has OTG capabilities...). If, at that situation, the one resource I mentioned, Deuce's script, would be great as it will flash all pertinent and important stuff if, for some reason, the flash-all can't get passed flashing certain portions like bootloader or vendor.
So that's the ideas that come to my mind as possibilities that might work...hope this helps...
Click to expand...
Click to collapse
Thank you simplepinoi177! Very helpful. I have also seen that it is possible to access adb via wifi. But I doubt that I am able to use fastboot via wifi.
In any case, I am deliberating what the best course of action at the moment is. It seems that the Pixel 2 XL's usb port is a common point of failure. Therefore, I am trying to make sure that I leave my phone in a state, where I can easily revert it into an RMA-able state. I think with TWRP installed, I could get the stock image easily installed. I am still not sure how to remove TWRP without a cable, should the USB port break.
hascherpur said:
Thank you simplepinoi177! Very helpful. I have also seen that it is possible to access adb via wifi. But I doubt that I am able to use fastboot via wifi.
In any case, I am deliberating what the best course of action at the moment is. It seems that the Pixel 2 XL's usb port is a common point of failure. Therefore, I am trying to make sure that I leave my phone in a state, where I can easily revert it into an RMA-able state. I think with TWRP installed, I could get the stock image easily installed. I am still not sure how to remove TWRP without a cable, should the USB port break.
Click to expand...
Click to collapse
To remove twrp without a cable, simply put the stock boot.img on your internal storage, and flash it with twrp. After you reboot, twrp will be gone.
Here's the February boot.img if your interested :good:
https://drive.google.com/file/d/1khLnNH7emt38sDsD7UmKX3HJG3lhxdXQ/view?usp=drivesdk
Badger50 said:
To remove twrp without a cable, simply put the stock boot.img on your internal storage, and flash it with twrp. After you reboot, twrp will be gone.
Here's the February boot.img if your interested :good:
https://drive.google.com/file/d/1khLnNH7emt38sDsD7UmKX3HJG3lhxdXQ/view?usp=drivesdk
Click to expand...
Click to collapse
Oh, thanks! I guess I am all set . Thanks to everyone for the very helpful answers!
Badger50 said:
To remove twrp without a cable, simply put the stock boot.img on your internal storage, and flash it with twrp. After you reboot, twrp will be gone.
Here's the February boot.img if your interested :good:
https://drive.google.com/file/d/1khLnNH7emt38sDsD7UmKX3HJG3lhxdXQ/view?usp=drivesdk
Click to expand...
Click to collapse
genius idea! I was actually asking myself that question, and this is a great set up. But, usually, if I'm in so much trouble that I need to return it to stock recovery that urgently, the device most likely is probably so messed up that it probably wouldn't be able to read/find the boot.img I would keep in the sdcard storage...
simplepinoi177 said:
genius idea! I was actually asking myself that question, and this is a great set up. But, usually, if I'm in so much trouble that I need to return it to stock recovery that urgently, the device most likely is probably so messed up that it probably wouldn't be able to read/find the boot.img I would keep in the sdcard storage...
Click to expand...
Click to collapse
You gotta approach this stuff like the first part of your name my friend. Take it from an old guy...."Simple" is good! :laugh::good:
Deuces script will synch your a and b sides so you don't need to worry about them getting weird.
madscribblerz said:
Deuces script will synch your a and b sides so you don't need to worry about them getting weird.
Click to expand...
Click to collapse
That is precisely why I use it every month.
So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.
@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.
@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.
I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.
Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers
I was thinking about purchasing a Google Pixel XL due to the reasonable specs and good rom support. But I was just wondering if the device was treble supported before I decided to buy anything as it would help me out quite a bit. Also I am quite the enthusiast when it comes to custom roms and stuff.
If anyone has an answer i will be very grateful.
Thanks.
Sent from my Samsung Galaxy A20e (SM-A202F/DS)
Got this
Check attached photo. I have been playing with one of these for a bit. I loaded up TWRP followed with the latest Resurrection Remix and the phone is so fun to use.
mindlery said:
Check attached photo. I have been playing with one of these for a bit. I loaded up TWRP followed with the latest Resurrection Remix and the phone is so fun to use.
Click to expand...
Click to collapse
How did you flash it? I've been trying to flash phh and lineage but it won't boot at all. Tried in both TWRP and fastboot.
Sorry i was not clear about my message. I'm not using any GSI images. I am using https://forum.xda-developers.com/pixel-xl/development/unofficial-resurrectionremix-8-5-8-t4149771
I used to flash a lot of GSI's on another model and often i would need patches, custom kernel and some needed a clean flash of one first to get what i wanted after. I really like this ROM, but i have no problems going to stock if i screw up, which i will. So i'll go see if i can get a gsi on top of Rrmix. I'll be back.
I tried a couple gsi's and twrp gives a partition size error. (Too small).. What methods other than factory resetting and trying to install have you tried?
Pretty sure the version of TWRP used is specific. I tried RR with 3.4 and it was a mess. Now i'm using 3.2.3.1 and things are not perfect, but close enough for me.
mindlery said:
I tried a couple gsi's and twrp gives a partition size error. (Too small).. What methods other than factory resetting and trying to install have you tried?
Pretty sure the version of TWRP used is specific. I tried RR with 3.4 and it was a mess. Now i'm using 3.2.3.1 and things are not perfect, but close enough for me.
Click to expand...
Click to collapse
TWRP 3.4.0.0 is only good because it brings decryption support - there's also a fork of 3.3.0.0 by NZedPred on the regular Pixel forum (but the port is built for the XL too) which brings the best of both worlds, 3.4.0.0 decryption and 3.2.3.1 stability.
The small system partition is a known problem with our Pixels, there are repartitioning scripts ... but here be dragons.
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.