Related
Hi all,
I'm currently not encrypted and prefer to keep it that way, I don't like entering passwords everytime I go to TWRP and I prefer the old school android system where encryption was a choice, not a mandatory decision made for you.
So when I install a ROM I run a few commands prior to installation to avoid forced encryption, unless it has an option within aroma to disable force encryption which most don't
Thanks to @j to the 4n for help with this, legend
Anyway if you'd like to install a ROM like lineage or aosp or resurrection remix etc and remain not encrypted? Keep reading.
*Note: if you're encrypted prior to doing this then stop, this is for people who've chosen to disable force encryption already but would like to retain it after installing aosp / lineage ROMs.
However if you'd like to remove encryption you'll need to format data via TWRP, not a wipe! Format.
Make sure you back up prior to doing this as it will format data, best to have the ROM on your SD card too so you don't end up with no OS.
If you've done the above or you already have a ROM installed without encryption, then you should be good to go.
------------------------------------------------------------------------------------------------
Just before youre about to install a ROM, let's say resurrection remix ( tested )
Make sure your phone is in TWRP and you're connected to your PC then just before you're about to click install, open up a command prompt on your PC then from ADB shell send the following commands to the device from your PC..
For Magisk:
echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk
If the rom uses SuperSU, send the following commands.
echo "KEEPFORCEENCRYPT=false" >> /data/.supersu
echo "KEEPFORCEENCRYPT=false" >> /cache/.supersu
Then install your rom as normal.
Obviously for ROMs like viper your don't need to do this as there is an option within aroma, but for the likes of RR or lineage this will mean your phone will not encrypt on boot.
Should work for all ROMs but I've not tested this on all of them so if it goes wrong then it's not on me, this worked perfectly for me on RR coming from viper whilst not encrypted.
*Note: if you're not sure what root method your ROM uses then simply send all three commands and you should be good to go.
By using these you're not going to find yourself in TWRP being asked for a password you don't have as your device has been encrypted, I've lost data myself this way and it's extremely annoying.
:good:
If I can ask if anyone tries this and it works, would you mind replying with what it worked on so I can update the OP.
Cheers.
PS: if you're not sure what this is or have any questions, please ask away
Anyway to do this from the device for when your not near a PC?
JohnFawkes said:
Anyway to do this from the device for when your not near a PC?
Click to expand...
Click to collapse
Yes i believe it is, would need to write up a script which is ran prior to installing the rom, i've not got around to doing it yet.
Strictly speaking this should be an option with all roms, it's not exactly a lot of work is it?
Deleted
Works pretty well on Stock ROM.
Just RUU'd, and before rebooting went into download mode, flashed Recovery, flashed SuperSU, used this Command. and boom.
Multirom works.
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
dladz said:
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah it pisses me off. But at least with this handy zip you can flash it anyway and have some mental relief that you stay decrypted.
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Haldi4803 said:
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Click to expand...
Click to collapse
Sorry I hadn't tested with all ROMs, not even sure Pure Fusion was even available when I had my HTC 10.
Stick to the script, it's quick, easy and works, you can try a zip but unless someone has gone before you you're potentially walking into a bad time.
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Haldi4803 said:
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Click to expand...
Click to collapse
That's absolutely fine. Because this thread isn't about the zip..I have nothing to do with that, so in regards to the zip you flash it at your own risk.
Deleted
Though i do agree with him that having a .zip and not needing a Computer every time would be pretty usefull.
Does anyone know how to create TWRP flashable zips that includes only this 2 commands?
Hello I tied this for RR rom but I got this message in the cmd, am i doing something wrong?
edit i found my fault I had to adb shell
I know it's been about a year, since somebody posted, but: if anbyone else like me stumbles across this thread, have a look at: https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
It gives you even more information how to enable or disable encryption or dm-verity while usinf magisk.
Btw. you can use the terminal in twrp also, see link.
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Subh4sh said:
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Click to expand...
Click to collapse
Ofcourse,cause echo command is available everywhere.just make sure you install the magisk/supersu first before running the command
hi,
If I format /data, then the encryption is gone and LOS can be installed where backup with TWRP work?
I have U11, but i think it is the same...
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?
Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs
Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?
Is there any news?
kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".
Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.
hope it will have LOS15.1
Even though Raymon left development does this mean there are no los 15 for us?
As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.
15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday
heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.
heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?
There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.
I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip
OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?
ermacwins said:
OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?
Click to expand...
Click to collapse
I'd try fastboot flashing with the MiFlash tool
On the MIUI forum they seem to use this as the best way to get back to stock.
It even has a "clean and lock" option to set the phone back to clean ROM and locked bootloader.
Pretty good actually.
Can grab the fastboot firmwares from en.miui.com and then tool as well.
Guides are easy to find on there as well.
Just extract the fastboot package (.tgz)
Then unpack the file from there (yeah I know twice ergh)
And then point the flash tool to the folder this creates.
Then you should be safe to flash.
That will get you back to clean device then you can install TWRP with fastboot again.
I'd go for the Global Developer ROM it's so much better than Stable.
And here's a tip for free: in developer settings disable "MIUI optimization" and set the memory optimization to "off". Makes it so much smoother and battery lasts longer as tasks aren't killed every 5 mins....
So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.
ermacwins said:
So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.
Click to expand...
Click to collapse
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked
Dobsgw said:
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked
Click to expand...
Click to collapse
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom
ermacwins said:
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom
Click to expand...
Click to collapse
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream
Dobsgw said:
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream
Click to expand...
Click to collapse
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?
ermacwins said:
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?
Click to expand...
Click to collapse
LineageOS Nougat.
Not so amazing for visual customisation, but definitely the most stable which means creating mods or adding them isn't as likely to cause issues.
I just want a ROM close to AOSP with all the features of the phone working like fast charging.
AOSPA looks good too.
Just flash again with fastboot ROM and mi-flash tool.
So I just got the OnePlus 5T and wanted to do a speed test comparison for my YouTube channel. I noticed temple run 2 exits. So want to try EU ROM but it gets stuck on bootlogo. Does anyone have a link to the fastboot ROM? Can only find an old one. I can flash the global ROM through with twrp which works fine. Flashing EU ROM fails.
Also will flashing through fastboot lock the bootloader?
I think you should wipe everything and wipe data if you have fbe because it messes up things
So I flashed a stock rom (sagit_global_images_V8.2.2.0.NCAMIEC) with mi flash tool. Unlocked it, installed twrp. Now flashed latest rom eu rom and its stuck on bootlogo still
ARGHHHHHH
Finally worked
After flashing EU ROM, enter fastboot mode and type
fastboot format userdata
(This will format all the data on your phone)
Reboot. Done.
Click to expand...
Click to collapse
https://xiaomi.eu/community/threads...mi-logo-after-flash-eu-rom.39979/#post-398231
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Uzephi said:
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Click to expand...
Click to collapse
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
blake .l said:
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Click to expand...
Click to collapse
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
blake .l said:
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
Click to expand...
Click to collapse
I use RC since I live on the wild side (I have tried to hard brick this phone so many times, only thing I won't try is locking BL since that's a stupid way to hard brick.) Airwalk says it perfectly. If you have Oreo on both slots, no need for the prep zip. I flash twrp.zip after booting into twrp, reboot recovery, flash rom, flash twrp again, reboot recovery, flash my kernel, flash magisk, reboot bootloader, fastboot -w, then boot to system.
Obviously I take more steps than needed. That's to flash my kernel, root and twrp after the flash before booting which isn't advised (wild child over here), you should fully boot first, then do the flashing of root, kernel, twrp, etc.
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
You beat me to it! I think we have a race going on here, lol. You are correct 100% though
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
Good deal brother thanks for the info.... I will give it a try for sure.....
blake .l said:
Good deal brother thanks for the info.... I will give it a try for sure.....
Click to expand...
Click to collapse
Let us know how it goes
Uzephi said:
Let us know how it goes
Click to expand...
Click to collapse
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
blake .l said:
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
Click to expand...
Click to collapse
Try the RC from 0509. I have been running it since the 9th with no issues.
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Technical said:
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Click to expand...
Click to collapse
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
mookiexl said:
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Technical said:
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Click to expand...
Click to collapse
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Uzephi said:
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Click to expand...
Click to collapse
Thanks. I've moved to https://forum.xda-developers.com/showpost.php?p=76754449&postcount=24 to ask you about .zip preparation file for XT1789-05 model.
Uzephi said:
Try the RC from 0509. I have been running it since the 9th with no issues.
Click to expand...
Click to collapse
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
blake .l said:
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
Click to expand...
Click to collapse
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Technical said:
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Click to expand...
Click to collapse
A few things, yes. Mainly the dirty tweaks in settings
Didn't really care for the DU. Although it does have working 4g on sprint(much props there). I just didn't personally like the "feel" of it. I'm rockin the unofficial LOS 15.1 right now and its pretty lovely. I'm limited to ROMs b/c of sprint but so far LOS kicks ass.
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.