Related
A week ago I flashed the current (lineage-14.1-20170504-nightly-oneplus3-signed.zip) lineage os nightly to my phone. I did not pay that much attention til I realize the impact, so no guarantee for the temporal order. I am pretty shure, that in the first place, I tried to flash the image via the update menu (is this called OTA update?). The previous update two weeks ago already results in partial data los. By this I mean some (maybe all) apps disappears after the update, but after installing them again, all of them provided the pre-update data - only exception was signal. This time the phone was like in factory state. But when I try to reinstall the telegram app - the app store refuses to install the app because of the presence of a identical named app.
Using adb shell shows me, that all apps and data where still present in the /data subdirectories. Even those I didn't had reinstalled til that time . So I took advantage of momentum and backed up some files and decided to perform a full pre factory reset formatting everything twrp let me format. After flashing the lineage update, another full format because things seems still weird, second lineage nightly flash, realizing I have to first flash OOS-x.y.z and a final third lineage flash, I thought I finally obtain a running system. After initial configuration I decided to only copy my previous wpa_supplicant.conf file back to the system. Since overwriting this file while running android didn't led to anything, I tried to replace this file in recovery mode. Instead of remembering my password, goatish oneplus 3 desides to perform factory reset.
After what seems to be a lower six digit number of flashing attemps I came to the conclusion that performing any modification to the file system while the native kernel is not running results in factory reseting the device. In the mean time I also figured out what dm-verity means - an error message I got used to and maybe a nice feature as long as you don't try to take your old config files to a new system. And I know I am the millionth person facing that problem in a dedicated thread, but I found nothing which links this annoying boot loader message to my reset problem.
I made my previous recovery attemps between the toilet and my bed, so I hadn't any strategy at all. But thank god its friday! I read: dm-verity is a feature of the device mapper which guarantees data integrity. When I alter the data using any other than the native system, the device mapper notices the integrity violation and reports to the system. I am only guessing that this makes the system to reset itself - Am I right? Even if I appreciate this concept, I think this might be a little too ambitious. Can I alter androids behaviour in this point? In the best case I want to temporary disable this feature, do some root stuff and turn it on again. Is this possible?
I could follow one of that numerous tutorials to remove that dm-verity message, but I am not confortable with flashing zip files from dubious file hosters as well as copy-pasting commands without any idea of what I am doing. So maybe someone could provide a little more information than the seven step recipe of getting rid of that error message blog posts.
I really appreciate material which explains my problem. I am quite new to android and I didn't figured out how to maneuver around all these google results which tells me to install a specific app which may will hide my problem. So thank you in advance.
hinerk0815 said:
A week ago I flashed the current (lineage-14.1-20170504-nightly-oneplus3-signed.zip) lineage os nightly to my phone. I did not pay that much attention til I realize the impact, so no guarantee for the temporal order. I am pretty shure, that in the first place, I tried to flash the image via the update menu (is this called OTA update?). The previous update two weeks ago already results in partial data los. By this I mean some (maybe all) apps disappears after the update, but after installing them again, all of them provided the pre-update data - only exception was signal. This time the phone was like in factory state. But when I try to reinstall the telegram app - the app store refuses to install the app because of the presence of a identical named app.
Using adb shell shows me, that all apps and data where still present in the /data subdirectories. Even those I didn't had reinstalled til that time . So I took advantage of momentum and backed up some files and decided to perform a full pre factory reset formatting everything twrp let me format. After flashing the lineage update, another full format because things seems still weird, second lineage nightly flash, realizing I have to first flash OOS-x.y.z and a final third lineage flash, I thought I finally obtain a running system. After initial configuration I decided to only copy my previous wpa_supplicant.conf file back to the system. Since overwriting this file while running android didn't led to anything, I tried to replace this file in recovery mode. Instead of remembering my password, goatish oneplus 3 desides to perform factory reset.
After what seems to be a lower six digit number of flashing attemps I came to the conclusion that performing any modification to the file system while the native kernel is not running results in factory reseting the device. In the mean time I also figured out what dm-verity means - an error message I got used to and maybe a nice feature as long as you don't try to take your old config files to a new system. And I know I am the millionth person facing that problem in a dedicated thread, but I found nothing which links this annoying boot loader message to my reset problem.
I made my previous recovery attemps between the toilet and my bed, so I hadn't any strategy at all. But thank god its friday! I read: dm-verity is a feature of the device mapper which guarantees data integrity. When I alter the data using any other than the native system, the device mapper notices the integrity violation and reports to the system. I am only guessing that this makes the system to reset itself - Am I right? Even if I appreciate this concept, I think this might be a little too ambitious. Can I alter androids behaviour in this point? In the best case I want to temporary disable this feature, do some root stuff and turn it on again. Is this possible?
I could follow one of that numerous tutorials to remove that dm-verity message, but I am not confortable with flashing zip files from dubious file hosters as well as copy-pasting commands without any idea of what I am doing. So maybe someone could provide a little more information than the seven step recipe of getting rid of that error message blog posts.
I really appreciate material which explains my problem. I am quite new to android and I didn't figured out how to maneuver around all these google results which tells me to install a specific app which may will hide my problem. So thank you in advance.
Click to expand...
Click to collapse
Your story is too long to go through. But most likely your issue will be solved if you install blue sparks twrp. Check his thread in the unified section
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps :
Open Gapps Click Here
Choose Platform: ARM, Android: 10.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 10 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lock screen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][10.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community the quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 17.x
Version Information
Status: Stable
Created 2020-24-01
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
duplicated
Really nice! Getting a battery replacement for my Droid so that it can work as a backup phone. Tysm for Android 10!
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Inform what you are doing
The ROM is much much smoother than pie ROMs...Thank you so much bro ......Android 10 on this 6 year old handset is just unbelievable....
fgl27 said:
Inform what you are doing
Click to expand...
Click to collapse
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
And just the ROM? What happens
fgl27 said:
And just the ROM? What happens
Click to expand...
Click to collapse
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Thanks / Flashlight issue
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
fgl27 said:
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Click to expand...
Click to collapse
Yoiks! Not quite that tech savy. Even tried after a full wipe & zip-by-zip install. If I have to be happy with RR Pie, so be it. Not all that bad. My Turbo has some miles on it, rebuilt twice already. Got one last battery & display in the wings. Best, last phone Motorola made. Don't waste your time, further, on what's likely a hardware flaw.
Sent from my LM-V405 using Tapatalk
I think your not using latest twrp
newbe1droidx said:
I think your not using latest twrp
Click to expand...
Click to collapse
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Kinzhal said:
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
Click to expand...
Click to collapse
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
Einsteindks said:
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
fgl27 said:
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
Click to expand...
Click to collapse
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
noting crashing to me, sim or no sim.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
TWRP HH for Nexus 5
About:
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
You can find the source code for TWRP on GitHub. If you would like to contribute to TWRP, please visit Gerrit Code Review.
Features:
HH.S version with stock partitions map. S means stock.
HH.R version with repartition support. R means repartition.
Working decryption on custom roms. Tested on LOS 16.0, LOS 17.1, LOS 18.1, but should work on all Androids since Nougat.
exFAT and NTFS support (read and write) for USB OTG
Requirements:
You need to have an unlocked bootloader to install and use TWRP!
Known bugs:
Everything looks good so far
Downloads:
https://sourceforge.net/projects/hammerhead-twrp/files/beta/
Credits:
TeamWin
@Clamor
@steadfasterX
And all the contributors out there in the community
Contributors:
@z3DD3r
Source Code:
Device tree: https://github.com/z3DD3r/twrp_android_device_lge_hammerhead
Version Information:
Satus: Stable
TWRP version: 3.7.0_9
HH Project versions: HH.S.17 and HH.R.17
Created: 2020-02-08
Last Updated: 2022-02-06
Repartition (HH.R versions)
ALWAYS DO THE BACKUPS!!!
No one is responsible for your actions!
Repartition may potentially brick your device, although risk is reduced to minimum.
Features:
Increases /system partition to ~1444Mb
Decreases /cache partition to ~255Mb
Doesn't provide /vendor partition
Doesn't touch /data partition
Requirements:
Not modified partitions by any other solutions
How to increase /system partition and change partitions map:
- Flash the HH.R version of TWRP and launch it
- Open terminal (TWRP -> Advanced -> Terminal)
- Type hh_repart -m
- Wait until your phone reboots
- Install your rom
How to revert back to stock /system size and stock partitions map:
- Launch HH.R version of TWRP
- Open terminal (TWRP -> Advanced -> Terminal)
- Type hh_repart -r
- Wait until your phone reboots
- Flash official TWRP or HH.S version of TWRP! Don't ignore this step!
- Install your rom
How to dump partitions map:
- Launch HH.R version of TWRP
- Open terminal (TWRP -> Advanced -> Terminal)
- Type hh_repart -d
- Wait until process finishes
- Look at /sdcard/partitions.log file
reserved
reserved
Some technical notes about the decryption and Android Q support.
Right now the only possible way to decrypt data on our devices is to use system's vold. This logic was added to TWRP some time ago but one required change wasn't in the tree. This change is here: https://gerrit.twrp.me/c/android_bootable_recovery/+/1919. Without this patch system's vold will fail on hammerhead. I don't know why but services in the sbin can't handle decryption. Also using the system's vold means that ROM should be installed to decrypt data. Without installed ROM decryption is not possible!
About SAR and Android Q. Work on SAR support in TWRP is still in progress but some patches are already available on gerrit. These patches are required to properly detect SAR and mount partitions. Also since Android Q one more service should be run before trying to decrypt data. This service is apexd. Android Q runs apexd on early-init stage to provide required runtime libraries. U can see how it launched at https://android.googlesource.com/pl...fs/tags/android-10.0.0_r29/rootdir/init.rc#37. Only after that step all other services like qseecomd, hwservicemanager, servicemanager and keymaster can be run from system or vendor.
The last point is prebuilt vdc. Prebuilt vdc_pie which is shipped with TWRP fails to run because of linker error. I don't remember exactly what was the error but i guess that something is removed in libc. To fix that problem i've built vcd_ten binary with Android Q sources and placed it into device tree for hammerhead as a temporary solution. The source code of that binary is identical to vdc_pie which located at https://github.com/TeamWin/android_...b/android-9.0/crypto/vold_decrypt/vdc_pie.cpp
This is just a quick notes about what was done.
Patched bootable_recovery is located at https://github.com/z3DD3r/twrp_android_bootable_recovery/tree/android-9.0
Device tree for Q located at https://github.com/z3DD3r/twrp_android_device_lge_hammerhead/tree/q-sar
I hope this will be helpful for TWRP Team!
PS: Changes i've made should be improved. Don't treat them as production ready and/or stable!
FYI @Dees_Troy
Hi, thank you very much for this solution.
hh_repart -d - worked but I couldn't read the log file before rebooting, maybe it's obvious
hh_repart -m - worked without any issues
I have also successfully flashed Lineage 17.1 from your other thread, gapps and Magisk.
New versions are up (HH.S.3 and HH.R.3)
Added exFAT and NTFS support (read and write) for USB OTG
Kernel image is compressed with XZ LZMA2 compression algorithm (smaller size of the recovery image)
New versions are up (HH.S.4 and HH.R.4)
Fixed mounting issues of the system partition
Fixed device overheating while in recovery
I highly suggest everyone update to this version!
I have a question, certainly not in any way a complaint.
I have been running HH4 for a few days. Last night I made a TWRP backup of my LineageOS 17.1, which I installed on 20th without Gapps to see how it works without Google - quite well, in fact, with the help of APK Updater.
This morning I stupidly applied the 22nd update with Gapps - I was on autopilot and forgot that this device had no Google.
No problem, I thought, I'll just restore last night's backup. So I did a total wipe and format ("yes"), but no backup will restore. I just get the LOS line-&-circle animation for ages. I've tried earlier backups, and even standard unmodified TWRP, all with the same result. No backup will restore.
It's not a big deal - I can start with a totally new installation - but I'd like to know if anyone has taken a backup and successfully restored it. Or am I just lucky...? If I can't restore, then it sort of defeats the point of TWRP, no?
Edit: Seriously, 85 people have downloaded HH4. Has not a single one of you tried a restore of a backup?
Edit: Tumbleweed...
Edit: Do I take it that nobody has tried to restore a backup? If you haven't, and my experience is normal, then we're risking a two-hour fresh install in case of update problems rather than a two-minute restore.
dahawthorne said:
I have a question, certainly not in any way a complaint.
I have been running HH4 for a few days. Last night I made a TWRP backup of my LineageOS 17.1, which I installed on 20th without Gapps to see how it works without Google - quite well, in fact, with the help of APK Updater.
This morning I stupidly applied the 22nd update with Gapps - I was on autopilot and forgot that this device had no Google.
No problem, I thought, I'll just restore last night's backup. So I did a total wipe and format ("yes"), but no backup will restore. I just get the LOS line-&-circle animation for ages. I've tried earlier backups, and even standard unmodified TWRP, all with the same result. No backup will restore.
It's not a big deal - I can start with a totally new installation - but I'd like to know if anyone has taken a backup and successfully restored it. Or am I just lucky...? If I can't restore, then it sort of defeats the point of TWRP, no?
Edit: Seriously, 85 people have downloaded HH4. Has not a single one of you tried a restore of a backup?
Edit: Tumbleweed...
Edit: Do I take it that nobody has tried to restore a backup? If you haven't, and my experience is normal, then we're risking a two-hour fresh install in case of update problems rather than a two-minute restore.
Click to expand...
Click to collapse
Have u tried to restore backup of other ROMS? I guess it is not TWRP's problem...
dahawthorne said:
I have a question, certainly not in any way a complaint.
I have been running HH4 for a few days. Last night I made a TWRP backup of my LineageOS 17.1, which I installed on 20th without Gapps to see how it works without Google - quite well, in fact, with the help of APK Updater.
This morning I stupidly applied the 22nd update with Gapps - I was on autopilot and forgot that this device had no Google.
No problem, I thought, I'll just restore last night's backup. So I did a total wipe and format ("yes"), but no backup will restore. I just get the LOS line-&-circle animation for ages. I've tried earlier backups, and even standard unmodified TWRP, all with the same result. No backup will restore.
It's not a big deal - I can start with a totally new installation - but I'd like to know if anyone has taken a backup and successfully restored it. Or am I just lucky...? If I can't restore, then it sort of defeats the point of TWRP, no?
Edit: Seriously, 85 people have downloaded HH4. Has not a single one of you tried a restore of a backup?
Edit: Tumbleweed...
Edit: Do I take it that nobody has tried to restore a backup? If you haven't, and my experience is normal, then we're risking a two-hour fresh install in case of update problems rather than a two-minute restore.
Click to expand...
Click to collapse
With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 14.1 with encyption = ok
With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 17.1 with encyption = ok
sant514 said:
With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 14.1 with encyption = ok
With TWRP 3.3.1-HH.R.4 nanroid backup and restore in LOS 17.1 with encyption = ok
Click to expand...
Click to collapse
Can u tell me which build of LOS 17.1 have u used for these tests?
Los 17.1 28-02-2020
sant514 said:
Los 17.1 28-02-2020
Click to expand...
Click to collapse
Thanks! U just confirmed that LOS 17.1 could not be restored due to selinux denials. Some days ago i've updated sepolicies and now everything works.
@dahawthorne, FYI
Excellent news - thank you.
And also a relief to find that I wasn't just being an idiot...
I see "E:Unable to decrypt FBE device" when flashing in TWRP.
Should I just disregard this message?
smsmasters said:
I see "E:Unable to decrypt FBE device" when flashing in TWRP.
Should I just disregard this message?
Click to expand...
Click to collapse
Just ignore it.
Our device doesn't support FBE (file based encryption). So this error doesn't affect our device at all.
Since I was the one to mention my problem with restoring a TWRP image, I think I should report that, as z3DD3r stated above, TWRP HH 4 does indeed work fine in making and restoring backups. I took a backup yesterday and restored it this morning; no wipe, just a straight recovery, and it all went through in less than two minutes.
Thanks for all your work, z3DD3r. It's great to have bleeding-edge software on such an old device.
Hello @z3DD3r , I've been working on a ship for the last couple of months, so missed some things.
I'm using the first original twrp-3.3.1-HH-hammerhead version you shared in the telegram group, but now I found this thread with newer versions.
Just wanted to double check if it's okay to update straight from that original HH version (ALREADY REPARTED) to the lates HH.R.4 without any problems.
z3DD3r said:
How to revert back to stock /system size and stock partitions map:
- Launch HH.R version of TWRP
- Open terminal (TWRP -> Advanced -> Terminal)
- Type hh_repart -r
- Wait until your phone reboots
- Flash official TWRP or HH.S version of TWRP! Don't ignore this step!
Click to expand...
Click to collapse
And just out of curiosity, cause I'm not planning on reverting to stock partitions. Why is it so important to flash official or HH.S version after reverting?
What is the difference between stock and HH.S.4 then?
Thanks for putting your time and efforts in to keeping this device alive!
TomiLynch said:
Hello @z3DD3r , I've been working on a ship for the last couple of months, so missed some things.
I'm using the first original twrp-3.3.1-HH-hammerhead version you shared in the telegram group, but now I found this thread with newer versions.
Just wanted to double check if it's okay to update straight from that original HH version (ALREADY REPARTED) to the lates HH.R.4 without any problems.
Click to expand...
Click to collapse
twrp-3.3.1-HH-hammerhead and TWRP HH.R uses the same script for repartition. So, yes, it is okay to flash HH.R over the twrp-3.3.1-HH-hammerhead.
TomiLynch said:
And just out of curiosity, cause I'm not planning on reverting to stock partitions. Why is it so important to flash official or HH.S version after reverting?
What is the difference between stock and HH.S.4 then?
Thanks for putting your time and efforts in to keeping this device alive!
Click to expand...
Click to collapse
Because TWRP includes size of system partition. This size should match the size of system partition on device. Otherwise bad things can happen...
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
What's working?
Everything as far as I can tell...
Installation
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads: http://1pwn.ixmoe.com/android/ginna/los-18.1/lineage-18.1-20210621-HOMEMADE-ginna.zip
Notes
This ROM comes with Google Apps!
This ROM comes with Customizations that are not apart of LineageOS
Sources: https://github.com/motoe7
Credits: @electimon, @RohanHasabe8, betaxab
Jan 27 2021: Fix Safetynet, fix touch issues, fix some other issues
Jan 28 2021: Fix PIP mode
Jan 30 2021: Fix Hotspot
June 2 2021: Fix touch for ginna models with the new panel
June 15 2021: Fix touch for focaltech panels
June 20 2021: June Patch, fix safetynet and other little stuff
Awesome, been waiting for this, thanks very much! Had some errors while loading copy-partitions.zip but the image flashed and seems to be working well. Look forward to future versions with SELinux enforcing and also without gapps (but maybe that's not likely with no opengapps for 11?)
Would be great if there was a way to remove the obtrusive "device can't be trusted" message at boot. It can be just as trusted as my desktop PC ffs. At least moto allows the bootloader unlock without much trouble.
anthony.d said:
Awesome, been waiting for this, thanks very much! Had some errors while loading copy-partitions.zip but the image flashed and seems to be working well. Look forward to future versions with SELinux enforcing and also without gapps (but maybe that's not likely with no opengapps for 11?)
Would be great if there was a way to remove the obtrusive "device can't be trusted" message at boot. It can be just as trusted as my desktop PC ffs. At least moto allows the bootloader unlock without much trouble.
Click to expand...
Click to collapse
hi, selinux is enforcing also there will be no version without gapps sorry
Electimon said:
hi, selinux is enforcing also there will be no version without gapps sorry
Click to expand...
Click to collapse
No worries about the gapps, i'm grateful to have a lineage rom for this device.
I tried flashing again. Pardon if the details below are excessive, I don't fully understand the process, and the dual-slice device config. Here's what happened:
copy-partitions gets to 47%, then fails with the following error:
Partition vendor_a
dd: /dev/block/dm-4: write error: No space left on device
installed lineage again, this time went to slot B. rebooted back into TWRP and tried copy-partitions again (to see if it was different after lineage had been installed in both slots) and this time it succeeded. Installed lineage again, this time to slot A. Wiped the device, rebooted, and I still get the selinux error. If it's relevant, the device model is XT2052-1.
Also want to add: I applied disable-verity both times, and cmd line output indicated writing to vbmeta_a and vbmeta_b.
weird, how are you checking for enforcing?
android_device_motorola_ginna/BoardConfig.mk at efea8269c9a6a232d8ba38b0629a61eb590b2db5 · motoe7/android_device_motorola_ginna
Contribute to motoe7/android_device_motorola_ginna development by creating an account on GitHub.
github.com
you can see here that permissive is commented out, the rom is enforcing.
I installed the rom mainly as a reference against the no speaker (except in calls) issue I'm having with 17.1. Also I'll note there the issue isn't jacksensing as I had guessed. A soundfile playback autopauses on headphone removal. With 18.1 here I do get speaker output, however one bug I noticed for me (boostmobile-sku:mot20526anb/xt2052-6) (also present in 0206 17.1) is that in-call volume adjust doesn't work. The indicator moves, but the actual volume does not. I'll send some logcats. Seems to be stuck at what is probably supposed to be max volume.
Electimon said:
there will be no version without gapps sorry
Click to expand...
Click to collapse
Is there a standard/safe way to uninstall gapps via scripted adb commands immediately after install? I experimented with a crude attempted pm uninstall/disable/disable-user of all com.google.* packages but was not too surprised when the result failed to boot past the lineageos boot animation.
Cyb3rSl4v3 said:
Is there a standard/safe way to uninstall gapps via scripted adb commands immediately after install? I experimented with a crude attempted pm uninstall/disable/disable-user of all com.google.* packages but was not too surprised when the result failed to boot past the lineageos boot animation.
Click to expand...
Click to collapse
I'm unsure of that
I finally figured out how to build 18.1 on my 8g-ram system such that I don't have to worry about uninstalling gapps (amongst other motivations). I'll post details once I've done another less manual build. The trickiest part was that the 17.1 workaround of setting JAVA_TOOL_OPTIONS/_JAVA_OPTIONS to -Xmx6g wasn't getting used by metalava in 18.1. I ended up editing the last line of out/soong/host/linux-x86/bin/metalava and putting it in there which finally worked. Perhaps tools/metalava/gradle.properties is the right place. My first pass doesn't have carrier data/call service working, but that may be because I did something with TimeService to get it to compile. In any event, I think the 16g minimum warning from the build system is more than a bit confusing combined with the metalava java heap issues. I may try a 4g-ram build sometime just for amusement... It just seemed inconceivable that there really was a 16g-ram requirement. I know even phones come with 16g these days, but still. Of course my hope is to see a cheap phone of mine self-hosting one of these days. Perhaps with some high end microsd card or an otg drive for swap partition and build tree...
Cyb3rSl4v3 said:
I finally figured out how to build 18.1 on my 8g-ram system [...] The trickiest part was that the 17.1 workaround of setting JAVA_TOOL_OPTIONS/_JAVA_OPTIONS to -Xmx6g wasn't getting used by metalava in 18.1. I ended up editing the last line of out/soong/host/linux-x86/bin/metalava and putting it in there which finally worked. Perhaps tools/metalava/gradle.properties is the right place.
Click to expand...
Click to collapse
I haven't quite done a fully automated build yet, but tools/metalava/gradle.properties didn't work for me. Then I found that the metalava (wrapper) script was build/soong/scripts/jar-wrapper.sh, and adding a next to last line of-- javaOpts+=("-Xmx6g") --seems to work. I also now better understand device/motorola/ginna/lineage.dependencies and seem to be able to reproduce this image sans gapps (though an selinux issue i haven't looked too much at yet). I may focus more on 17.1 until 18.1 becomes more generally official. I also seem to be getting occasional sigsegvs with jre/metalava dumping hs_err_pid*.logs. However thus far a simple rerun of brunch/ginna has never reproduced the problem.
Camera apps have quite a lag related to camera apiv2. Haven't had time to debug, but Open Camera works perfect as it defaults to the old api.
Do we have system read/write on these builds and does magisk work?
Idk about system r/w, but Magisk works fine. This is also a really good rom. Stable and nearly everything works.
fddm said:
Idk about system r/w, but Magisk works fine. This is also a really good rom. Stable and nearly everything works.
Click to expand...
Click to collapse
I checked, it has system rw. I can't believe how fast my LTE speeds are too. 7-10MBs vs 50kbs on stock. The only thing holding me back is no full screen toggle for apps, and the in call volume is stuck at the maximum at all times. Soon as those get fixed I'm running this 24/7.
2+ months now with 18.1 on my daily driver.
No hardware issues.
Ofox recovery.
Magisk 21.4 thru the latest canary build have worked as far as I can tell.
No volume troubles.
Can mount system RW.
My only setback is that I don't have access to around 9Gb on /data and /sdcard, including /sdcard/Android/obb
I can set perms any way in terminal and in recovery terminal 0777, 0655, etc., but upon reboot, I cannot read or write.
Can read and write to /system and /system_root, no problem.
This is possibly due to me forgetting to wipe encrypted /data after first flash? I wiped after first boot, no change.
Then, started the flash process from scratch and wiped before first boot, but must have missed something.
The file and folder names are not random characters.
One of those things I thought will work out when I get around to it, but now just found my pics are being saved to a folder in the mystery space, and I need to place a .zip in *./obb.
Im learning, A/B is new to me.
Maybe my mistake will help someone when I find a solution.
I am open to suggestions, lessons, and any other info, even if I should already know it.
I will report when something changes.
RaceyMcRacerson said:
2+ months now with 18.1 on my daily driver.
No hardware issues.
Ofox recovery.
Magisk 21.4 thru the latest canary build have worked as far as I can tell.
No volume troubles.
Can mount system RW.
My only setback is that I don't have access to around 9Gb on /data and /sdcard, including /sdcard/Android/obb
I can set perms any way in terminal and in recovery terminal 0777, 0655, etc., but upon reboot, I cannot read or write.
Can read and write to /system and /system_root, no problem.
This is possibly due to me forgetting to wipe encrypted /data after first flash? I wiped after first boot, no change.
Then, started the flash process from scratch and wiped before first boot, but must have missed something.
The file and folder names are not random characters.
One of those things I thought will work out when I get around to it, but now just found my pics are being saved to a folder in the mystery space, and I need to place a .zip in *./obb.
Im learning, A/B is new to me.
Maybe my mistake will help someone when I find a solution.
I am open to suggestions, lessons, and any other info, even if I should already know it.
I will report when something changes.
Click to expand...
Click to collapse
I never had this issue so I'm guessing it's something to do with encryption. I would try clean flashing LOS to both slots then formatting data using the type "yes" option to remove encryption. Are you using adoptable storage by chance?
How can I install this rom via recovery, I have never used side load. Why is it not booting? What is wrong. I flashed rom in slot B with twrp in slot A sorry still a little new with this device. But regardless it is not booting whatsoever and I am confused as to why
Mr.Conkel said:
How can I install this rom via recovery, I have never used side load. Why is it not booting? What is wrong. I flashed rom in slot B with twrp in slot A sorry still a little new with this device. But regardless it is not booting whatsoever and I am confused as to why
Click to expand...
Click to collapse
Flash it to both slots and format data before booting up.
Spaceminer said:
Flash it to both slots and format data before booting up.
Click to expand...
Click to collapse
Is there any benefit of having it flashed to both? Cause I did get it working. There's not currently anything on slotB
Mr.Conkel said:
Is there any benefit of having it flashed to both? Cause I did get it working. There's not currently anything on slotB
Click to expand...
Click to collapse
Not that I'm aware of. I've never got it to boot without flashing to both slots though. Did you use the zip, or fastbootd images?
Hello everybody. I installed LineageOS 19.1 for microG on my Xiaomi Mi 10T Lite and so far everything is ok. The problems began to appear when I attempted to install Android Auto using the NikGapps package (which I compiled by entering only Android Auto as mentioned in this thread https://forum.xda-developers.com/t/microg-android-auto-fully-working.4319159): the package installation fails as it detects the "system" partition is full and after some checks I found that there are only a few MBs free (while for the installation of Android Auto I would need something like 40 MBs). In the aforementioned post this problem is mentioned but the only solution proposed is to manually compile the ROM from source in order to reserve less space for the installation of microG, but I haven't found any guide to do such a thing. The last thing I tried to do was to replicate the instructions in this other article (https://androidhiro.com/source/ques...-system-partition-and-decrease-data-partition) where they discuss about resizing the "system" partition, but as I have seen the partitioning scheme is definitely different from the Nexus 5's (the device mentioned in this other thread). Any tips or workarounds at this point would be really appreciated