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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, 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.
Important info:
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4
- Note: Warning! You are the only responsible of your actions, and especially of your use of your phone. Neither I, neither XDA, are responsible of your handling with your phone.
- Note: You must have unlock your bootloader on sony's page
- Note: You need to use the stock bootloader. If you switched to the Open Device Bootloader (D2203), please flash again the old bootloader. Here you have FTF file: (https://drive.google.com/file/d/0B07I-JdP5dQzSWs3SW1uYXVsWjg/view?usp=sharing). If you don’t remember the process, you can check it on Google.
Working
All
Almost working
Cameras are not fully working. You can take panorama pictures but no videos nor photos (with Snap app). In some other apps you can take them sometimes. In cameringo for example you can take everything. Fixed on V4!
Known issues
WiFi MAC address is a default address because TA is not being read yet. We are working to fix it. This only makes that some WiFi networks does not allow your phone to connect because another device with the same address is connected, but this is not usual so you shouldn't have problems with that. Fixed on V4!
Audio bugs:
Songs may pause randomly after some time and continue after some secs.
Some games might have a laggy audio problem (Pokémon Go for example).
Download
You have to download the latest version of boot.img, recovery.img and system.img or flashable zip from this link https://drive.google.com/drive/folders/0B07I-JdP5dQzM1FRbXY4bGt4VzQ?usp=sharing
For Google apps (Play Store, Google account...) go to http://opengapps.org/, choose Arm for Android 7.1 and select any variant you want. We recommend Pico variant as is the smalles one (you can choose stock if you want Pixel launcher).
Install
You need to install adb and fastboot. If you don’t know how to do that, click on the link down below.
https://forum.xda-developers.com/showthread.php?t=2588979
Then, in your file explorer, go to « This computer » and search for the file « adb ».
Next, put files in the folder « adb ». Hold shift and click (right click). Then click on « open terminal » or do « cd » (you need to find the location of your file « adb »).
Boot your phone in Bootloader/fastboot (this is the exact same thing but with different names depending on how you call it).
Before all, you have to start cleaning the device so do a wipe then:
In the terminal, type the command « fastboot devices »
You should see something like this for example :
Code:
CVH7N15B11004115 fastboot
If it isnt’t the case
go to Device Manager
Find your phone
Click on properties
Update the driver for your phone
Choose « Bootloader interface » and retry the command « fastboot device »
Now, you’ve done a big part of the work! You only have to type the following commands.
Commands
Code:
1. fastboot flash boot "name of boot".img
2. (Starting from V4 - 2020-01-23) fastboot flash FOTAKernel "name of recovery".img
[COLOR="SeaGreen"]3. Boot TWRP with Vol - and flash LineageOS zip[/COLOR]
[B][COLOR="Red"]IMPORTANT:[/COLOR] Only if Magisk was automatically installed after flashing LineageOS zip and after the first reboot the ROM is not booting:[/B] [COLOR="SeaGreen"]Flash again any boot.img with fastboot or TWRP (using "Install image" option)[/COLOR]
[COLOR="red"][STRIKE]fastboot –S 256M flash system "name of system".img[/STRIKE] (that was for v1 && v2 )[/COLOR]
You will boot into your new ROM.
IMPORTANT!
If your Xperia E3 model is D2202 or D2212 (3G-only single and dual SIM variants) you may need to flash an additional firmware zip in order to get SIM card working if it does not work after the first boot. Here you have the link:
https://drive.google.com/drive/folders/0B07I-JdP5dQzRG83U2d2aXBmUWM?usp=sharing
Note that there is a zip for each variant, but this is only to avoid confusion. Both are the same zip and you can flash any of them.
Extras
Now all you have to do is to flash the GAPPs in the recovery.
For Magisk go to https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
and download Magisk app and zip (ONLY FOR VERSIONS BEFORE V4: using the boot named Magisk) and its corresponding Magisk version.
Contributors
@rmnhg Ramón Hernández
@infus38 Thomas
@Konstantinosj77
@galaxyfreak
@adfad666
@vinay
@jerpelea
@Ｄｈｒｕｖ
@jpzex
@Nicklas Van Dam
@madcodez
Changelog
- note only last change will be post ( change log for v1 and v2 was remove )
New release 14/02/20 v4.1
Fixed a sensors bug introduced on V4. Now sensors should work as before.
New release 23/01/20 v4
Recovery is now independent from Boot partition! Now you should flash recovery image to FOTAKernel using fastboot or to "recovery" partition using TWRP. With this measure you can flash any Magisk version without waiting us to update boot.img.
Camera fully working now! Torch also works. The only thing you can't do is to enable Noise Reduction on Snap as it is not supported on Stock ROM
Bluetooth and WiFi addresses are now fine. They should be the same as the stock ones.
Compass may work better.
New release 06/01/18 v3
Tethering works now (in WiFi, BT and USB)
NFC works perfectly now
Now no user needs to flash additional firmware blobs This is not always working.
Camera working partially (I recommend you taking photos with panoramic mode and videos with other apps, like Instagram)
TWRP 3.2.1
Magisk v15.2 is now supported
Sony's framework is preinstalled, you are able to download Sony's Apps from Google Play
Safety net passed using Magisk+Magisk Hide
XDA:DevDB Information
LINEAGE-OS OMSv7, ROM for the Sony Xperia E3
Contributors
infus38, rmnhg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: V4.1
Stable Release Date: 2020-02-14
Created 2018-03-23
Last Updated 2020-02-14
Screenshots, do you have? And steal in development?
eladiocesar said:
Screenshots, do you have? And steal in development?
Click to expand...
Click to collapse
Yes i have screenshots i can not now post them the rom work and is very stable you Can try
When I give the 2nd command, a list of commands shows up. What to do?
Edit: Resolved by @infus38 Thomas
First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:
..
device dosn't boot only boot animation are show(D2202) please help.
edit-solved
priyesh9 said:
device dosn't boot only boot animation are show(D2202) please help .
Click to expand...
Click to collapse
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Edit now solved
UPDATE: now you have boot.img with latest TWRP included
Edit-Solved
Ali Haide 001 said:
First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps http://opengapps.org/ choos arm 7.1 pico and flash in recovery (you can choos stock if you want pixel luncher)
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them
infus38 said:
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager (If this does not work, wait for the next version of the boot.img it will have to include the root with magisk)
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps https://www.androidfilehost.com/?w=files&flid=171931&sort_by=date&sort_dir=DESC
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them
Click to expand...
Click to collapse
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:
Ali Haide 001 said:
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )
rmnhg said:
UPDATE: now you have boot.img with latest TWRP included
Click to expand...
Click to collapse
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
infus38 said:
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )
Click to expand...
Click to collapse
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.
Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.
Click to expand...
Click to collapse
Yes just flahs lates boot_twrp_root.img ??
Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
Click to expand...
Click to collapse
You're welcome ?. TWRP is in it's latest version (3.1.1). Material design and multi language.
infus38 said:
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Click to expand...
Click to collapse
edit -solved
I was able to flash this ROM. I followed the instructions stated above but my d2203 was just stock at the LOS boot logo. I don't know what I did wrong. I came from stock KitKat rom before I flashed this. If that helps. HELP PLS! I really wanna try this ROM so badly
thanks @infus38 Thomas for helping me solve the problem
Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.
infus38 said:
Yes just flahs lates boot_twrp_root.img
Click to expand...
Click to collapse
Hey,One More Thing-
1-Do I Need To Flash This ROM above Stock ROM Or It Does Not Matter Cause I Am On CM 11 Unofficial Flamingo?
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
Ｄｈｒｕｖ said:
Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.
Click to expand...
Click to collapse
So,You Have Flashed This ROM.
How Is The Battery Life?
Can You tell Me What are The Features In This ROM (By Features I mean The Features Which are in cm Roms Like Center Clock,Privacy Guard,Performance Profile,Etc)?
Is Substratum Theme Manager Working Fine?
Thanks In Advance.
{
"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"
}
.
Screenshots attached below.
TeamWin Touch Recovery for BLU Tank Extreme Pro
Code:
* [U][B]Disclaimer[/B][/U]
* 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Older Version
CHANGELOG for 3.1.1-0:
TWRP 3.1.1 is Out, Brings Minor Fixes
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
FEATURES
Backup & Restore fully functional
Micro SDcard and USB OTG storage support
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Full SELinux support
Built with android-7.0 TWRP tree
CHANGELOG for 3.2.0-0:
TWRP 3.2.0 is now out
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
TWRP 3.2.2-0 brings ADB fixes and improvements to OTA updates
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
TWRP 3.2.3-0 is out now for most currently supported devices.
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
BUGS:
MTP NOT Recognize Driver--So No mtp connection-- work-around for this now, is to use "mount as USB drive", this will allow similar function as MTP, but only for your micro-SDcard
SUPPORT: Post your questions below. I'll answer whenever I get time.
INSTALLATION
Most devices can be updated quickly and easily within TWRP if you already have version 3.x.y-z or higher installed
1) Download the latest version from DOWNLOAD TAB
2) Copy that file to your sdcard
3) Reboot to TWRP
4) Hit INSTALL and tap the "Images..." button in the lower right
5) Browse to the location of the TWRP image (recovery.img) on your device and select it
6) Select RECOVERY from the PARTITION list and swipe to flash
7) Go to Menu: Reboot recovery
If First time install
You can install with spft as described in following link BUT FIRST NEED unlock bootloader.
Instructions for Flash stock recovery or Custom recovery MEDIATEK devices only
You can also install with fastboot commands after unlocking bootloader.
****UNLOCKING BOOTLOADER WILL CAUSE WARNING ON SCREEN WHEN POWERING ON****
****WARNING WILL PAUSE THE BOOT PROCESS FOR % SECOND DELAY , Not big problem****
BOOTLOADER UNLOCK
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
RECOVERY INSTALL
1. make sure developer options is enabled
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the 3.2.0 version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/twrp-3.2.0-recovery.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
adb reboot bootloader
fastboot flash recovery Desktop/twrp-3.2.0-recovery.img
fastboot boot Desktop/twrp-3.2.0-recovery.img
adb wait-for-device
adb reboot recovery
ROOT
If your device haven't ROOT:
Thanks to @Chainfire for the file!
Rooting instructions: put the SuperSu...zip on sdcard. Go to TWRP and tap INSTALL. Search the zip file and select. Swipe to install. Reboot system.
Dowload: SuperSU V2.82
DOWNLOADS In Download Tab
SCATTER File
Stock boot ----- Stock recovery
TWRP 3.1.1 ------ TWRP 3.2.0 ------ TWPR 3.2.1 ------ TWPR 3.2.2-0 (based in stock V7.0.04.04_GENERIC 24-05-2018)
-----Added--TWRP 3.2.2-0(repacked)Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.
TWRP 3.2.3-0 [Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.] (based in stock V7.0.04.05_GENERIC 06-08-2018) download in post#2
Note:
After TWRP3.2.2 the partitions for the backup save have been modified to: /dev/block/platform/mtk-msdc.0/by-name/
So if you have a version older than TWRP3.2.2 you should copy the
Root [Internal Storage or MicroSD] / TWRP/ BACKUPS / VCIBIZMR7HT8GES8 / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
folder to the new one folder
Root [Internal Storage or MicroSD] / TWRP / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
of the version TWRP3.2.2 or last.
We've added the partition for internal storage if you want to create a backup of it. But keep in mind that the more files there are in the internal storage, the larger the size of the backup made and this will depend on your choice and how you can save it to other larger storage capacity.
So be more careful!
Contributors
@lopestom
@Dees_Troy
@teamwin
@vampirefo
Version Information
Status: Beta
Current Beta Version: 3.2.3-0-20181013
Beta Release Date: 2017-12-24
XDA:DevDB Information
Tank Xtreme Pro Recovery, Tool/Utility for all devices (see above for details)
Contributors
mrmazak, lopestom, vampirefo
Version Information
Status: Beta
Created 2017-12-08
Last Updated 2018-10-13
Instructions to unlock and relock bootloader
Instructions to unlock and relock bootloader soo... :silly:
https://youtu.be/5ZVW-XzPCXE
https://youtu.be/Zf6hMqGbC_4
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
vampirefo said:
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
mrmazak said:
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
Click to expand...
Click to collapse
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Sent from my Tank Xtreme Pro using Tapatalk
vampirefo said:
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Click to expand...
Click to collapse
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
lopestom said:
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
Click to expand...
Click to collapse
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
vampirefo said:
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I assume you already looked, but, the recovery log shows mtp error , over and over again.
Code:
E:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 22
pretty sure it happens with all versions
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
mrmazak said:
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
Click to expand...
Click to collapse
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
vampirefo said:
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
Click to expand...
Click to collapse
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
mrmazak said:
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
Click to expand...
Click to collapse
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
vampirefo said:
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
Click to expand...
Click to collapse
thanks, is it ok to add this version to the downloads of this thread?
mrmazak said:
thanks, is it ok to add this version to the downloads of this thread?
Click to expand...
Click to collapse
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
vampirefo said:
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I've added you as contributor and added your version, with the fstab that has system_image and also cache enabled (because of an error message in recovery.log that stated could not mount cache)
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
gabmika69 said:
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
Click to expand...
Click to collapse
No!
Each device should have the own Custom Recovery.
Sent from my BLUBOO Xtouch using XDA Labs
Please HELP!
Was hung on boot with TWRP installed. Fixed the problem by installing SuperSU to unlock the bootloader. No help needed.
{
"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 Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:
Micromax Canvas 5 E481
Blu Life One X
Myphone 36
Qmobilez10
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.
*/
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
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)
Not working:
XDA:DevDB Information
madOS_O_FEVER, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, twrp
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-03-19
Created 2018-03-13
Last Updated 2018-03-22
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Ensure you are running Wiko Fever Android 6 already (also/especially when your device is not wiko fever, but a clone). If you are not, please update to it, before continuing here (replace the preloader from the wiko rom with your stock one, then use 'firmware upgrade' mode in sp flashtool. NEVER use 'format all + download')
Extra steps, if you are on blu life one x:
https://forum.xda-developers.com/showpost.php?p=76003104&postcount=81
0.3) Download “twrp_wiko_fever_oreo.img“: [url]http://www.mediafire.com/file/e96x8ltlyka392e/twrp_wiko_fever_oreo.img[/URL]
0.4) Download “madOS_8.1.0_fever_2018xxyy.zip“ [url]https://www.facebook.com/MediatekAndroidDevelopers/[/URL]
0.5) Optional, Download “Google Apps (aka Gapps)“: [url]http://opengapps.org/[/URL]. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Unlock bootloader (if not done already):
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking” and “USB debugging” (if not enabled already), and choose to alollow usb debugging in the popping up window.
1.2) Boot the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
2.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_wiko_fever_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
2.1b) Boot to your current TWRP. Choose install --> image, and select “twrp_wiko_fever_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
3) Install
3.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
3.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_fever_2018xxyy.zip“ and the Google Apps to your phone.
3.2) Go to "Wipe", and directly slide the slider to the right.
3.3) Get back to main menu with the "back" button
3.4) Go to "Install" and hit “madOS_8.1.0_fever_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
3.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
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 for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
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: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
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)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
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 Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
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/pico
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.
Pure Nexus
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...
Changelog 19th March 2018:
fixed offline charging
fixed proximity and light sensor
fixed applying smartwake settings after reboot
Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used
Thank u so much sir...we owe you?
superdragonpt said:
Android Oreo released
https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804
Click to expand...
Click to collapse
superdragonpt said:
The ROM was made using an Wiko device in the bring up
I know very well this TINNO devices, that are rebranded to many OEMs
In case of baseband (ie: BLU,Qmobile, MMX, you should use your stock baseband modem and place it under vendor/etc)
Cheers
PS: can you, that have other clones ( non-wiko) send us your working baseband?
(This way, we could perhaps just made an flashable zip for baseband or so)
Click to expand...
Click to collapse
Here is firmware folder(baseband) from Life One X with MM update.
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
mrmazak said:
Here is firmware folder(baseband) from Life One X with MM update.
Click to expand...
Click to collapse
FERRARI81 said:
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
Click to expand...
Click to collapse
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
superdragonpt said:
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
So the sensor.lib from Blu?
I will pull it and share.
superdragonpt said:
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
FERRARI81 said:
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
Click to expand...
Click to collapse
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
I am away from my LOX now and for few days , so cant give direct test of light sensor.
attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.
I believe on oreo they go into /vendor/
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
mrmazak said:
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
Click to expand...
Click to collapse
It doesn't work in call too : the screen is always on.
QUIZILLA said:
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
Click to expand...
Click to collapse
Please remove the quote of the whole FAQ. This is totally useless to ask your question...
You need to flash wiko mm rom first
FERRARI81 said:
It doesn't work in call too : the screen is always on.
Click to expand...
Click to collapse
I'll check it today
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Rikadoo said:
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Click to expand...
Click to collapse
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.
If I copy the ROM on the SD card. Can I then install?
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
Code:
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
One and more questions,....
1. Our bootloader is blocked or already unlocked?
2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?
3 if isn't locked, how I install a custom recovery like twrp manager?
4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?
5 at the end, from twrp can I flash the ROM Oreo?
AHH , last question, can I flash this ROM from my phone with Android MM?
mrmazak said:
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
Click to expand...
Click to collapse
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us
{
"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"
}
A special thanks to @EmanuelCN for work hardly on Device Tree, Kernel and Recovery, without it this Rom wouldn't be possible.
ABOUT LINEAGE:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
• Android OS version: 13.0 / 12.1(A12L)
• Android Release: android-13.0.0_r8 / android-12.1.0_r22
• Build Release date: 2022-10-15
• Security patch: October 5, 2022
• Build author/Device Maintainer: @DanCS1995
• Kernel version/Author: Linux 4.9.235-N0kernel+ by @EmanuelCN
• Device: LG G7 ThinQ
• Device codename: Judyln
DOWNLOAD:
LineageOS 20.0 (Android 13.0) October 5
LineageOS 19.1 (Android 12.1) October 5
OrangeFox
fastboot-tools.zip
fastboot-driver.zip
fix-fastboot.zip (You'll may need this)
ABOUT GAPPS:
Does this Rom come with GAPPS?
No, it doesn't. It means you'll not have "Google Play Store" app or any other Google related service or application in it.
If i wanna use it, wich one should i use?
Make sure to flash the right one that matches to your current Android version, AVOID Stock packages, and the ones that contains "Pixel Launcher" in it, it seams conflicts with Lineage Stock Launcher, and it will give you black screen.
For Lineage 19.1 ONLY!!!
For sure the better one seams to be the one that Lineage recomends you, that you can find it right here in Google Apps | LineageOS Wiki
CHANGELOG 15-10-2022:
• October 5, 2022 Security Patch.
• Whatsapp audio call issues now gone.
• No more "Internal Error" message.
BUGS:
• VoLTE (Will never work on custom roms on LG phones)
• 10 bit video recording (Watching content in 10 bit works, you just cant record video in 10 bit format).
• You tell me!
QUICK FASTBOOT-DRIVER GUIDE INSTALLATION:
How to install:
1. Extract the fastboot-driver.zip.
2. Open device manager
3. Click right on " Android " it should have a yellow warning icon, press on update driver
4. Select browse my computer then press on let me pick from a list of available drivers
5. Press on Have disk and then go to where you have extracted the zip file and select android_winusb.inf
6. Done.
IF YOU FACE SOME FASTBOOT ISSUES DOWNLOAD FIX-FASTBOOT ZIP :
Instructions: Copy it in main directory (usually in C: drive) and run it as administrator, problem solved.
ORANGEFOX GUIDE:
If you have acces to fastboot, download fastboot-driver.zip and fastboot-tools.zip for the tools necessary to boot ofox.
Open the CMD and use the following command to boot ofox:
Code:
fastboot boot ofox-metadata.img
If you don't have access to fastboot, enter in 9008 mode, open qfil and load ofox image on boot_a and boot_b then force reboot (hold volume - and power button for 10s), after it reboots it will get you automatly in ofox.
DISCLAIMER FLASHING OFOX IN QFIL WILL LEAD IN YOUR ROM NOT BOOTING AS LG G7 IS AN A/B DEVICE WHICH MEANS IT DOESN'T HAVE A RECOVERY PARTITION, BOOT IMAGE IS MANDATORY FOR YOUR PHONE TO BOOT, FLASHING OFOX USING QFIL ITS ONLY FOR YOU TO BE ABLE TO FLASH A CUSTOM ROM AS IT OVERWRITES THE BOOT IMAGE WITH THE CERTAIN ROM'S ONE.
INSTALLATION
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
"ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model"
CLEAN FLASH : (If on A11/A12/A12L based rom other than Lineage 19.1)
1. Boot in OFOX metadata;
2. Format Data (Press on the recycle bin icon —-> format data ——> type yes);
3. FROM HERE YOU CAN CHOOSE BETWEEN 2 METHODS TO FLASH:
3.1. USING ADB SIDELOAD: 3.1.1. Press on "back" and flash the rom using adb sideload (Go to 3 lines in the bottom right corner, choose "ADB Sideload", Then "Swipe-->", open the cmd from adb tools folder in computer, then type "adb sideload", hit "Enter", then < drag and drop the zip over the cmd>); 3.1.2. Flash ofox zip the same way through adb sideload, it will automatically reboot to ofox after flashing is done; 3.1.3. Flash gapps; (Only if the rom does not contain gapps); 3.1.4. Flash magisk (Optional);
3.2. OR IF YOU HAVE A MICROSD CARD, YOU CAN FOLLOW THIS: 3.2.1. Move the rom and ofox, and gapps(if you will use) zip file into your microsdcard; 3.2.2. Press on "/sdcard" area and choose "Micro SDCard", navigate straight into your rom zip file, then press on it, then "swipe ---->", it will start flashing it; 3.2.3. After flash the rom, locate your ofox zip file and flash it as you did with the rom; 3.2.4. Flash gapps; (If you want); 3.2.5. Flash Magisk (Optional);
4. Change filesystem to f2fs (Go to 3 lines in bottom right corner ----> manage partitions ----> select data -----> change fs ------> f2fs);
5. Reboot.
DIRTY FLASH/UPGRADE ROM : (If you are already on Lineage 19.1)
• Boot in OFOX metadata;
• Flash the rom zip;
• Flash ofox zip, it will automatically reboot the phone to ofox after the flashing is done;
• Flash gapps (ONLY IF THE ROM IS WITH GAPPS ALREADY, MAKE SURE TO FLASH THE SAME ONE);
• Flash magisk (Optional);
Sources and Documentation
• ROM Source Code
• Kernel Source
Created 2022-05-24
Last Updated 2022-10-15
Screenshots:
Can the call be made? (Sim)
buymoney said:
Can the call be made? (Sim)
Click to expand...
Click to collapse
yes
fzdfdzff
Will 30E AWM work or do I need to reflash to 30D?
debianmain1 said:
Will 30E AWM work or do I need to reflash to 30D?
Click to expand...
Click to collapse
You can try with 30E AWM
deleted
Would it pass safetynet with microg, zygisk etc? I've heard ungoogled experience improved a lot recently
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
I also can boot to firmware update mode only and cant boot to edl...
09mysh said:
Would it pass safetynet with microg, zygisk etc? I've heard ungoogled experience improved a lot recently
Click to expand...
Click to collapse
I'm not familiar with microg, sorry
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
You need to get the boot_a.img and dtbo_a.img from the kdz stock rom a10 file and you can try flashing it in both boot_a and boot_b, dtbo_a and dtbo_b in qfil, this might fix it. ANd edl is still there, you need to try a fill more, and you will do it
XScorpionX72YT said:
So I Accidently flash ofox to boot a/b with qfil and now my phone won't boot. Now the screen just show
"Your device has failed a routine safety check and will not boot." Is there a way to fix my phone so I can boot it back?
Click to expand...
Click to collapse
I have also faced that issue. in my case, only edl mode was working. I followed the following steps & it worked for me. You should give it a try.
[Guide - HOW TO] Recover LG G7 (or other newer LG phones) from EDL or 9008 mode.
****** Unbrick all LG G7 models ****** ********** This guide has updated into two methods ********** (i). Recover from any boot problem to system or download mode.(which is defined below) This...
forum.xda-developers.com
XScorpionX72YT said:
I also can boot to firmware update mode only and cant boot to edl...
Click to expand...
Click to collapse
go over to the following link :
[Guide - HOW TO] Recover LG G7 (or other newer LG phones) from EDL or 9008 mode.
****** Unbrick all LG G7 models ****** ********** This guide has updated into two methods ********** (i). Recover from any boot problem to system or download mode.(which is defined below) This...
forum.xda-developers.com
Is there any way to enable VoLte on custom ROMs on LG G7?
sandip999 said:
Is there any way to enable VoLte on custom ROMs on LG G7?
Click to expand...
Click to collapse
sadly not, even if you just do a crosflash with another stock rom that isnt from your region, you cant use VoLTE, LG's fault
Hi,
I want to put this Lineage 19 rom on my G7. Can you help me please? My G7 is LM-G710EM, bootloader is unlocked. Its running LG's android 10 up to 01/11/2020 (that appears to be my final update possible - though I thought there was one in 2021?? - no available updates showing there now anyway)
1. (very noob question) when we say 'stock' do we mean just 'what came with the phone, and its subsequent updates?' As in, we didn't install any roms or recovery at this point. Is that right? Thats what i have right now. UK phone.
2. My firmware is V30h-EUR-XX, in this thread it says I need: "ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model" - So do I need to find and install the 30F EM firmware? Where can I find the files and instructions please? Is it here: https://lg-firmwares.com/lg-lmg710em-firmwares/ ? ...Or is my V30h ok without this as its newer firmware?
**KEY QUESTION**
3. Could someone please outline for me the 'roadmap' for getting my G7 from: LG A10 -- to ---> L19
(Please correct / advise below)
1. use ofox to replace firmware 30H with 30F
2. use ofox to install L19 over existing LG A10
Is that right? ...or are there steps missing? e.g. I need to install x, then do y, ... and then install L19, or something like that?
Very grateful for any help you can give!
I am a noob but I had some success already putting cyanogen / lineage roms on old devices:
amazon kindle fire, my old HTC oneX, Samsung Galaxy Trend, LG G4 ...all still working fine ;-) ...thanks to XDA.
(I might not be able to reply straight away - work hours - but I'll try to get back asap)
Many Thanks,
tommy_brock said:
Hi,
I want to put this Lineage 19 rom on my G7. Can you help me please? My G7 is LM-G710EM, bootloader is unlocked. Its running LG's android 10 up to 01/11/2020 (that appears to be my final update possible - though I thought there was one in 2021?? - no available updates showing there now anyway)
1. (very noob question) when we say 'stock' do we mean just 'what came with the phone, and its subsequent updates?' As in, we didn't install any roms or recovery at this point. Is that right? Thats what i have right now. UK phone.
2. My firmware is V30h-EUR-XX, in this thread it says I need: "ROM Firmware Required: Must be on 30F EM, 30D EMW/EAW/AWM, 30D EMW for N model" - So do I need to find and install the 30F EM firmware? Where can I find the files and instructions please? Is it here: https://lg-firmwares.com/lg-lmg710em-firmwares/ ? ...Or is my V30h ok without this as its newer firmware?
**KEY QUESTION**
3. Could someone please outline for me the 'roadmap' for getting my G7 from: LG A10 -- to ---> L19
(Please correct / advise below)
1. use ofox to replace firmware 30H with 30F
2. use ofox to install L19 over existing LG A10
Is that right? ...or are there steps missing? e.g. I need to install x, then do y, ... and then install L19, or something like that?
Very grateful for any help you can give!
I am a noob but I had some success already putting cyanogen / lineage roms on old devices:
amazon kindle fire, my old HTC oneX, Samsung Galaxy Trend, LG G4 ...all still working fine ;-) ...thanks to XDA.
(I might not be able to reply straight away - work hours - but I'll try to get back asap)
Many Thanks,
Click to expand...
Click to collapse
Hey, you are fine with your 30H firmware, you should have no problems with it.
Anyway, to change firmware you don't use ofox, you use LGUP
the guide you can find on this thread
Cross-Flash Oreo or Pie firmwares for all LG G7, G7+ dual sim Thinq except t-mobile
Once in ofox you can do from "CLEAN FLASH" steps of this guide
DanCS1995 said:
Hey, you are fine with your 30H firmware, you should have no problems with it.
Anyway, to change firmware you don't use ofox, you use LGUP
the guide you can find on this thread
Cross-Flash Oreo or Pie firmwares for all LG G7, G7+ dual sim Thinq except t-mobile
Once in ofox you can do from "CLEAN FLASH" steps of this guide
Click to expand...
Click to collapse
Hi,
Thanks so much for your reply.
I will not try to flash firmware as you think mine will be OK, but I will check out the linked information you gave for my own understanding.
I will use ofox and follow the 'clean flash' guide from here, as you advise.
That's great! Now I have a plan for action
I will try this over the next couple of days.
Many thanks,
Success!!
Thanks for your help, I have L19 running on my G7 now. the install was painless! all seems good and working. I'm just trying it out, but so far, smooth. It is really nice to have something so up to date running on the phone. also so clean and simple, without all the crud the original system had. a huge improvement.
I have some questions,
- After reboot, trebuchet gives me an Android System message: 'There's an internal problem with your device. Contact your manufacturer for details'
...after I dismiss it, I don't see it again. Have you seen this message? It is too cryptic for me to troubleshoot, but it doesnt seem to be causing a problem (as yet....?)
- Android System Trust Security throws up 2 alerts: This build was signed with public keys ; SELinux is not enforcing, your security has been weakened
...I'm guessing these are ok?
- In the Lineage camera app, the wide camera does not function (only main and front present).
I already put Open Camera app on there, which recognises all three cameras, and gave me great results before this on the G7, so I use Open Camera anyway.
- Can anyone recommend a GCam build for this rom? even better if its older and I don't have to root and do the 'buffer fix' stuff.
If anyone could advise, That would be great thank you!
Cheers,