Related
14 November 2014
There are several great lollipop builds out there currently with a lot of work being done to give us all a great product. So far multirom is working perfectly in Primary slot as well as secondary slots in multirom with @scrosler AOSP builds 5-7, Build 7 here as well as @scrosler Factory Stock Rooted ROM LRX21P which can be found here
If your favorite dev is making a Lollipop build for the Nexus 7 and you have successfully used it with multirom, please let us know so we can tag it and place a link for future users to this thread.
06 November 2014 (ORIGINAL POST)
Ever since I mentioned this in an email, I have received a few requests on how I got @scrosler Pure AOSP 5.0 Build to work with MultiROM on my Nexus 7 flo.
First off, I have only done this with the build by @scrosler which can be found HERE, but I would guess that it can work with similar builds.
Secondly, this worked perfectly on my device. If you mess up your device, I am not responsible.
Thirdly, and most importantly thank you to:
@scrosler for the lollipop build and all the extras
@Chainfire for SuperSU
@sykopompos for the permissive boot image
@flar2 for the ElementalX Kernel
@Tasssadar for MultiROM
if I forgot to mention someone, please holler at me
Okay, on to the easy stuff...
This has been tested and is successful on Nexus 7 flo (2013). For information on Deb procedures, please refer to this post by @drewski_1 but at the request of @scrosler, please bring all multirom questions back to this thread. Also for Nexus 7 deb, @darkobas has given us a modified boot image to use which can be found here
This ROM (this particular build I've been working with) cannot go into a secondary slot of MultiROM, I have tried everything. If you found a way, please share it.
1. go HERE and read the OP, download necessary files, (latest build, latest gapps, busybox flashable, etc), update bootloader if needed, and goto step 2.
2. go HERE to get ElementalX Kernel for Lollipop
3. go HERE to get a very permissive boot image that works perfectly with this setup.
4. go HERE to get the latest SuperSU
After you have everything in order, reboot into recovery...
1. Move your primary ROM into a secondary slot in TWRP recovery.
2. Go back out to the main TWRP page (outside of Advanced/MultiROM)
3. Install Scotts Pure AOSP build 5.0
4. Install Recovery Saver
5. Reboot Recovery (just to make sure your recovery is still intact)
6. Install GAPPs
7. Install Permissive boot image
8. Install SuperSU
9. Install ElementalX Kernel
10. Reboot and Enjoy
When you get into your ROM, check to verify that your SuperSU is functioning properly and set your ROM up to your likings. :good:
appreciated clarification
OP said:
I've gotten a few requests about multirom with this build since I posted something earlier. If you need to know how to do it (you should already if you're using multiROM), you can check it out HERE.
I didn't want to post the info in here and muddy up the dev thread.
http://forum.xda-developers.com/showpost.php?p=56558107&postcount=802
Click to expand...
Click to collapse
I know but tend to forget details over time - THANKS. I like to verify procedures before committing anyway - saves me from bricks soft or hard. With the file structure changes, etc I like to know what I'm getting into and how best to do it safely.
I'm in the process of moving roms and should have this latest L in slot #1 before dusk, heh.
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
hhairplane said:
Heads up, the modified boot image does not stick after booting into secondary ROM (IE KitKat or other earlier based ROM), so if this happens just reflash modified boot image. You will be good to go and back to root. :good:
Also, @darkobas has created updated boot images for both FLO and DEB. Would be great if OP could be modified as such. The new images can be found in @scrosler 's thread.
Make sure to have MultiROM zip and recovery installed when trying this method, as the MultiROM code must be injected for it to work well.
Click to expand...
Click to collapse
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Megaflop666 said:
I had no issues with the modified boot image sticking after booting into either of my secondary Roms.
I will look at the modified boot images in a few. I'm reading through scrosler's thread now.
Click to expand...
Click to collapse
It might just be with Deb, then...
hhairplane said:
It might just be with Deb, then...
Click to expand...
Click to collapse
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Megaflop666 said:
Would be my guess. I am currently reading through the section in scrosler's thread that you mentioned. Is the new boot image you mentioned for deb only?
Click to expand...
Click to collapse
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
hhairplane said:
Yes, but I think there is a different boot image in scrosler's thread (not for Lollipop preview, but for AOSP scrosler build). It is attached in OP and made by darkobas. Not sure what is different than older boot image.
Also, my secondary are KitKat and earlier ROM's, not Lollipop-should be a different boot image. Not sure if that's the same for you? Perhaps, flashing a KitKat boot may solve the problem, since it seems that MultiROM has to mod Lollipop's for KitKat to work?
Click to expand...
Click to collapse
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Megaflop666 said:
OP has been updated, I think I found all the pertinent info you mentioned regarding making deb part of this thread. If I missed something, please let me know. Thanks
Click to expand...
Click to collapse
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
hhairplane said:
This one is the better Deb Modified Boot.img http://forum.xda-developers.com/showpost.php?p=56564714&postcount=856 Sorry, I should have more clearly laid it out myself.
Click to expand...
Click to collapse
Its all good. There's been conversation scattered everywhere, that's one of the biggest reasons I wanted to start this thread.
Edit: Link has been updated to the correct post.
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
dadeo1111 said:
I followed the OP instructions very closely (twice) and can get the primary L rom installed, rooted and running smooth - very smooth, in fact. Nice rom scrosler! But the rest of my multirom roms won't load even the boot ani - I get only to the Google screen and loop there on any rom - I have a jellybean, a couple of kitkats and one of the dev releases of L and they all do the same. I've not yet tried to install a secondary rom but will.
Anyone with a suggestion? I have the new primary backed up and have some nandroids of a couple of the secondarys. I'm not that worried about losing them and have considered starting from scratch if nec.. tia!
Click to expand...
Click to collapse
Try going into twrp into one of the secondary ROMs and fixing it's boot? Something must've gotten missed in the setup or something happened because this issue is new.
Megaflop666 said:
Try going into twrp into one of the secondary ROMs and fixing it's boot sector?
Click to expand...
Click to collapse
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
edit to add:
I am able to install/add roms, btw. I successfully re-added a jellybean rom from nandroid backup just fine. I'll probably throw them out except one anyway. I'm not sure what happened or when but I followed your steps verbatim. thanks again.
dadeo1111 said:
I should use the remove/add boot.img function? I've never done this but will look into how. If you have a link to some specifics it would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
All the multiform specifics can be found in that thread here.
I would try restoring your backup first and see if that fixes the secondary ROMs. Especially since you don't have much time in the lollipop ROM yet. If you restore and it works, let me know.
@scrosler has build 4 up, please see his thread which can easily be found in the OP, second paragraph.
OP will be updated shortly if necessary.
Okay, I've gone through this a few times now. @scrosler work is perfect unless we want to use it on multirom. Continue the same steps listed in the OP or you will lose root, as well as the ability to boot multiple Roms.
Build 6 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Megaflop666 said:
Build 5 is out from @scrosler. Follow the same installation process listed in the OP. Only add on would be that scrosler added a flashable busy box zip on his threads OP that you can flash in twrp around the same time you flash SuperSU. :thumbup:
Click to expand...
Click to collapse
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work too - as usual. If not I'll post so here.
This is going to be my daily driver now. :good:
I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
dadeo1111 said:
I have successfully installed @scrosler's latest (build 6) as a secondary rom and in the usual fashion - Flash ROM, Flash GAPPS. I then booted into the new install and allowed Google to update me (successfully). Everything worked but root apps, of course. I then rebooted to TWRP, flashed the beta superuser zip - rebooted and checked and have root. All per usual and as expected.
Titanium bup didn't work after accepting root permissions but it was from the play store so this is also per usual. I'll try the one I got from twitter and expect that to work - as usual. If not I'll post so here.
This is going to be my daily driver now. :good: I'll add a custom kernel later. ElementalX 3.x has been solid for me on all lollypop roms so probably that one.
Click to expand...
Click to collapse
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Megaflop666 said:
Awesome. I was going to try it with the latest build later when I had some time but you saved me the work. :thumbup:
Besides checking tibu, also check es file explorer. I have both working on this build in the primary slot but I know a lot of people are struggling with es.
Click to expand...
Click to collapse
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
dadeo1111 said:
ES seems fine - even sees my lan. Also sees and navigates sd card but am unable to do root tasks in system folder (rename, copy, delete). When I do a root action it requests root and I accept then the task fails.
Click to expand...
Click to collapse
Are you using the permissive boot image from the OP and elementalX kernel 3.01? Just curious why I have full function with ES and other people don't.
Hello,
Bought a Nexus 6P the other day and now attempting to install CM13, latest official snapshot. Of course, I ran into issues., and I am in dire need of help.
I unlocked the bootloader via Fastboot. Then installed the latest TWRP, also using Fastboot. All fine so far. Then I tried flashing CM13, which first failed because I missed to wipe the data/cache. I realised my mistake, re-did it and successfully flashed CM13.
The installation process was successful, yet when I boot the phone up and it finishes loading CM, I get the following error message:
"Android-system
An internal problem has occurred. Contact the manufacturer if you want more information."
Why is this happening? And more importantly, how do I fix it?
I did try and ignore the warning and proceeded to install OpenGAPPS from TWRP. As soon as CM loads up again however, there is an infinite stream of Google Play Service and "first time setup" crash messages, making the phone unusable.
On a related note. The guide at https://wiki.cyanogenmod.org/w/Install_CM_for_angler tells me to "update the vendor.img", but it never tells me how I figure out which Build ID I need for my version of CM13. The guide hints at MTC19V, but I am not sure if this is right. I did try flashing this, but nothing changed.
Please advice, I am stuck.
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Ahh, I see. That makes sense now. Thanks!
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Really? I didn't think it would matter. Anyways, even with this part fixed, would it not continue to claim being corrupted? I understood it as if CM itself has an issue and not GApps.
Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!
I was saying the latest available vendor.img was from august. I use DU so i don't know how far behind CM nighties are.
NodCom said:
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!
Click to expand...
Click to collapse
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.
Gizmoe said:
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.
Click to expand...
Click to collapse
I am only willing to use stable builds, not nightlies.
Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app
Pollie81 said:
Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I agree. CM was great on the N4 and N5 but not so much on the 6P
NodCom said:
I am only willing to use stable builds, not nightlies.
Click to expand...
Click to collapse
Why would I care which release you prefer? You asked how you messed up flashing CM and people responded. It's because of mismatched Vendor images. And no one seemed to know for sure which one it is so I looked for you. I've compiled CM with the right proprietary blobs and I have had no stability issues.
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
At this point I have TWRP on two partitions—3.2.2 on recovery and 3.2.1-3 on laf. Running stock 10p + root is now working great. No issues.
Every time I flash lineage (with optional gapps + su), I tell TWRP to reboot. It consistently causes the phone to have the blinking backlight where it flashes on and off every 1 – 2 seconds. The LG logo appears, and then you're faced with the blackness. Think of it as an all black screen turning on and off. To recover from this, I pull the battery, hit the volume up button + USB cable to boot into TWRP, flash a 10u flashable zip, and then repeat from square one.
Things I have tried:
• I have tried flashing Lineage on the TWRP on recovery and the TWRP on laf to see if it would make a difference. Same blinking black screen.
• Before installing Lineage, I went into format and typed ‘yes’ to remove decryption. I installed Lineage. Hello blinking black screen.
• Under ‘advanced wipe’, I tried clearing everything onboard (Dalvik / ART Cache, System, Data, Internal Storage, and Cache). I went to installing Lineage. Hello black blinking screen.
• One guide suggested hitting ‘advanced wipe’ and to clear the /data and /cache partitions before installing. No difference. Hello blinkyness.
• I did the general wipe before installing Lineage. No change.
• I tried just installing Lineage images (tried different build dates) with no gapps or su to reduce the chance of any complications.
If I can get this phone working with Lineage with my triple capacity battery, tacos for everyone.
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
runningnak3d said:
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
Click to expand...
Click to collapse
I believe the lineage builds include it's own kernel
Sent from my LG-H910 using XDA Labs
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
You're good, I don't use Lineage due to it's deficiencies, I just read up on it
Sent from my LG-H910 using XDA Labs
michaeljh9 said:
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
Click to expand...
Click to collapse
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
Click to expand...
Click to collapse
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
michaeljh9 said:
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
Click to expand...
Click to collapse
Info is buried deep in one or more of the 3 lineage threads. Been watching them closely for ages.
Phoenix591 said:
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
Click to expand...
Click to collapse
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
Phoenix591 said:
x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
michaeljh9 said:
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
Click to expand...
Click to collapse
yeah guess I forgot to mention that the first boot of lineage 14 after wiping takes 15-35 minutes. Usually not stuck on the lg logo.. ill take a look.
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
Oh God dude!!!!!!! If and when you get involved in LOS, I will definitely flash that build.
You are by far my favorite Dev. That's why I'll always buy the same device you get. I know it would be WELL supported!
Sent from my LG-H918 using XDA Labs
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted
Ok my friends, it's true that family moto g6 (specifically g6 play) will receive android 10? if it's possitive... When will we have news about this?
Also ... does anyone know if there is any rom in development with android 10 for this model (lineage, RR, etc.)?
If anyone knows about this, I think several would appreciate this valuable information.
Answer 1, just wait for Moto to announce it, usually they announce when there gonna do a soak test of a new Android version so whenever Moto does that will be some sort of answer however soak test usually go on for a few months basically it's prolly gonna be almost another year before we hear anything I mean we just got official pie about 2 months ago now after they did soak test for months.
Answer 2, there is not even a custom rom like rr or anything for this device for Oreo or pie so doubtable. Best you can do is try out gsi A only builds, custom rom means it's made specifically for this device where as gsi is compatible with any phone that shipped with Android 8. There is a gsi thread you can out
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
PimpMy5Ton said:
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
Click to expand...
Click to collapse
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Spaceminer said:
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Click to expand...
Click to collapse
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
PimpMy5Ton said:
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PCP29.118-41
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Glad to have it running with Pie and more stable, those are great news
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Can you guide us? I install the test img but cant boot on pie vendor
Grom9A said:
Can you guide us? I install the test img but cant boot on pie vendor
Click to expand...
Click to collapse
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
ry755 said:
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
Click to expand...
Click to collapse
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Grom9A said:
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Click to expand...
Click to collapse
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
I want to try but can't root this rom
Grom9A said:
I want to try but can't root this rom
Click to expand...
Click to collapse
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
ry755 said:
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Click to expand...
Click to collapse
Maybe I flashed the wrong boot.img... I might've mixed up Oreo and Pie boot images. I have both firmwares sitting right next to each other.
Spaceminer said:
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
Click to expand...
Click to collapse
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
ry755 said:
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
Click to expand...
Click to collapse
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Spaceminer said:
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Click to expand...
Click to collapse
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
ry755 said:
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
Click to expand...
Click to collapse
I'll check it out and see what I can do. That's not surprising though. It's extremely alpha, so he's probably just prioritizing stock functionality over everything else right now.
I can't get it rooted, but v202 just went up, so I'm going to try my luck with it.