Related
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/hero2qlte/twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
travis82 said:
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
Click to expand...
Click to collapse
It doesn't matter, dm-verity isn't enabled in the fstab, nor does the TWRP image contain any verity signatures to enforce.
finally...
thank god!finally!but the front cam issue have been solved?
Anyone know what roms work with this device? Also how to return to stock?
When compression is enabled on backups the device freezes.
What happened to CROM Service? It's not in the Galaxy Apps and .apk's from mirror websites crash when opened.
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
ryan49er said:
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
Click to expand...
Click to collapse
this recovery is for unlocked bootloaders only. IE chinese and hong kong models only.
Well that sucks
Report...
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
Click to expand...
Click to collapse
I had G9350ZCU2APK2 ROM (China), so I installed the Hong Kong ROM G9350ZHU2APK2 (I needed the google services) and the phone work great except the part of receiving or sending SMS's, I have two sim cards cards (China Telecom and China Mobile), if I sent a message from the CT the message was sent also from CM, if I send from CM is not working, when I receive messages I received on both sim cards... , big problem for me, so, I installed the last G9350ZCU2APL3 ROM (China) and is working ok but no google services...
I've tried your method and is working... (kind of) once I installed the TWRP and the last SuperSU the phone had no Wifi and no network signal, so I put back the original firmware...
All I need are the google services because Signal is not working without, the email client is not receiving the email (automatically) without and so on... I've tried all the "possible" ways, no luck...google installer v2 and so on...
Any ideas on how to put the google services?
----- Edit - 28 January 2017 ----
I reinstalled the TWRP provided in the first post and the phone is working, has signal (China Telecom and China Mobile) and also the WIFI is working, I didn't install the SuperSU, kind of weird, with SuperSu installed the phone has no WIFI and no signal...
I've tried to install the gapps pico and the TWRP is saying that "could not mount/data and unable to find crypto folder", "Failed to mount '/data' (invalid argument)", "Unable to recreate /data/media folder", "failed to mount '/data' (Invalid argument)", "Unable to mount storage" , "Unable to mount / data/media/TWRP/. twrps.
The last error is: "Failed to mount'/data' (invalid argument)
After reading more posts on the forum I found the following:
"You CANNOT mount an encrypted partition in TWRP.
You do NOT wipe the partition.
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button."
Probably I will try this method when I am in the mood...
This works for SM-G935P? It says manufactured in china on the back.
Salanrm said:
This works for SM-G935P? It says manufactured in china on the back.
Click to expand...
Click to collapse
The post is for the Qualcomm, Galaxy S7 Edge SM-9350, China Open and Hong Kong, same hardware, different software (the Chinese one has no google services).
For your phone SM-G935P, search on google and you will find more instructions, I don't know if I am allowed to post here links from other websites.
jcadduono said:
As a joke, here you go USA!
twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
good afternoon
Reference is unfortunately not working
Can somebody share twrp-3.0.2-0-hero2qlte.tar.md5
thank you in advance for your response
So, this will 100% NOT work for the g935A? (Att s7 edge)
Craz Basics said:
So, this will 100% NOT work for the g935A? (Att s7 edge)
Click to expand...
Click to collapse
No. Locked bootloader
Sent from my SM-G935T using Tapatalk
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Craz Basics said:
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Click to expand...
Click to collapse
It's a serious long shot but it is slowly being worked on.. check out this thread. It's for t mobile but the solution if found will apply to all us carriers as we all use the same method to root on marshmallow.
https://forum.xda-developers.com/showthread.php?t=3544220
Sent from my SM-G935T using Tapatalk
Team Win Recovery Project
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
#include <std_disclaimer.h>
{
"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"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy S9:
https://twrp.me/samsung/samsunggalaxys9.html
Galaxy S9+:
https://twrp.me/samsung/samsunggalaxys9plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - Discussion, Testing, Feedback and Support
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
To contribute:
TWRP Code Review
Github pull requests will be ignored.
XDA:DevDB Information
TWRP for Galaxy S9 and S9+, Tool/Utility for the Samsung Galaxy S9+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2018-03-15
Last Updated 2018-08-15
Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
USB connection fixes
Mar 14, 2018:
Initial version
Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Since Android O, Samsung introduced a new security feature, Remote Mobile Manager (RMM) aka Remote Lock Control (RLC). This feature allows stronger theft protection but unfortunately it also imposes a burden on users like you.
Samsung added a 7-day buffer period for enterprises or device owners to spot a missing/rogue device so they can use this feature to lock the device remotely.
In this 7-day (Prenormal) period, you can NOT flash any custom binaries including but not limited to this TWRP. OEM Unlock option won't appear, either.
(You will meet "custom binary blocked due to remaining installment balance" or "custom binary not allowed" error when you try)
The 7-day timer will start/reset once you completed the setup wizard. After 7 days (168 hours), RLC service will send an inquiry to Samsung's server. If your device is "clean", the RMM state will become "Normal".
Then you can enable "OEM Unlock" option and flash TWRP. Be careful, DO NOT reboot to a stock ROM before you flash patch in part 2 of this guide or you will have to go through another
Whether you have RMM problem or not depends on your model, region and/or carrier.
If you don't have any wait period to enable OEM Unlock option, congratulations but please do NOT mislead other people.
NOT EVERYONE IS AS LUCKY AS YOU.
If you don't have RMM problem when you get the device, it is unlikely that you will get any RMM problems later.
But note that this problem applies to MAJORITY of people.
Note that the special patch will freeze RMM, FRP and OEM lock state.
This is an anti-stupid measure to prevent careless users from enabling security measures which are not compatible with custom binaries.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings, remove all Samsung and Google accounts and if your device is registered to an enterprise, de-register it.
3. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
NOTE: You will be asked to do a factory reset, that's normal.
BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.
You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.
4. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
5. Download and extract Odin (Samsung's Flash Tool) to your computer.
6. Download a .tar image of TWRP.
7. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
8. Open Odin and place that TWRP tar file in the [AP] slot.
9. Connect your phone.
10. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
11. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP:
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO".
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
Now you may want to flash a root solution (Magisk, SuperSU, etc) or custom ROM but keep in mind that:
1. This thread does NOT provide technical support to any root solution or ROM unless the problem is DIRECTLY related to TWRP and there is no other solution without modifying TWRP itself.
Please contact developer of respective ROM or root solution for technical support.
2. Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection". https://www.samsungknox.com/en/blog/real-time-kernel-protection-rkp
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
Awesome work Jesse. Thank you!
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
@jesec hey mate, happy to see you again (S7 ROM)
Sorry i don't have this device but my friend will try soon
spackeddie01 said:
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset.
Click to expand...
Click to collapse
Please boot to recovery instead of system.
Be aware that Android Verified Boot requires data to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data,*all*state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot) It is normal to get such prompt.
Got twrp installed formatted data, rebooted twrp, do we need Dm-Verity? If so how to get it on as MTP is not working, or OTG, and system bootloop so can't get back in to do it that way.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
Click to expand...
Click to collapse
You have to flash dm-verity/magisk.
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
iamnotkurtcobain said:
Awesome work Jesse. Thank you!
Click to expand...
Click to collapse
Dis you try treble AOSP ?
giorgior.r said:
Dis you try treble AOSP ?
Click to expand...
Click to collapse
I can't. This TWRP is for 9+. I have a normal S9.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
BokkieAndijk said:
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
Click to expand...
Click to collapse
You formated system it seems.
Steps are:
-flashing TWRP
-boot into TWRP
-format Data
-reboot recovery
-install magisk
-reboot
iamnotkurtcobain said:
You have to flash dm-verity/magisk.
Click to expand...
Click to collapse
pls can you give me a link to the packages you have used?
Thanks.:good:
Nice to see you doing work on the S9 @jesc
deleted
@jesc good to see you in the s9 forums. Great work as usual
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
BokkieAndijk said:
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
Click to expand...
Click to collapse
check in this site
https://www.sammobile.com/firmwares/database/SM-G965F/
Flashed twrp then flashed no dm verity - seemed to flash ok - but saw one error message that says "failed to mount '/cpefs' - I haven't seen that error before but thought it might be important. THis message happens after the flash has finished -(after it says updating partician details)
Tried to flash magisk after I flashed twrp and phone bootloops had to flash stock in odin
{
"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"
}
Official TWRP 3.6.1-* For Galaxy A5/A7 (2017)Only for exynos variants - A520F (Europe, Global Single-SIM); A520F/DS (Global Dual-SIM); A520K/L/S (South Korea); A520W (Canada), A720F (Global Single-SIM); A720F/DS (Global Dual-SIM); A720S (South Korea)
Disclaimer
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 recovery 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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
A5 2017 - https://twrp.me/samsung/samsunggalaxya52017.html
A7 2017 - https://twrp.me/samsung/samsunggalaxya72017.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A5 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a5y17lte
A7 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal7880/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks
like!
bootloop
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
e.ahangari said:
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
Click to expand...
Click to collapse
What device and what method of flashing did you used?
a7, when installing Odin, bootlooр
bootloop
corsicanu said:
What device and what method of flashing did you used?
Click to expand...
Click to collapse
A720F oreo stock rom - I wanted to update from twrp_3.1.0-1 to 3.2.2
cant flash in a7 2017 (a720f)using odin
on my a7 bootloop too, flash via twrp. flash through odin previous version helps
A520F, zip downloaded and flashed in TWRP, It's perfect, no problem (bootloop) at this time!
Thank you corsicanu.
Well done.
Works great for me, flashed .img in TWRP,A520F.
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Thanks
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
Thanks a lot.
Its now fixed and work properly.:highfive::highfive::highfive:
Thanks
A7y17lte
is anyone installed root succesfully?
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
I'm about to receive a new A5 2017 and update it to official OREO right out of the box.
After having updated, there's the TWRP step and I just wanted to know of I have to also flash the usual encription thing (opt verity or something like that) I have almost always flashed after a fresh twrp install.
Works fine for me so far... I will test with the official fw to know if the /data is decrypted. We appreciate the work corsicanu. :good:
@edit
For me, everything works fine! including support for all languages.
A7y17lte
corsicanu said:
Unofficial TWRP 3.2.2-0 For A5 / A7 2017Disclaimer
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 recovery 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.
Special features:
Code:
- built from Oreo kernel source
- built in full 64 mode
- updated TWRP source
- fully compatible with all Oreo roms
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.zip, push it into phone storage and flash it as normal zip in your current recovery.
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/twrp_android_kernel_samsung_universal7880
Credits:
@Dyneteve
@TwrpBuilder
Click to expand...
Click to collapse
is anyone installed root succesfully?
Hey,
I have a problem and I don't know how to fix it, cuz I never had that.
I've installed TWRP successfully and I can start it normally, but TWRP don't have access to any Files in Internal Storage.
I installed TWRP on A520F (with Firmware DBT, Android 8.0)
Kind regards,
DasNuddel // Charles
{
"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"
}
Official TWRP 3.6.1-* For Galaxy S9/S9+ ExynosOnly for exynos variants - G960F (Europe, Global Single-SIM); G960FD (Global Dual-SIM); G960N (South Korea); G965F (Europe, Global Single-SIM); G965FD (Global Dual-SIM); G965N (South Korea);
Disclaimer
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 recovery 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.
Features:
Code:
- built from Android 10 kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 9.0/10.0
Downloads:
S9 - https://twrp.me/samsung/samsunggalaxys9.html
S9+ - https://twrp.me/samsung/samsunggalaxys9plus.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
S9 Device tree - https://github.com/TeamWin/android_device_samsung_starlte
S9+ Device tree - https://github.com/TeamWin/android_device_samsung_star2lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9810/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
First:laugh:
Nice af!
support f2fs？
Many Thanls bro ?
Thanks
Congratz Corsi
Thanks for your hard work?
Data decryption working?
thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks
Is the issue described here:
https://forum.xda-developers.com/showpost.php?p=81072679&postcount=1832
fixed with this release?
jamaljmys said:
thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks
Click to expand...
Click to collapse
I think I have a similar problem. These were my steps:
flashed TWRP through Heimdall
booted into TWRP
wiped data
flashed the no verity opt encrypt zip
flashed LineageOS (official nightly from May 1st), gapps and Magisk
After that I booted the system and encryption was forced during boot. When I rebooted into recovery I was prompted to enter the password, which was not successful (decrypt failed because it took too long).
Before all that I was running an official and up-to-date Android 10 Samsung (April security patch).
Hi. I need emergency help. I'm new on s9+ & flashed twrp as well formatted data partition then flashed no-verity-opt-encrypt-6.1 but whenever entered to system then returned to recovery mode then i lost internal storage again again & again. Please help me. I'm on latest android 10 firmware.
Hi ?
Will you update the SHRP to latest TWRP Base ?
And will be very good if you will support the Orange Fox Recovery
I like those two recoveries because of password protection and they have more features…
Thanks for your work for our devices!
Seems the dl link isn't working. I tried connecting to the dl site on my phone and my PC and both returned with a "This site can't be reached" error.
I just tried contacting TeamWin through the contact form on the TWRP website and it seems as though the submit file for the form was deleted.
Could I live WITHOUT disabling encryption via flashing no-verify? I want to have my /data encrypted.
Hi Mate just wondering would this working with a Samsung Galaxy S9 plus
Model SM-G96F
Android version 10
One UI version 2.1
Cheers
Dan Ger said:
Lineages os not support encryption ..so that why you have it problem like that...feel free to check on telegram support group So you will understand
Click to expand...
Click to collapse
So are you saying that LOS does not support disabling encryption? I tried the whole procedure multiple times and it seems that the patch fails because the fstab entries are not found in LOS.
Could an encrypted data partition cause issues recognizing the sim card? I find this hard to imagine, but I have both issues pretty persistently.
Cheers
The OP says:
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
I've downloaded twrp-3.3.1-1-starlte.img.tar (as recommended elsewhere for my S9) but how do I do the last part?
What is TWRP_*.tar.md5 file? How do I get it?
Is there anyone who got TWRP 3.4.0 working with encryption on a Samsung Galaxy S9?
My experiences after 1 hard week:
1. On Stock: TWRP always showed an unlock option via PIN, but it was never able to decrypt (neither default_password, nor disabling lockscreen, nor setting another PIN/Password in locksetings helped)
2. On Magisk: TWRP never showed an unlock option & was never able to decrypt
3. Only option was to disabled encryption --> the old encryption disabler from OP doesn't work, updated Disable_Dm-Verity_ForceEncrypt_03.04.2020 has to be used ( https://forum.xda-developers.com/an...rceencrypt-t3817389/post77091359#post77091359 ) --> patter lock & fingerprint cannot be used in the future
A little disappointing considering that the unlock option of TWRP & changelog suggests that decrypting should work.
@moocou
BTW: Put TWRP_*.tar file into AP tab
{
"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"
}
Disclaimer:
I'm not responsible of any damage made to your device by installing this ROM
Following the installation process will trip Knox, thus your device warranty may be void.
Click to expand...
Click to collapse
What's working?
- Audio
- Bluetooth
- LTE
- Display
- WiFi
- Charging
- Location
- Encryption
- Camera
- S-pen
- Enforcing SELinux
What's not working?
- You tell me
Installation instructions
Spoiler: Installation instructions
Installation requirements
- A computer
- ADB installed on the computer, you can find a guide here
- Odin (v3.14.1 is verified to work fine), you can find it here
- A decent battery level on the device
Step 1 - Unlocking the bootloader
You may skip this section if you have already unlocked your device
- Enable developer options
- In developer options, toggle the "Allow OEM unlocking" setting
- Reboot into download mode following the instructions below
- Once into download, long press the volume up button and follow the instructions on the screen
- After the bootloader is unlocked, your data will be erased, so make sure to back it up first.
- Now, once the system has finished booting, you MUST connect to a WiFi network, enable developer options again, and make sure that the OEM unlocking toggle is on and grayed out. If you do not see the toggle on the developer settings, close the settings and try again a few times.
- Once you see the toggle greyed out, all is set.
Step 2 - Installing the LineageOS recovery
In order to flash the ROM, you need a custom recovery, which you can find on the downloads section.
For installing the recovery:
- Boot into download mode as described below
- Press the volume up button a single time to fully enter download mode
- Connect your device to your computer
- Once you are in download mode, open Odin and make sure that it detects your device
- Go to options on Odin, and disable auto-reboot (DO NOT ENABLE ANY OPTIONS OTHER THAN F. Reset Time and Auto-Reboot)
- Download the vbmeta.tar file from the downloads section
- Select on the "Ap" button the vbmeta.tar file and then click "Start"
- Download the recovery.tar file from the downloads section
- Select on the "Ap" button the recovery.tar file and then click "Start"
If Odin gets stuck (specially when flashing recovery.tar), you might try the following:
- After you flash vbmeta, reboot into download again, and directly flash the recovery (once you have flashed the vbmeta once you shouldn't need to flash it again)
- Try a different PC or USB cable
- Try a different version of Odin
Click to expand...
Click to collapse
- Once the flashing completes, power off your device by pressing power + volume down, and after the screen turns off, quickly press the key combination for booting into recovery
- If everything went fine, you should be now on the LineageOS recovery
Warning: if you boot into the OneUI again, it will overwrite the custom recovery and you'll need to install it again!
Step 3 - Installing the ROM
- Download the ROM from the downloads section (make sure you download the .zip file and not the .sha256sum file)
- Once in recovery, go to the "Apply update" section, and click "ADB sideload"
- Connect your device to the computer, and sideload the update with adb sideload path/to/file
An example of the command on Windows can be adb sideload C:\Users\myuser\Downloads\lineage-20.0-20230223-unofficial-gta4xlveu.zip
Click to expand...
Click to collapse
- Your device should start verifying and installing the update
- After the installation has finished, you need to format the data partition (Factory reset -> Format data/factory reset)
- Now, click "Reboot to system"
- If everything went correctly, you should be booting LineageOS
How to boot into recovery/download modes:
Spoiler: Booting into recovery/download
Download
- For booting into download, you will have to press at the same time the power and the two volume buttons until the "Download" screen shows up.
- If you want to boot into download with the device powered on, you have to press the reboot option and right after that, press the key combination as mentioned above.
Recovery
- First, make sure to connect the device to a computer, otherwise the tablet won't allow you to boot into recovery (it's a Samsung restriction).
- For booting into recovery, just press the power and volume up buttons. Once the Samsung logo / bootloader unlocked warning has appeared, you can release the buttons and press the power button to skip the warning screen.
- Just like with the download mode, if you want to boot into recovery with the device powered on you just have to press the keys right after pressing the reboot button.
DownloadsAll files (ROM, recovery and vbmeta) are available at https://files.danielml.dev/android/gta4xlveu/.
Both models (WiFi and LTE) are compatible with the same ROM zip (gta4xlveu).
Help and supportJoin the Telegram group for getting support
Other details:
Kernel source: https://github.com/gta4xlve-dev/android_kernel_samsung_gta4xlve
Device source: https://github.com/gta4xlve-dev/android_device_samsung_gta4xlveu
Reserved
Thank you very much, i will test it next week.
Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!
K9droid56 said:
Testing out the new ROM, glad to see one for the Qualcomm 2022 version.
Battery stats works
Camera works
Using lawnchair 2 and it works! Pixel keeps crashing (?)
Thanks!
Click to expand...
Click to collapse
Glad to see that you liked the ROM.
Here Pixel launcher works, not sure why it doesn't there.
Anyways, I'll remove GApps by default on future builds so the Pixel launcher won't be present. (Of course, you'll be able to install a custom GApps package).
Thank you! Also started to test now. I disabled most of google app from the start and went fdroid/aurora way (waiting with anticipation for no google version). Nothing crashed yet.
btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?
bugit said:
btw, how to root this image? is patching boot.img and replacing it in zip and then flashing as above enough, or is there any changes required for vbmeta?
Click to expand...
Click to collapse
Well, I didn't try, but just flashing Magisk *should* be enough.
daniml3 said:
Well, I didn't try, but just flashing Magisk *should* be enough
Click to expand...
Click to collapse
unfortunately this method does not work: during sideload it fails with `Unable to repack boot image` and recovery logs are somehow empty, but still managed to boots after this error
i will try with patching boot.img when i will have more time
ok, i managed to flash image with patched boot.img (extract zip, uload boot.img to device, patch with magisk, download patched boot.img, remake zip image),
but just flashing patched image from recovery made my existing system unbootable
and i had to reflash stock firmware and then repeat flashing steps from scratch
(flash vbmeta/recovery, and then flash patched image),
with this the device is booting and root is working
notes:
- the unbootable state from above was device going into black screen just after samsung logo, with no hints of activity (10 min was max i waited)
- only pressing all tree keys (power, volume up and down) made it reboot with about one second of turn off state (so one can't actually power off the device, it just boots up again into black screen after logo)
- after reboot i was not able to enter recovery or download mode by just pressing known combinations of buttons, and the only way to enter download mode was: during this 1 second power off state to press volume up and down keys and connect usb cable (spend some time finding this solution)
- during flashings after uploading vbmeta i could not flash recovery right after vbmeta (it gets stuck during upload) and i had to reboot again into download mode and then flash recovery (this happened both during my first try to install this image, and with the patched image)
- for some reason in this image i have two sets of navigation buttons at the bottom of the screen (the triangle, circle and square buttons), one is standard android set and one compressed to the right side of nav.bar; stopping pixel launcher removes the compressed one, but the square button (task switching) stops working
- after installing patched image i also noticed (in hindsight) that actually during first install the scroll was very choppy (and the system was kind of slow), but in second install this problem went away
Thanks a lot for the ROM. The following steps for rooting lead to success for me:
1. flashing according to the instructions as described by daniml3.
2. copy Magisk 25.2 to the external SDCARD and rename to .zip
3. reboot in recovery
4. factory reset -> format data/factory reset
4. do not boot, but install Magisk from tablet via ADB from SDCARD
5. reboot
6. rename magisk to .apk again and install the app
7. set up Magisk
8. after reboot be sure to complete ANDROID setup
It rocks!
The navigation buttons are also duplicated for me.
I hope I could help.
I wish a LineageOS without Google.
Thanks everyone for the feedback! There are a few notes:
- I'll release a version without Google Apps as soon as possible (most likely this weekend).
- The lag when booting is caused due to some overlay issue, I still have to look into it, but as it doesn't affect much to the functionality after a few seconds its not a "priority".
- The duplicated navigation buttons are actually an issue from the Google Apps (maybe the Pixel Launcher?). This will be fixed with the Google app-less version of the ROM. If you switch to gesture navigation this issue dissapears.
Is there a possibility for SM-P619 LTE version?
Razor64 said:
Is there a possibility for SM-P619 LTE version?
Click to expand...
Click to collapse
As I said on the post, if you have the LTE model, and want to try a build, just let me know (preferably by Telegram).
Uninstalling the pixel launcher via adb removes the extra icons.
Small lag at start-up but other wise a smooth-running rom.
Thanks!
Today (if everything goes as planned) I'll publish a new update for the WiFi-only model, including:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
This will probably be the last update in a (few) week(s), as I'm working on an source-built-vendor device tree, which may take some time.
I'm also working on a build for the LTE variant, which will be published as soon as I verify that it works correctly.
At the moment I am not at home. After my short vacation I am looking forward to try it at the end of the week.
Many thanks for your work.
A new update for the SM-P613 (gta4xlvewifi) was published just now with the following changes:
- Enforcing SELinux
- Removed GMS by default (you can install them as a separate package, personally BitGapps worked perfectly)
- Fixed some background services crashing
Download it at https://sourceforge.net/projects/gta4xlve-dev/files/gta4xlvewifi/lineage-20.0/
Warning: If you used GMS, you'll need to manually install them (I use BitGapps and they work correctly).
Latest update runs really smooth with bitgapps. Lawnchair works with no problems. Thanks again for this ROM!
Bit of a stretch to ask, but would it be possible for the build to identify itself as a tablet, rather than a phone? And the possibility of defaulting the orientation to landscape? (90 degree rotation as default rather than 0)