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.
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.
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
DrakenFX said:
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
Click to expand...
Click to collapse
Which is the patch date? G B09 has the December 1 patch, just wanted to know which one fixes this stuff
Can someone provide a B35 update zip? It's no issue for me to connect to Wi-Fi to install it, but I like to keep offline cached copies of files for recovery purposes, so that I can update even without Internet.
Thanks!
Edit: I have A2017U.
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Predatorhaze said:
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Click to expand...
Click to collapse
As soon as you make one?
Pretty sure it's available now. Let us know how the battery life is.
I know I asked before, but if someone can post a direct URL link to the B35 update file (whether it be a zip or something else) then it would be much appreciated. I know @DrakenFX released a system and bootstack zip, but I would rather use official files. I can't save an offline copy of the file since I'm not currently rooted, I suspect it is stored in the /cache partition. The file size is close to 700MB. I just want a copy for offline use. Maybe someone with root can capture a copy of the file after it has downloaded, but before the phone reboots to apply it. Or maybe the URL can be sniffed with WireShark or whatever. A B35 full OTA zip is better, but ZTE hasn't posted an SD card update download on the zteusa.com website yet.
Thanks!
I was able to grab the B35 update zip without rooting. I let the updater download the file, then quickly powered off the phone before it had a chance to reboot and install. Then I booted into EDL mode, and used @tennear's Axon7Tool to write TWRP. From TWRP I went to /data/data/com.zte.zdm/files, and grabbed a file called fota_update.zip. Then I reflashed the stock recovery with Axon7Tool, and installed the zip. All went fine. I suspect you can grab any OTA zip this way. Maybe I'll upload a copy of the file later.
If there's any interest in a B35 SL!M➀ aroma-version let me know
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
raystef66 said:
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
Click to expand...
Click to collapse
Yes. I downloaded those 'init' files way back last Spring & found them more effective (at least impression-wise) than the AKT stuff. His "Conservative" mod helps w/ battery w/o a noticeable performance hit.
Early on I found the A7 was not happy when some apps were removed & replaced, but functioned OK if they were kept frozen & then replaced. Fortunately there is enough storage & memory that inefficiency does not (so far) cause issues. Sort of like the legacy SubStratum which could (sort of) work as long as system apps were excluded.
I look forward to your "hobby". Thanks
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
redhou said:
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
Click to expand...
Click to collapse
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
davisml said:
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
Click to expand...
Click to collapse
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
amphi66 said:
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
Click to expand...
Click to collapse
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
redhou said:
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
Click to expand...
Click to collapse
It will download, but the install will simply fail as it checks the system files, but certainly you are free to do as you wish. Good Luck!
raystef66 said:
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
Click to expand...
Click to collapse
Uploading A2017(U)(N-B35)_AROMA_SL!M¹_DF!NR now Preparing a seperate thread on ROM section. Keeping you updated when ready :good:
EDIT : DONE ! LINK
hi, i am installing the new OTA update but it when my restarts TWRP asks for password to mount and doesn't allow me to install this new OTA update. I entered my phone password which said it decrypted the pkg but then it only opens the TWRP GUI. I tried to install the zip manually but it said it failed.
How can I let the phone install it without TWRP interfering?
Thanks a lot.
lachdanan said:
How can I let the phone install it without TWRP interfering?
Click to expand...
Click to collapse
You can't. Use stock recovery if you insist on OTA, or use DrakenFx's zips to flash from TWRP. The latter is much more convenient.
It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!
garfius said:
It's been 5 days since i installed lineage in my Oneplus One.
Yesterday it started to randomly shut down or reboot, now it hardly boots.
Procedure followed:
Original cyannogenmod --> oxygen os --> lineage os
Formated all partitions befre installing lineage OS
Any idea?, it rushes!
Click to expand...
Click to collapse
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?
i think not..?
kurtn said:
I doubt LOS is the root cause. Did you somehow restore apps? Did you install something new yesterday? Did you change settings of installed apps?
Click to expand...
Click to collapse
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?
garfius said:
Let's recap.:
1-original CyannogenMod
1.1 -- Screen+battery is replaced
2-install Oxygen OS
2.1 -- flash firmware (antennas+something+recovery)
2.2 -- flash oxygenOS
3 - Install latest twrp for oneplus: https://eu.dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
3.1 -- erase system,cache and dalvik cache
3-2 -- flash https://mirrorbits.lineageos.org/full/bacon/20180425/lineage-14.1-20180425-nightly-bacon-signed.zip
3 days perfect
yestarday found powered off (1st time ever!)
today rebooted about 4 times
Any idea?
Click to expand...
Click to collapse
Delete data for clean install.
garfius said:
It's been 5 days since i installed lineage in my Oneplus One...
Click to expand...
Click to collapse
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Can't save update script for lineage version 14.1
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse
What twrp?
Probably found it!
It seems to be a problem with the wifi firmware, seems to be pretty common :crying: :crying:
Anyways, thank you for your time.
Regards.
Ibuprophen said:
I don't have this device but, if the support/guidance here, for any reason, doesn't work out here then you can always post your question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3543489
If needed, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2731638
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Try latest
I used lineage tuto, and flashed the latest TWRP and worked like a charm (wifi issue apart).
asadc said:
I recently have tried to flash lineage version 14.1. however i get an error that says cant flash because incorrect device. I have tried to edit the update script to remove the line of code that triggers that. after i edit saving it doesnt work and i cant flash lineage. Any suggestions?
Click to expand...
Click to collapse
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
I usually wait for a while until official Android 10 ROM for international OnePlus 6T version (and flash it via TWRP both times so I don't get any conflicts, with same copies of the OS across both slots), then I do whatever I want (I usually upgrade the bootloader and vendor this way so newer flavor of LineageOS 16 or later ROMs work best). I didn't run into hardware mismatch warning, yet I managed to successfully flash the successive OxygenOS updates meant for the international OnePlus 6T on my T-Mobile OnePlus 6T so far without seeing any UEFI bootloader warning at all. I had to be careful, I partly bricked my Google Pixel phone the last time (rendered Slot A completely unbootable by accident, so I had to figure out how to restore it the hard way, without the computer).
Sent from my OnePlus 6T using Tapatalk
bigmikey307 said:
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
Click to expand...
Click to collapse
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
ajnexus5 said:
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
Click to expand...
Click to collapse
I'm not interested in rooting my phone :silly: so is there any work around for unrooted users at the moment? Ty
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
That file was deleted. Is there any other way to flash it?
jaceypoo said:
That file was deleted. Is there any other way to flash it?
Click to expand...
Click to collapse
Yes. Payload.bin decrypt and manual fastboot flash.
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
bradhoschar said:
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
Click to expand...
Click to collapse
How is the Zip? I am new to the OnePlus forums do not see the least of two of 0 years ago I do so much trust that this would not happen as with P there were never problems with the V T which Vojo is some without root version?
Installed just fine, I love the new interface. BT isn't working for my Garmin watch. I guess I will have to wait for a full release for this to be fixed up.
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
No issues on the T-mo fastboot ROM
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
EspElement said:
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
Click to expand...
Click to collapse
I even tried to fastboot boot recovery.img
It didn't work, just sits at fastboot screen.
bradhoschar said:
No issues on the T-mo fastboot ROM
Click to expand...
Click to collapse
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and prox works for me.
Emojis work after magisk module flash.
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and Prox are working fine for me. Dont know about fonts and emoji's as I dont use them. Everything "else" seems fine at this point.
Scott said:
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
aer0zer0 said:
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Scott said:
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Click to expand...
Click to collapse
root your boot.img using magisk 20.0 stable.
but your going to need to reflash? are you tmob or stable?
bradhoschar said:
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
Click to expand...
Click to collapse
is this the pre rooted version
Sent from my ONEPLUS A6013 using Tapatalk
Hello everyone! I have managed to get Global firmware on VZW UW OnePlus 8 and thought I would share.
Donations are appreciated. PayPal user @igp1490
You will need to download to get started.
1. FastbootEnhance: https://github.com/libxzr/FastbootEnhance/releases
2. Jaguar Rom Full: https://drive.google.com/file/d/1RIIZzz0IyVXeFdjjKRjgqdSphLxaE--w/view
3. Recovery: https://androidfilehost.com/?fid=15664248565197198941
4. PayloadDumper GUI. Download version 2.3: https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
5. Global OTA Firmware 11.0.11.11.IN21AA: https://www.thecustomdroid.com/download-oneplus-8-pro-oxygenos-ota-updates/
6. OnePlus 8 Visible OTA firmware: https://oxygenos.oneplus.net/OnePlu..._OTA_0080_all_2203082133_56fdf9c8718742cb.zip
7. Platform-tools, I'm using 33.0.3: https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062
Now to get started. First have bootloader unlocked of course.
1. Extract payload.bin from Visible OTA, then dump payload.bin with payload dumper. next find modem.img and move to desktop
2. Install Recovery
3.Be on A11 rom with A11 custom recovery or Install Jaguar Rom and go through setup.
Thanks to Bishop1312! for pointing out any A11 rom with A11 custom recovery works in step 3.
4. When Jaguar is setup reboot to fastboot
5. Run FastbootEnhance, double click your device that says fastboot
6. When in fastbootenhance click fastbootd then click little box to the left of "ignore unknown partitions" then select flash payload.bin and select global firmware zip. When flash is complete "select activate slot" my second slot to flash was slot B, you want to flash global to both slots.
7. After it installs click back in in Jaguar recovery and select "Factory reset", I did f2fs and regular format options
8. Afterformat is done reboot system
9. It may take a few minuets to get into the setup and you may get a message saying phone app has stopped working, don't worry just go through the setup process and connect to wifi.
10. when phone is setup turn off phone and boot into fastboot holding power+Vol down, when in fastboot connect to computer and run FastbootEnhancer. You should see your fastboot device, double click on fastboot, now in fastbootenhancer click reboot to Fastbootd. when in fastbootd go to Partitions tab in fastbootenhancer and look for Modem_b, click on modem_b to highlight it, then click erase then click flash and look for modem.img you put in desktop and select it to flash and after look for modem_a and follow same steps then reboot phone to system.
11. When phone is booted go to system updates and update. After update is finished reboot, after reboot follow steps 10 again for modem, continue step 10 until fully updated to Android 13. Verizon service will work in Android 13 but not 11 or 12.
One problem I have is if I turn on then off airplane mode it wont reconnect to Verizon service, you have to reboot phone and it will work again. I'm thinking maybe because it's an older modem.img, so if anyone can get there hands on the newer modem from Verizon or Visible newest OTA maybe that will fix the issue but no sure. This is my first guide so If anyone has problems let me know and i'll do my best to help you.
Hope ya'll enjoy.
Edit: I got EvolutionX A13 rom working! also airplane mode is working in EvolutionX A13 rom. You have to do step 10 every time after setting up new A13 roms. I Tried step 10 before going through setup but it just goes to bootloader, So make sure to complete rom setup before step 10.
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
Click to expand...
Click to collapse
Thank you. I'll edit step 3.
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Click to expand...
Click to collapse
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Incognit420 said:
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Click to expand...
Click to collapse
No, video playback i don't test for now. I tried to flash two roms and i apologize for unchecked words - after first flashing modem.img at the beginning, in the future no needs to flash modem, cellular data work fine.
Great work @Incognit420. A video guide will also be helpful for noob like me.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
Even though reading is fundamental - a how-to video would take it over the top.
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Xryphon said:
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Click to expand...
Click to collapse
Yes OOS13 works. This method flashes OOS11 global firmware then you update to OOS12 in setting and then update to OOS13 in settings. Make sure to flash modem.img in fastbootd after each update. OOS13 works. Data and calling are not working in OOS12 global, don't know why but does work in OOS13. the only problem I have is OOS13 is if you turn off wifi it won't turn back on but data, calling and text work. I'm on a custom OOS13 rom and it fixed wifi.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
I'm horrible at making videos lol but I'll give it a try.
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
faritz1903 said:
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
Click to expand...
Click to collapse
What rom were you on before flashing global firmware?
Incognit420 said:
What rom were you on before flashing global firmware?
Click to expand...
Click to collapse
oos 11, then install jaguar rom
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
faritz1903 said:
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
Click to expand...
Click to collapse
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
faritz1903 said:
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
Click to expand...
Click to collapse
Install EvolutionX 13 and then install Crdroid 9.0. or you can try just using EvolutionX vbmeta and recovery to install Crdroid, both roms use the same method.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
The reason why the various issues on the ROMs exist is because the OOS12/ OOS 13 firmware has not been released by Verizon officially, and there are fundamental changes in the firmware such as the modem (since the Verizon model has the mmWave functionality). This leads to various networking issues such as Wi - Fi not working, cell data not working sometimes, etc. IN2019/ Verizon OnePlus 8 users will never get a stable OOS12/ OOS13 build unless Verizon decides to release the firmware for it - the custom ROMs are the same way since they rely in the OOS12/ OOS13 firmware in order to function properly.
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
The0919 said:
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
Click to expand...
Click to collapse
Yes, MSM will bring you back to vzw firmware.