Related
On my Samsung GT-N7000 I'm trying Omnirom again. I've tried it in the past and also tried vanilla CM stable and nightlies. I have also tried SuperNexus and PA and some other stuff that left no impression. Basically on this device for functional hardware, reasonable user control and a coherent UI it is Samsung's Touchwiz rooted, or Omnirom.
It is a bit too hard to install Omnirom and it can be horribly tedious to go from Omnirom back to stock or to another ROM. It's OK after you have done it a few times, but it is a huge obstacle for anyone trying to discover the way via inaccurate, misleading and fragmented documentation. The install guide at omnirom.org is actually utterly useless for this particular device, a complete non-starter. XpLoDWilD your GT-N7000 specific thread at http://forum.xda-developers.com/showthread.php?t=2516933 almost guarantees a boot loop because it only mentions but doesn't identify or link to versions of CWM which are adequate. In fact unless the user by diligent searching (or more likely by blind chance) comes across a link to the specific suitable raw kernel then it is one big dead end. You could spend hours and days searching for a suitable CWM and never find it because actually you should be searching for raw_kernel_r#_j##.zip. But how is anyone meant to know this. It turns what is actually a reliable and rather trouble free 15 or 20 minute process into a some kind of waking torment. In the past the documentation on installing via CWM was so bad that I used ODIN, which is less than ideal IMO because it means that anyone switching from stock to Omni doesn't get the chance to make a full nandroid backup of the original system (so to revert means a very tedious clean install).
So assuming the end user somehow finds the right raw kernel whose recovery can install Omnirom, what should they do? Of course they should back up their current apps and also make a nandroid backup. Apps backup is easy with oandbackup or titanium or similar. How about a nandroid backup to external SD? No problem in CWM but once you have TWRP installed you can't use it to access anything on an exfat formatted external SD card! You can back up before installing Omnirom but afterwards you can't restore! This is 100% nuts. exfat has now been around for 8 years. CWM supports it brilliantly. Even my crusty old Debian stable desktop reads and writes to exfat at very high speeds even via a FUSE FS and my puny Asus EeePC netbook running XP Home handles it fine. TWRP? Nope. exfat? Wha tha? Aaaaaagh.
Sorry to rant But for these specific devices Omnirom (with an exfat SD) is really the only high quality competitor to the stock Samsung, and there surely isn't a good reason for it being so frustrating to install and also to revert? Is TWRP really such a killer facility that it is worth foregoing the ability to backup and restore to the now very common exfat microSDHC? I run plain CM 11 on another device and OTA updates work fine on that. In these days of phatter pipes is it really worth making a huge compromise in functionality simply to avoid 200MB of downloads sometimes? On this device the delta updates are going to fail for many anyway unless they use an exfat card, but if they use an exfat card they.....oooouuuurrrggg...vicious circle.
/rant over.
Loving Omnirom btw and writing as a fan.
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Entropy512 said:
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Click to expand...
Click to collapse
Thanks for responding. I do appreciate that the exynos based devices are sons-of-b...b...bad persons.
I know documentation is boring and mostly thankless but it also matters a lot, most especially for projects which invite the user to perform realtively complex and potentially hazardous tasks.
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Omnirom has some issues but on the GT-N7000 is probably the only really mature and coherent alternative UI to Samsung's Touchwiz. To me it seems simply insane to direct newcomers into an unnecessary, time consuming, badly described and potentialy hazardous obstacle course, when in fact installation can be done with only small inconvenience.
I'm currently looking for information about installing OmniROM (I'm currently running CM11 nightlies), and I can attest the information in XpLoDWilD's post is somewhat vague, and also doesn't fully correlate with the directions to install Omni at the official wiki -- I'm assuming this lack of correlation is partly due to the fact, mentioned in this thread, that the N7000 doesn't have a separate recovery partition.
Something which made me especially uncertain about the installation process is the following part:
XpLoDWilD said:
- Make sure you're running a proper working ClockworkMod-Recovery - WITH SELINUX SUPPORT!
Click to expand...
Click to collapse
My understanding is that SeLinux is a feature of the kernel -- not the recovery console -- am I wrong about this? Or should I look for SeLinux in the features of the recovery console as well? (if so, how?)
What I currently do, is run adb, or start a console from the normal operating mode (not recovery mode), run the command:
Code:
getenforce
and confirm the reply is:
Code:
Enforcing
which means I have a kernel with SeLinux. Is that good enough to ensure the requisites for the installation are provided?
I'd appreciate any input about this matter.
julian67 said:
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Click to expand...
Click to collapse
Cant you add device-specific installation guide at the official wiki?
sagie said:
Cant you add device-specific installation guide at the official wiki?
Click to expand...
Click to collapse
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
I'm pretty sure I can save my twrp backups to my exfat sdcard.
edit: yup. just touch "internal storage" on the twrp backup page and select your sdcard.
julian67 said:
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
Click to expand...
Click to collapse
i've been using omnirom as my daily driver for 2 weeks now. love kitkat and omnirom features, but its still very unstable i think. stuff that's bothering me for now:
-stock camera is really plain, can't even switch to front camera
-video playback sometimes fail
-music playback will fail the first time i launch and play a song or 2. have to reboot and it'll work all day long
-intermittent random reboots, about 3 times so far the whole week
-wifi signal range is somewhat lower compared to touchwiz rom
-stock clock app, can't manually input time via keypad when you want to add an alarm
-contacts app is very confusing, can't even add a contact with ease. well at least for me that is
other than that kit kat is sure a welcome on this legendary device. contemplating the switch back to stock touchwiz, but loathe at the idea of setting up everything again zzz
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Polux44 said:
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Click to expand...
Click to collapse
Per my earlier post - You cannot change kernels on the Samsung GS2 family (including N7000) without also changing recovery.
Conversely, you can't change recovery without changing kernel. It's a limitation of this device since the recovery partition is not actually used, and recovery is in the normal kernel.
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Entropy512 said:
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Click to expand...
Click to collapse
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Polux44 said:
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Click to expand...
Click to collapse
Correct. Sony devices also have this limitation, there is a semi-workaround (where the kernel pulls recovery ramdisk from another location) on those that *in theory* could be done on the old Samsungs... but so few people are working on the old Samsungs that it isn't likely to happen.
Pretty much all GS1s and Exynos GS2s had this limitation. Qualcomm GS2s (Skyrocket/Hercules) had a separate recovery, as did all GS3s and onwards.
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for other devices too. (See the list below to see if your device is supported)
Disclaimer
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 the features in this tool
* before using 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. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in current devices it's the CPU's task. Even though modern devices have quite fast CPU cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any scientific measurements though)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher).
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then, if necessary, it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?
cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.
Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Worked on my N9 - thanks!
provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.
I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
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 ROM
* 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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:
I DONT TAKE ANY WARRANTY WHATSOEVER IN ANY DAMAGE THAT MAY RESULT IN FOLLOWING THIS GUIDE OR USING THE SOFTWARE, ROM IN QUESTION, IN ANY WAY, MAY IT BE AS INTENDED OR NOT. IF YOU HAVE ANY FEELING YOU COULD END UP SUING ME FOR RISKS *YOU ALONE* ACCEPTED TO TAKE, YOU SHOULD IMMEDIATELY STEP BACK AND LEAVE THIS POST, ALL THE OTHERS: BE CAREFUL. YOU WILL LOSE ALL OF THE DATA ON YOUR PHONE'S USERDATA, CACHE AND SYSTEM PARTITION AND THE PHONE WILL BE FACTORY RESET!
STOCK FIRMWARE INSTALLER: https://support.wikomobile.com/maj/Lenny5_OPE_V34.zip <-- if you brick your device.
Hey folks
This is just a brief explanation on how i built this ROM, a complete guide to building the rom may be published at a later point in time. For the Downloads, go to the Links section. The flashing guide will be focused on Lenny 5, but the image may work on other treble-enabled devices, too, so feel free to try and report if your device works with this build.
Build variant: arm-aonly-floss-su-userdebug
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Build description:
I have an old Wiko Lenny 5 around here and wanted to use it as a Kodi Remote etc. at home, but didn't want to use their stock ROM. Also i wanted some freedom in using my device, specifically a rooted device and microg implementation. After trying to build TWRP with no success and the Wiko Build information being massively outdated i then focused on Generic System Images, as Lenny 5 is Treble-enabled. Big thanks to @phhusson for the whole lot of effort he put into building AOSP GSI's (and also clues towards building LineageOS GSI's). After having AOSP9 installed on it for some time, i got bored and tried to compile LineageOS using the patch-and-build system provided on phhusson's github. That worked just great on AOSP9, but failed to build a bootable LOS16 in the first place. So after some recherche, i stumbled across @AndyYan's thread, containing some LineageOS GSI's prebuilt and ready to use. These worked great on my phone, but as stated above, i wanted to customize my LineageOS even further, so i manually patched my build-tree with AndyYan's Lineage-Treble-Patches by doing what this build script does, tested and it booted (i guess it's mainly related to the SELinux Policies not being correctly built for LOS with only phh's treble-patches). So far so good.
Additionally, i implemented the MicroG services by cloning these prebuilts on github to the respective folder in the build tree and before the build executed
Code:
export WITH_SU=true
to include LineageOS's root system in the build. I adapted the treble_arm_afS.mk device config to not use phh's su and the device/lineage/floss.mk file to include
FDroid
FDroidPrivilegedExtension (which is being built from treble sources)
MicroG services (use Play Store Apps)
FakeStore (use Play Store Apps)
MozillaNlpBackend (MicroG Network Location backend)
NominatimNlpBackend (MicroG Network Location backend)
OpenWeatherMapWeatherProvider (for LineageOS Weather Provider)
You are then free to use no Playstore at all or i.e. Yalp Store to download Play Store Apps.
After downloading the Image you may need to Unpack it via 7-zip or another tool.
Flash the device:
To install this custom ROM on the Wiko Lenny 5, in your stock ROM go to Settings->Developer Options->OEM unlock->Enable. Also, in the Developer Options, make sure, ADB Debugging is active and, on prompt, accept debugging connections from your computer.
On your computer, enter Command Prompt and issue the following commands:
Code:
adb reboot bootloader
*wait for device reboot*
fastboot oem unlock [COLOR="Red"]<-- this will factory reset the device!!![/COLOR]
*press vol up on the phone to allow unlocking the bootloader, and wait for the phone to return to fastboot mode*
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot flash system <path-to-the-downloaded-gsi>
*wait for each process to finish*
fastboot reboot
now, wait for the phone to reboot, it should, after some time, show you the usual LineageOS startup screen. Take your time to set up your phone. To make MicroG and FakeStore work properly, you will have to Go to Settings->Apps&Notifications->App-Permissions->Spoof package signature->Menu->Show System Apps and allow FakeStore to spoof Signature. Go to Settings->System->Advanced->MicroG Settings and add your Google account. Activate Device Registration. Then activate Google Cloud Messaging and Google SafetyNet, if you want to take advantage of those services. Inside the UnifiedNlp Settings choose MozillaNlp in the first, and NominatimNlp in the second setting.
Go back and choose "Self check", if required, if required, grant MicroG GmsCore the permission to spoof signature, this should make most of the boxes go "checked". If Phonesky shows errors about signature spoofing, this should normally be gone after a reboot of the phone (given you allowed FakeStore sig spoofing). Disable battery optimization and then reboot the phone.
Check back in MicroG Settings->Self check, if all the boxes have been checked. If not, most mandatory points are self-explanatory.
This Lineage ROM will not allow you to update to a newer version. I cannot guarantee continuous updates, but encourage you to try building LineageOS treble with the way explained above, yourselves. If enough interest is around, i will consider doing updated builds from time to time.
Update:
Today i compiled a recent source tree containing the 5th of October patches. I will try to keep up with updating the Image whenever security fixes are released. The download links below have been updated to the newest version. To update your phone without deleting the data on it (make sure you have adb debugging enabled), you can simply do
Code:
adb reboot bootloader
fastboot flash system <system-image.img>
fastboot reboot
and then give your phone some time to "update". it should boot normally without erasing your data.
Links:
ROM .7z [~430MB]
ROM .img (~1.1GB)
(version was compiled at 19th of October '19, containing the October 5th security fixes.)
Let me know if this works for you, too!
Cheers
ivelischt
*reserved for additions/build guide*
Nice work
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Hanthonious said:
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Click to expand...
Click to collapse
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
ivelischt said:
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
Click to expand...
Click to collapse
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Hanthonious said:
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Click to expand...
Click to collapse
Hi Hanthonious
ivelischt said:
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Click to expand...
Click to collapse
as the microG variant requires some "special sauce", namely the ability to spoof signature as well as other small fixes in the source code, my source tree is a bit different from the "vanilla/gapps" source tree. thus, to build variants not containing microg, you can simply sync the lineage source tree and apply the additional phh treble sources&patches. *edit: next to phh's patches, you will also need AndyYan's patches; you can find information about it in the OP. given, i write a guide (which i still intend to, but this takes some time), the patching step will be explained more clearly* basically, it's one step less than compiling it with microg. at the moment i cannot afford enough disk space to create another work tree, which is why i "can't promise" other build variants, until this issue is gone. which may be tomorrow or in a year. maybe you can find a gapps-version of treble-lineage 16 here in the xda boards. otherwise you will have to wait, or try to build it yourself. also, you might be interested in @AndyYan's lineage version, which is vanilla (no gapps or microg).
i would guess that the system image will not grow excessive just by including opengapps, but i may be wrong. i think that you'd possibly would have to choose a "non-complete" opengapps-package, to make it fit.
to quickly summarize what microg does is, that it spoofs its signature to make your phone think that you have the real Google Services Framework, Google Cloud Messaging, etc. services installed. this makes apps, which depend on these services, work even though you don't really "have" them. additionally, microg establishes an "essential" communication between itself and the real google services to allow you to use google services despite having all their bloatware.
to round this up, you have fakestore which spoofs existence of Google Play Store for those apps and games, which specifically check for GPS's existence (Phonesky app).
i think this should quite generally point out, what microg is for (an api which connects you to google, whilst only handing out information, which is crucial to keep a specific connection alive)
you can then use i.e. Aurora Store to download and update your preferred playstore apps. i tell you this specifically, as i hope that, using it right, microg might be able to give you a "fully stocked" phone experience, whilst keeping most of your data secure and your phone unbloated by google's app-hoard.
if you follow the instructions in the OP on how to fully enable microG, this might be a very handy solution for you, too, so maybe, you want to give it a chance.
to point out my issues with twrp (as far as i can tell using my little experience): twrp is device specific. which means, you need a vendor tree and you need to include it whilst building, so twrp can compile against it. now, treble is a way of excluding your device specific vendor tree from the build altogether (your system image basically doesnt contain the vendor files in a "folder" (/vendor), but in a seperate partition. this partition is "simply" beeing symlinked to from your system partition. this way you will never need to build vendor-specific sources but android builds against standardised "api's" which are being "serviced" by treble-enabled phone's vendor-files (lying at the vendor-partition). this makes building aosp and/or lineage, etc. easier as you can build one variant per architecture, which fits all treble enabled phones of that architecture (arm/64/binder32/64,a/ab,...). this is, very basically said, what is called a HAL (hardware abstraction layer) on a desktop computer.
but at the same time it's much more difficult to find vendor sources for those phones, as there is no more need at all for manufacturers to make these sources publich (as far as i understand it). as a matter of fact, you may not need these vendor sources for modern aosp (8.1+), which really is a grace!! but twrp doesn't seem to work when compiled against treble trees.
i even managed to compile a kernel which is mentioned at the wikogeek site for the lenny 5. i tried to include that kernel when compiling the recovery image but even that did not work out. as i am no experienced programmer (especially not in the high languages), i will not be the person to ask when it comes to finding out what bugs and how to circumvent it.
there is a little light at the end of the tunnel, though. as far as i understand it, treble-phones come with mostly generic kernels, which *could* make it easier to find a way to build a kernel/boot/recovery image in a similar fashion we build the gsi (generic system image) with. additionally, if there is some effort on it, i imagine, that it would be possible to generally modify twrp in a way so it's able to build against treble source trees with missing vendor source. this would enable twrp to run on virtually any phone which is treble enabled and there would be few to no need to port it for each device, specifically. maybe there would then be versions as in the treble gsi's (arm/64,a/b,...) as well as build variants for alternative display sizes etc.
but i wouldn't even know where to start...
i hope i was able to answer your questions. if you decide to stick with the variant in the OP, you should consider downloading and installing the most recent updated build.
best regards
Problems I found in the rom and if there is a way to solve them
Yo,
I wanted to point out the problems I found in the rom and if there is a way to solve
These are the problems I encountered:
1: *THE MOST IMPORTANT*
I can't pass the safetynet test, I researched a lot and I still couldn't solve
When I try to pass the safetynet test on magisk it gives "safetynet API Error"
When I try to do the test with the "SafetyNet Helper Sample" app it gives "SafetyNet request: success
Response validation: fail
Error Msg:
ApException [17]: API: SafetyNet .API is not
available on this device. Connection failed with:
ConnectionResult {statusCode = SERVICE_INVALID,
resolution = null, message = null}
And the "SafetyNet Test" app gives me "fail (Google Play services not available)"
I am aware of the new problem with the safetynet:
(sometimes people are still able to pass the test probably because it is still in maintenance or something)
https :// www . androidpolice . com /2020/03/11/safetynet-improvements-kill-magisk-hide
https :// twitter . com /topjohnwu/status/1237656703929180160
https :// twitter . com /topjohnwu/status/1238514375150850048
https :// twitter . com /topjohnwu/status/1237830555523149824
But even so I should be able to run the test even if it give both negative should run instead of showing those errors
2: The contacts I had on the SIM card and Google account do not appear in the contacts.
So I went on WhatsApp to save the ones I wanted to save, but after a few days and a few restarts the contacts are still saved, but on WhatsApp it shows that they are not saved even appearing in the contacts, to appear again saved on WhatsApp, I have to save them all again
3: Cant login in Clash Royale with google play games account, can i flash the rom and gapps to work or the microg and google play services will create some conflict, is there a way to unninstall microg completly and reflash the rom without microg and flash gapps?
4: Error when login in pokemon go: unable to authenticate, I researched it and it seems to be because the safetynet is negative but I can't even run the test (only after I became aware of the new safetynet problem) even with this new problem I would like to try to run the test to see if it passed since some people still are successfully passing the test
5: in the microg settings in self-check an option is not checked in the box "UnifiedNlp do not have location to test geocoder" I already researched to see if it solved something but I couldn't
edit: I solved it using the "Apple WI-FI" backend instead of the "Déjà Vu Location Service"
BUT NOW ITS GIVE ME AN UNCHECKED BOX
"Network-based location enabled:
you either disabled network-based location
(in system settings) or the system is not
supported"
6: some times in the time widget just appear "loading widget..."
and these are all the problems that I encountered, pls help me
solving these problems, thx!:good:
sorry for some mistakes i translated from portuguese to english with google translator and my knowledge of english
CooperTUGA, thanks for writing. And I want to apologize for letting you wait for so long. In fact, at the moment i do not actively develop this ROM (due to data loss on my virtual machine).
Anyways, i will try to address your issues as good as i can, though i must admit, none of these issues happened on my device.
ad 1: The only thing that comes to my mind is, that something went wrong when registering your device with the Android-ID. (see OP activation instructions). The SafetyNet-API itself should be working, atleast I had no similar issues (after Registering the device it takes some time - around 5 minutes - for Android to reflect the registered state).
But if someone happened to have this issue and knows another solution, you are welcome to tell!
ad 2: Does it help when you try to import the Files from the SIM card? As for Google contacts, it is - from my POV - stringent, that, if the SafetyNet API doesn't work properly, you will be unable to access Google Services (as Google Contacts) which would explain the missing Google Contacts.
ad 3: GApps and microG are two different things. GApps install a version (open-source fork, contains proprietary binaries) of the Official Google Apps, that is, they provide full functionality towards google services, provided you registered your device correctly.
microG is a pure Open Source fork of that, providing but the Framework with which Google Apps can be run. It does not provide Google Apps (like PlayStore etc.) by itself but merely allows them to run, given the configuration is right. This microG-ROM is not built to work with GoogleApps like PlayStore, but instead relies on the microG Services to get Apps, providing same or similar services, running (like Aurora Store etc.). To address your question, it is possible, to change the source code which was used to build this ROM, so it builds with Gapps or completely free of any such services, in fact it would mean to exclude certain patches, but such projects (Treble-enabled) are covered by others and because of above stated reasons i will not be able to provide such in near future.
Short but clear: No, there is no way to "uninstall" microG as it is built together with the ROM and the source used was especially prepared to use microG. But if configured right, you should be able to use your Google-Account in combination with Google-Services-Apps or Games despite using microG.
ad 4: See above. If everything's configured right, you should be able to play Pokemon GO, although i don't use any of these Apps (Clash Royale, Pokemon GO, WhatsApp). I never encountered any Problems along using Google Apps with this ROM.
ad 5: Well, the error says it all. I have Mozilla Location Service installed, which works like a charm. Maybe try this one? You can get it from FDroid, search for "MozillaNlpBackend" and see if it helps to sort this out? This works for me, after all.
ad6: as this is very unspecific, i cannot really tell what's the problem, but i would guess it has to do with the SafetyNet API not doing what it should or even the Location Backend not reporting position in time...
Did you clean your cache and data partitions while installing this ROM? I really am not sure what could create the behaviour you describe. Maybe there was a change in the SafetyNet/Device Certification process since this ROM-Build, maybe theres someone in those boards who could answer this, but i unfortunately can't...
I'm sorry that i cant give you more positive news, but hopefully it helps you in orienting what some common problems could be caused by.
Let me know about your success in trying to get the ROM working.
Best regards and greetings to portugal!
ivelischt
additionally: if you are interested in porting the Lineage Source for GSI/Lenny 5, you might be interested in this Thread: https://forum.xda-developers.com/android/help/how-to-root-wiko-lenny-5-t3819469
specifically, i wrote a guide there on how to build Android/Lineage Source for Treble devices. Maybe this helps you in getting your own build environment, enabling you to build to your disguise.
Images are not available anymore. Anyone here?
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
A very similar thread with the same topic has been discussed a few days ago - you can check here
Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).
robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.
nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?
s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!