Device: LG V30+
No matter which ROM I try, device encryption (from settings) fails every time. The process does nothing, it just shows the Android logo and reboots. It works on stock firmware (I think, just an option to require password upon boot) but I need encryption on a ROM without Google apps.
I've been trying to get this thing set up all day, if anyone can help I will be beyond thankful.
Averie said:
Device: LG V30+
No matter which ROM I try, device encryption (from settings) fails every time. The process does nothing, it just shows the Android logo and reboots. It works on stock firmware (I think, just an option to require password upon boot) but I need encryption on a ROM without Google apps.
I've been trying to get this thing set up all day, if anyone can help I will be beyond thankful.
Click to expand...
Click to collapse
Which ROMs? On AOSP based ones encrpytion is (for now) completly disabled, because it ****ed with TWRP (even though only encryptable, twrp couldnt mount /data anymore)
an option would be to modify the fstab
(/systen/vendor/etc/fstab.joan or so), commit that removed it is here: https://github.com/SGCMarkus/androi...mmit/e285c593f249e48d1b3a8048a1d173cc2a6f21a0
just add that back (after mounting system as read/write), and then reboot after saving
SGCMarkus said:
Which ROMs? On AOSP based ones encrpytion is (for now) completly disabled, because it ****ed with TWRP (even though only encryptable, twrp couldnt mount /data anymore)
an option would be to modify the fstab
(/systen/vendor/etc/fstab.joan or so)
just add that back (after mounting system as read/write), and then reboot after saving
Click to expand...
Click to collapse
Ohh OK, that makes sense now. The ROMs were a few you have listed, Lineage, AospExtended, RR, etc.
Thank you for clarifying!
Question, how would I go about modifying the fstab? I'll try it myself but I've never done this before.
Averie said:
Ohh OK, that makes sense now. The ROMs were a few you have listed, Lineage, AospExtended, RR, etc.
Thank you for clarifying!
Question, how would I go about modifying the fstab? I'll try it myself but I've never done this before.
Click to expand...
Click to collapse
for modifying it
spaces matter (the amount doesnt though), same for new lines
and to make it writeable
either go to twrp and mount system as rw (you could adb pull it, then edit it on pc (just not with windows editor) and push it back to the old location, overrides it)
or remount system (adb remount)
and then edit it with some text editor on your phone (from a root file explorer most likely)
how it should look like, check the commit from the link in my previous post
SGCMarkus said:
for modifying it
spaces matter (the amount doesnt though), same for new lines
and to make it writeable
either go to twrp and mount system as rw (you could adb pull it, then edit it on pc (just not with windows editor) and push it back to the old location, overrides it)
or remount system (adb remount)
and then edit it with some text editor on your phone (from a root file explorer most likely)
how it should look like, check the commit from the link in my previous post
Click to expand...
Click to collapse
It works
Thank you so much, I appreciate your work.
SGCMarkus said:
Which ROMs? On AOSP based ones encrpytion is (for now) completly disabled, because it ****ed with TWRP (even though only encryptable, twrp couldnt mount /data anymore)
an option would be to modify the fstab
(/systen/vendor/etc/fstab.joan or so), commit that removed it is here: https://github.com/SGCMarkus/androi...mmit/e285c593f249e48d1b3a8048a1d173cc2a6f21a0
just add that back (after mounting system as read/write), and then reboot after saving
Click to expand...
Click to collapse
This does not seem to be working on LG v30 H932 LineageOS 16 lineage-16.0-20190610-UNOFFICIAL-h932.zip
It hangs at 00:00 time left and never finishes encrypting. If I reboot the phone tells me that data is corrupted.
ShapeShifter499 said:
This does not seem to be working on LG v30 H932 LineageOS 16 lineage-16.0-20190610-UNOFFICIAL-h932.zip
It hangs at 00:00 time left and never finishes encrypting. If I reboot the phone tells me that data is corrupted.
Click to expand...
Click to collapse
See the age of the thread? It was for Oreo (encryption still worked there). Not for Pie, that has broken encryption on AOSP (idk if the pie blobs for los17 or so help with that)
SGCMarkus said:
See the age of the thread? It was for Oreo (encryption still worked there). Not for Pie, that has broken encryption on AOSP (idk if the pie blobs for los17 or so help with that)
Click to expand...
Click to collapse
I'm sorry, but not all the information for this device is terribly organized. It was hard for me to figure out that it was broken and not just "user error" by myself. It took you to tell me this, thank you!
Do you happen to have a idea exactly what is crashing or going wrong when encryption is triggered? I'm not that familiar with the lower level hardware and software so I'm not sure how the newer blobs would help.
ShapeShifter499 said:
This does not seem to be working on LG v30 H932 LineageOS 16 lineage-16.0-20190610-UNOFFICIAL-h932.zip
It hangs at 00:00 time left and never finishes encrypting. If I reboot the phone tells me that data is corrupted.
Click to expand...
Click to collapse
ShapeShifter499 said:
I'm sorry, but not all the information for this device is terribly organized. It was hard for me to figure out that it was broken and not just "user error" by myself. It took you to tell me this, thank you!
Do you happen to have a idea exactly what is crashing or going wrong when encryption is triggered? I'm not that familiar with the lower level hardware and software so I'm not sure how the newer blobs would help.
Click to expand...
Click to collapse
Were you on stock Oreo or stock Pie before installing LOS-16?
ChazzMatt said:
Were you on stock Oreo or stock Pie before installing LOS-16?
Click to expand...
Click to collapse
I was in talks with SGCMarkus on Telegram and others. It's been determined to be a SELinux policy issue. It encrypts fine with SELinux set to permissive but not enforcing. I'm trying to sort out the issue but hopefully some others are also working on it now that I have found the issue and reported it in the Telegram channel.
ChazzMatt said:
Were you on stock Oreo or stock Pie before installing LOS-16?
Click to expand...
Click to collapse
ShapeShifter499 said:
I was in talks with SGCMarkus on Telegram and others. It's been determined to be a SELinux policy issue. It encrypts fine with SELinux set to permissive but not enforcing. I'm trying to sort out the issue but hopefully some others are also working on it now that I have found the issue and reported it in the Telegram channel.
Click to expand...
Click to collapse
You're still not answering the question. And reporting in actual ROM thread is still best.
So I assume you installed stock Pie and didn't read the MANY warnings about needing permissive kernel if you go back to LOS-16 ROMs. Also that LOS-17 ROMs are still unfinished work in progress with bugs.
This is Root Sticky Guide. Read post #2:
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
ShapeShifter499 said:
I'm sorry, but not all the information for this device is terribly organized. It was hard for me to figure out that it was broken and not just "user error" by myself. It took you to tell me this, thank you!
Click to expand...
Click to collapse
It's organized quite well. There's a Root Sticky Guide that tells everything you need to know about custom ROMs.
Seems you ignored that.
It's also linked in HUGE hyperlink in the WTF instructions (near top of that post), pointing to that Guide if you missed it for some reason. You ignored that, also.
It's also linked in post #1 every KDZ Pie thread I maintain.
If the ROM threads themselves don't contain such information -- or at least links to such information -- that's the fault of the ROM maintainers. But
* Sticky Guide
* HUGE Link in bootloader unlock/root instructions
* Link in post #1 of Pie KDZ threads
is quite good organization of material.
ChazzMatt said:
You're still not answering the question. And reporting in actual ROM thread is still best.
So I assume you installed stock Pie and didn't read the MANY warnings about needing permissive kernel if you go back to LOS-16 ROMs. Also that LOS-17 ROMs are still unfinished work in progress with bugs.
This is Root Sticky Guide. Read post #2:
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
It's organized quite well. There's a Root Sticky Guide that tells everything you need to know about custom ROMs.
Seems you ignored that.
It's also linked in HUGE hyperlink in the WTF instructions (near top of that post), pointing to that Guide if you missed it for some reason. You ignored that, also.
It's also linked in post #1 every KDZ Pie thread I maintain.
If the ROM threads themselves don't contain such information -- or at least links to such information -- that's the fault of the ROM maintainers. But
* Sticky Guide
* HUGE Link in bootloader unlock/root instructions
* Link in post #1 of Pie KDZ threads
is quite good organization of material.
Click to expand...
Click to collapse
I've already been compiling my own LineageOS. It's been determined that due to the issues I've been experiencing that the previous owner must have installed PIE at some point. The seller then seems to have gone back to stock Android 7 Nougat which didn't help the permissive issue. I personally never have installed stock Android 9 PIE. I brought this phone used from a seller on Amazon, there was no way for me to know before receiving the device whether or not the device had been upgraded to PIE before.
However according to SGCMarkus, encryption was never reported working for anyone regardless of if they had the permissive issue or not. I know why, there are no SELinux permissions set up for it. From what I can tell his sources doesn't have them. So even if you didn't have a permissive issue from upgrading to PIE, encryption wouldn't have worked.
ShapeShifter499 said:
I know why, there are no SELinux permissions set up for it. From what I can tell his sources doesn't have them. So even if you didn't have a permissive issue from upgrading to PIE, encryption wouldn't have worked.
Click to expand...
Click to collapse
Well that's interesting.
ChazzMatt said:
Well that's interesting.
Click to expand...
Click to collapse
https://github.com/ShapeShifter499/...mon/blob/lineage-16.0/sepolicy/vendor/vold.te
This needs to be added to a new build in order to allow things to work for encryption. Otherwise the phone attempts the encryption but hangs after rebooting because it's unable to double check that the encryption was successful due to SELinux blocking Vold.
Related
This is a ROM Base of the latest LP VS985 23C & 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working updater-script, but this way is much easier & straightforward.
23C Installation Instructions: - Official
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v7.0.zip - BE PATIENT !
FLASH SuperSU for ROOT access
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23C Installation Instructions: - Leak
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v6.0_Unmodified.zip - BE PATIENT !
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23B Installation Instructions: - Leak
The installation of 23B is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
1. Make Nandroid backup of your ROM via TWRP recovery
2. Download & extract JasmineROM_v5.0.zip (use Zarchiver)
3. Make sure you don't have any partition images in internal storage (/sdcard)
4. Copy all files in JasmineROM_v5.0 directory to internal storage (/sdcard)
5. (Re)boot into TWRP recovery
6. Use Terminal Command (in TWRP) OR ADB (from PC/Mac/Linux via adb shell) to run the following 3 commands:
Code:
cp /sdcard/installROM.sh /sbin/
chmod 0755 /sbin/installROM.sh
sh /sbin/installROM.sh
The first two commands shouldn't print anything.
The 1st command copies the script to /sbin & the 2nd sets its permissions.
The 3rd command runs the script only if it's in /sbin (1st command) & has executable permissions (2nd command).
If you've messed up with your partitions layout or filesystem (e.g., formatting f2fs), revert to factory setup (e.g., ext4 filesystem - since stock kernel doesn't support f2fs).
The last command will take some time (~10 minutes). BE PATIENT !.
Some entries will appear to hang, do not interrupt or disconnect cable!
The "No space left on device" warning is NORMAL
You should see command prompt & ROM info/release date at the end !
Click to expand...
Click to collapse
7. Flash Download Mode Fix + Debuggable Kernel & Reboot
If you run into issues, it's because you've conflicting data from KK.
Do a factory reset in Settings to restore default LP databases!
You may use TitaniumBackup instead of factory reset > Tap batch actions on the top right > Scroll down to "Manipulate data" > Run "Wipe data for user & system apps"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Please read carefully the instructions above before proceeding at you own risk!
JasmineROM v7.0 Release: JasmineROM_v7.0.zip
md5: 7ac04a41e1f6bb26f51e50760023395d
JasmineROM v6.0 Unmodified: JasmineROM_v6.0_Unmodified.zip
md5: 18887557219ccbf428a4fe99733698da
CRONTAB + Disable IPv6: CRONTAB_DisableIPv6.zip
md5: c6487922357b330cbb6257d91076ca7d
JasmineROM v5.0 Unmodified: JasmineROM_v5.0.zip
md5: 4e6aec50ab9763c4396dcb5e45408a95
Click to expand...
Click to collapse
Thanks to:
All devs/testers/users contributed to it
@HolyAngel for collaboration on Stock-based ROMs
@bweN diorD & @autoprime for the images!
@annoyingduck & @krazy_smokezalot for final tests
Click to expand...
Click to collapse
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
guitarbedlam said:
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
Click to expand...
Click to collapse
Yep, just flash the KK ROM + proper kernel & modem
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
jthompson0019 said:
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
Click to expand...
Click to collapse
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
hsbadr said:
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
Click to expand...
Click to collapse
Is there a method you would recommend? I can't seem to get anything to work.
jthompson0019 said:
Is there a method you would recommend? I can't seem to get anything to work.
Click to expand...
Click to collapse
You may try this at your own risk. It may work, but not tested.
hsbadr said:
This is a ROM Base of the latest LP VS985 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working installer-script, but this way is much easier & straitforward.
The installation is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
Installation Instructions:
Did you know that... You are the best? ?????
Click to expand...
Click to collapse
Thanks a lot. Worked great. Is anyone having trouble with ADB after updating? My ADB worked fine before. I'm trying to find new drivers to install but can't seem to get it.
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
AngryManMLS said:
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
Click to expand...
Click to collapse
You can just flash the modem, but I have no idea if the 23B modem works with AOSP/CM 12.
Sent from my VK810 4G
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200.
Click to expand...
Click to collapse
You shouldn't post the same thing in multiple threads.
Sent from my VK810 4G
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
Click to expand...
Click to collapse
Hey, friendly advice. Don't cross post. Especially 3 different threads.
From my VS985 - Jasmine 5.0.11
whatever gets the fastest response
cap1tal1sm said:
whatever gets the fastest response
Click to expand...
Click to collapse
Lol. Ok, not really the best justification. This isn't an IT help desk.
Sent from my Nexus 7 2013
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
cap1tal1sm said:
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
Click to expand...
Click to collapse
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
I never bothered doing Bump to get a custom recovery installed. I simply got root on 10B and then disabled automatic updates. As such, I figure this method won't work for me as it involves steps within TWRP. Would my best bet for getting stock rooted Lollipop be to enact Bump to get a custom recovery, and then follow these steps? The Bump stuff didn't make sense to me so I didn't dare venture down that road, and am hoping I can still avoid it...
crazy4android said:
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
Click to expand...
Click to collapse
It's called trolling son. Back in my day, it was an art. Now I just do it for the thrill.
I have no idea how to change file systems. The whole boot partition thing is what weirded me out, I have no idea about that stuff. I ended up flashing back to my kit kat recovery (which had a date of like january 5, lol. So I had been off stock rooted xposed for almost 4 months) and running the commands. Then instead of hanging at the verizon screen at boot, it went into the android is upgrading thing fine.
So I guess it's a directional thing, where you can go forwards in time but not backwards. Which was where I was coming from on Illusion 6.0.
NOTE: This thread is for the discussion of kernel development. If you don't recompile kernels, please don't post/reply.
After a couple years playing with nexus devices, I'm coming back over to Samsung (until I get bored) and I'm seeing that no one has managed to root a Note 5 device without a recompiled kernel. Why? Because using the stock kernel seems to result in just boot loops.
From what I've been able to observe, the custom kernels all have one thing in common in regards to allowing root to work: They are all changing sepolicy to run permissive instead of making modifications to allow 'su' to work in enforcing mode.
Why?
I have to be honest in saying that I haven't studied how @Chainfire had managed to get su working on the nexus devices while retaining sepolicy in enforcing mode, but it seems that this would be a far better solution than just neutering sepolicy all together.
Has anyone yet attempting to get a sepolicy enforcing kernel working with root? If so, are you willing to share what you tried and how things worked out?
My end-goal is probably to throw together a "as stock as possible" kernel that's root-able. If at all possible, I'm hoping that just some modifications to the ramdisk would be enough to get things working. However, I'd like to take advantage of any previous work done (if any) to get this working.
Thanks
Gary
Edit:
FOR CLARIFICATION. THIS THREAD IS NOT FOR GENERAL USER DISCUSSION. THIS IS FOR DEVELOPERS TO DISCUSS SELINUX, THE NOTE 5 KERNEL, AND METHODS BY WHICH ROOT CAN BE ACHIEVED WITHOUT CHANGING SELINUX TO PERMISSIVE.
Reminder,
Read the OP and stay on topic.
Thanks.
The_Merovingian
Forum Moderator
I have to ask my friend. Since I'm back to Samsung at the same time as you it seems. I see very little advantage of running root atm but I see none of running Selinux non permissive. Also these devices being exynos you will not find much support for it.
I may be wrong but Selinux non permissive has been a problem on samsung custom roms from day one guys just disabled it and be done with I've never seen anyone complain ;p
DAGr8 said:
I have to ask my friend. Since I'm back to Samsung at the same time as you it seems. I see very little advantage of running root atm but I see none of running Selinux non permissive. Also these devices being exynos you will not find much support for it.
I may be wrong but Selinux non permissive has been a problem on samsung custom roms from day one guys just disabled it and be done with I've never seen anyone complain ;p
Click to expand...
Click to collapse
I'm in the process of trying to modify the sepolicy in the stock boot image ramdisk to see if that allows root to work with the stock kernel (modified ramdisk.)
Wish me luck.
Dammit - all of my tools are out of date. Have to recompile mkbootimg, unpackbootimg, etc.
Okay, so I'm finding out all kinds of Fun Things that Samsung has done with this device...
First, at least some versions of this phone (mine is a 920i) have something in the stock firmware kernel(?) that restores factory recovery on first boot. This is my first sammy device in several years, but I seem to remember reading that other samsung devices have done this as well. (This is the reason that people are having to not allow ODIN to auto-reboot the phone.)
What's really pissing me off, however, is that if I allow TWRP to modify the system partition (based on the prompt on the initial boot) and don't actually make any system changes, the normal stock kernel won't boot... it gets stuck in a boot loop. (pre-bootanimation)
This is similar to the reports people are having of boot loops if they install root without changing the kernel. I'm starting to think it has nothing to do with actually being rooted, but that ANY system partition change is causing the bootloop. (Surprise!)
So, I decided to try something a bit different: I restored stock firmware (tar.md5 via odin) and after the reboot, I went back into ODIN mode. This time, I flashed TWRP and rebooted immediately back into ODIN and a flashed kernel with a modified sepolicy in the ramdisk. I then booted normally. My kernel loaded. I used adb to reboot to recovery. TWRP loaded. From TWRP, reboot normally.. it worked. Good start. adb reboot recovery, and this time I uncheck the option to "only mount system R/O." (It's in the "mount" section of TWRP.) Reboot system... and... BOOTLOOP.
(This has nothing to do with root. I'm not installing root... )
Time to start digging in the kernel ramdisk to try and figure this one out...
Tried the same as above, but with Philz compiled by @arter97. This time, I was stuck in a bootloop after the first time recovery ran. I'm guessing that this particular recovery will ALWAYS touch the system partition without first asking? Not sure... Philz did ask if I wanted to install root when I chose the option to reboot, but I declined.
Note to self:
http://forum.xda-developers.com/showpost.php?p=61542104&postcount=433
Just remove support_scfs,verify from the fstab and altering system will work.
Click to expand...
Click to collapse
I have NFC what "support_scfs" is, but I'll have to spend some time with google to figure it out. Perhaps a bit of SourceDiving. Won't have a chance to test this until tomorrow evening.
I love replying to myself. The truth is, I'm probably one of the few people who could stand talking to me. Of course, even I feel like killing me every now and then. It gets complicated.
Oh.. anyway.. I got it. A stock kernel with a modified ramdisk running selinux in enforcing mode and root-able. I want to spend a day running tests, but will post results of the results in about 20 hours. (assuming I get to sleep tonight...)
As well as gaining the enforcing selinux security (somewhat degraded by being rootable), this also ensures all hardware is working even if samsung "cheats" in posting source code.
(see attached screenshot... it's really the stock kernel and still enforcing SE for Android. )
Edit:
Then again, there's no harm in posting the boot image now. This is from a n920i device using the N920IDVU1AOH6 firmware. I'm attaching a file that can be unzipped and flashed with ODIN (AP slot.) Someone fluent should be able to pull the boot image out of the tarball and flash it directly with TWRP or even via 'dd' (assuming you're already rooted.)
(If you try to flash the .zip file directly, you deserve whatever horrible things happen to your phone.)
THIS IS NOT A RELEASE. THIS IS FOR DEVELOPERS WHO KNOW WHAT THEY ARE DOING TO FIND FLAWS WITH IN REGARDS TO ROOT AND SELINUX. I can't claim this would work for any device without the above mentioned firmware. If you don't know exactly how to recover from Bad Things, don't even download the attachment.
No support. No help. If you have to ask how to flash this or anything of the sort, this isn't for you.
Changes from stock ramdisk:
1. Modify sepolicy as @Chainfire documented (ironically using an unrooted note 5) to allow supersu to work it's magic.
2. Modify fstab to remove support_scfs,verify from the mount options for the system partition. (this solves the boot loops)
That's IT.
One warning, though: This is using supersu beta 2.51. That's not released. Actually, I think it's flagged as a work in progress.
garyd9 said:
Changes from stock ramdisk:
1. Modify sepolicy as @Chainfire documented (ironically using an unrooted note 5) to allow supersu to work it's magic.
2. Modify fstab to remove support_scfs,verify from the mount options for the system partition. (this solves the boot loops)
That's IT.
One warning, though: This is using supersu beta 2.51. That's not released. Actually, I think it's flagged as a work in progress.
Click to expand...
Click to collapse
Please, publish original boot.img from N920IDVU1AOH6
svadev said:
Please, publish original boot.img from N920IDVU1AOH6
Click to expand...
Click to collapse
Did you not bother to read any of the posts in this thread? There are known locations for stock images. This thread isn't one of them.
Read the very first line in the first post.
I made it for my SM-N9208, and it is really works with supersu 2.50 .
Thanks!
garyd9 said:
Changes from stock ramdisk:
1. Modify sepolicy as @Chainfire documented (ironically using an unrooted note 5) to allow supersu to work it's magic.
2. Modify fstab to remove support_scfs,verify from the mount options for the system partition. (this solves the boot loops)
That's IT.
One warning, though: This is using supersu beta 2.51. That's not released. Actually, I think it's flagged as a work in progress.
Click to expand...
Click to collapse
Hi
Could you please post a more detailed guide ? I want to do it myself for my n920c.
Thanks
geek78 said:
Could you please post a more detailed guide ? I want to do it myself for my n920c.
Click to expand...
Click to collapse
yeah. well, at least assuming you know how to unpack and repack boot images... (Because this stuff is very experimental at this point, and still very much a work in progress, you should have a certain level of proficiency before mucking with it. I can't and won't hold anyone's hand for this stuff at this point.)
you need to unpack the boot image. Get the boot.img and unpack. Open the ramdisk. In the ramdisk is a file called 'sepolicy.'
Start with this post to figure out how to change it:
http://forum.xda-developers.com/showpost.php?p=63190351&postcount=2071
Find the reply to that post from Chainfire to see how it can be done without a "reference" device.
You'll also have to change the proper fstab as I documented already in this thread.
Then pack up the ramdisk and repack the boot image.
Thanks. Perfect !
DAGr8 said:
I have to ask my friend. Since I'm back to Samsung at the same time as you it seems. I see very little advantage of running root atm but I see none of running Selinux non permissive. Also these devices being exynos you will not find much support for it.
I may be wrong but Selinux non permissive has been a problem on samsung custom roms from day one guys just disabled it and be done with I've never seen anyone complain ;p
Click to expand...
Click to collapse
I'm trying to place your name. Do I know you from SGS2 days or Note2 days?
Anyway, I'm not happy with settling. Never have been...
Edit:
Note or Note 2. Must have been Note2. You were doing smali edits for enabling tablet mode. That was pre-xposed days.
Edit 2:
To answer the question: enforcing selinux adds a layer of security on the device and blocks many security infractions. Basically, if you haven't been given permission to do something, you can't do it. Even as root. In theory, selinux could block the stagefright security issues. When a device is in "permissive" mode, selinux is there, but isn't actually blocking anything. It just logs violations and then ignores them.
In other words, permissive mode completely negates having the se extensions at all. Permissive was a mode that devs could run in to see what might break and what might not.
"root" access is, of course, a hole in the scheme. Chainfire, with supersu, has done quite a bit to ensure that the hole is controlled, but it's still a hole. However, a rooted device with an enforcing selinux kernel is still significantly more secure than a non-rooted permissive selinux kernel.
Another edit:
Here's some links:
https://su.chainfire.eu/#selinux
http://linux.die.net/man/8/selinux
<sarcasm> Wow, I almost forgot how much JOY and FUN it is working with Samsung sh!t kernels. </sarcasm>
So, in testing this (yes, I really DO test things.. imagine that) I found that my device wasn't going into deep sleep. Wow. How interesting. Oh, and not a single wakelock. WTF?!
Instead of google'ing first, I reverted to being a kernel dev (that is now trying to debug a kernel that he hasn't even compiled.) The first thing a kernel dev looks at: "dmesg" So, I copy dmesg to a file and transfer it my PC. (BTW, Notepad++ is God's gift to windows editors.) I search for various strings like "error" and "fail" and "suspend." What I end up seeing is a crapload of messages like this:
Code:
[0: system_server: 3858] PM: Device 0:0:0:x failed to suspend: error -5
(replace x with 1, 2, or 3)
Huh? So, before I dive into the code (because I really don't believe that samsung actually shares the kernel code that they use for themselves), I decided to google around a bit. I finally had enough search terms to hopefully narrow down the search results.
Guess what I found? People having the exact same problem on another samsung device: the S6 (and edge.) Here's the best of the threads:
http://forum.xda-developers.com/galaxy-s6-edge/help/deep-sleep-t3079705
It gets into some interesting detail around page 4 and 5. You'll have to skip past all the clueless people preaching about turning off wifi, downloading snake oil, and worshipping recycled NiCad batteries.
To make a long story short, the stock kernel (or perhaps the bootloader? That shouldn't be possible...) marks a few block devices as read-only if you're using a modified device. (If it's rooted, it's modified. If KNOX is tripped, it's modified, etc.) The kernel from Sammy is trying to flush caches to those devices (which is ironic when you consider they are marked read-only) before going into the suspend. The flush fails, so the entire suspend process fails. It seems that on the SGS6, there were only two devices like this. On the Note5, it seems to be 3 (everything except sda)
In that thread, @HomerSp not only tracked down the problem there, but also (thankfully) figured out that writes to a file in the /sys tree could work around the issue. Thankfully, because the entire point of THIS thread is to use the stock compiled kernel (with a modified ramdisk) to make life Happy. With 3 writes to the /sys tree, magically the device goes to sleep.
(Yes, I'll be taking care of it... and documenting it better...)
What a pain... for some reason, I couldn't write to the cache_type files from within the init.rc structure. No clue why not. Ended up having to add a "service" to the init structure
Anyway...
If you're following along at home, add the following lines to the bottom of init.rc:
Code:
service fix_cache_types /system/bin/sh /sbin/fix_cache_types.sh
class core
user root
oneshot
Then add a new file in the ramdisk's sbin directory called (I bet you guessed this already): fix_cache_types.sh
That file should have perms of 0750 and contain the following:
Code:
#!/system/bin/sh
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:1/cache_type
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:2/cache_type
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:3/cache_type
If you're using the same kernel as I am (n920i), I've attached an updated image. Same rules, conditions, instructions as the last one I posted earlier in this thread. Except this one lets the device take naps. It helps the battery life.
Tomorrow (or Sunday) I'll see if this all works with xposed or not. (I seem to remember something about xposed not working with selinux enforcing kernels, but I could be wrong.) After that, if nothing prevents it (or me), I'll repackage this stuff again, and also throw together an n920c kernel (based on N920CXXU1AOH6) for general use.
BTW, at least on my n920i, I've confirmed that I don't reboot when getting a call (or making one), that NFC works, that bluetooth works, that I can wirelessly charge and quick charge. I'm trying to ensure all the "common" complaints with non-stock boot images are non-issues before giving this out... The whole purpose of using the stock kernel is to retain enforcing selinux and retain completely functional hardware.
garyd9 said:
yeah. well, at least assuming you know how to unpack and repack boot images... (Because this stuff is very experimental at this point, and still very much a work in progress, you should have a certain level of proficiency before mucking with it. I can't and won't hold anyone's hand for this stuff at this point.)
you need to unpack the boot image. Get the boot.img and unpack. Open the ramdisk. In the ramdisk is a file called 'sepolicy.'
Start with this post to figure out how to change it:
http://forum.xda-developers.com/showpost.php?p=63190351&postcount=2071
Find the reply to that post from Chainfire to see how it can be done without a "reference" device.
You'll also have to change the proper fstab as I documented already in this thread.
Then pack up the ramdisk and repack the boot image.
Click to expand...
Click to collapse
Hi
I have unpacked my boot.img. So I can see my sepolicy file in ramdisk/, I have patched it with my rooted Nubia Z9 but I don't understand next steps. Do you have time to explain a little more ?
For the fstab mods I have done it in fstab.samsungexynos7420 and fstab.samsungexynos7420.fwup. Is it ok ?
Thanks.
garyd9 said:
No support. No help. If you have to ask how to flash this or anything of the sort, this isn't for you.
Click to expand...
Click to collapse
garyd9 said:
I can't and won't hold anyone's hand for this stuff at this point.)
Click to expand...
Click to collapse
garyd9 said:
Same rules, conditions, instructions as the last one I posted earlier in this thread.
Click to expand...
Click to collapse
geek78 said:
Do you have time to explain a little more ?
Click to expand...
Click to collapse
Need I say more?
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb
LineageOS 17.1 - Official
There is now an official LineageOS 17.1 build available for Ocean! This was not created by me. Most credit seems to be due to SyberHexen. I'm simply posting here because nobody else has done so.
Main Page
Installation Instructions
Greek2me said:
...LineageOS 17.1 - Official...
Click to expand...
Click to collapse
A tear of joy comes to my eye. Thanks for the heads up.
I've been using it daily and so far it's great. No bugs to report yet.
Greek2me said:
I've been using it daily and so far it's great. No bugs to report yet.
Click to expand...
Click to collapse
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
IronTechmonkey said:
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Click to expand...
Click to collapse
I'm glad I could reach you on time! I'll keep that in mind about the thread - thanks for the heads-up.
toddk63 said:
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
Click to expand...
Click to collapse
I would recommend that you try the installation again, taking care to follow the pre-installation instructions here. Additionally, I recommend that you wipe everything (system, data, internal storage, and cache) before attempting to install LOS.
Install went fairly smooth last night.
Have had a few times (usually when playing a video via the browser) that the "shutdown" popup will show. Phone reboots but the Lineage "corrupt" screen comes up. Hitting Try Again works and it boots successfully.
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
Click to expand...
Click to collapse
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.
[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
IronTechmonkey said:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
Click to expand...
Click to collapse
Well the official one is missing some things then one I posted whit h has no problems I use it
roadkill42 said:
Well the official one is missing some things then one I posted whit h has no problems I use it
Click to expand...
Click to collapse
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
IronTechmonkey said:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
Click to expand...
Click to collapse
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
roadkill42 said:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
Click to expand...
Click to collapse
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.
[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Click to expand...
Click to collapse
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Greek2me said:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Click to expand...
Click to collapse
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
IronTechmonkey said:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
Click to expand...
Click to collapse
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
I'll be making new devdb posts for official G7 ocean/channel..
once threads are active please post there.
Thx
SyberHexen said:
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
Click to expand...
Click to collapse
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.
I compiled android13 using Ubuntu 2204_ The r7 code, corresponding to the driver, is also officially downloaded and successfully burned to the phone. It can also enter the system, but it automatically restarts a few minutes later, and then restarts again a few minutes later. After cycling several times, it cannot enter the system. The prompt is: Cannot load Android system, Your data may be corrupt, If you continue to get this message, You may need to perform a factory data reset and erase all user data stored on this device. Have you encountered this error and how should I handle it? I need AOSP
aosp_cat said:
I compiled android13 using Ubuntu 2204_ The r7 code, corresponding to the driver, is also officially downloaded and successfully burned to the phone. It can also enter the system, but it automatically restarts a few minutes later, and then restarts again a few minutes later. After cycling several times, it cannot enter the system. The prompt is: Cannot load Android system, Your data may be corrupt, If you continue to get this message, You may need to perform a factory data reset and erase all user data stored on this device. Have you encountered this error and how should I handle it? I need AOSP
Click to expand...
Click to collapse
hi,
have you erased data before flash your AOSP compiled ?
@aosp_cat
I'm no dev by any means but I've been compiling aosp and others for some years now and I too have this issue. A while back I asked around and the answer I was told is that encryption must be removed in fstab. When I tried to do this I couldn't exactly pinpoint what needed deleted in fstab on the device because it's not worded the same as it once was years ago last time I removed it back then... Maybe you'll have better luck than me at finding what exactly to delete to remove force encryption. (If that is indeed the cause of this...) There used to be a zip that was TWRP flashable that did this but it's no longer maintained and hasn't been for some years now. Please let me know if you can figure out how to manually remove force encryption in fstab. Hope this helps...
NO I have compiled aosp-master in past ( september 2022 )
Encryption no need to be disabled . I have no get problems
Today you will find fix easy in lineage github for gs101 trees. ( Overlay , esim , camera ... )
flash713 said:
@aosp_cat
I'm no dev by any means but I've been compiling aosp and others for some years now and I too have this issue. A while back I asked around and the answer I was told is that encryption must be removed in fstab. When I tried to do this I couldn't exactly pinpoint what needed deleted in fstab on the device because it's not worded the same as it once was years ago last time I removed it back then... Maybe you'll have better luck than me at finding what exactly to delete to remove force encryption. (If that is indeed the cause of this...) There used to be a zip that was TWRP flashable that did this but it's no longer maintained and hasn't been for some years now. Please let me know if you can figure out how to manually remove force encryption in fstab. Hope this helps...
Click to expand...
Click to collapse
ada12 said:
hi,
have you erased data before flash your AOSP compiled ?
Click to expand...
Click to collapse
No, my original system version number was tp1a. 221005.002, and the branch where I downloaded AOSP was Android 13.0.0_ R7. Do I need to restore the factory settings before brushing into the AOSP image?
flash713 said:
@aosp_cat
I'm no dev by any means but I've been compiling aosp and others for some years now and I too have this issue. A while back I asked around and the answer I was told is that encryption must be removed in fstab. When I tried to do this I couldn't exactly pinpoint what needed deleted in fstab on the device because it's not worded the same as it once was years ago last time I removed it back then... Maybe you'll have better luck than me at finding what exactly to delete to remove force encryption. (If that is indeed the cause of this...) There used to be a zip that was TWRP flashable that did this but it's no longer maintained and hasn't been for some years now. Please let me know if you can figure out how to manually remove force encryption in fstab. Hope this helps...
Click to expand...
Click to collapse
Thank you. If I find a solution, I will reply to you
aosp_cat said:
Thank you. If I find a solution, I will reply to you
Click to expand...
Click to collapse
Usually best to try and figure it out on your own. That's what I've discovered anyway.. Many people don't check the Q & A much these days.. I'm sending a pm to a few devs I know here. If they check their messages I'm quite sure they'll reply.. As soon as I hear anything, if and when I do I'll shoot you a pm and tell you what I've found out..
Edit added june 8, 2023 @11:27am CST.
I'm going to compile a fresh aosp, a master and a tagged build and I'll make sure the same matching bootloader is on both A and B slot and then I'll flash and see if I still get the reboots... I'll report back later.. I could have come from Los 20 or beta 14 when I flashed i really don't remember exactly. This was brought to my attention in a reply from a fellow xda'er I had messaged about it . I'll compile a tagged build TQ2A.230505.002 android-13.0.0_r43
with Pixel 6 binaries for Android 13.0.0 TQ2A.230505.002 and a master with the Preview binaries soon as I get home hopefully.. Might be a lil later but once I do I'll comment here. I don't believe I had bootloader on both slots.