Related
Hello,
I just ordered my X820 for dirt cheap (€136). I wanted to ask you about the routine of getting custom ROMs up and running.
From what I understand the procedure is the following:
1. Activate USB debugging and OEM unlocking
2. Go to fastboot and use OEM unlock
3. Fastboot flash recovery TWRP.img
4. Boot into TWRP and format data????
5. Wipe system, caches, data, blah blah
6. Sideload lineage.zip, gapps.zip and magisk.zip eventually
7. Profit
Is this procedure correct? On my other (Xiaomi Redmi Note 3) phone I skipped formatting data and it still worked.
I don't need the stock ROM backup, lineage is the main reason I purchased this device.
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
popoyaya said:
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
Click to expand...
Click to collapse
I saw a guide where it says I should boot into TWRP (yes, boot into TWRP, via fastboot) and do a backup from there... Than actually install TWRP and other zips. So I'll do that, thanks.
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Psps. once you flash a custom ROM you will want to flash an updated modem firmware as it fixes the fingerprint reader when the device sleeps for Nougat and experimental Oreo ROMs.
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
ThE_MarD said:
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Click to expand...
Click to collapse
Thanks for the valuable info. I appreciate OmniROM, and SlimRom, and basically everyone that has contributed with a line of code. But I'm more of a LineageOS guy, I like the official Lineage stuff.
You say that on the official TWRP adb sideload doesn't work??? Edit: Oh I see, I will try, if that fails I will use push, thanks again.
ThE_MarD said:
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Click to expand...
Click to collapse
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Happy Hepatitis said:
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Click to expand...
Click to collapse
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
ThE_MarD said:
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
Click to expand...
Click to collapse
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Happy Hepatitis said:
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Click to expand...
Click to collapse
Ah cool! You should be lucky then and not be stuck on one of those vendor ones like my x829.
The easy way to tell is in your settings you will have an update checker. My x829 did not and wouldn't let me try the recovery update.zip method.
So you'll want to get the EUI ROM latest for your phone and then rename it to update.zip and place it into the root of your sdcard (/sdcard) and then boot to recovery and there should be a selection for "update from file".
https://forum.xda-developers.com/le-max-2/how-to/le-max-2-official-stock-firmware-links-t3433761/
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
About
**********
I've created a flashable ROM zip of the latest H990DS KDZ SEA Region. Everything is working correctly on my H990 Single SIM.
ARB
**********
0
Security Patch
**********
1 April 2019
Download
**********
1. With modem & cust partitions (only if you know what you are doing):
https://drive.google.com/open?id=1YARnnE4-V1y9Jd1EhTzdizdkd6DaAYz_
2. Without modem & cust partitions (keeps your existing modem, recommended):
https://drive.google.com/open?id=1gCHxAk3hXjCsA4Qm3djgSmJEb3rSL5WA
Installation process:
**********
1. Upgrading / flashing over another stock Oreo ROM:
• Flash latest TWRP
• BACKUP everything
• Wipe (caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
2. Clean from scratch install:
• Flash latest TWRP
• BACKUP everything
• Backup everything you want to put back, it will be wiped
• Clean wipe (data, system, caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
sniper9911 said:
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
Click to expand...
Click to collapse
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
updated successfully
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
I just added H990DS_Hide_Boot_Warning.zip to remove the error message at boot start.
sniper9911 said:
Thanks for the update
Click to expand...
Click to collapse
tapir1505 said:
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
Click to expand...
Click to collapse
Thanks for your feedback!
Glad to know it is working correctly
Against 20a the only difference is s3curity patch?
faeterov said:
Against 20a the only difference is s3curity patch?
Click to expand...
Click to collapse
I'm not sure of any other difference except the security patch.
I assume there are some minor tweaks as the update notification
generally mentions "usability improvements", but LG being LG don't
release a change-log so who knows unfortunately...
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
luuhungit said:
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
Click to expand...
Click to collapse
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
jl10101 said:
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
Click to expand...
Click to collapse
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
luuhungit said:
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
Click to expand...
Click to collapse
Go to 10c root flash 20a partitions through Patched LGUP ignoring aboot aboot.bak and recovery recovery.bak (tarp may be gone but as long as you'll have boatloads unlocked you can flash twrp back)after that just flash only 20b system via LGUP Partitions DL I dunno whats going on with LG KDZs from now on all you should keep the old partitions from 20A and just flash system
jl10101 said:
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
Click to expand...
Click to collapse
unfortunately im using F800L, so it will not work if i flash this rom into my device.
is there any change to tell me how to update the security patch for my device?
thx b4 m8
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
stingbandel said:
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
Click to expand...
Click to collapse
Yes. Use mk200 beta38
Update to 20B and Just remember to back up firmware and efs folders from Oreo 20A and restore after flashing 20B otherwise you will lose the second sim
sniper9911 said:
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
Click to expand...
Click to collapse
I followed exact steps in OP (wiped caches, flashed 20b ROM, Magisk 19.3, MK2000 v2.2b38 H990DS, rebooted) and thought it worked for me as well until I noticed some built-in system apps were not working. Calendar, Chrome and others had strange names in Apps list (Chrome was called "add to dictionary" and Calendar was something like "on time (%s,..."). I managed to get them working again by stopping them and reinstalling from the apk files in system but wasn't sure I woudn't have other issues, so I wiped system partition and reflashed it although it didn't seem to change anything. When I noticed Bluetooth wouldn't enable I decided to go back to 20a by flashing full ROM (all done through TWRP) but that didn't fix the issue. I had even tried going back to MK2000 2.1 but no change. Finally had to do full restore from TWRP backup to get BT working again. Would like to have latest security patch.
Does anyone have any ideas what went wrong? Could any Magisk modules cause issues? Any help is appreciated.
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
(LG H990DS)
albaniax said:
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Salvaparalyzer said:
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Click to expand...
Click to collapse
I'm not sure why 20H is effectively a "newer" ROM going by LG's naming convention.
They used 20B (this ROM) with a newer security patch, and the actual file is newer than 20H.
I would normally assume that 20H should have a newer security patch and be a newer build of Oreo, but it seems not.
This ROM essentially is the latest available. I cannot find any changelogs to verify that 20H has a newer system / android build though. Sorry!
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
deleted
What version of RR Pie did you test? The May Release?
JDBS30 said:
What version of RR Pie did you test? The May Release?
Click to expand...
Click to collapse
all of them.
this link i used and choose one of them from your choice arm a only of course: https://get.resurrectionremix.com/?dir=gsi
I can't install Resurrection Remix
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
elfennani said:
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
Click to expand...
Click to collapse
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
rudi021 said:
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
Click to expand...
Click to collapse
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
elfennani said:
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
Click to expand...
Click to collapse
like i wrote your device must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
rudi021 said:
like i wrote you must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
Click to expand...
Click to collapse
How did you downgrade your firmware?
elfennani said:
How did you downgrade your firmware?
Click to expand...
Click to collapse
i found oreo firmware. if you want you can download from my google drive. here is link: https://drive.google.com/file/d/1KnqHZ8_EVTstJP5AMsMy_8Uc1QV-vMHe/view?usp=sharing
Please help
rudi021 said:
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
Click to expand...
Click to collapse
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Maxmiliano Coelho said:
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Click to expand...
Click to collapse
my dear friend just ask i will help you. this patched boot.img is made by ashyx. i will be bad member if i share his works without permissions.so i share with you his link. here is link for oreo patched boot.img https://androidfilehost.com/?fid=1395089523397921797
please follow instructions carefully. read twice and try to understand.enjoy.if you have any doubt please ask. thank you.
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
why not.i am not star just ask and if i can help i will please to do that.you can always send me personal message(PM) on xda
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
rudi021 said:
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
Click to expand...
Click to collapse
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Maxmiliano Coelho said:
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Click to expand...
Click to collapse
once you perform flashing gsi,no need repeat every time this steps,just (at least i do like that) format data,reboot to recovery,flash gsi(as system.image) and flash magisk then mount system and reboot.about audio volume install viper fx audio apk(Magisk module),and then fix volume as your own.
kapmino269 said:
If anyone faced problems with booting some roms on
ROM LOGO NOT SAMSUNG .
use this :
https://www.androidfilehost.com/?fid=6006931924117925309
Tested on j415f
RR
AOSP
DESCENDANT ZERO .
Click to expand...
Click to collapse
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
rudi021 said:
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
Click to expand...
Click to collapse
me i have not a network on aex extended but on dot os i have
Envoyé de mon Phh-Treble vanilla en utilisant Tapatalk
kapmino269 said:
Guys , sorry I found error in my script and I fixed it I tested it on AEX official , I will test it in others then post it .
@rudi021
---------- Post added at 09:15 AM ---------- Previous post was at 08:29 AM ----------
v2 : https://www.androidfilehost.com/?fid=6006931924117930007
tested : work with rom logo bootloop 100%
Click to expand...
Click to collapse
thank you bro. i definetly try this on pie upgrade and inform you.thank you for your hard work. i am on vacation and when i come home i will try this.thank you and greetings from Croatia.:good:
also i stop build gsi roms for j4+ because my pc is old so i need little upgrade of same( RAM(have only 4 gb,need for pie at least 8 gb ,my motherboard can have 32 gb,), my processor is i3 but i will upgrade on i5 and after that i will continue work on it. but now i am on vacation with my wife and children and when i come hom ei will continue to work it.thank you once more.
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.