{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
PROJECT STATUS:
- Everything seems to work fine at this point.
HOW TO INSTALL LINEAGEOS:
- Check your current firmware version: required version is V3.150 (March 2021 update, Android 11).
- If you're not on this version or unsure:
1 Reboot to recovery
Code:
adb reboot recovery
2 Download https://android.googleapis.com/packages/ota-api/package/37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip3 Sideload the file
Code:
adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip
4 Reboot to recovery again5 Sideload the file again to have it in both slots, A & B
Code:
adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip
- Flash Lineage recovery/bootimage to active slot via fastboot:
- Find out active slot:
Code:
fastboot getvar current-slot
- Flash boot.img to active slot:
Code:
fastboot flash boot_X boot.img
- Reboot to Lineage recovery via the fastboot UI
- Sideload LineageOS via Lineage recovery
Code:
adb sideload lineage-18.1-20210718-UNOFFICIAL-panther.zip
- Optional: flash GAPPS before rebooting to system
GOING BACK TO STOCK:
- Sideload https://android.googleapis.com/packages/ota-api/package/37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip in Lineage recovery
DOWNLOADS:
- LineageOS 18.1
- Lineage recovery
- Google Apps: MindTheGapps
DEVELOPER RESOURCES
- LineageOS source code: https://github.com/LineageOS @ lineage-18.1
- Device tree: https://github.com/trautamaki/android_device_nokia_panther @ lineage-18.1
- Kernel: current: https://www.nokia.com/phones/en_int/opensource (prebuilt)
(for reference: https://github.com/trautamaki/android_kernel_nokia_sdm439)
Android version: Android 11
Kernel version: Linux 4.9.y
Required firmware: March update, Android 11, V3.150 (Nokia/Panther_00WW/PAN_sprout:11/RKQ1.200928.002)
THIS IS ONLY TESTED BY ME ON MODEL TA-1157.
Indian variant may or may not work with this.
Telegram: https://t.me/los_panther
Info for curious:
This uses prebuilt stock vendor, hence the need to have 2 proper slots (as well as correct firmware version)
UPDATE:
* Sync LineageOS sources
* Audio is fixed
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
All the basic functionality appears to be working now. It is still built with selinux permissive and eng-variant, which reduces security.
* Download
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* Built the userdebug variant
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
All the basic functionality appears to be working now.
Todo:
* Light HAL for notification indication LED
* Firmware version checks for checking vendor & firmware version
* Download
I was surprised when I saw lineage for my nokia 4.2 that sits in box since I got it for free from operator when renewing contract.
I am not a novice for lineage, but first time working with nokia. I unlocked bootloader, although I still have message every time when I turn it on, that bootloader is unlocked and device is not secure. I hope that is fine.
I checked slots and slot B is in use, so, as a novice and because of securing my existing OS (i hope that counts) decided to set slot A as active.
I didnt touched anything else except tried to sideload suggested image and install it. But, everytime I encouter a error at 47% - pc saying "adb: failed to read command: No error" while device saying that it is wrong image and it is for PAN_sprout?
Then I tried to sideload Nokia-4.2-V3.150_B01.zip with same error, wiping data between retries. And on slot B I have latest update - march 2021 and andr 11.
Also, I presume that my device is locked to operator and it is dual sim. I returned to slot B and device is in working condition.
Any idea what can be done so I can install lineage?
vladabgd said:
I was surprised when I saw lineage for my nokia 4.2 that sits in box since I got it for free from operator when renewing contract.
I am not a novice for lineage, but first time working with nokia. I unlocked bootloader, although I still have message every time when I turn it on, that bootloader is unlocked and device is not secure. I hope that is fine.
I checked slots and slot B is in use, so, as a novice and because of securing my existing OS (i hope that counts) decided to set slot A as active.
I didnt touched anything else except tried to sideload suggested image and install it. But, everytime I encouter a error at 47% - pc saying "adb: failed to read command: No error" while device saying that it is wrong image and it is for PAN_sprout?
Then I tried to sideload Nokia-4.2-V3.150_B01.zip with same error, wiping data between retries. And on slot B I have latest update - march 2021 and andr 11.
Also, I presume that my device is locked to operator and it is dual sim. I returned to slot B and device is in working condition.
Any idea what can be done so I can install lineage?
Click to expand...
Click to collapse
The instructions were purposefully a bit obsecure when the project status was hardly WIP. I should update the instructions soon.
Basically you need to flash LineageOS with the provided recocery image (see downloads).
Going back to stock, use boot-no-assert.img (it doesn't check device before install).
This is needed because I named the device panther instead of PAN_sprout. I will fix this some day.
T1mb3, thanks on all efforts. And thank you on reply! It is easy to follow your procedure once I figured out how these devices working - well I figured out enought to work with installing lineage. I am little bit more rusty. Ive heard for a slots for the first time now. lol. I have 2 sony compact devices - with lineage, only because windows 8.1 died. and I had 8.1 only because 6 died. hah...
So, after your explanation I successfully installed lineage on Nokia 4.2!!!
T H A N K YOU!!!
for those who will give a try I can add this:
- I had problems with unlocking bootloader - device was visible in adb mode, but once restarted fastoot didnt worked - check device manager in windows and if you see nokia 4.2 as other device just manually update driver with android adb device from list.
- once that worked well, everytime I start phone I see screen with warning that bootloader is unlocked. just wait for some seconds and it will disappear.
- once booted back to operating system check for enabled developer options and check does adb working. if it works reboot to fastboot with "adb reboot fastboot"
- with fastboot choose right slot for experiment: "fastboot getvar current-slot" shows current. mine was b so I changed to a with "fastboot set_active a"
- once set slot, flash boot with "fastboot flash boot_a boot-no-assert.img" where _a is slot you choose.
- reboot with "fastboot reboot"
- enter new boot and choose adb. with adb sideload zip "adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip". maybe there will be warnings but continue anyway. after some time and with step 2/2 check on computer did adb command finished. after finish restart nokia.
- i went directly to os, expecting that this is android from zip flile, on slot a. but then I checked and saw that active slot was again b and that android was mine.
- i went to fastboot again and set active slot to a again, tried to restart device and got message that operating system is corrupt. holding power button turns off device and i entered again bootloader with power button and vol down.
- then I decided to sideload lineage on same slot - a, who cares, hah, and sideloaded it after I wiped all data.
- restarted device and voila - lineage works!!!
maybe this will help someone who have nokia 4.2 and want to install lineage. time consumed is about one hour.
thanks T1mb3
vladabgd said:
T1mb3, thanks on all efforts. And thank you on reply! It is easy to follow your procedure once I figured out how these devices working - well I figured out enought to work with installing lineage. I am little bit more rusty. Ive heard for a slots for the first time now. lol. I have 2 sony compact devices - with lineage, only because windows 8.1 died. and I had 8.1 only because 6 died. hah...
So, after your explanation I successfully installed lineage on Nokia 4.2!!!
T H A N K YOU!!!
for those who will give a try I can add this:
- I had problems with unlocking bootloader - device was visible in adb mode, but once restarted fastoot didnt worked - check device manager in windows and if you see nokia 4.2 as other device just manually update driver with android adb device from list.
- once that worked well, everytime I start phone I see screen with warning that bootloader is unlocked. just wait for some seconds and it will disappear.
- once booted back to operating system check for enabled developer options and check does adb working. if it works reboot to fastboot with "adb reboot fastboot"
- with fastboot choose right slot for experiment: "fastboot getvar current-slot" shows current. mine was b so I changed to a with "fastboot set_active a"
- once set slot, flash boot with "fastboot flash boot_a boot-no-assert.img" where _a is slot you choose.
- reboot with "fastboot reboot"
- enter new boot and choose adb. with adb sideload zip "adb sideload 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip". maybe there will be warnings but continue anyway. after some time and with step 2/2 check on computer did adb command finished. after finish restart nokia.
- i went directly to os, expecting that this is android from zip flile, on slot a. but then I checked and saw that active slot was again b and that android was mine.
- i went to fastboot again and set active slot to a again, tried to restart device and got message that operating system is corrupt. holding power button turns off device and i entered again bootloader with power button and vol down.
- then I decided to sideload lineage on same slot - a, who cares, hah, and sideloaded it after I wiped all data.
- restarted device and voila - lineage works!!!
maybe this will help someone who have nokia 4.2 and want to install lineage. time consumed is about one hour.
thanks T1mb3
Click to expand...
Click to collapse
Nice!
The issue you had in the end was that you only flashed the 37a17a09b0b0d8ab0a3c398f373af4f0e1f067a1.zip once to slot a. Now when you go install Lineage, it installs to slot b -> there's a mismatch. Therefore you should install the stock rom twice.
UPDATE:
* Sync LineageOS sources
* Light HAL works now, features include battery light and static notification light (no breath effect)
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Fix tethering
* Download
Thanks on new update!!!
1 yes, you are right. I noticed that lineage is on slot b. I didnt understood when you wrote mismatch - do you mean that I needed to flash zip twice on slot a, or once on slot a and once on slot b?
2 also, I do not know how to flash updated version of lineage: if I just sideload it on existing and working lineage on slot b should I wipe data on slot b before install or I can just install over existing version?
3 finally: I never used opengapps - I meant mindthegapps so I wanted to try - I was late: already installed lineage and booted into it. do you have idea what to do now.
thanks on great efforts T1mb3!!!
vladabgd said:
Thanks on new update!!!
1 yes, you are right. I noticed that lineage is on slot b. I didnt understood when you wrote mismatch - do you mean that I needed to flash zip twice on slot a, or once on slot a and once on slot b?
2 also, I do not know how to flash updated version of lineage: if I just sideload it on existing and working lineage on slot b should I wipe data on slot b before install or I can just install over existing version?
3 finally: I never used opengapps - I meant mindthegapps so I wanted to try - I was late: already installed lineage and booted into it. do you have idea what to do now.
thanks on great efforts T1mb3!!!
Click to expand...
Click to collapse
1. Yes, you need to have the correct stock rom (vendor partition and firmware) version on both slots. Flashing it twice with a reboot back to recovery will do the job.
2. Download the zip, reboot to recovery and sideload normally. Data-partition does not have a/b slots, it's shared across both slots so no need to wipe it.
In your specific case, you will likely need to flash the stock rom once again to populate the vendor and firmware partitions, then Lineage update (both on the same slot).
3. Wipe data, flash Gapps, reboot. This makes you to start from the setup wizard.
UPDATE:
* Previous update I accidentally built eng variant instead of userdebug, this is same but userdebug.
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Fix tethering
* Download
I just tried it yesterday. Am I the only one whose nokia 4.2 constantly reboots after a minute or sth? Bc it seems like there are stability issues with the current build
el-chuerro said:
I just tried it yesterday. Am I the only one whose nokia 4.2 constantly reboots after a minute or sth? Bc it seems like there are stability issues with the current build
Click to expand...
Click to collapse
I have experienced no issues.
2 days with lineage on nokia 4.2 and no single issue. all is working even notification led.
i had issues with gapps - even i tried to wipe data and reinstall clean lineage google kept returning and crashing system. so I ended with what I didnt do at first place - complete wipe and starting from step one - stock rom on both slots with whole procedure one by one. it was exhausting but all worked fine after.
even I have branded phone I tested it with sim card from another operator and device is sim free now.
at the end, thanks to Timb3 we have very nice debloated and degoogled device. and I thought that I will never take it in hands... brilliant work...
UPDATE:
* Wifi causing whole system to crash (only affected a few) is fixed
* Wifi tethering is fixed
* Updated CarrierConfig
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
Todo:
* Firmware version checks for checking vendor & firmware version
* Download
I tried installing MindTheGApps from the start a handful of times. I don't know why, but it's never worked. I then tried to install OpenGApps too, but that also didn't seem to work? I'm very confused.
I don't get any errors, so I don't know what's happening. They seem to install fine, but when I get into LineageOS, there's no google apps installed.
UPDATE: I figured it out. I didn't realize I had to reboot back into recovery after the lineage install.
Wifi wont even turn on at all, I tap the quick button for it and it just turns itself off, I go into the settings themselves and switch it on, it turns itself off again.. so I guess wifi isn't causing system to crash now, but that's only because you cant even turn WiFi on at all
UPDATE:
* Headphone jack fixed
NOTE:
You may need to update recovery (= fastboot flash boot_X boot.img) to install this update.
Download updated recovery: https://sourceforge.net/projects/lineageos-panther/files/recovery/boot-2021-08-01.img/download
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
* Download
UPDATE:
* Security patch from August
Old news (only needed if upgrading from older build than 2021-08-01): Download and flash updated recovery if installing fails: https://sourceforge.net/projects/lineageos-panther/files/recovery/boot-2021-08-01.img/download
* Using prebuilt kernel & dtbo image (due to Nokia not releasing the source code for audio-kernel aka techpack/audio).
* Download
Related
Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix P v7.0.2
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.[/CENTER]
About Resurrection Remix:
Resurrection Remix is a custom ROM based on LineageOS, SlimRoms, Omni and the original Remix ROM builds. This creates an awesome combination of customization & performance optimizations while bringing the latest features directly to your device.
Introduction:
This is an unofficial build of Resurrection Remix for the Motorola G7, codename ocean.
It should support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable. Sadly, we can not support the Verizon or AT&T variants, as their bootloaders are permanently locked.
ROM:
RR-P-v7.0.2-20191103-ocean-Unofficial-signed.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy A to B: (prevents bricks)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
1. Download TWRP and the Firmware for your variant from the links above.
2. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
3. Unlock your bootloader Instructions HERE.
4. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
5. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
6. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
7. While in TWRP choose Reboot > bootloader
8. Now you're ready for ROM Steps below
ROM - Installation:
1. Download the ROM, TWRP and GApps from the links above.
2. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
3. Flash signed ROM.zip
4. TWRP_installer/boot.img ramdisk method
5. Tap Reboot > Select opposite slot > Back > Recovery
6. Install Gapps + Magisk (if you choose)
7. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
It is imperative that you flash copypartitions.zip before flashing any OTA zips via TWRP. If you fail to do so you may require a blank flash to recover your device from QCOM DL when it switches slot suffix from A to B.
Any time your internal storage aka "Userdata" is directly from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Unofficial Resurrection Remix for G7 Power , ROM for the Moto G7 Power
Contributors
Geofferey, SyberHexen, erfanoabdi
Source Code:
kernel_motorola_msm8953
android_device_motorola_ocean
proprietary_vendor_motorola-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock vendor.img
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 2019-11-03
Stable Release Date: 2019-10-31
Created 2019-10-31
Last Updated 2019-11-07
Changes:
- 10-31-19
Initial signed release
- 11-03-19
Improve notification led
Add picture adjust to livedisplay
This would get released an hour after my phone bricks. This is so f'ing frustrating. I'm sure the rom will be awesome.
Thanks a lot for this Rom!
With RR arrival for the G7 Power, the G7 power is becoming a viable solution for a main phone now!
disobey said:
This would get released an hour after my phone bricks. This is so f'ing frustrating. I'm sure the rom will be awesome.
Click to expand...
Click to collapse
How bricked? Lol. QCOM_BULK? Phone can prolly be unbricked with blank flash. Check out this group on telegram with some valuable resources & info http://t.me/G7Power.
the recovery .img you provided doesnt boot
---------- Post added at 06:07 AM ---------- Previous post was at 05:37 AM ----------
i just did an install following your instructions but using the recovery zip/img from here: https://forum.xda-developers.com/g7-power/development/rom-lineage-os-16-0-t3969341 and it seems to have worked fine
Everything seems to work fine but I just cannot get the twrp to permanent flash to the recovery... This ramdisk method is it literally just flashing the installer zip?
Geofferey said:
Resurrection Remix P v7.0.2
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.[/CENTER]
About Resurrection Remix:
Resurrection Remix is a custom ROM based on LineageOS, SlimRoms, Omni and the original Remix ROM builds. This creates an awesome combination of customization & performance optimizations while bringing the latest features directly to your device.
Introduction:
This is an unofficial build of Resurrection Remix for the Motorola G7, codename ocean.
It should support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable. Sadly, we can not support the Verizon or AT&T variants, as their bootloaders are permanently locked.
ROM:
RR-P-v7.0.2-20191031-ocean-Unofficial-signed.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy A to B: (prevents bricks)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
1. Download TWRP and the Firmware for your variant from the links above.
2. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
3. Unlock your bootloader Instructions HERE.
4. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
5. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
6. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
7. While in TWRP choose Reboot > bootloader
8. Now you're ready for ROM Steps below
ROM - Installation:
1. Download the ROM, TWRP and GApps from the links above.
2. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
3. Flash signed ROM.zip
4. TWRP_installer/boot.img ramdisk method
5. Tap Reboot > Select opposite slot > Back > Recovery
6. Install Gapps + Magisk (if you choose)
7. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
IIt is imperative that you flash copypartitions.zip before performing any ROM flashing via OTA zips in TWRP. If you fail to do so you may require a blank flash to recover your device from QCOM DL when it switches slot suffix from A to B.
Any time your internal storage aka "Userdata" is directly from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Unofficial Resurrection Remix for G7 Power , ROM for the Moto G7 Power
Contributors
Geofferey, SyberHexen, erfanoabdi
Source Code:
android_device_motorola_ocean
kernel_motorola_msm8953
proprietary_vendor_motorola-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock vendor.img
Based On: Lineage OS
Version Information
Status: Beta
Current Beta Version: 2019-10-31
Beta Release Date: 2019-10-31
Created 2019-10-31
Last Update
d 2019-10-31
XT1955-4 work?
Click to expand...
Click to collapse
Fully working now for 6 hours I can't see any bugs also fully bypassing the safety metrics and compatible with smali patcher spoofing Pokémon and able to use Google pay etc....
Match love man
sithuphyo said:
XT1955-4 work?
Click to expand...
Click to collapse
I don't see why it wouldn't.
By the way sorry I had posted the wrong link to TWRP, I've updated the link now.
I'm using Verizon, but plan to buy the variant with CDMA support that's unlocked. Do you know if this ROM will have any problems with it? Also, does VoLTE work with this rom?
@rocktone As I have no CDMA variant to test with I'm not sure. You might have problems with APNs but I wouldn't doubt that it would boot. VoLTE, wifi calling and messaging all work in my test but that's with a GSM carrier.
Nice ROM. Geofferey, thank you for your contribution!
I was only running Lineage OS for a few days when I decided to give this ROM a try. I performed the steps in 'dirty flash'. The ROM booted OK. Wow, there are a ton of options in this ROM!
For some reason, many Google apps did not show up. I flashed open_gapps-arm64-9.0-stock-20191025. I did not get Chrome, Drive, Duo, Maps, News, YouTube and others. I was able to install these via the Play Store. I think I figured out why this happened, but I will not attempt to replicate the problem; I'd rather stay with what I have.
Two notes for users: 1) stay away from the option which allows you to bypass PIN entry after reboot (w/fingerprint), 2) music visualizer on the lock screen does not work for me. It's difficult to find faults with this ROM.
PS: @sithuphyo or anyone else, please do not repost or quote the original post in its entirety. It makes comments difficult to follow.
I'm looking forward to trying this rom. I just got my phone yesterday and plan on trying this at some point. Probably not right now. I haven't even unlocked the bootloader or anything yet. I want to use it for a bit before doing that. I just got it all setup and don't want to wipe out my data yet. After coming from a phone I dropped in a sink full of water, I'm happy to have a 100% working phone. I look forward to seeing where this build goes.
Does it work on the 1955-2 ocean model, South American version?
danny8 said:
Nice ROM. Geofferey, thank you for your contribution!
I was only running Lineage OS for a few days when I decided to ....
Click to expand...
Click to collapse
How is battery life compared to stock ?
Sent from my moto g(7) power using Tapatalk
Battery life seems to be as good as stock.
KUSANAGUI said:
Does it work on the 1955-2 ocean model, South American version?
Click to expand...
Click to collapse
I have 1955-2 RETLA (I'm in USA) and it seems fine, as does Lineage OS.
A small feature in the stock ROM that's not in LOS / RR is the ability to turn off BOTH sims. You must have at least one sim active. If I were to do it over, I might've bought the USA version, even though it has less RAM, storage, and only one SIM slot. None of the previous is germane to your question, however.
Resurrection Remix ROM should work fine on your phone model.
MrCamby said:
How is battery life compared to stock ?
Click to expand...
Click to collapse
It is about the same or greater. See screenshot.
Unknown IMEI & No Sim Dectected
After install I have no sim dectected and unknown imei., everything else works just fine. Has anyone else had this issue and if so is there an easy fix?
I installed the update. I then put my phone down. When I came back the notification led scared me lol
Stock doesn't support the notification LED @Metalheadx you should have flashed the copypartitions.zip file. I think it's in the instructions.
Working great but is there an option to disable the fingerprint scanner acting as a home button? Only issue so far..
Edit: Replaced /system/usr/keylayout/uinput.fpc.kl with the one from Lineage to get rid of the fingerprint home gesture.
24hrs in it's very stable, no crashes or visual glitches :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.
*/
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with no more volume rocker or power buttons to mash. The GUI is also fully XML-driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open-source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Pease note! TWRP cannot currently decrypt any A12 ROM on any device. This is a known issue as AOSP changed the way encryption keys are stored. If a new workaround isn't found? TWRP may never decrypt again... We recommend removing lockscreen security, rebooting to TWRP, make your changes and then reboot to system and setup your lockscreen security again.
This is for OFFICIAL and BETA builds of TWRP for the Motorola Moto X4 (payton)
Stable Downloads:
https://twrp.me/motorola/motorolamotox4.html
Test Downloads:
https://osdn.net/projects/twrp-for-payton/releases/
Sources:
Official: https://github.com/TeamWin/android_device_motorola_payton
Tests: https://github.com/ThEMarD/android_device_motorola_payton-twrp
Platform Tools (adb/fastboot):
https://developer.android.com/studio/releases/platform-tools.html#download
Installation:
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of file is you downloaded):
Code:
fastboot boot twrp-3.4.0-1-payton.img
Optionally at this point, if you want TWRP to be your default recovery? You can install TWRP via the TWRP installer zip. Please note that ROM upgrades overwrite boot which in turn overwrites recovery so this process would need to be repated.
Upgrade instructions
Download desired TWRP installer zip version
Reboot to recovery
Select Install
Tap on install and select the TWRP installer zip you downloaded from step one
Reboot to recovery and confirm that the updated version of TWRP is installed
Nandroid backup/restore
Have an available microSD Card or USB OTG drive
Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
Reboot to TWRP
Restore boot, dtbo, system image and vendor image
Reboot to system
Once it boots to system without issues? Do not set any lockscreen security and reboot to TWRP
Restore data
Reboot to system
After it finishes boot? Your data and ROM will be restore but sometimes the UI might be incorrect, so reboot to system again
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
bigbiff for helping me get setup on on gerrit.twrp.me for official status and updating official TWRP
kaneawk, erfanoabdi for working on TWRP for payton
All the users who tested my builds of TWRP
ok I could literally be here all day typing so essentially anyone who has worked on the Motorola sdm660-common kernel for LineageOS and TWRP
i have seen you are trying to fix encryption in recovery.fstab - please note the file is overwritten from twrp.fstab during runtime, so either remove twrp.fstab or do the changes in there
for working encryption the flags should be written completely, afaik there is no autocomplete in twrp (like in android)
fileencryption=ice:aes-256-cts
---
furthermore i recommend /system_root instead of /system to keep things in line with other devices (although most flashable zips meanwhile can detect SAR)
to avoid `mount /system` (perhaps silently) fail instead of symlink i recommend bind mount (not standard so far, at least haven't seen that in official builds)
Code:
/system_root ext4 /dev/block/bootdevice/by-name/system flags=display="System Root";backup=1;wipeingui;slotselect
/system auto /system_root/system flags=fsflags="bind";backup=0;usermrf;ignoreblkid
---
another change what seems official now and (in request of user @lowerhater) you may include /data/media/0 aka Internal Storage for backup purposes (decision is up to you, external storage is required for backup location)
Code:
/storage auto /sdcard flags=fsflags="bind";display="Internal Storage";backup=1;usermrf;ignoreblkid
Hey thanks!
Any clue if restoring a nandroid backup works on the newest builds?
Heyyo @aIecxs , thanks for the suggestions! For the fstab change before erfan was saying that's optional as mentioning ice was the only important part, but I can definitely put the full description in for payton. FBE decryption on payton is fixed already as I used the same commits that I did to fix it on nash since sdm660 and msm8998 are the exact same CAF tags.
For the /system_root thing? Afaik that was for devices with A-only SAR that use the pie SAR implementation as it doesn't look like beyond1lte is an A/B device like Motorola sdm660 devices are. berkeley would be another example of A-only SAR device using pie's SAR implementation, but sadly though it seems they haven't had TWRP updates since 2019... Tbh I don't really know any other devices like that offhand...
As for that last suggestion? Yes we can implement that too.
ThE_MarD said:
fastboot boot twrp-3.4.0-1-payton.img
Click to expand...
Click to collapse
when i am giving this command
fastboot boot twrp-3.2.1-1-payton.img
downloading 'boot.img'...
its keeps stucks on this.
Heyyo @DARK EMP3ROR , unfortunately it seems Motorola devices are super picky... For me? It wouldn't work on my Windows 10 PC or Ubuntu Mate 20.04 either... My wife's old Windows 7 notebook it worked fine though, so you might need to setup a USB Live Boot for Windows 7 or something to get it going
you can try to figure out with fastboot options like kernel offset etc..
fastboot boot TWRP.img Not working
edit: or boot from bootable slot
aIecxs said:
found another possible reason why fastboot boot won't work when it should.
Exelios said:
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
Click to expand...
Click to collapse
Worth a try checking which slot is flagged bootable and set as active (the one with yes)
Code:
fastboot getvar current-slot
fastboot getvar slot-bootable
fastboot getvar slot-successful
fastboot --set-active=other
Click to expand...
Click to collapse
Heyyo, I have TWRP 3.6.1_11 test10 build up. It's rebased on TWRP-11 branch with source-built bootctrl HAL and libgptutils.
Please note! This will decrypt Android 11 ROMs, but can't decrypt Android 12.x ROMs unless you remove your lockscreen security first within the ROM before rebooting to TWRP. Currently TWRP does not have a method to decrypt A 12.x ROMs so this isn't a bug specific to payton.
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton - OSDN
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton #osdn
osdn.net
Your test 3.6.1_11 test 10 build with lineageOS 19.1 does boot when I use 'fastboot boot <file>', but it cannot unencrypt the drive like 3.5.0_9 was doing on lineageOS 18.1. this is the same behavior I see with the default 3.6.0_9.img file from twrp.me for Payton. All the 3.5.x versions of twrp get stuck booting and I never get far enough to enter a pin. I can't compare against the lineage recovery from the 19.1 test build, as whenever I try a fastboot of that img file, it just boots lineageOS rather than recovery, which seems weird given it works for twrp.
ThE_MarD said:
Heyyo, I have TWRP 3.6.1_11 test10 build up. It's rebased on TWRP-11 branch with source-built bootctrl HAL and libgptutils.
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton - OSDN
Release twrp-for-payton twrp-3.6.1_11-test10-payton - twrp-for-payton #osdn
osdn.net
Click to expand...
Click to collapse
The previous version prevented me from booting into the rom I installed. Will this work?
Heyyo @jtnc , the twrp.img file is only meant for temporary use (fastboot boot) and then install the twrp-installer.zip to install TWRP to both slots. Please check the installation instructions. Installing the twrp.img will overwrite your kernel which will break the installed ROM.
It didn't decrypt LOS 18.1 for you? That's odd, other users confirmed it did.
@Dukenukemx I confirmed on my payton it works. As I mentioned, the problem before with TWRP builds was the prebuilt bootctrl HAL and libgptutils.
Here is the latest pre-official TWRP test builds from their build server.
TWRP image:
https://build.twrp.me/twrp-3.6.1_11-0-payton.img
TWRP installer zip:
https://build.twrp.me/twrp-installer-3.6.1_11-0-payton.zip
Please test these. If they are confirmed as working? I will ask for a new official TWRP build for payton.
I understand the .img file is only for temporary use (fastboot) and that was all I was using it for. I could fastboot with the twrp 6.1 test10 image fine, but it would not decrypt. As such I did not bother installing it and stayed on 3.5.0_9. I did eventually realize my sdcard was not encrypted (d'uh!) and was able to flash the lineage recovery w/o a problem. I can't see the bulitin storage with lineage, so I'm assuming it's not decrypting either (nor did it prompt).
Using fastboot boot (so .img files for all), I saw:
twrp < 3.6 -- hangs on the twrp boot screen
twrp 3.6 -- fails to decrypt, but boots fine otherwise
lineeageOS recovery (any) -- boots to OS not to recovery when running 'fastboot boot lineage....recovery.img
I will try the official build you just posted later today when I can get back to my old laptop.
I just tried out the 3.6.1_11-0-payton.zip version of twrp on the official build server you pointed me at. It had the same results as with your test build, namely it does not decrypt internal storage for me. Probably worth someone else validating - assuming others are encrypted.
Since all the 3.5 series hang for me, I tried rolling back to an older version that used to work with encryption, namely a 3.3.3_1 version by Syberhexen, but it too failed decryption. I haven't looked at how encryption works, but it makes me wonder if something changed in 19.1 related to it.
18.1 encrypted worked fine with 3.5.0_9. I can't recall if I was running 3.5.0_9 or the 3.3.3_1 syperhexen version with 17.1/HavocOS.
Depending on how time goes this weekend, I might try rolling back to 18.1 and see if your build will decrypt that or not.
@jtnc, just to check, are you using FBE and not FDE for encryption methods? I just formatted the data on my payton and wiped dalvik and flashed LOS 18.1 and tested both via fastboot boot twrp-3.6.1_11-0-payton.img and adb sideload twrp-installer-3.6.1_11-0-payton.zip and both booted fine and I could PIN decrypt my LOS 18.1 ROM
It does take a minute or three to boot into TWRP, so I do recommend giving it a bit of time for decryption to work.
As I mentioned above though, TWRP cannot currently decrypt A12.x ROMs, so users MUST remove lockscreen security in the ROM before rebooting to TWRP.
Will there some time be a chance to decrypt A12 ROMs with lockscreen security by TWRP?
Thanks for an answer.
Heyyo @woodpe, from my understanding? Android 12.1 changes the way security key storage works, so the path that TWRP usually uses for decryption does not exist... so unless a new solution is found? Potentially TWRP might never decrypt lock screen security ever again...
Please test the pre-official TWRP build from their built server.
TWRP image:
https://build.twrp.me/twrp-3.6.1_11-0-payton.img
TWRP installer zip:
https://build.twrp.me/twrp-installer-3.6.1_11-0-payton.zip
If they are confirmed as working? I will ask for a new official TWRP build for payton.
I'm using lineageos19.1 in combination with the pre-offical TWRP.
All works fine, but no decryption.
@woodpe for A12 ROMs? You must remove lockscreen security, reboot to TWRP, make changes, reboot to system and then setup your lockscreen security again
ThE_MarD said:
Heyyo @woodpe, from my understanding? Android 12.1 changes the way security key storage works, so the path that TWRP usually uses for decryption does not exist... so unless a new solution is found? Potentially TWRP might never decrypt lock screen security ever again...
Click to expand...
Click to collapse
I think this is the problem I've been seeing then. I think I was hoping your test build fixed that problem! All my decryption issues with TWRP have occurred after moving to LineageOS 19.1. I did not have a chance to roll back to 18.1 and revalidate the 3.6.1 build you posted over the weekend, but given the above comment and your experiment on 18.1 I'd expect it to work fine for me.
Removing the lock screen pin and rebooting to recovery worked fine with 19.1 and TWRP 3.6.1_11, I have not tried it on TWRP 3.5.0_9. It's a bit annoying that you have to redo fingerprints every time you remove the lock screen security (at least for PIN, I assume that's true for any).
But given that TWRP 3.6.1 is not expected to work well PIN and 19.1, I'd say go ahead and make 3.6.1_11 official. The only thing I haven't tried is a complete ROM install but I was able to flash recover and other zips from it fine.
Question, would it be worth adding a note to maybe the second post of the lineageOS 19.1 thread indicating TWRP + 19.1 + lockscreen PIN does not currently work?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
TWRP version: 3.6.0_11
For device: gta4lwifi
Device tree: https://github.com/pazos/android_device_samsung_gta4lwifi
Maintainer/Authors build: paziusss
Known limitations
FBE encrypted storage (Internal Data) not able to be decrypted in TWRP.
Changelog
2021-12-08:
Added: exfat support
Added: mass storage support
Fixed: USB composition rules
Supressed audit messages in logcat
Misc changes (see device tree for details)
2021-12-05: Initial release
Motivation and credits.
AFAICT there're two TWRP builds on xda for the SM-T500, made by ragarcia87 and agreenbhm
The main motivation for Yet Another TWRP build was getting fastboot working, so we can follow official instructions to flash GSI builds on our devices.
Credits to u/agreenbhm for the device tree: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Credits to u/ragarcia87 for the thread, which I used as a template for this one
Installation Instructions
Spoiler
From computer:
Download Odin Flashable Tar from bellow
Put tablet into Odin Download Mode
Flash Blank vbmeta via Userdata
Flash Odin Flashable Tar via AP
From TWRP:
Download recovery.img from below
Copy recovery.img to device
Install > Install Image > recovery.img to Recovery
Reboot > Recovery
Flashing system/vendor/product/odm partitions
Spoiler
Logical partitions are read only from TWRP. If you want to flash them you'll need to reboot in fastbootd.
Boot in TWRP
Go to reboot and select fastboot.
Wait until you see a TWRP dialog saying "entered in fastboot"
Once you flashed all desired partitions reboot to recovery
In recovery wipe -> format data.
Notes on GSI flashing:
/product partition is unused in GSI builds. You can flash an empty image to gain 1GB for other logical partitions.
/system partition will be resized to the size of the GSI image you're flashing.
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Hi Magendanz. Thanks for your feedback.
I have no issues mounting the MicroSD card. Do you have some logs?
Updated DT link!
About the device tree: I'm having trouble pushing the changes to github because my slow connection. Will see if I got them pushed somehow. If not I will revert blobs to agreenbhm version.
Magendanz said:
Thanks for migrating this to Android 11! One issue I'm seeing is that I can't mount the Micro SD card.
Also, the link for your device tree seems to be broken. Could you please update?
Click to expand...
Click to collapse
paziusss said:
I have no issues mounting the MicroSD card. Do you have some logs?
Click to expand...
Click to collapse
Here's the log...
Hi!
Indeed, I didn't test with exfat. Should be fixed soon. Also adb sideload don't work in the version attached.
I will make the changes ASAP and give a better commit history in device tree
Hi. Device tree updated with support for exfat and ADB sideload fixed.
Will upload the binaries in a few hours!
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
stompysan said:
Thanks for bringing a nicer TWRP for GSI loading to our devices. I flashed this with no issues, but I am really struggling to get my device to boot any GSI. I am sure it is something that I am doing wrong on my end, since I have not messed with Samsung devices or any GSI installations before. Is there a change to have a more in-depth guide written up on installing a GSI on our device, or is there one already available that has similar instructions? I am planning on starting from scratch once I get home, and would like to have all of my ducks in a row before attempting again.
Click to expand...
Click to collapse
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Hi. I've updated recovery binaries and added a changelog.
Please report the issues you find.
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
Will it work with Pixel Experience?
EdwardTCM said:
Will it work with Pixel Experience?
Click to expand...
Click to collapse
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
paziusss said:
I didn't try. Install instructions are the same for all GSI roms. You can get a big list of GSIs in https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Some roms are bigger than stock, so you'll need to delete/wipe your product partition first. OP has instructions about it. I personally prefeer to flash an empty product.img instead of deleting the logical partition, to avoid TWRP warnings trying (and failing) to mount the partition.
Click to expand...
Click to collapse
Alright Thanks
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Edit: Maybe this is happening because of the ROM being A only
EdwardTCM said:
I flashed phhusson's GSI rom but my galaxy tab a7 keeps boot looping
Click to expand...
Click to collapse
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
thank you for twrp and fastboot but i noticed that most gsi images are bugy no brightness or randemly rebooting
paziusss said:
You need one of the ARM64 AB variants. No matter if it is vanilla, floss or gapps.
Click to expand...
Click to collapse
OOOH I thought it was A Only
EdwardTCM said:
I'm trying to flash the ROM I downloaded but I keep getting Sparse errors and when it finishes I get this FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
paziusss said:
Sure, I'll write a deep guide when I get basic stuff sorted out.
For starters, it is:
On TWRP -> Reboot -> Fastboot
Let the device reboot, wait until you see TWRP "entered fastboot"
Check your computer sees the device with
fastboot devices
(retry until it does)
Now erase system and flash a new image:
fastboot erase system
fastboot flash system whatever-aosp-gsi-ab-arm64.img
Finally reboot to recovery
fastboot reboot recovery
And format data:
Wipe -> Format data
Now you can reboot to the system. It will work.
I've tested it with Google AOSP builds, PHH builds and LineageOS builds based on PHH.
Bugs you'll find on any GSI build:
1. MTP doesn't work (needs a kernel change)
2. Brightness slider doesn't work (can be fixed easily without kernel change)
3. Probably more that I didn't found yet
Click to expand...
Click to collapse
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
EdwardTCM said:
To anyone who wants to try the Pixel Experience rom
USE A/B NOT A ONLY
Click to expand...
Click to collapse
Btw the wifi doesn't work
One Issue when downgrading to TWRP 3.5 is that it will boot loop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.
@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@aswin_a_s
@Gero
@melvingarcia
Support Us if you like our work
Got an issue or suggestion? Reach us at
Telegram: https://telegram.me/pixysos_chat
Phone calls & messaging
Wi-Fi & Mobile data
VoLTE (but no icon in statusbar)
Fast charging
Dark theme, night mode
Fingerprint sensor
Face unlock
NFC
FM Radio
Wireless Bluetooth audio with AptX codec
and much more...
Less customizations but more stability...
Pixys: PixysOS
Pixys Device Sources: PixysOSDevices
NOTE: It is recommended to update your stock ROM to Android 10 before flashing this custom ROM.
IMPORTANT: If you want to use GAPPS build, it is necessary to resize system and vendor partition on your phone before flashing rom! This step will perform format of system and vendor partition and even userdata partition so make a backup if you don't want to lose your data!
If you downloaded VANILLA build, you can skip this step and if you want then you can flash gapps of your choice.
Please download this nice and user friendly Nokia Repartition Tool brought to you by Raghu Varma and look at this instructional video:
Just use the first option "3.5G S - 1G V" - it is enough for this rom.
NOTE: After resize your phone will be automatically booted to TWRP, but because this tool is intended for Nokia 6.1 Plus, this TWRP will refuse to flash ROM zip on 6.1. In this case just reboot to bootloader and download this TWRP for our Nokia 6.1, boot it and everything will be fine. Now you can begin flashing.
After booting to TWRP:
1) If you just resized your system and vendor partitions using Nokia Repartition Tool then you have already formatted userdata so you can skip this step, otherwise if you want to do a clean flash then please Format Data by typing yes, then go to the Bootloader and reboot TWRP. (For dirty flash use adb sideload method because TWRP can not decrypt Android 12 userdata partition.)
2) Flash latest ROM zip via TWRP
3) Switch to alternative slot (if you are on slot a switch to b if you are on b switch to a)
4) Reboot system
Now you are done!
SafetyNet on latest PixysOS builds passes out of the box, so you won't need root/Magisk anymore. Flash Magisk only in case that you really need to root your device.
ROM: Sourceforge download linkAt the download page, you can choose GAPPS build (with Google play store and other apps included) or VANILLA build, which contains only basic apps without Google play store (in this case you can flash gapps of your choice).
Wi-Fi Hotspot works only without password. FIXED
Custom statusbar icon pack is reverted back to default after device reboot.
Credits:
- Google for AOSP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Superior OS
- Statix OS
- YAAP
- Krypton AOSP
- Project-Kaleidoscope
- AICP & POSP Team for thread template idea
- Also many pro developers who all help us to bring this rom to you...
- Please let us know if we forgot to mention your name in credits...
Contributors:
Big thanks to LineageOS developers and maintainers for Nokia 6.1 device and vendor tree on which this build is based!
Since PixysOS v5.1.5 thanks to Raghu Varma Android developer for new Nokia 6.1 device tree + vendor and kernel sources!
Kernel source:
https://github.com/LineageOS/android_kernel_nokia_sdm660
Kernel source since PixysOS v5.1.5:
https://github.com/RaghuVarma331/android_kernel_nokia_sdm660/tree/android-12.0-gcc
ROM OS Version: 12.1
ROM Kernel: 4.4.x
Based On: AOSP
Version Information
Status: Stable
Current Version: v5.1.5
Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!
Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!
I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)
Just tell me about the experience you had with the Rom. is it smooth or not
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Gcam not working fix it
Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.
Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)
Is anyone able to check if Duo Mobile 2fa is working?
I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.
Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.