[Discussion] Dual booting with TWRP - Google Pixel 2 XL Guides, News, & Discussion

Hey all --
I found a discussion arising in the LOS beta thread about dual-booting with TWRP. The idea was that since our devices have separate A/B partitions for 'seamless updates', that we could potentially take advantage of this system to boot 2 separate ROMs from within TWRP.
Apparently this has been done with the original Pixel, and I found a guide here: https://ausdroid.net/2017/02/20/goo...tions-use-it-to-deliver-dual-booting-*****es/
I'm thinking of giving it a shot this weekend, but if anyone would like to giving it a go before me make sure to report your results and procedure here!

TheNightman said:
Hey all --
I found a discussion arising in the LOS beta thread about dual-booting with TWRP. The idea was that since our devices have separate A/B partitions for 'seamless updates', that we could potentially take advantage of this system to boot 2 separate ROMs from within TWRP.
Apparently this has been done with the original Pixel, and I found a guide here: https://ausdroid.net/2017/02/20/goo...tions-use-it-to-deliver-dual-booting-*****es/
I'm thinking of giving it a shot this weekend, but if anyone would like to giving it a go before me make sure to report your results and procedure here!
Click to expand...
Click to collapse
Keep in mind there is only one user partition. So both slots have to be running pretty much the same thing. You won't be able to run stock on one and a custom ROM on the other. One rooted and on not is about as far as you will get.
We went pretty far down this rabbit hole with the OG pixels and it lead no where.

TonikJDK said:
Keep in mind there is only one user partition. So both slots have to be running pretty much the same thing. You won't be able to run stock on one and a custom ROM on the other. One rooted and on not is about as far as you will get.
We went pretty far down this rabbit hole with the OG pixels and it lead no where.
Click to expand...
Click to collapse
Oh damn...
Still, one stock and one rooted would be kinda cool...
Sent from my Pixel 2 XL using Tapatalk

slaydog said:
Oh damn...
Still, one stock and one rooted would be kinda cool...
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Now with Xposed working on 8.1, it would be great to have one slot with Xposed and its modules and the other with a passing SafetyNet.

mnrivera210 said:
Now with Xposed working on 8.1, it would be great to have one slot with Xposed and its modules and the other with a passing SafetyNet.
Click to expand...
Click to collapse
Yes I could see myself using that setup.

Dual booting Pixel 2XL with TWRP
TonikJDK said:
Keep in mind there is only one user partition. So both slots have to be running pretty much the same thing. You won't be able to run stock on one and a custom ROM on the other. One rooted and on not is about as far as you will get.
We went pretty far down this rabbit hole with the OG pixels and it lead no where.
Click to expand...
Click to collapse
Hmm . . in fact I WANT to have the data shared but I would like an unlocked, rooted, TWRPed, Magisked stock in say Slot A and unlocked, rooted, TWRPed, Magisked Google Beta / update in Slot B - that should work shouldn't it?
For example, today I updated to PPP2.180412.013 (and had to reinstall TWRP and Magisk) but then I found a number of apps "xxx keeps stopping" . .
So I would like to test the updates but have a quick fall-back that will work immediately and only continue to use the updated slot when I am confident everything is 100%.
That would be an extremely nice situation!
Thanks!
Phil.

Is there sufficient Interest in a Guide on how to do Dual Boot and discussion there to ?

Perseus said:
Is there sufficient Interest in a Guide on how to do Dual Boot and discussion there to ?
Click to expand...
Click to collapse
Yes

Related

To root or not to root

My hat goes off to hauwei and Google for building this handset.
I have been using a galaxy s6 for the past year rooted and tweaked to the best of my knowledge and what could be mustered with the closed source and exynos7420. I have been using the 6P for two days and honestly I'm considering something I thought I wouldn't try...... Stock no root. I have always rooted my devices and played round with them built a popular rom back in the gt540 days but this phone this beast I'm actually considering stock.
So my question currently cyanogenmod shows nightly builds but no stable builds, so unofficial at best and it looks to be the same for a lot of other roms as cm seems to be the major base for 90% of roms now, so what are currently the advantages of these builds or the builds based off stock?
Obviously there is adaway and Xposed and viper4android but in terms of build performance battery life and stability is it worth moving off stock atm?
Sent from my Nexus 6P using Tapatalk
Bump[emoji14]
Sent from my Nexus 6P using Tapatalk
Danzano said:
My hat goes off to hauwei and Google for building this handset.
I have been using a galaxy s6 for the past year rooted and tweaked to the best of my knowledge and what could be mustered with the closed source and exynos7420. I have been using the 6P for two days and honestly I'm considering something I thought I wouldn't try...... Stock no root. I have always rooted my devices and played round with them built a popular rom back in the gt540 days but this phone this beast I'm actually considering stock.
So my question currently cyanogenmod shows nightly builds but no stable builds, so unofficial at best and it looks to be the same for a lot of other roms as cm seems to be the major base for 90% of roms now, so what are currently the advantages of these builds or the builds based off stock?
Obviously there is adaway and Xposed and viper4android but in terms of build performance battery life and stability is it worth moving off stock atm?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
CM definitely isn't the base for most (or even a small percentage) of ROMs on a Nexus, most ROMs are based on the official aosp source. Most ROMs that I've tried are as stable as stock. What are the advantages? Added features. You're probably better off of gaining extra features via a custom ROM with those features built in, than gaining them by adding Xposed modules to the stock ROM. If you need instructions on unlocking/flashing/rooting this device I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
PS. As per the rules, please only bump a thread once every 24 hours, it had only been exactly 94 minutes in this case.
Heisenberg said:
CM definitely isn't the base for most (or even a small percentage) of ROMs on a Nexus, most ROMs are based on the official aosp source. Most ROMs that I've tried are as stable as stock. What are the advantages? Added features. You're probably better off of gaining extra features via a custom ROM with those features built in, than gaining them by adding Xposed modules to the stock ROM. If you need instructions on unlocking/flashing/rooting this device I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
PS. As per the rules, please only bump a thread once every 24 hours, it had only been exactly 94 minutes in this case.
Click to expand...
Click to collapse
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Danzano said:
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, Nexus devices do not have any sort of flash counter. Though, during the first 1-2 months of the 6P release, rumor had it that the phone has a blowable QFuse, which would be irreversible if you unlock the bootloader.
However, later on the skepticism was wiped away, and it was clarified that nothing as such exists. Yes, the QFuse exists, but its completely unrelated.
Danzano said:
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No flash counters or anything like that on the Nexus, never has been and probably never will be. It is first and foremost a development device, it just happened to catch on in the mainstream too. If you have any questions don't be afraid to ask, we have a great community of people helping out in the guide thread.
DJBhardwaj said:
No, Nexus devices do not have any sort of flash counter. Though, during the first 1-2 months of the 6P release, rumor had it that the phone has a blowable QFuse, which would be irreversible if you unlock the bootloader.
However, later on the skepticism was wiped away, and it was clarified that nothing as such exists. Yes, the QFuse exists, but its completely unrelated.
Click to expand...
Click to collapse
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Danzano said:
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Click to expand...
Click to collapse
My advice: don't use a toolkit. They can make things easier sometimes but easier isn't always a good thing. They've been known to cause issues, and there's really no substitute for ensuring things go right by doing it yourself. Plus, if you're going to be modifying your phone, you really need to have a good working knowledge of fastboot, especially on a Nexus. That's what will get you out of trouble if it arises.
If you're looking for a pretty stock-like experience but with some great features added I'd recommend trying out Pure Nexus, it's a rock solid ROM with useful extra features. I have links to all ROMs (and basically anything useful for this device) in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Heisenberg said:
My advice: don't use a toolkit. They can make things easier sometimes but easier isn't always a good thing. They've been known to cause issues, and there's really no substitute for ensuring things go right by doing it yourself. Plus, if you're going to be modifying your phone, you really need to have a good working knowledge of fastboot, especially on a Nexus. That's what will get you out of trouble if it arises.
If you're looking for a pretty stock-like experience but with some great features added I'd recommend trying out Pure Nexus, it's a rock solid ROM with useful extra features. I have links to all ROMs (and basically anything useful for this device) in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Click to expand...
Click to collapse
Fantastic thread mate ill be getting my study pants on haha used to use fastboot with my one x and the g2 but havent in awhile so ill go make sure im all up to date before I pull the trigger
One last question if ive already downloaded my whole spotify playlist 8GB can I pull that from the phone with adb backup and restore it so i dont have to re download everything pretty sure its encrypted so not sure it can be done.
Danzano said:
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Click to expand...
Click to collapse
Depends entirely on your choice. If you want to learn more about your device and how things work on it, you can perform things by yourself. Doing it manually also helps you keep a track of things that are going on, so if somehow your device is stuck, or not functioning as it should, you can always track back the source of the issue. And since you performed it yourself, you will know it better.
On the other side, toolkits have their own benefits. If you just want to perform procedures without much hassle and automate everything, you can go for them. All the toolkits here is the 6P section have proved useful to many users. You can try all of them, and see which one works better for you and your phone.
I for once have tried SKIPSOFT Android toolkit, offers a lot of functions. At the same time, there is Squabbi's Nexus 6P Toolkit, which has a more user-friendly interface, and much simpler to use.
Personally, I don't prefer toolkits, they could be buggy, at times. And have never suited my purpose.
Danzano said:
Fantastic thread mate ill be getting my study pants on haha used to use fastboot with my one x and the g2 but havent in awhile so ill go make sure im all up to date before I pull the trigger
One last question if ive already downloaded my whole spotify playlist 8GB can I pull that from the phone with adb backup and restore it so i dont have to re download everything pretty sure its encrypted so not sure it can be done.
Click to expand...
Click to collapse
That depends, is it just stored in a folder on your internal storage or is it stored as app data?
Heisenberg said:
That depends, is it just stored in a folder on your internal storage or is it stored as app data?
Click to expand...
Click to collapse
I believe its stored as app data because even with root explorer on the S6 I couldnt find it but if I looked at the app size in the S6 app manager it didnt show the music as part of the apps usage if that makes sense.
Ill try pull data and see if it works if it does ill be sure to post it as it could be a life saver for others who once they start flashing wont stop
Danzano said:
I believe its stored as app data because even with root explorer on the S6 I couldnt find it but if I looked at the app size in the S6 app manager it didnt show the music as part of the apps usage if that makes sense.
Ill try pull data and see if it works if it does ill be sure to post it as it could be a life saver for others who once they start flashing wont stop
Click to expand...
Click to collapse
Well it'd only be an issue right now due to the bootloader unlock process wiping your internal storage. It isn't necessary to do so when flashing ROMs so the data would remain intact through ROM flashes.
Heisenberg said:
Well it'd only be an issue right now due to the bootloader unlock process wiping your internal storage. It isn't necessary to do so when flashing ROMs so the data would remain intact through ROM flashes.
Click to expand...
Click to collapse
If I have developer options enabled on stock could i not adb pull all data?
If not ohwell just means my connection will get another day of thrashing lol
So dirty flashes are not a big issue on the nexus roms? or you mean backup data in twrp and restore after the rom flash?
Danzano said:
If I have developer options enabled on stock could i not adb pull all data?
If not ohwell just means my connection will get another day of thrashing lol
So dirty flashes are not a big issue on the nexus roms? or you mean backup data in twrp and restore after the rom flash?
Click to expand...
Click to collapse
Yes you should be able to use adb pull to grab the data. What I meant was that'd only be necessary if your entire internal storage is about to be wiped, like prior to unlocking the bootloader.
And no, definitely don't dirty flash when changing ROMs, and definitely don't restore the /data portion of a nandroid backup on a different ROM. Both will cause major issues. What I meant about that was sometimes some of the data (your playlist for example) is not stored as a part of the app, but is instead stored in the internal storage. Because the internal storage itself isn't wiped during a wipe preceding a ROM flash (a clean flash involves wiping system, data, cache, dalvik cache) the playlist would still be present on your storage after flashing the new ROM.
Anyway, the whole point was in response to your comment about it being useful to frequent flashers, when in reality it (adb backup) is only really ever needed once (before your storage is wiped during the bootloader unlock). Sorry if I'm not making sense, I don't feel like I am haha.
Heisenberg said:
Yes you should be able to use adb pull to grab the data. What I meant was that'd only be necessary if your entire internal storage is about to be wiped, like prior to unlocking the bootloader.
And no, definitely don't dirty flash when changing ROMs, and definitely don't restore the /data portion of a nandroid backup on a different ROM. Both will cause major issues. What I meant about that was sometimes some of the data (your playlist for example) is not stored as a part of the app, but is instead stored in the internal storage. Because the internal storage itself isn't wiped during a wipe preceding a ROM flash (a clean flash involves wiping system, data, cache, dalvik cache) the playlist would still be present on your storage after flashing the new ROM.
Anyway, the whole point was in response to your comment about it being useful to frequent flashers, when in reality it (adb backup) is only really ever needed once (before your storage is wiped during the bootloader unlock). Sorry if I'm not making sense, I don't feel like I am haha.
Click to expand...
Click to collapse
That makes sense almost got all the updated sdk tools now so will get to backing up then rooting just wanted to double check on the backing up because i have to nuke the internal storage when i unlock the bootloader
On pure nexus now with elementalx kernel well worth it
Sent from my Nexus 6P using Tapatalk
Danzano said:
On pure nexus now with elementalx kernel well worth it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nice
Unlocking bootloader.
Quick question regarding unlocking bootloader on 6p.
I understand that unlocking will trigger the software verification warning when starting the phone. If I return completely stock at a later date and re-lock the bootloader will the verification warning be disabled?
I'm not new to the rooting/flashing thing and have modified all of my previous Androids, but there are conflicting reports as to whether this is the case. A couple of videos on YouTube make it appear that the message is disabled after a return to stock.
Chipbutty.80 said:
Quick question regarding unlocking bootloader on 6p.
I understand that unlocking will trigger the software verification warning when starting the phone. If I return completely stock at a later date and re-lock the bootloader will the verification warning be disabled?
I'm not new to the rooting/flashing thing and have modified all of my previous Androids, but there are conflicting reports as to whether this is the case. A couple of videos on YouTube make it appear that the message is disabled after a return to stock.
Click to expand...
Click to collapse
Yes, the message will disappear if the bootloader is relocked. That's the only way to remove it. Not sure if you need it but I have a detailed unlock/root/flash guide for our device here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Verizon Lg v20 root is it worth it?

I have been reading about people bricking there devices trying to root. Are they doing something wrong or is it just not stable? I have rooted a few phones before but what i am reading is scaring me from rooting this one. Any input would be appreciated thanks.
I use my phone often. Not much gaming. And go to bed with usually 60+% battery. I'm currently using Weta Rom but they all are good. Its a trickier root than normal however I think this may be the new normal so just follow directions carefully and you will be fine.
Bubba Fett said:
I use my phone often. Not much gaming. And go to bed with usually 60+% battery. I'm currently using Weta Rom but they all are good. Its a trickier root than normal however I think this may be the new normal so just follow directions carefully and you will be fine.
Click to expand...
Click to collapse
Debating it . i dont have a back up phone in case something goes wrong........ I cant even find the thread on how to root now lol.
pcwizkid1994 said:
Debating it . i dont have a back up phone in case something goes wrong........ I cant even find the thread on how to root now lol.
Click to expand...
Click to collapse
Here is a great tutorial with pics that I and few others followed https://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/ . I was kinda overwhelmed with info esp the horror stories about rooting as well. That tut made life much easier.
2muchspl said:
Here is a great tutorial with pics that I and few others followed https://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/ . I was kinda overwhelmed with info esp the horror stories about rooting as well. That tut made life much easier.
Click to expand...
Click to collapse
Will that work for the verizon one?? It says its for the t-mobile one
pcwizkid1994 said:
Will that work for the verizon one?? It says its for the t-mobile one
Click to expand...
Click to collapse
Not sure, the previous link is basically Jcadduono instructions in pic form for the H918,H830 and US996 https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
sorry I couldn't help more
2muchspl said:
Not sure, the previous link is basically Jcadduono instructions in pic form for the H918,H830 and US996 https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
sorry I couldn't help more
Click to expand...
Click to collapse
No thats fine. i appreciate any help.
Rocking VS995 here. Followed the Dirty Santa steps and it worked easily. Been flashing everything I could on this device and settled on Weta because of the sound mods and still having all the stock features. I've gotten 8hrs SoT with a Blacked Out theme, Substratum themeing, no lag, and Deep Sleep like it's in a coma. Rooting the v20 is a must really at this point. The only downside I've come across is it vibrating during boot up while it's connected to a charger. Otherwise I've rooted, flashed, and been living the life.
pcwizkid1994 said:
Debating it . i dont have a back up phone in case something goes wrong........ I cant even find the thread on how to root now lol.
Click to expand...
Click to collapse
Do not follow any of the above guides that are posted you will kill your phone with those methods. Please follow every detail of this threat to a T to root your verizon v20 https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
It has been done guys. i thought i bricked it a few times but i am up and running on stock again with super su and root chaecker saying i am rooted
I am still debating on rooting myself I prefer to keep it root free for at least 6 months in cause something goes wrong with the hardware.
Main reason I root is so I can control what runs and what doesn't which should be a default ability in android in my opinion. I don't root to use custom roms I am always concerned about security of 3rd party roms
Sent from my LG-H918 using XDA-Developers Legacy app
KittySparkles said:
Rocking VS995 here. Followed the Dirty Santa steps and it worked easily. Been flashing everything I could on this device and settled on Weta because of the sound mods and still having all the stock features. I've gotten 8hrs SoT with a Blacked Out theme, Substratum themeing, no lag, and Deep Sleep like it's in a coma. Rooting the v20 is a must really at this point. The only downside I've come across is it vibrating during boot up while it's connected to a charger. Otherwise I've rooted, flashed, and been living the life.
Click to expand...
Click to collapse
I can not get weta to boot for some reason. I get static on the screen when booting and when its on set up screen.
pcwizkid1994 said:
I can not get weta to boot for some reason. I get static on the screen when booting and when its on set up screen.
Click to expand...
Click to collapse
Hit the power button to turn the screen off. Then hold your hand over the proximity speaker to turn off the second screen. When they're both black, you can use the phone regularly. It explains all this in the Dirty Santa root method thread.
pcwizkid1994 said:
I can not get weta to boot for some reason. I get static on the screen when booting and when its on set up screen.
Click to expand...
Click to collapse
If you want the static to go away. @BackCheck made a stock verizon kernel that works just a good as the konverged kernel. I get the same battery life as I did on the konvergered kernel and plus its more stable Just do a backup in twrp. Then hit wipe, advanced wipe, and check mark cache and dalvik and then go back and flash the restock kernel. The first boot take a bit of time so make sure your phone is charged a bit! You wont lose data or anything so dont worry.
Any chance you know how to get apps that cheack for saftynet to work on rooted phones?
pcwizkid1994 said:
Any chance you know how to get apps that cheack for saftynet to work on rooted phones?
Click to expand...
Click to collapse
I can't answer this - my question to you, however, has to do with your experiences in rooting.
I have the Verizon V20, non-rooted. The software version (it has taken one update since I bought this a few weeks ago) is VS99513A.
Can you confirm that this was the software version you had (have) when rooting?
And you said you thought you had bricked the phone a few times - what, specifically, are you referring to? I've read enough of the DirtySanta rooting thread to see some of the issues people have run into (static, long wait for first boot, etc.).
One of the unfortunate problems with a universal carrier rooting thread is that it doesn't delineate any one specific carrier and issues with rooting that might be particular to that carrier among all the posts. You have to wade your way through, lol, to find specific Verizon issues, for example. (That said, I'm very happy there's a rooting thread!)
It seems that from what I've read in the DirtySanta thread, many issues came up because people didn't explicitly follow the guide.
So, can you comment on your software version (13A?) before rooting, and what, specifically, gave you pause during the process and what I should be prepared for?
(By the way, the major thing I want from rooting is to be able to get hotspot wifi capability without having to pay Verizon for it. I'm on the grandfathered unlimited data and have not been convinced that it's in my interests to switch to their new "unlimited", particularly since I can't use my corporate discounts, and will potentially run into hotspot throttling after a certain limit, etc.)
Thanks!
pcwizkid1994 said:
Any chance you know how to get apps that cheack for saftynet to work on rooted phones?
Click to expand...
Click to collapse
This is possible with a rooted phone that has a kernel patched to bypass boot state verification (most kernels have this now) and using something like SU hide + Root Switch. I am currently running this setup and can use root switch to turn off root on the fly, use AndroidPay and then turn root back on when done.
I'll admit, I have yet to actually pay for anything with Android pay......but using this approach, I was able to add my credit card as well as bypass all checks with the SafetyNet helper app.
pcwizkid1994 said:
Any chance you know how to get apps that cheack for saftynet to work on rooted phones?
Click to expand...
Click to collapse
Some of the roms like notsostock have people explaining how to pass the checks and all the apps used.
You can run the exploit on 13a without any problems. If you still don't believe me or whatever just use the kdz to downgrade to 12a then do the exploit.
Sent from my VS995 using Tapatalk
is there a Developer that I can pay to root my T-Mobile v20

[GUIDE][addison] SETUP Moto z play XT1635-02 : from stock 6.0 to custom ROM.

I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194

AICP Rom is here

Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
AICP isn't available for Taimen just yet.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
Thanks for the info, can't wait.........:good:
ROM is up guys!
Great to see here! Kudos
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Namolas said:
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Click to expand...
Click to collapse
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
tmoore3496 said:
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
Click to expand...
Click to collapse
Same, I started from a flash-all factory image in both slots. Most interesting part ( to me ) is after the 4th try I flashed only the AICP zip, and not TWRP zip this time. Still wouldn't boot and when I booted back to recovery, expecting the stock recovery, but instead now I have Lineage recovery...
Seems I still have a thing or 2 to learn about this device.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Anyone installed this one?....any exclusive features?
amandeepparmar said:
Anyone installed this one?....any exclusive features?
Click to expand...
Click to collapse
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
elliwigy said:
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Click to expand...
Click to collapse
+1 for Pure Nexus
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Namolas said:
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
Click to expand...
Click to collapse
*fart*
Nochis said:
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So what do you think? You stick with it? Worth trying?
Namolas said:
So what do you think? You stick with it? Worth trying?
Click to expand...
Click to collapse
Don't know yet if I stay on it. I don't know if worth a try. Most roms have same stuff. I normally try for battery life and volte and wifi calling.
Sent from my Pixel 2 XL using Tapatalk
Can confirm that dirty flash over RR ROM does indeed allow it to boot!
Dirty flash worked like a charm..
Do you need to delete data to dirty boot? Were you still rooted with magisk installed? Thinking by about trying to over stock but wanna be prepared for the worst so have some fresh backing be up to do first. Lol
I dirty flashed, without wiping data on previous rom. I was going to try on stock but didn't want to turn on computer.
Sent from my Pixel 2 XL using Tapatalk

Trying to root, stuck at the first hurdle

Hi guys
I have a spare phone now my son upgraded, the S5 SM-G901F. I thought it wound be fun to install another software, possibly more up to date. So I first set out to root it but I haven't played around much with this sort of thing for long while.
I googled and found it seemed to be Odin to use so I downloaded 3.10. Also downloaded cf root. I went into download mode and when I plugged it in, the light in Odin lit up showing successfully connected. When I added the cf file and clicked start it went through some steps but stuck at Recovery. Img and wouldn't progress further.
I tried multiple times, tried a different cable and USB port and also Odin 3.07 and a different cf file even though I think it was the same one but from a different site. All no better.
Originally I bought it a few years back, used from a colleague. I think it was a carrier phone, EE iirc, and I had to get a code to unlock the SIM to use with mine. Maybe that also means it's software is locked?
Any help much appreciated
Thanks, marc
No one guys?
Please help
Marc
Please help
marc.knuckle said:
Please help
Click to expand...
Click to collapse
well to be honest, i would need to spend some time, "Googling" your model .... . I believe , your S5 is a Dev phone, meaning, it was not set up for any carrier, just for running demo's and such. IF this is true, I have no true answer for you.
Odin yes, you need that, that is true! (Believe 3.07, 3.09 and 3.10 work the best for these phones. Had tried a very newer version, several month back, and it did not do the job.. something like 3.14 or 16)
I recommend going to Sam Mobile, and run your model # through them. They will give you all the info about your model and possibly the latest firmware for it.
Sorry that I can not give you all that you are needing. I just don't know a ton about those S5 Plus models. (( I had to even look 'em up too) the plus has a slight better chip was well as graphics, but again, I dont know of any that actually work on a modern carrier like sprint, Verizon, T-Mobile , etc.)
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
marc.knuckle said:
Thanks for the reply mate.
It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.
I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.
Any other help from anyone appreciated
Click to expand...
Click to collapse
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
OK, Was only going off your model # you had given.
Did check... Odin and a good copy of CF auto root... That should be that.
Then of course, get away from a really old non sucure os (6.01 MM was their last made) .
Other than those 2 pieces, you should be good to root
Not pushing, or anything but LineageOS is rather good and does run well on these!
Plus, get a monthly security injection!
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
marc.knuckle said:
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
Click to expand...
Click to collapse
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Well, I would have to say NOPE!
Well only trying to keep your Q, on the top, so folks that might know, could help!
BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.
Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.
Mean time, Hopefully someone could chime in and point you towards the correct path to take...
OH
Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))
Might want to check for one for your phone.
I would actually start with TWRP, see what they have for ya.
( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate
It's stock recovery at the minute
marc.knuckle said:
Cheers mate
It's stock recovery at the minute
Click to expand...
Click to collapse
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...
That said, I take it, that you have a custom Recovery, and also Root?
Hope so, if not, I'm still here for ya
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
marc.knuckle said:
Cheers mate. So, some progression.
Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.
So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.
So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.
So i tried Lineage and that was a boot loop.
Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.
I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.
Shame really as i fancied a more up to date OS.
Thanks, Marc
Click to expand...
Click to collapse
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
godofsalt said:
Wait, isn't what you were wanting?
Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!
( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)
OK, not sure if you picked up a new info about LineageOS, across the pond....
But
They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too
So, keep an eye out for that, cause am in same Boat, waiting for the Official release.
( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Thanks mate

Categories

Resources