Related
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T 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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
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.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
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 the next step 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 your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
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-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.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 for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.
{
"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"
}
This is a Official Build of madOS ( based on AOSP 8.1.0 ) for Vernee Apollo Lite & X with MTK 6797 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* 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.
*/
Installation Instructions:
The latest 7.1.2 build must be flashed in SPFT with firmware upgrade mode before this ROM can be flashed (Downloads: VAL, VAX)
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download 8.1 GApps from xda devdb (Mirror)
Backup
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Fingerprint
Lights
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Bugs:
-
XDA:DevDB Information
madOS_O_VAL_VAX, ROM for all devices (see above for details)
Contributors
fire855, DerTeufel1980, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-12-25
Created 2017-12-25
Last Updated 2018-01-13
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery
--> Check xda Download Section
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file (LP rom layout)
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: is the Data connection issue of going to / from 4G still present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulkan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: Does 4k video recording work?
A: Yes, but not every phone supports it. If 4k worked in the stock rom, it will work in madOS too.
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A:OpenGapps arm64 nano/mini
Since there's no Official GAPPS for 8.1.0 just yet...
... we had built OpenGapps nano and pico versions
--> Check Download Section
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelogs
[Stable] Build [8.1.0] 20171225
First Release
madOS version: 2.1
Patch Level: 8.1.0 [OPM1] December 5, 2017
Kernel: 3.18.89 (o-8.1.0 branch)
[Stable] Build [8.1.0] 20180102
madOS version: 2.1.1
Fixed UI lags / hangs
Fixed deepsleep
Fixed screen recording
Fixed video playback issues
Updated graphics system
Improved GSM/LTE signal handling
Fixed alarms
Fixed FMRadio
Fixed wallpaper scrolling setting in madLauncher
Fixed 5GHz hotspot issues
Improvements in bluetooth for A2DP
Updated included APNs list
madOS color Engine:
Rebased & many improvements on the engine
Better support on theming Quick Settings
New option to override default Google 8.1 QS theming
New reset button to get back to default 8.1 theming
New MAD mode
Merry Christmas !!
Thanks. Merry Christmas.
The computer died. I will not make the sd card backup.
Marry Xmas to all.
Wow.... Oreo release and directly 8.1 weeeeeeeeeeee!
Didn't expect this before the new year, what a surprise.
Thanx you @fire855
Thank you MAD-team
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Should we come from the last 7.1.2 build (which has different partitions from stock)?
I really appreciate the work, but it's somewhat unflashable. New recovery is not stable, it gets stuck sometimes. Also I didn't manage to bring 8.1 to run with Gapps yet.
€: To provide somewhat more information: System crashes when running playstore.
€2: Full wipe made, advanced wipe and wiped every partition. It gets stuck coincidential, there's no proper reason for it, it got stuck once when I flashed MadOS itself, second time it got stuck flashing gapps, so I hope I get it run that night...
€3: Recovery freezes and after 30 seconds (approx) phone reboots.
€4: Nope, I don't get it to work, goddamnit. It freezes almost immediately after I enter my pin.
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
TJFA81 said:
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
Click to expand...
Click to collapse
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Xorianator said:
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Click to expand...
Click to collapse
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
TJFA81 said:
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
Click to expand...
Click to collapse
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Xorianator said:
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Click to expand...
Click to collapse
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
TJFA81 said:
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
Click to expand...
Click to collapse
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
€5: Nope, didn't fix a thing. So well, at least I could capture this "sack down" thing:
The red line is where the display ends. As you can see the symbols are still in place. The blue line marks where the activity "sack down" and if this happens (which happens just on coincidence) nothing will happen any further, system's frozen and it reboots afterwards.
TJFA81 said:
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Click to expand...
Click to collapse
TWRP
Xorianator said:
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
Click to expand...
Click to collapse
Thank you, already did it... reflash recovery.img but by spflashtool. Now im inside twrp3.2.1...
Now its time to try install oreo and gapps
cedricboquiren said:
Should we come from the last 7.1.2 build (which has different partitions from stock)?
Click to expand...
Click to collapse
Yes, the latest 7.1.2 is mandatory. Added this to the first post now too.
I tried to install the new rom, after I installed the new twrp, the phone is still restarting, I tried to return to 7.1.2 with spft but no success even does not connect with the laptop, what I could do they 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:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04
OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
NIce, thank you
hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation
Can this ROM be installed on top of LineageOS 16 without wape?
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse
@NeoArian Any chance for a screen recording of how it runs?
JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.
{
"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"
}
Crab Experience V1.7 for Galaxy A8
Made by TeamCrab (Github @TeamCrab)
Experience whole new world
Introduction:
(This may have an Some bugs, Because Its my first Custom ROM Made with an Samsung's Stock Firmware. and i am bad at english. as you can see, i can't use grammer. I am currently learning an Grammer.
I am a korean and i am student. that means i have to learn more and that means i don't have an many time to do development. The Update may late.)
Do you want to downgrade to Samsung Experience?
Do you want the Samsung Experience?
If you can back to samsung experience, do you will back to Samsung Experience?
Then, This may be a good choice for you!
This is the stock rom from samsung and we got the stock rom of android 8.0 from A530N. and when we got official rom of A530N (Galaxy A8 2018) We made this rom with making a project. and that project name is the "Crab". And Thats the start of Crab Experience.
How to Download?
We uploaded the Crab Experience V1.5 in MEGA and You can use it for Free. I was not spended many times for developing this ROM Because This is an Stock ROM. Here is the Link:
Developer Edit: Removed Download link because its deprecated. To be continued in Project Samsu..
Test Some Early Releases and Feedback My Early Release!
Shh... This is the Secret Early Releases only opened for XDA Users.. If you want to test some new features, We think the Early Release is not bad for you!
The Early Release may not Stable for Your Device. We need more fixes for Early Release, So We need your feedbacks. The Feedbacks makes Early Release is stable for Device.
No more things today! there is not have to test it. We'll send you a notification if the beta test is started!
---------------------------------------------------------------------------------------------------------------------------
How to Install Early Release
1. Odin 3.14.4
2. Samsung Driver for Smart Devices
3. TWRP for jackpotlte: https://twrp.me/samsung/samsunggalaxya82018.html#google_vignette
4. Flashable Crab Experience
5. Magisk or SuperSU for Enable Boot
So Thats all. lets continue to manual!
Before Start this..
Please Enable the OEM Unlock in Device's Developer Mode and Enable an USB Debugging in Developer Mode.
If you disable OEM Unlock and If you flash the TWRP then Your Device may get bricked. So Please, Before do it, UNLOCK OEM AND ENABLE USB DEBUG PLEASEEEEEEEE
0. Press Volume Button's Middle + Power Button (In A530N Volume Down + Power is Not works and This method works in A530N. If you're A530F or A530W then it may have other method to boot to bootloader.)
1. Extract the Odin and Download the TWRP, Flashable ZIP, Samsung Driver
WARNING: If you extract Flashable ZIP File You can't Flash the Device Because TWRP Only Allows to Flash .zip and .img Format Files.
2. Open the Odin and Select TWRP We downloaded at the Partition Named "AP"
If you ready, Click the Start button and Flash the Recovery to Device.
3. If the Device Reboots, Get into Recovery with a Volume Up + Power Button
4. If the TWRP Screen Appears Swipe the Bar. The Message in the TWRP Screen is nothing effective.
(Optional) Wipe System, Data, Dalvik, Internal Storage and Cache for Clean Install. If the Device includes the important files, please select dirty install. Dirty Install just updates device like OTA from Official Samsung Update.
5. Flash the System (Crab) First and After Flashed System Flash the Magisk or SuperSU for Patch Boot Kernel.
--------------------------------------------------------------------------------------------------------------------------
If The Link broke, Please Comment. We'll check Is Link has broken and We'll fix it!
Changelogs:
Heres the Update Logs we made. we don't have any monehs lol so i just made with google sites and it will like trash but we are okay because you're thinking right well we'll add an update notes
Team Crab
March 31, 2022 FixesBuild Number: did:knox:26:SPE_80_711b469aa76840b7a3f72fe38e7f6d1784378a2891f14999aa538d15db93602b - Team Crab format Build Number Security Level PatchedSecurity Level is improved to 2020-12-01, This update will be last update. Build Number Changed that get displayedThis
sites.google.com
Please Read This!
DEPRECATED
This ROM's Development is Deprecated and We should not keep this project. This project is now closed. Thanks for testing This ROM. (To be countinued in Project Samsu. To Download, Visit here... https://samsu.xyz)
Developments are done (No more fixes) But for the personal use MEGA Link will be not deleted. I will upload a some screenshots that i worked on DarkOreo, DarkPie, DarkNougat in here after the 1 months
Thread reopened.
Badger50 said:
Thread reopened.
Click to expand...
Click to collapse
Hello Staff and Thanks for reply. We checked the Thread has reopened. Thanks for Reopening My Thread Again We found an Problem and we uploaded the fixed firmware.
i used rom for a530n device and found it quite stable (beta version)
Hi.
Do you know if it still has Mirrorlink available in this rom?
Thank you
knd said:
Hi.
Do you know if it still has Mirrorlink available in this rom?
Thank you
Click to expand...
Click to collapse
Hello! Thanks for waiting the Reply. We checked Mirrorlink has available in Previous Android! Mirrorlink was renamed to Smart View. So If you want to use mirrorlink then, please use the smart view at notibar. Thank you.
cuongnguyen2906 said:
i used rom for a530n device and found it quite stable (beta version)
Click to expand...
Click to collapse
Thank you for your reply! If you find some errors, please report it here Thanks for using Team Crab!
Hello Brother! I am the Team Perl! I am so surprised with your work. We Tested on A8 Beta and It worked stablly!
Be a awesome adventure!
Sincerely,
Team Perl
ShinyPerlTwentyTwo said:
Hello Brother! I am the Team Perl! I am so surprised with your work. We Tested on A8 Beta and It worked stablly!
Be a awesome adventure!
Sincerely,
Team Perl
Click to expand...
Click to collapse
Hey Team Perl! We are so glad because you are here. Wanna Work it together on Crab? We don't have many developers for development of Crab.
Hai! Nice works bro. Btw, I'm try install your works, but get stacked on Samsung Galaxy A8 logos. My device is A530F, did you know why ?
Envy_ said:
Hai! Nice works bro. Btw, I'm try install your works, but get stacked on Samsung Galaxy A8 logos. My device is A530F, did you know why ?
Click to expand...
Click to collapse
You have to install an Patched boot.img, That means you have to patch boot image with a Root like Magisk or SuperSU. Try it again, it works normally if you install Root. Btw, We are currently fixing an Boot.img Patch error with using a Magisk's Boot Image Patch Script.
(Sorry for being late Envy_!)
TwentyTwentyTwo said:
You have to install an Patched boot.img, That means you have to patch boot image with a Root like Magisk or SuperSU. Try it again, it works normally if you install Root. Btw, We are currently fixing an Boot.img Patch error with using a Magisk's Boot Image Patch Script.
(Sorry for being late Envy_!)
Click to expand...
Click to collapse
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Envy_ said:
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Click to expand...
Click to collapse
Thanks for reply! WE WILL WORK HARD FOR CRAB! THANKS!
Envy_ said:
Woahhhh, okay, I'll try it soon. Thanks. Btw, can't wait for the next update. Fighting!!
Click to expand...
Click to collapse
Thanks for waiting update! the early release is released to every XDA Users with a ZIP format (not a zip.lz4) and the new early release includes the Patched Boot.img!
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Samuraj89 said:
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Click to expand...
Click to collapse
Agreed!! Korean samsung phone with mobile operator so many bloatware, maybe you can deblot that @TwentyTwentyTwo
Samuraj89 said:
The firmware is super, but it is possible to somehow remove duplicate items from the settings.
Click to expand...
Click to collapse
Thanks for reply! We're currently thinking to base on A530F for debloat the Service Operator menu.
Envy_ said:
Agreed!! Korean samsung phone with mobile operator so many bloatware, maybe you can deblot that @TwentyTwentyTwo
Click to expand...
Click to collapse
Yep thanks for the reply, and we're currently thinking to base on A530F for debloat the Service Operator menu, i hate that menu too lol
TwentyTwentyTwo said:
View attachment 5533425
Crab Experience V1.7 for Galaxy A8
Made by TeamCrab (Github @TeamCrab)
Experience whole new world
Introduction:
(This may have an Some bugs, Because Its my first Custom ROM Made with an Samsung's Stock Firmware. and i am bad at english. as you can see, i can't use grammer. I am currently learning an Grammer.
I am a korean and i am student. that means i have to learn more and that means i don't have an many time to do development. The Update may late.)
Do you want to downgrade to Samsung Experience?
Do you want the Samsung Experience?
If you can back to samsung experience, do you will back to Samsung Experience?
Then, This may be a good choice for you!
This is the stock rom from samsung and we got the stock rom of android 8.0 from A530N. and when we got official rom of A530N (Galaxy A8 2018) We made this rom with making a project. and that project name is the "Crab". And Thats the start of Crab Experience.
How to Download?
We uploaded the Crab Experience V1.5 in MEGA and You can use it for Free. I was not spended many times for developing this ROM Because This is an Stock ROM. Here is the Link:
File on MEGA
mega.nz
Test Some Early Releases and Feedback My Early Release!
Shh... This is the Secret Early Releases only opened for XDA Users.. If you want to test some new features, We think the Early Release is not bad for you!
The Early Release may not Stable for Your Device. We need more fixes for Early Release, So We need your feedbacks. The Feedbacks makes Early Release is stable for Device.
This Early Release Includes:
Team Crab Version Checker Added - It includes in System files so you are only able to disable apps, not a delete apps but it may look trash because i am new at creating apps with a kotlin from android studio lol
New Build Number Builded - New Build Number is generated from One UI Base and the build prop and updater script tweaks New Build Number into the system
Security Level Upgraded - the Security Level is Upgraded from SU2 to SUC (SU13) but its only the build prop tweaks and it is uneffective to flash roms you can still flash the Android 9.
Boot Image Patched - Now, you don't need to root, Because the Boot image was patched with Magisk! Boot Image is modded with Magisk and meaning the boot image includes magisk manager.
Build Number: A530NXSUCBVCC
File on MEGA
mega.nz
---------------------------------------------------------------------------------------------------------------------------
How to Install Early Release
1. Odin 3.14.4
2. Samsung Driver for Smart Devices
3. TWRP for jackpotlte: https://twrp.me/samsung/samsunggalaxya82018.html#google_vignette
4. Flashable Crab Experience
5. Magisk or SuperSU for Enable Boot
So Thats all. lets continue to manual!
Before Start this..
Please Enable the OEM Unlock in Device's Developer Mode and Enable an USB Debugging in Developer Mode.
If you disable OEM Unlock and If you flash the TWRP then Your Device may get bricked. So Please, Before do it, UNLOCK OEM AND ENABLE USB DEBUG PLEASEEEEEEEE
0. Press Volume Button's Middle + Power Button (In A530N Volume Down + Power is Not works and This method works in A530N. If you're A530F or A530W then it may have other method to boot to bootloader.)
1. Extract the Odin and Download the TWRP, Flashable ZIP, Samsung Driver
WARNING: If you extract Flashable ZIP File You can't Flash the Device Because TWRP Only Allows to Flash .zip and .img Format Files.
2. Open the Odin and Select TWRP We downloaded at the Partition Named "AP"
If you ready, Click the Start button and Flash the Recovery to Device.
3. If the Device Reboots, Get into Recovery with a Volume Up + Power Button
4. If the TWRP Screen Appears Swipe the Bar. The Message in the TWRP Screen is nothing effective.
(Optional) Wipe System, Data, Dalvik, Internal Storage and Cache for Clean Install. If the Device includes the important files, please select dirty install. Dirty Install just updates device like OTA from Official Samsung Update.
5. Flash the System (Crab) First and After Flashed System Flash the Magisk or SuperSU for Patch Boot Kernel.
--------------------------------------------------------------------------------------------------------------------------
If The Link broke, Please Comment. We'll check Is Link has broken and We'll fix it!
Changelogs:
Heres the Update Logs we made. we don't have any monehs lol so i just made with google sites and it will like trash but we are okay because you're thinking right well we'll add an update notes
Team Crab
March 31, 2022 FixesBuild Number: did:knox:26:SPE_80_711b469aa76840b7a3f72fe38e7f6d1784378a2891f14999aa538d15db93602b - Team Crab format Build Number Security Level PatchedSecurity Level is improved to 2020-12-01, This update will be last update. Build Number Changed that get displayedThis
sites.google.com
Please Read This!
Sorry for being late update, We're currently working on new pc. Because, We moved from the Old PC and while moving my pc's hardware was not worked normally so my hard drive was got destoried. Well, we have to download it Firmware again. Please Help us!
TMI: My PC is not using Windows Anymore, My PC is Now using Rectify11 V2.5 so it may not compatible with a program that makes an Custom Firmware i use lol so it may be a late update
Problem:
We checked the software won't boot to System if you not rooted with magisk or SuperSU. We'll check how to fix to boot system without root.
Google apps are too old and YouTube not works because YouTube is old too.
Early Release Problems:
We don't know why, a build we are currently testing is not works normally it stops in setup wizards (its stock boot image, not a modded. we are thinking to stop a project now.. its impossible to fix it because its a system's problem.)
Click to expand...
Click to collapse
work on A530F?
{
"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"
}
Hi everybody, I have been looking for a way to get an official version of Vanilla Android 14 on the Tab S6 for and wanted to make sure the community finally had access to a fully working and sufficiently detailed guide.
This ROM improves battery life by 200%, it's absolutely insane.
Every source, link or file referenced in this guide is 100% official and safe.
Cheers!
Download Firmware + Extract:
Install SamFirm and download the latest firmware for the Tab S6.
(You will also need to install Visual Studio C++ 8 & 9 for this software to function properly)
SamFirm Tool
Download the latest version of SamFirm Tool, which helps you download the Samsung Stock Firmware (ROM) for free.
samfirmtool.com
Install 7Zip and extract the firmware zip.
Then open the CSC file with 7zip and extract the PIT.
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
Disconnect USB/power cables and turn your device OFF
Hold both Volume buttons (do not press Power) and plug in the USB cord connected to your PC
The download/unlock screen should come up immediately. Select the option for device unlock mode.
Download TWRP:
Download the official TWRP and vbmeta image
TWRP > https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
vbmeta > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Download Official AOSP / Android 14 Image:
The official Android 14 (or 13/12/11) GSI is available on Google's developer page and needs to be extracted via 7zip. (This will also contain a vbmeta.img but disregard it)
(GMS = Gapps | No GMS = Vanilla | FLOSS = Open Source Apps Only)
(Make sure to get a arm64 version) https://developer.android.com/about/versions/14/gsi-release-notes.html
If you prefer the consumer grade "prettier" version of AOSP, you can also download one of the arm64 images provided by phhusson on Github, who exclusively uses official sources code, as well.
https://github.com/phhusson/treble_experimentations/releases
You can also download one of the official daily builds directly from the ACI Project's master-branch (Android Continuous Integration) which represents the literal bleeding edge of AOSP straight from Android : https://ci.android.com/builds/branches/aosp-master/grid?
Flashing Firmware with Odin
Download Odin Flash Tool from a safe source.
Odin - Download
Odin: Samsung-Geräte rooten und flashen - Kostenloser Download für ✓ Windows
www.netzwelt.de
Put the Tab S6 in Download Mode by pressing both Volume Up + Volume Down, while simultaneously connecting the USB cable. (The tablet needs to be off)
Open Odin and add the Firmware Files to the appropriate slots
BL > BL , AP > AP, CSC > CSC
Then click on PIT and add the previously extracted PIT file
Lastly click options and select Nand Erase, Re-Partition, while unselecting Auto Reboot
Flashing TWRP & vbmeta with Odin
After successfully flashing hold down Power Button + Volume Down for 7 seconds but be ready to immediately hold down Volume up + Volume Down to re-enter Download Mode.
(USB Cable needs to be connected at all times)
(If you missed your chance and it's booting, hold down Power Button + Volume down to reset and try again)
Once back in Download Mode click Reset in Odin
Deselect Auto Reboot in the Options again
Then add the TWRP image in AP and vbmeta.tar in the CP slot.
Wiping Cache & Partitions
After flashing hold down Power Button + Volume for 7 seconds and immediately hold down Power Button + Volume Up the entire time until you see TWRP.
Once inside TWRP wipe Dalvik Cache and Cache in the Advanced Wipe menu. Subsequently re-enter the wipe menu, select Format Data and type yes.
After this (USB cable still connected) make sure the Internal Storage is mounted and transfer the system.img (extracted from the AOSP GSI zip) to the tablet
Finishing Up
In TWRP click Install, select the system.img and choose system image.
Flash it, Reboot to System and your DONE!
Current build - Android 14:
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
Working:
Fingerprint
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Top Speakers
This issue has already been fixed in the Beta Version which will soon be moved to stable.
Current build - Android 13 (Beta):
(at the time of writing this)
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
Generic System Image releases | Platform | Android Developers
developer.android.com
Many, many thanks for this.. If i understand correctly, we can choose the android 13 file which includes gaps, so to have Google services?
Also there must be an error. The pit file is in CSC file and not in AP file.
Il try it, I'll post the results when i do it.
Thanks again!
I just installed it. Working fine. It does have gaps and playstore and it is vanila android, doesn't have samsung ui.
I suppose i can install in twrp magisk to root it.
After i flashed twrp and restarted, it didn't boot in twrp, but all screen had an error message with yellow txt, something about microsd (which i didn't had). I restarted again to boot in twrp, and this time it did boot in twrp, so i did flash image.
Thanks again!
Anyone knows how to root it?
After flashing system image from android 13, twrp is deleted as i understand. Trying to boot in recovery, it boots to normal recovery, not twrp.
I flashed in odin again only twrp and vbmeta
(TWRP image in AP and vbmeta.tar in the CP slot.). Only those files i used, I'm not sure if this is correct. Anyway, i booted in twrp this time. I couldn't find download folder where i had magisk.zip to flash, trying to root, so i finally just restarted the tablet. It booted ok, but when i tryed again to boot in twrp, it booted in normal recovery again, not twrp.
---If anyone can show me the contact steps to install twrp and root..
--- Aslo in this 13 rom, there isn't fingerprint scanner. Is there any way (xposed, something) to install it?
Thanks!
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated. Until then, i have to go to android 12 original..
sosimple said:
Although rom is fantastic, with excellent battery life, Ulunfortunately i found a bug which is important for me. Only the 2 right speakers work. The other 2 dont. If some time in the future there is a fix to this, it would be much appreciated.
Click to expand...
Click to collapse
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
tablet_seeker said:
The speaker issue has already been fixed in the Daily Beta Version of Android 13 offered on the Google Developer's page. Just flash one of those.
Versions des images système génériques | Plate-forme | Android Developers
developer.android.com
Click to expand...
Click to collapse
Ok thanks. I'll try the beta.
sosimple said:
Ok thanks. I'll try the beta.
Click to expand...
Click to collapse
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
tablet_seeker said:
Additionally, you can also try the arm64 image from ACI's master-branch. This is literally straight from Android and built/updated hourly.
https://ci.android.com/builds/branches/aosp-master/grid?
I just flashed the one that was released this morning and all four speakers work.
Click to expand...
Click to collapse
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
weinbers said:
Which version/build did you use? Also, for updates, does the system>update function within the room work or does the full zip file need to be flashed each time?
Click to expand...
Click to collapse
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
AOSP GSI with Android 14 has just been released! You can flash it right now with this guide.
Android 14 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 14 preview builds.
developer.android.com
tablet_seeker said:
The first column named "aosp_arm64"
Branch Grid
ci.android.com
That will lead you to this page: https://ci.android.com/builds/submitted/9909221/aosp_arm64-userdebug/latest where you'll choose "aosp_arm64-img-9909221.zip"
As for your question about updates, it depends on whether your device supports seamless system updates. The SM-T860 and SM-T865 do not support it.
Click to expand...
Click to collapse
This one have gapps included ?
Stable ?
Thanks for your work
Amr.Bendari said:
This one have gapps included ?
Stable ?
Thanks for your work
Click to expand...
Click to collapse
GMS = Google apps included
The regular arm64 image is Vanilla Android without Gapps.
You can also grab daily gsi builds from ci.android.com
Android 14 is brand new, so it's not perfectly stable but definitely usable.
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Hello ,
Thank you for sharing the info
I have checked Rom and answered my own questions .
Widevine is L3 (so only 480p on Netflix)
Performance in Hearthstone is way better .
Unfortunately for me only bottom speakers works , i have checked both 14 and 13 beta
When using spen or Samsung keyboard pointer is set to vertical orientation when tablet is in Horizontal position ,
So they are unusable .
Cannot relock boatloader since it is erroring out on the VBmeta
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
maybe with some magisk modules.. or if your lucky just by flashing the apk
Sage said:
In the title you have Android 14.. though then in Post #1 you have Android 13?
I did try 14 though they brightness did not work properly? and the it kept freezing? You said "Android 14 is brand new, so it's not perfectly stable but definitely usable." which version did you use? Cause the one i tried definately wasn't
Click to expand...
Click to collapse
Thanks, fixed.
The Preview version on Google's main GSI site is unstable. You need to get the latest build on ci.android.com
They are literally building and releasing new artifatcs every 30 minutes.
Also, do you know where to get a Disabler for force encryption on Android 13 for the tab s6? Can't find anything.
Scodera said:
Hello!
Has anyone rooted now?
How about updates?
Can I just play it like that? I'm currently on Android 13...
Click to expand...
Click to collapse
Sure. Just download the Magisk APK from Github.
Install the Magisk APK, then extract the boot.img from your firmware files. Transfer the boot.img to your tablet, patch it with Magisk and then flash this patched img in TWRP choosing the boot option. There are tons of guides for this online.
No updates bc the tab S6 does not support seamless updates. You have to flash new versions. But its super fast because you just flash system and ur good.
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
Yes. I don't trust APKMirror so what I do is install the stock ROM from the latest samfirm firmware. Root it. Install File Commander, or any other root file manager.
Then navigate to /data/app and grab the Samsung Notes APK. All other apps are stored in this directory BTW. Then just install the APK once you flashed AOSP GSI
niklas389 said:
Is there any way to use Samsung Apps like SNotes?
Thats the only thing I would need from OneUI
Click to expand...
Click to collapse
If you still want to keep using Samsung apps under a different OS like this one (AOSP, A14) install the Magisk module " Xmlpak a road to vendor apps".
After reboot, the Samsung apps you want to use again should show up in the app store for you to install. If not you can use APKMirror to download the APKs. Contrary to what a user posted above, this site is more than safe and verified.