Related
{T2 Ultra}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 4.4 which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about 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.
*/
XDA:DevDB Information
{Z2}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project, ROM for the Sony Xperia Z2
Contributors
jerpelea, Kali-, Bin4ry
Version Information
Status: Testing
Created 2014-07-08
Last Updated 2014-07-08
XDA:DevDB Information
{T2 Ultra}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project, ROM for the Sony Xperia T2 Ultra
Contributors
jerpelea, Kali-, cdesai, adfa666, tilal6991
Version Information
Status: Testing
Created 2014-11-03
Last Updated 2014-11-03
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
DOWNLOAD
http://unrestrict.li/FXP
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
Can ot be used fr dual sim variant????
working, non-working things?
Camera isn't working as of yet and its not for dual sim variant. Dual SIM builds should be there soon.
Cheers,
AJ
What is the need to flash Boot.img ?
What if i have recovery already installed.
Should i Flash it directly via CWM Recovery ?
Any ETAs on Camera Bug fix and Dual Sim ?
lostfurby said:
What is the need to flash Boot.img ?
What if i have recovery already installed.
Should i Flash it directly via CWM Recovery ?
Any ETAs on Camera Bug fix and Dual Sim ?
Click to expand...
Click to collapse
No ETAs
Cheers,
AJ
For Xperia T2 Ultra LTE users who cant find the FXP link
http://uploaded.net/file/0x3ztg29/from/ruwncw
@jerpelea
Please update your download links
the unrestrict website hasnt been updated for a long time
lostfurby said:
What is the need to flash Boot.img ?
What if i have recovery already installed.
Should i Flash it directly via CWM Recovery ?
Any ETAs on Camera Bug fix and Dual Sim ?
Click to expand...
Click to collapse
Please don't ask for ETA's mate!
hi there
what is the code name for t2 i didn't find it in download section
It is Tianchi
@jerpelea
its always a greatest challenge to find any thing on http://unrestrict.li/FXP
and yes dont know why but never ever able to download from that website in india
same issue happens while downloading flash tool latest version
dont know how to use that website
Quick question. If I have TWRP already installed, do I still need to flash the boot.img? Or can I just flash the ROM directly from recovery?
hackerxx said:
Quick question. If I have TWRP already installed, do I still need to flash the boot.img? Or can I just flash the ROM directly from recovery?
Click to expand...
Click to collapse
You need to flash boot.img. Its the Cm11 kernel.
Sent from my D5322 using XDA Premium 4 mobile app
Hi everyone! I've just installed boot.img, etered the CWM, and so there is the ROM.zip? Help me faaster plz, i'm the noob, but i'll need a phone today.:crying::crying::crying:
MrSmileXe said:
Hi everyone! I've just installed boot.img, etered the CWM, and so there is the ROM.zip? Help me faaster plz, i'm the noob, but i'll need a phone today.:crying::crying::crying:
Click to expand...
Click to collapse
no worries
open flash tool select ftf and flash
get you phone working again
chauhanjayc said:
get you phone working again
Click to expand...
Click to collapse
I know how to return to stock, but I still want to install CM.
Can somebody help me?
Ok, I'm installing Rom.zip, but it wrote me EROR STATUS 7, what to do?
Can i just delete first words in updater script?
Sorry for spaming, but im so laaaarge noob, so i don't know how to defuse eror 6, if u send me a file with the correct code I will so happy so won't be able to say a word ^^.
PLZZZ
About
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
(Source: https://twrp.me/)
Is this the official TWRP thread?
YES until you find any further notice on https://twrp.me .
Features
<MM> (PREVIEW): Build on (Android 6.0) sources
<N> (PREVIEW): Build on (Android 7.1) sources
<O> (PREVIEW + current OFFICIAL): Build on (Android 8.1) sources
<P> (PREVIEW): Build on (Android 9.0) sources
TITAN kernel inside (build with UBER Toolchain)
Time is working (for both STOCK and CM/AOSP based)
Decrypting is supported on: MM, N, O (CM/LOS/AOSP based ROMs) and on STOCK based ROMs (N only)
DT2W (double tap to wake up) - thx for the idea ufocus removed, sorry.
see the Changelog post for all features!
Requirements
You need to have a unlocked bootloader (see FAQ #9) to install and use TWRP!
To avoid issues with some ROMs (e.g. CM) this TWRP version comes without any supersu
Known issues
decrypting STOCK (other then N) is not working - only CM / LOS / AOSP based are fully supported
on some devices (unfortunately not on mine) the screen keeps unresponsive during a backup. Please just be patient it will start working again after the backup has finished.
after flashing Nougat bootloader (e.g. v29a) TWRP may lag. This has been reported by a few but I cannot reproduce that on mine.
Download
official twrp download page (search for your device model)
unofficial / PREVIEW releases:
From time to time I may release unofficial PREVIEW versions before merging them to official builds.
Those are meant as test builds only! Keep in mind that all my changes when they go stable will be merged with the official tree so you can just wait for a stable release.
Keep in mind that unofficial versions may contain unknown bugs!! so don't rely on backups taken from these versions!
Unofficial PREVIEW downloads (most current):
1) When do you need to install a specific flavor (MM, N, O,...) ?
if you want correct time setting in TWRP
if you want to decrypt - so encrypted your device
2) Is there any other reason why I should use a specific flavor (MM, N, O,...) ?
no!
you can use ANY flavor if you don't care about the above 2 reasons
3) So I can use ANY TWRP version to install ANY ROM?
Or do I need to use a specific flavor (MM, N, O,...) when it comes to install ROMs or other ZIPs?
read 2) again!
Download Link: http://leech.binbash.rocks
BETA downloads (extremely outdated): Download section above.
Installation
Optional but highly recommended:
Backup with SALT (click) before doing ANYTHING else!
Method 1) TWRP app (recommended but requires a rooted device)
Google play store: TWRP-App
Without play store: official twrp website
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled!
Install the app and open it. Agree to the Terms.
Select TWRP Flash.
Select your device from the device list (H811, H815) and choose a version.
The file will download to your Downloads folder.
Browse to and select the file.
Tap on Flash to Recovery.
Find out more about the app here.
Method 2) fastboot
This howto works 100% up to and including MM (scroll down for N):
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
It is highly recommended to verify your TWRP installation by booting into Android now
fastboot reboot
Then execute: adb reboot recovery
or in a Android terminal app execute: reboot recovery
If you see TWRP afterwards then you are safe to use the key combo:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
This howto is for the Nougat bootloader (for LP or MM scroll up):
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC (fastboot BOOT command has been removed from Nougat!):
fastboot flash recovery twrp.img
(replace twrp.img with the real file name you downloaded)
There is no 100% way to verify your TWRP installation so you have to take the risk but ensure you follow this next step briefly:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Do this right now!! open the factory reset screen to get into TWRP!
If you skip the step and boot into Android before doing this TWRP will be overwritten by Android so it is crucial important to do this step above directly after flashing TWRP!!!!! if you miss it you will have to flash TWRP again!
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
Upgrade
Upgrading TWRP is easy. Just push the new image file to your device and flash from TWRP!
boot into TWRP (check the FAQ for a howto)
copy the new twrp.img to your device while still in twrp (e.g. enable MTP in TWRP and use a file explorer or by typing adb push twrp.img /sdcard on your PC (needs ADB installed. Again check FAQ for how to set this up))
In TWRP switch the view to show image files by choosing the button at the bottom named Image and walk to the place where you pushed the new twrp image file.
Choose the new twrp image file and when asked choose the "recovery" partition
done. You can now reboot into recovery again to check that the upgrade has worked.
Support
I have created a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
I'm normally also available in the official twrp IRC channel and besides that it is always the best way for getting direct TWRP support (channel #twrp)!
Before actually going there or if you're new to IRC please read and follow FAQ #5 What is required to get support?
Thread rules
Never ask for ETA's !
Sources
Official builds device tree: github
PREVIEW builds device tree github
Kernel: TITAN kernel
Thanks/Credits
TEAMWIN of course
@DevUt for the continues help on IRC
@jcadduono for some help with qseecomd libs
@kessaras for the TITAN kernel and for being often enough my testing *****
XDA:DevDB Information
Official TWRP, Tool/Utility for the LG G4
Contributors
steadfaster, draymond1987
Source Code: https://github.com/TeamWin/android_device_lge_g4
Version Information
Status: Stable
Current Stable Version: 3.4
Stable Release Date: 2020-06-22
Current Beta Version: any PREVIEW
Created 2016-08-18
Last Updated 2020-08-21
Changelog
Latest Official release
twrp-3.4.0-0
Release date: 2020-06-22
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: no changes
Summary changelog:
TWRP release notes
Previous Official(!) builds
twrp-3.3.1-2
Release date: 2020-02-28
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: github
Summary changelog:
you REALLY wanna now what has changed?
check it out
twrp-3.3.1-1
Release date: 2019-07-18
Download: https://twrp.me
Device Tree changelog: while the version seems to be minor this is a MAJOR change: I switched from Android-6.0 to Android-8.1, removing 5.1 support
Summary changelog:
Official TWRP now supports Oreo by default (decrypt, correct time)
This removes support for Lollipop bootloader stack - thats why the image size is almost just the half.
If you are still using an Lollipop / 5.1 bootloader stack (wth..?!) UPGRADE it - or 3.3.1-0 is the last supported for yours. You can always check the PREVIEW flavor for MM which is backwards compatible but do not expect any official builds for LP anymore.
you REALLY wanna now what else has changed?
it is way too much but here check it out and see what you have missed from not using a PREVIEW flavor ....
Latest Official release
twrp-3.3.1-0
Release date: 2019-05-22
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
Latest Official release
twrp-3.3.0-0
Release date: 2019-04-10
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/04/15/twrp-3.3.0-0-released.html
twrp-3.2.3-0
Release date: 2018-08-06
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.2.2-0 <--> twrp-3.2.3-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html
twrp-3.2.2-0
Release date: 2018-07-01
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.2.2-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
twrp-3.2.1-0
Release date: 2018-05-25
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.2.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-1 <--> twrp-3.2.1-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
twrp-3.1.1-1
Release date: 2017-06-21
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
Summary changelog:
decryption fixed (again) for CM/AOSP
twrp-3.0.2-1
Release date: 2017-06-15
Download: https://twrp.me/devices
Device Tree changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
Summary changelog:
LL supported again
Unification of h811 and h815
many bugfixes, speed and other improvements (pls check the above changelog links!)
Latest PREVIEW release
read more about PREVIEWS and the <flavor>'s in the OP (what they are and when to use)!
twrp-<version>-PREVIEW-<buildnumber>_g4_<flavor>
Status: stable
Release date: see leech server
Download: sfX leech server (same download for all G4's)
Kernel: preview builds compile the kernel on build automatically (official not) - so the kernel differ between official and preview
Device Tree changelogs:
MM flavor - NOTE: The support for the MM flavor has reached its END OF LIFE (2020-02-28)
N flavor
O flavor
P flavor
Previous builds
twrp-3.2.1-PREVIEW-116_g4_O (only O!)
Status: testing
Release date: 2018-03-28
Download: Download Page (same download for all G4's)
Device Tree changelog: O flavor
Summary changelog:
newest TITAN
switched kernel toolchain (same then TITAN uses)
decrypting O works (aoscp tested)
complete build on O sources (TWRP)
twrp-3.2.1-PREVIEW-109_g4_N (only N!)
Status: stable
Release date: 2018-03-17
Download: Download Page (same download for all G4's)
Device Tree changelog: N flavor
Summary changelog:
Decrypting STOCK N is working now!
twrp-3.2.1-PREVIEW-106_g4_<flavor>
Status: stable
Release date: 2018-03-15
Download: Download Page (same download for all G4's)
Device Tree changelog: MM flavor and N flavor
PREVIEW vs. OFFICIAL changelog: MM PREVIEW <--> latest official TWRP and N PREVIEW <--> latest official TWRP
twrp-3.2.0-PREVIEW-43_g4_<flavor>
Status: stable
Release date: 2017-12-07
Download: Download Page (same download for h811/h815)
Device Tree changelog:
<custom-m>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-6.0
<custom-n/stock>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-7.1
PREVIEW vs. OFFICIAL changelog:
<custom-mm>: this PREVIEW <--> twrp-3.2.0-0
<custom-n/stock>: this PREVIEW <--> twrp-3.2.0-0
Summary changelog:
<all>: replaced LLAMA kernel with TITAN (thx @kessaras for the kernel )
<all>: updated TWRP codebase to 3.2.0 (https://github.com/omnirom/android_bootable_recovery/compare/android-7.1...android-8.0)
<all>: removed legacy LP decryption support (it MAY still work though bc of the next line)
<all>: using new decryption support by TW_CRYPTO_USE_SYSTEM_VOLD ( https://github.com/omnirom/android_bootable_recovery/commit/71c6c50d0da1f32dd18a749797e88de2358c5ba1 )
This means in theory: decrypting stock and any other ROM should be much easier now.
<custom-n>: enabled debug when decrypting (will be disabled once all decrypting tests are done)
<stock>: builds are now based on 7.1 tree (like custom-n)
<custom-mm>: in some beta versions decrypt was broken which is now fixed again
<all>: fixed time (again)
<all>: from now on I will generate md5 hashes for all unofficial / PREVIEW twrp releases
twrp-3.1.1-BETA-g4-sfXbuild3
Status: stable (it's a BETA though)
Release date: 2017-06-20
Download: Download Page (same download for h811/h815)
Device Tree changelog: previous BETA <--> this BETA
BETA vs. STABLE changelog: this BETA <--> twrp-3.1.1-0
Summary changelog:
decryption fixed (again) for CM/AOSP
BETA-5 Build id #327 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-19
Download: Download Page (same download for h811/h815)
Device Tree changelog: build #317 <--> build #327
TWRP sources changelog: build #317 <--> build #327
first working unified TWRP version for both h811 and h815 in one build. That means:
from now on there will be 1 single download file which works for both devices.
factory reset in Android will do it's job now! That means:
using the factory reset hardware key combo will just open TWRP (as it is in all builds)
but when you do a factory reset in Android settings it will boot into TWRP and wipe now
Hint: This requires the ROM uses /grow as /misc partition! Example: CM supports this in CM14.1 since 15th of Dec 2016
Other ROMs may have to change their fstab to make this working for them
BETA-4 Build id #317 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-16
Device Tree changelog: build #285 <--> build #317
TWRP sources changelog: build #285 <--> build #317
fixing an issue with cmupdater preventing to upgrade
Using /grow as /misc because the CM devs preferring this (https://review.cyanogenmod.org/#/c/177122/)
BETA-3 Build id #285 (h811 + h815)
Status: stable (but cmupdater is broken here)
Release date: 2016-12-14
Device Tree changelog: build #186 <--> build #285
TWRP sources changelog: build #186 <--> build #285
first fully working version for the h811 device
governor=intelliactive, IO scheduler=sioplus, rhsize=1024. see twrp benchmark
adding /misc to support CM internal updater! Now cmupdater would work if the CM devs will enable it again (will work up to 5th of Dec CM 14 builds nevertheless. The internal cmupdater will prevent booting into recovery after that build date... Tested on h811 and h815.).
Ensuring that factory reset by the hardware key combo will not reset the device (proven on h811 and h815 that it will NOT wipe when open "factory reset" page with hardware key combo)!
Switched back to android-6.0 branch because bigbiff recommended that
BETA-2 Build id #186 (h815)
Status: stable
Release date: 2016-11-21
Device Tree changelog: build #162 <--> build #186
TWRP sources changelog: build #162 <--> build #186
Using FIOPS I/O scheduler
read_ahead_kb=2048
Build id #162 (h815)
Status: stable
Release date: 2016-09-12
Device Tree changelog: build #91 <--> build #162
TWRP sources changelog: build #91 <--> build #162
new: build on the latest 7.0 branch of TWRP
CRITICAL fix: bug when restoring EFS! (Due to an issue in the TWRP sources it was not possible to restore EFS which is fixed now)
fix: time was not correct for CM based ROMs
fix: time was not correct for STOCK based ROMs
new: double tap will awake device
fix: minor issue for bootdevice
fix: launch qseecomd on boot to avoid issues with decryption
fix: logfile messages now all in /tmp/recovery.log instead of cmd specifics
fix: removed /firmware from backup menu --> DO NOT TRY TO RESTORE ANY PREVIOUS /firmware BACKUP! You can restore it with LG Up if you do that by mistake
... for the rest and details checkout the changelog above
Build id #091
Status: abandoned
Release date: 2016-08-18 - Removed due to a bug in twrp sources. Pls see my post here
Device Tree changelog: TeamWin official <--> build #91
TWRP sources changelog: TeamWin official <--> build #91
initial public release
making decryption work
... for the rest and details checkout the changelog above
FAQ
Frequently Asked Questions (FAQ)
What's the meaning of decryption in terms of TWRP?
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it does not really matters in performance in all normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. Ok some users still believe that this is minimal diff is what they need but to be honest: The ONLY way to find an answer for yourself is testing on your own using the SAME ROM and same version! One time with encryption once without. Use the exact same ROM and use the exact same configuration like governors, custom kernels etc.
On the other hand you will get a minimum of security if you enable encryption but give access to everyone finding your lost phone if not!
So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is not permanent! Your data gets just decrypted for backing up nothing more nothing less.
[*]You talked about using IRC to get support. What is this and how can I use that?
Note: check the support topic as from now on there is also a Telegram group for that available.
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#twrp" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
[*]What is that "adb" thing??
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
I highly recommend to use FWUL to connect your device. Not for TWRP only but also for anything else adb/fastboot related.
What Logfiles have to be provided and how?
Two options are available:
Option A is the absolute minimum when reporting an error and it can be done by every user without installing anything or any special skills!! Reports without this minimal requirement will be ignored!
Option B is also very simple but you need to install ADB if not installed already. The steps are very easy and there is an easy installer available.
Keep in mind that if you have a problem and want that to be solved the more you can tell and the more you can provide the better it is. So choose your option wisely....
A) The absolute MINIMUM: recovery.log:
Start in TWRP and connect an USB cable to your device
Menu: Advanced
Menu: Copy Log
Click Home button and go to Menu: Mount
Ensure MTP is enabled (button at the bottom)
Open the file explorer on your PC and go to Sdcard
open the file "recovery.log" in a text editor (windows users: Wordpad)
copy the whole content and paste it on http://bpaste.net (choose a long duration in the drop down). After you pasted your log there a LINK WILL BE GENERATED!!! I NEED THAT URL !!!.
Here are 2 screenshots which should guide you in this:
paste the log file:
copy URL:
Report the link of that paste URL by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
B) But for THE BEST SUPPORT provide not recovery.log only but also dmesg by executing the following cmds on your PC:
Start in TWRP and connect an USB cable to your device. Then on your PC (requires ADB installed! Check FAQ #3 of this post!!):
adb shell
dmesg > /tmp/dmesg.txt
OPTIONAL (only when requested by me): logcat -d -b all > /tmp/logcat.txt
OPTIONAL (only when requested by me): adb pull /tmp/logcat.txt
OPTIONAL (only when requested by me): cat /proc/last_kmsg > /tmp/kmsg.txt
exit
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.txt
OPTIONAL (only when requested by me): adb pull /tmp/kmsg.txt
Open all logs one by one with a text editor like wordpad or similar and paste it here: http://paste.omnirom.org (do NOT paste all in one! Every single log should have a single paste URL)
If the logfile(s) are too big to get them uploaded on paste.omnirom.org use something like gists.github.com if you have a github account or zip it and upload it at www.filedropper.com
Report the link of that paste URLs by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
[*]What is required to get support?
Get IRC running (see FAQ 2)
Get adb running (see FAQ 3)
Collect logs (see FAQ 4)
Go to IRC and paste your problem together with the paste URLs you done before
If you can't see me on twrp or if there are any reasons why you may not get IRC running (serious? even not the webchat??!) answer to this thread and paste your URLs here
[*]Why is the time wrong in TWRP?
most important: use the latest TWRP (atm of writing it has to be the latest BETA 3.1.1 sfx-14). This has been fixed several times on our journey for different ROMs and their versions and should work for STOCK (up to N) and on any custom ROM now very well.
if you still encounter issues: set the time zone correctly in TWRP once. then reboot into TWRP and it should be still the correct time
if you still encounter issues: scroll up to FAQ #4 A) and pull the recovery log and attach it to your post.
For reference here the previous explanations (when using the latest TWRP no actions are required anymore!! even when switching between STOCK and custom ROMS !)
Before CM12.1:
Time setting was handled with the proprietary qcom time_daemon which was responsible to save a time offset of the qcom RTC (Real Time Clock). This time_daemon gets the time from the RTC and save the offset to the current "real" system time in either /data/time or /data/system/time. That means it SHOULD work out of the box for you but as you're reading this it may not.
Since CM12.1 and newer:
The proprietary time_daemon was completely replaced with an open-source alternative provided by sony: "timekeep".
The main principal is the same: the time gets read from the RTC and then gets not written to files in the file system but instead a persistent property is written (timekeep save) each time the time or timezone changes or when Android shuts down. This property is then read at the next boot again by timekeep (timekeep restore).
The handling of timekeep is fixed since build 127 of this twrp version / official 3.0.2-1 version so it should just work for you if you have that build running (or newer).
Stock ROMs:
Stock ROMs or stock based ones like Imperium ROM uses the proprietary qcom time_daemon. That means it SHOULD work out of the box for you but as you're reading this it may not.
When you had read the above and it states it SHOULD work for you but it doesn't:
Boot into twrp:
Menu Mount: select Data to get it mounted
On your PC:
adb shell rm /data/system/time/ats_2
adb shell rm /data/time/ats_2
adb shell rm /data/property/persist.sys.timeadjust
One of the above adb cmds may fail but that doesn't matters.
Now reboot into recovery again and the time should :fingers-crossed: be fine.
If the above give you NOT the correct time:
Please follow all steps of the above FAQ #5 and additionally also give an output of the following cmd while in twrp:
adb shell mount /data
adb shell ls -la /data/time /data/system/time
[*]Does this build supports F2FS?
Yes
[*] Why are some builds about ~50% smaller then other versions of twrp for these devices?
TWRP builds with more than 30 MB contain an uncompressed kernel image and support both bootloader versions : MM and LL
TWRP builds with about 16 MB contain a compressed kernel image and will run with MM bootloader only. As soon as I found out that this was the reason for not booting TWRP on LL devices I reverted the compression to support both again
btw the kernel is build with UBER tool chain
so the short answer is just "compression".
[*]Unlocking? Rooting?
official unlock (h811, h815 EUR) http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
unofficial unlock (any G4): https://bit.do/unlockg4
[*]Don't trust TWRP for EFS backups? Do you want to have an independent backup of EFS? Do you wanna restore EFS without TWRP?
Consider to use the brand new backup method even for locked devices! DLM Backup
words in blue are commands you have to type on your PC
boot into TWRP
connect usb cable
adb shell
Backup
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2
dd if=/dev/block/bootdevice/by-name/fsg of=/external_sd/fsg
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc
Restore
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/external_sd/modemst1 of=/dev/block/bootdevice/by-name/modemst1
dd if=/external_sd/modemst2 of=/dev/block/bootdevice/by-name/modemst2
dd if=/external_sd/misc of=/dev/block/bootdevice/by-name/misc
dd if=/external_sd/fsg of=/dev/block/bootdevice/by-name/fsg
[*]You can't unlock your screen after you encrypted your device?
First of all: this has absolutely nothing to do with TWRP but as I encrypt always and everything I encountered a problem after encrypting my device and I just want to share you my solution:
checkout the following tool if you have the same issue described there: http://forum.xda-developers.com/g4/development/tool-lock-screen-fix-encrypted-devices-t3499478
[*]How to open/start/boot into TWRP?
You have 2 options at least:
when Android is booted:
you can do "adb reboot recovery".
Besides that many custom ROMs have a special power option or just download one of the dozens apps letting you do this
via key combo:
The only valid and always working and supported way on getting with a hardware key combo(!) into twrp is using the factory reset screen.
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Any other key combo like vol up + power depends on the kernel of the ROM! So it may work or not. Factory reset will work always.
If you are interested on the background why the factory reset page cannot be bypassed read on here: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424/post72628311
For this you have to ensure that you have the latest twrp version really installed(!) because if twrp sits in recovery it will ignore the factory reset command when going through it.
Power down and pull out the battery. Do not forget to remove any USB cable.
Press power down and hold it down. Put battery back while keeping vol down pressed. Press power button and keep now both buttons pressed. When you see the LG logo the first time just release the power button for 1 second ( do not release vol down ) and then press power again and keep both pressed until you see the factory reset screen.
Once you see that screen just go through the steps like you would do a factory reset. If twrp is installed you will just open twrp without wiping any data. Again it is mandatory to have twrp installed otherwise it would really reset your device.
For the paranoid: If you want to be sure use "adb reboot recovery" when in android. When you see twrp all is fine but just do a full backup and then go through the factory reset first.
[*]What is a system IMAGE backup and why does it fail?
Using this new option is an ALTERNATIVE method to backup in opposite to the regular file based method. It is like a bit by bit backup of the COMPLETE partition which is the reason why it is much bigger as a regular backup.
So you likely will NEVER use the Image option or when you're a paranoid one only.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
user reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
So you may ask now why or when should I select this method? Never. So why is this option here? The main reason is TWRP in FIsH. I want to keep both device trees identical.
.
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
+1 for this question
I'm curious what that technical talk means as well!
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it doesn't matter in performance in normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. The ONLY way to find an answer is testing on your own using the SAME ROM and same version! Once with encryption once without.
On the other hand you will get a minimum of security if you enable it but give access to everyone finding your lost phone if not! So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is *not* permanent it is just decrypted for backing up nothing more nothing less.
Hope that answers your question
.
Sent from my LG-H815 using XDA Labs
ufocus said:
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
Click to expand...
Click to collapse
I think that is possible without problems. I check that.
checked:
its not such easy as stated in your commit link. we do not have "touchpanel" there so we need to check what else we could choose maybe those: https://github.com/CyanogenMod/andr...mmit/d3c0189ab7384d42906eea9d521c4d591a160c2f
edit 2:
changing /sys/devices/virtual/input/lge_touch/tap2wake --> 1 (as set in CM) has no effect in twrp.. Need further research..
edit 3:
ok got it. double tap will be added in the next build
.
Sent from my LG-H815 using XDA Labs
steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk
albuntu said:
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.
steadfaster said:
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.
Click to expand...
Click to collapse
I'm on CM13 and yes, the time and date are always correct. I know for sure because i often reboot with flight mode enabled.
Sent from my LG G4 using Tapatalk
steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
Now that was fast Thank you! Appreciate the effort. For now we can live with wrong date and time it's not that big of a deal.
I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM
HorstiG said:
I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM
View attachment 3852244
Click to expand...
Click to collapse
Please see the the comment of Dees_Troy and bigbiff (both main devs of TWRP):
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/178#issuecomment-35728685
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/238#issuecomment-28525937
--> Means the ROM have to save the time data and TWRP tries to read that. If the ROM do not save that time data TWRP can't know the time.
Well there is a flag for QCOM since some day:
https://github.com/TeamWin/android_...mits/8b9b9c5d869e57cb7857723592044028a8874f61
--> that one is set already in my build but it is still not working
I still looking through the code what the devs actually expecting maybe ... well lets see.
update:
ok so far I can say the following
The Qualcom Time Daemon (proprietary) need to be available in your ROM (e.g. not available in RR)
The time daemon has to run properly (it has to work actually)
The time daemon has to write into either /data/time/ats_* or /data/system/time/ats_*
If those are ok then TWRP will display the time correct. If not blame the ROM not TWRP..
.
I have 4 Files, but all without content.
It´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip
On my older Baby LG D290 the Time is OK
HorstiG said:
On my older Baby LG D290 the Time is OK
Click to expand...
Click to collapse
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
HorstiG said:
I have 4 Files, but all without content.
It�´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip
Click to expand...
Click to collapse
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Click to expand...
Click to collapse
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs
HorstiG said:
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
ok no I meant IRC channel thats much much better because it is a chat so much more responsive
but I want to investigate that further (I mean my nick says it all) - can you do the following when booted into Android and paste their results:
ls -la /dev/rtc0 /dev/rtc
hwclock -uw (<-- if this gives you an error let me know but continue with the next part)
ls -la /dev/rtc0 /dev/rtc (again)
Boot up in TWRP and paste the results of:
ls -la /dev/rtc0 /dev/rtc
If it is not the correct time in UTC do the above hwclock command again
reboot recovery (so reboot into twrp again)
let me know your results
I'm normally online daily so grab an IRC client like hexchat or pidgin and connect to the channel #twrp. you will see me there. If you do not want to install anything simply use the webchat here: http://webchat.freenode.net/?channels=twrp
.
I WILL BE POSTING THIS ROM TRY AT YOUR OWN RISK NOT MY ROM NOT MY DEVELOPMENT BRICKED PHONE NOT MY ISSUE SRY ( OPPO TOOLS HELP WITH BRICKED DEVICES )
Sang Nguyen
Sang Nguyen ADMINISTRATOR MEMBER BQT
Posts:119 Likes:86 Trophy Points:96
JOIN NOW10/05/16
Information Rom Hexagon Hexagon Rom was developed based on CyanogenMod With the combination of customization features from Slim , Omni , Travel , Aicp, DroidOS ... Brought to you a Custom ROM with many features customized, high stability, convergence of the latest Android essence encapsulated in your smartphone. After all these attempts are today DroidVn-Team will send to you the first Hexagon OnePlus device .. .The other devices will be updated in the coming days, respectively.
Team DroidVN sincere thanks to AOKP , Omni , Travel , AICP , The Muppest
We can not accomplish this rom without you.
- Droid Version: Stable (Stable) - Android Version: 6.0.1 MM - Kernel: 3.4.x - Community Development: Droidvn-Team - Deverloper: Sang Nguyen , Tuan Nguyen, Phuocbull , Nthoa.it - Forum support Forum: Droidvn.com - Source code: Github
: Changelog:
SPOILER: CHANGELOG
Installation Guide (you must ensure the implementation of all the steps below to process successfully installed , we will not be responsible for your phone case damaged SD card, Brick)
Download the ROM and GApps in the phone memory
We recommend using TWRP recovery, and the machine you have to root and custom recovery installed
Boot into recovery
Wipe Cache / System / Dalvik / Data ( No Internal SDcard format )
Install, select the ROM zip file
Next select the GApps zip
Reboot and enjoy. (Note the first boot time can take a while, you should be patient)
Note flash GApps bottom.
: Download:
: GApps:
: Screenshots:
Screenshot_20160623-164246.png Screenshot_20160623-164323.png Screenshot_20160623-170429.png Screenshot_20160623-170648.png Screenshot_20160623-170748.png Screenshot_20160623-171558.png Screenshot_20160623-171609.png Screenshot_20160623-171635.png Screenshot_20160624-120022.png Screenshot_20160625-152441.png
[url]https://mega.nz/#!0VJXHBAD[/url]
KEY- !G96FyEt7Ux8T8t6PPVPNjEsbdML99RN6nPwEPFJ-2I0
This rom comes with supersu already installed and dolby installed also it supports stock partition not sure about the others please test and find out on your own
storage
if you want a unified storage do the chinese storage partition once you have that set up with twrp follow these steps
1: flash rom
2:flash modem if you need to
3:flash cm13 unified storage patch from the cm14 thread ( also available on community.oppo)
4:flash gapps
5:flash any extra mods you might like fyi this rom comes with a built in super user and dolby atmos
give it time to load then check your storage it should say calculating storage then show a full unified partition
support lvm?
how about new lcd? anyone tried?
Code:
clxer said:
support lvm?
Click to expand...
Click to collapse
LVM not support
Lineage 15.1 for Xperia X Performance [Stock based]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock 41.3.A.2.149 before flashing this ROM.[
4. This ROM is suitable for dual and single model
5.VoLTE is supported, but you need to enable it on stock firmware at first./COLOR]
Downloads Links
LineageOS 15.1:
Unofficial: https://www.androidfilehost.com/?w=files&flid=307067
A special twrp recovery for this ROM:
https://www.androidfilehost.com/?fid=8889791610682924454
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 9.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
LineageOS addonsu for root access:
Download the addonsu for arm64: LineageOS Downloads / Extras
Flash the zip on a working Lineage installation (once)
Upon ROM updates, the addonsu is preserved
Reboot
About the builds:
Source: https://github.com/sony-msm8996
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Chippa_a
Everyone involved in working and testing
Contributors
Sjll, Olivier
ROM OS Version: 8.1
ROM Kernel: Linux 3.18.x
Version Information
Status: Stable
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: No
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: No
- SEPolicies: Permissive
Result
I tested the project you didn't test and I can test it once. Now I know that GPs and microSD are working
And I hope you will continue to optimize lineages OS based on sodp
LeafNic said:
I tested the project you didn't test and I can test it once. Now I know that GPs and microSD are working
And I hope you will continue to optimize lineages OS based on sodp
Click to expand...
Click to collapse
Thanks for feedback.
New version uploaded, it is stable now.
will you make los 17.1 for it?. your build make my device cool not like treble, i can cook eggs on it
um....btw , he is the one who maintain project treble on dora
correct me if i'm wrong
Thestardr said:
will you make los 17.1 for it?. your build make my device cool not like treble, i can cook eggs on it
Click to expand...
Click to collapse
LOL
amnesia1408 said:
um....btw , he is the one who maintain project treble on dora
correct me if i'm wrong
Click to expand...
Click to collapse
Yup.
Is there a guide to isntall this? I got the bootloader unlocked using the key generet with the IMEI from the sony website, but when I tried "fastboot boot recovery.img", the phone just booted up normally.
I then tried flashing the recovery.img, this was reported as succesful, but the phone still booted normally whenever i did "adb reboot recovery".
Right now I got it back to stock, with bootlaoder locked and 41.3.A.2.149 NOBA installed.
try to boot to recovery manually
turn off your phone
hold power+volume down to turn on your phone
it take time to enter recovery mode so be patient
amnesia1408 said:
try to boot to recovery manually
turn off your phone
hold power+volume down to turn on your phone
it take time to enter recovery mode so be patient
Click to expand...
Click to collapse
I tried that now. I can see the "Sony" logo on the screen for around 5 seconds, but then a very brief red flash and the phone reboots. This behavior repeats itself while holding power and volume down.
If I release any of the two buttons during the "Sony" logo, the phone boots the system normally.
you can try out recovery at the project treble pie thread , i think the fstab file is still same with this recovery , well i dont think it worth to try , it consume your time to reinstall the stock if it fail when installing the rom
good luck if you want to try that
MartinFierce said:
Is there a guide to isntall this? I got the bootloader unlocked using the key generet with the IMEI from the sony website, but when I tried "fastboot boot recovery.img", the phone just booted up normally.
I then tried flashing the recovery.img, this was reported as succesful, but the phone still booted normally whenever i did "adb reboot recovery".
Right now I got it back to stock, with bootlaoder locked and 41.3.A.2.149 NOBA installed.
Click to expand...
Click to collapse
some version of twrp dont work with this phone so it will boot to system instead of twrp, it dont care how many times you have tried. try using sjii twrp-Q, its support many roms
Hi, thanks for the continued development!
Can I flash this rom over the one based on SODP?
leandrox said:
Hi, thanks for the continued development!
Can I flash this rom over the one based on SODP?
Click to expand...
Click to collapse
you should flash 41.3.a.2.149 first and then install for original performance
edit: but why. sodp support gcam and more hyper performance
can someone give me a link download firmware 41.3.a.2.149 pls
Thestardr said:
you should flash 41.3.a.2.149 first and then install for original performance
edit: but why. sodp support gcam and more hyper performance
Click to expand...
Click to collapse
Thanks, yes, I will stay on the SODP based ROM.
SikeClaus said:
can someone give me a link download firmware 41.3.a.2.149 pls
Click to expand...
Click to collapse
you can download it on xperiasite.pl here
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Thestardr said:
you can download it on xperiasite.pl here
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Click to expand...
Click to collapse
Xperifirm always worked fine for me
Thestardr said:
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Click to expand...
Click to collapse
Fine here , you should choose the correct region
#OxygenOS #Q #Port #ROM #Miatoll
Oxygen OS 10.3.7 | Android 10
Updated: 19/12/20
#NeverSettle
Changelog:
- November security patch
- Switch to OnePlus vendor thermals
- MangoKernel : use 4.14.117 Oxygen
- Fixup some RIL stuff
- Switch back to miui vendor
- Zip : use Hybrid flasher, can flash in recovery & fastboot
- Some misc changes
Bugs:
- Face unlock
- Lift up display
- Some features inside OnePlus camera
- More? idk
Credits and thanks:
Everyone that contributed in porting OOS
My testers
And U
Notes:
- To fix cellular data not working after changing sim, make a new file named simfix inside /sdcard and hit reboot, not tested but it should work
- It takes time for recovery to flash the ROM, be patient. Fastboot flashing is always recommended tho.
- If you get any 3rd party camera issues try the JoyUI camfix, cuz i forgot to merge lol
- Don't use LOS recovery if you want to flash this ROM in recovery
By @henloboi
MOD EDIT: Links Removed
Download - Join MOD EDIT: Link Removed on telegram
"Download - Join MOD EDIT: Link Removed on telegram"
This is just silly and shouldn't be allowed on this forum.
razerphynx said:
"Download - Join MOD EDIT: Link Removed on telegram"
This is just silly and shouldn't be allowed on this forum.
Click to expand...
Click to collapse
It already got deleted once but for some reason he added it back https://forum.xda-developers.com/t/...-9-pro-9s-miatoll-recovery-flashable.4204947/
This should be removed
THREAD LOCKED
@JallaaD69 Please check your PM.
Regards,
shadowstep
Forum Moderator