{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for ZUK Z2 Pro (z2_row).
This is an official recovery support thread.
Known Issues
MTP broken in 3.3.0 and newer builds because of a TWRP issue with 4.4 kernel (you can still use adb push and adb sideload)
Requirements
Unlocked bootloader
Common sense and a Z2 Pro
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial z2_plus TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
cosmedd for his work on the TWRP tree for z2_row
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.
gg
*Insert some random thx sentence*
I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?
robert_b said:
I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?
Click to expand...
Click to collapse
As first because this has the factory mounted as vendor support instead of factory renamed as vendor. If you're already using a build with this support and you downloaded it recently it means that the build is the exact same as this one. I created a thread so that things can get out of Telegram only and also because soon it'll become official (the old one is deprecated pretty much)
Thread updated with the official tag and a new official build on the TWRP.me website. Enjoy
Encryption with latest AEX is not working.
rower19 said:
Encryption with latest AEX is not working.
Click to expand...
Click to collapse
What do you mean with "is not working"? What happens when you try to encrypt?
DD3Boh said:
What do you mean with "is not working"? What happens when you try to encrypt?
Click to expand...
Click to collapse
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Hi, sorry for the late answer. Can you pm me on telegram so that we can discuss the issue and I can eventually send you some builds to test? t.me/DD3boh
Thank you!
rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Checked with @DD3Boh and decryption for pie is working in a test build. He gonna push the new version after some more testing.
But be patient, we will be finally able to encrypt our device and decrypt it in twrp.
Thanks to him,
G0r3t3x
TWRP 3.3.0 just got released
Encryption was fixed, although mtp is broken because of 4.4 kernel (which is a must for encryption)
Instead of mtp you can just use adb push to push files to the internal memory, or either adb sideload <package path> to flash them directly without transferring to the internal storage (works only after having enabled adb sideload in the advanced TWRP tab)
Download link in the first post
Hi, thanks for your work.
I've tried to reinstall baseband but log says it's not installing nothing. Using twrp 3.3.0, i'm on ArrowOS.
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Perfectooo :good:
..btw: what about MTP? ..it works now?
satmaster said:
Perfectooo :good:
..btw: what about MTP? ..it works now?
Click to expand...
Click to collapse
It doesn't work on official builds for some reasons, so I had to disable it
I could though make a build locally where for some reasons it should work fine
I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.
lunloon said:
I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.
Click to expand...
Click to collapse
I tried USB-OTG and it worked. Thankfully.
Can't make any sense out of the driver game.
Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.
Dolour said:
Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.
Click to expand...
Click to collapse
Probably you don't know why I even switched to 4.4 kernel, which is because 3.18 kernel in TWRP breaks decryption, which is quite an important thing.
Anyway I can build TWRP locally and send a build as that will somehow have mtp and USB in general working.
Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
Main Highlights
✪ MTP support
✪ Can flash stock os Images
✪ Backup/restore works with any os
✪ Restore your old twrp backup
✪ Optimized and faster
✪ Build On A29 Pre Built Kernel By Realme
✪ Full compatible with color os
ScreenShots
Download Link:
https://mega.nz/#!5gYnjQSB!YhC_ZTHuopwwP50LxTvJ1VOq4zYSfG0LAudWr6gatUA
Code:
Bugs
:GSI Flashing Has Some Issues
:If You Finds Any Other Bug Then Report Me
Credits;
AnuragRai(Developer)
Hamza(Tester)
RK(Tester)
Jatin(Tester)
MKS(RM2p Dev,Always Supported Me)
And Whole Realme Tester Team
XDA:DevDB Information
TWRP[UNOFFICAL]-BETA-BUILD-[12-03-2019], Tool/Utility for the Oppo Realme 1
Contributors
anurag rai, hamza
Version Information
Status: Beta
Current Beta Version: 01
Beta Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
Flashing Guide
Code:
[CENTER]
:adb reboot bootloader
:fastboot flash recovery recoveryname.img
:reboot phone manually ,not from fastboot
:After phone boots up,power off it
:Press Power Button+Volume UP &Down For Approx 20 seconds
:After You Are Inside Of Twrp,do this
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Reserved
Thankyou bro..
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
anabhi said:
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
Click to expand...
Click to collapse
Bro can you help me with fixing reboot to recovery issue
anurag rai said:
Flashing Guide
Code:
[CENTER]
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Click to expand...
Click to collapse
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
It's Working ! Thanks Alot Mate.:victory:
awesome work bro.. thnks a lot u r too fast..
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Awesome man!??
svsexodia said:
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Click to expand...
Click to collapse
Yes you can
manavkush said:
Flashing Guide
Caution
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
Click to expand...
Click to collapse
Charge it bro
Realme 1 - Treble Rom
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
johndoe5 said:
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
Click to expand...
Click to collapse
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
It's_Shawn said:
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
Click to expand...
Click to collapse
Which TWRP did you use?
And where can I find the stock firmware?
johndoe5 said:
Which TWRP did you use?
And where can I find the stock firmware?
Click to expand...
Click to collapse
That Time I Didn't Use Any Recovery,I Used Fastboot Commands
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
5s4rnv33r said:
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
vikas2316 said:
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
Click to expand...
Click to collapse
Updating OS will remove root but will it also remove TWRP ???
One more question I followed all the steps correctly (including wiping data) but from TWRP I can't mount DATA.
---------- Post added at 10:01 PM ---------- Previous post was at 09:13 PM ----------
After wiping data if I just reboot to TWRP recovery then I can mount the DATA but once I have started the phone and set it up then again I boot into TWRP recovery and when I try to mount DATA I am not able to do so. Can't mount /data invalid argument. Please suggest something.
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
All function in a normal TWRP
Multi-language support
Supports MTP
Support decrypt /data!
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery recovery.img" in command line
5. Reboot and enjoy it
Download:
https://drive.google.com/uc?id=1rp_cgVuk6fsRybN0wDoOTbt_Pc-vOiHx&export=download
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thelazyindian/android_device_xiaomi_lavender-twrp
Note:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
When you flash twrp for the first time in MIUI you need to goto Wipe > Format Data otherwise you won't be able to boot to system as it will ask for password.
GAPPS FIX: In TWRP, goto Mount > system_root and try reflashing.
FAQ:
How is it different from other TWRPs available for lavender ?
This build uses standalone decryption which is better than the recoveries using vold decrypt as vold decrypt will fail if system ROM is corrupt or wiped
Credits:
Huge thanks to @abhishek987 and @vasishath for helping
@tufadorin @faraz shafi (For testing)
Reserved
Work fine with encryption
This is working with Global Variant ? greatz ...
It works well. Just one detail. You can not see the clock, because it appears in the same place as the camera.
Thank you for everything.
Just 5 more days left to test this ?
Can you install official miui ota zip after installing twrp and magisk?
Would it brick the device?
Nice built.. I think official build arrives soon
strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.
vkmcondor said:
Can you install official miui ota zip after installing twrp and magisk?
Would it brick the device?
Click to expand...
Click to collapse
It won't brick the device, but no you can't install them.
The update will just fail and reboot you back into MIUI. Everything working as usual.
If you want TWRP/Magisk installed and get updates then you'll have to manually download the 'Recovery ROM' to the update you want to update to. Then flash it in TWRP like you would a custom ROM.
You'll want to reinstall Magisk after you flash the Recovery ROM to get root back.
TWRP remains intact
Enddo said:
It won't brick the device, but no you can't install them.
The update will just fail and reboot you back into MIUI. Everything working as usual.
If you want TWRP/Magisk installed and get updates then you'll have to manually download the 'Recovery ROM' to the update you want to update to. Then flash it in TWRP like you would a custom ROM.
You'll want to reinstall Magisk after you flash the Recovery ROM to get root back.
TWRP remains intact
Click to expand...
Click to collapse
Do I need to format or wipe data?
great work, just need a few days to unlock my bootloader and try this one
Diniodoc said:
strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.
Click to expand...
Click to collapse
same happend to me.can you explain how you fixed it via commandline ? i have to wipe phone and flashed successfully Xiaomi.eu rom . i have global device.
also i flashed now Magisk 19.0 .and it works.
much thx for your work admin ?
majo3000 said:
same happend to me.can you explain how you fixed it via commandline ? i have to wipe phone and flashed successfully Xiaomi.eu rom . i have global device.
also i flashed now Magisk 19.0 .and it works.
much thx for your work admin ?
Click to expand...
Click to collapse
I did not fix it, but you can decrypt your /data via terminal in TWRP : "twrp decrypt PIN"
But I didn't understand you, are you still facing that problem or did you solved it by reflashing MIUI?
Diniodoc said:
strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.
Click to expand...
Click to collapse
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
Updated in OP
vkmcondor said:
Do I need to format or wipe data?
Click to expand...
Click to collapse
Not if you're just manually updating by flashing the Recovery ROM. Think of it as a dirty flash a custom ROM. Just install it on top of your current build and then flash your Magisk ZIP and any other mods that may have been overwritten (due to needing to patch the boot.img
Diniodoc said:
I did not fix it, but you can decrypt your /data via terminal in TWRP : "twrp decrypt PIN"
But I didn't understand you, are you still facing that problem or did you solved it by reflashing MIUI?
Click to expand...
Click to collapse
i was first on original rom.then i flashed TWRP from here.after reboot i hang on screen were i have to enter password to access android.so i never have set a password and tryed mi Pin and miui Account password...but none pin was acceptet.
then i wiped data ...reboot ...but android doesnt load.
so i flashed xuaomi.eu Rom . after flashing it .the phone startet succesfully....
the thing is.... i never entered a pin or password to dercrypt my device....and what helped was wipe and flash rom .... greatz..
I am getting error 64 when flashing arm64 gapps.
ebautista said:
I am getting error 64 when flashing arm64 gapps.
Click to expand...
Click to collapse
Why did you even flash gapps?
thelazyindian said:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
Updated in OP
Click to expand...
Click to collapse
Good to know THX. I'm still using original MIUI so I think there is nothing to do than waiting or better use a custom ROM
One more question. Does anybody know if there is the possibility to use a separate password for encryption different from the lock screen? This was possible in earlier versions of Android.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
WLAN and USB tethering
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8504, https://github.com/lenovo-devs/android_device_lenovo_tb-common/tree/lineage-16.0-msm8937
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo/tree/lineage-16.0-msm8937
2020-03-19
Fixed USB flash mounting when using OTG
mailru: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
Previous versions:
2020-03-13
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
mailru: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
2020-03-04
first release
mailru: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F or one from link below
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TWRP
Built from omnirom android 9.0 source (twrp 3.3.1), includes same kernel as Lineage build, with support for pstore (kernel logs after crash), exfat, ntfs, reboot to EDL mode.
mailru: twrp-3.3.1-1-TB8504.img
gdrive: twrp-3.3.1-1-TB8504.img
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8504f/x] LineageOS 16.0 for Lenovo TAB4 8, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2020-03-04
Last Updated 2020-03-19
hero - thank you
Can this be installed on my 8704v?
jcthrower said:
Can this be installed on my 8704v?
Click to expand...
Click to collapse
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
highwaystar_ru said:
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
Click to expand...
Click to collapse
ok thanks for the response. Are you still planning on updating Lineage 16.1 for the 8704v?
Thank you so much for that rom, I'll be trying to flash it next week!
I have question - is there any possibility to get working stock Dolby atmos which is different from that one we can find in other threads
Or
You prefer Viper4android?
Edit: does Netflix work fluently?
Thanks a lot!
Installation went smooth, so far everything seems to be working.
Still need to set up the tab, but I'm glad I finally got rid of the Lenovo bloatware (like kidoz).
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Update:
2020-03-19
Fixed USB flash drives mounting connected by OTG
Lucinde said:
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Click to expand...
Click to collapse
If anyone else would have the same question: I found a workaround. You can create a new user via adb with the command "adb shell pm create-user --restricted <username>".
I didn't find a way to create the restricted profile from the settings menu, but once created, it can be managed via the menu.
In the meantime I installed some apps and so far, so good. From the limited time I worked with it, it seems to run smoother than with the stock ROM :good:
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Managed to install Lineage on my TB-8504F, but it doesnt get past the Lineage boot animation, no matter how long I leave it.
Pushed TWRP to Recovery, formatted as required. Had to amend the Lineage image to remove the device checks, as although I definately have TB-8504F, it didnt like that TWRP reported it as TB_8504f - ?
Installed and installed GAPPS, cant get past load screen.
I do have a backup, so not concerned, but frustrated!
Any help appreciated
BigBrother84 said:
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Click to expand...
Click to collapse
Sorry it took me so long to see this, but I had similar problems as you initially. It turns out you actually have to install TWRP to the tablet for it to mount /system properly, booting into it from fastboot doesn't work for some reason - that was what fixed it for me at least. It may be different for your device but I had to run the flash recovery command twice for it to stick..
Also want to say thanks to highwaystar_ru, the past few builds have been running great
Slack3r said:
It turns out you actually have to install TWRP to the tablet for it to mount /system properly
Click to expand...
Click to collapse
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
BigBrother84 said:
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
Click to expand...
Click to collapse
Yep, you'd need to flash TWRP via that fastboot command and boot to recovery by holding vol up/power. I put the ROM and gapps files on a MicroSD card which was picked up by TWRP.
I had similar problems with the ROM not being compatible after the first failed flash, you should be able to modify the updater-script file located at META-INF\com\google\android to include "tb_8504" as a compatible device. I didn't test this method however, as I reflashed the stock image which combined with installing TWRP on the device solved my issues.
If you need to, the full stock image can be flashed using QFIL and the instructions from here, but I'd recommend trying to restore the backup posted by Plant as the QFIL method can take some time to get figured out. I'm not sure how this compares to MiFlash but that would likely produce the same results.
Hope this helps!
screen rotation
Does anybody have problem with auto rotation for screen? In mine TB-8504F it doesn't work. Installed some apps which are testing sensors and none sensor responsible for screen rotation is vsible after flashing this system.
---------- Post added at 04:43 AM ---------- Previous post was at 04:24 AM ----------
If you will brick your device as me you can always use Qualcomm Flash Image Loader (QFIL) with proper files for your device. Note for mine works QFIL v2.0.0.1. Newer versions won't work with my device. It will load stock android 7 then under TWRP you can wipe and flash Lineageos. Firstly was bricked while was going from And 8.0 and not flashed but only booted TWRP. As mentioned above need to flash TWRP
I tried restoring the backup, but after I tried booting into system I got a black screen I can't fix. Power buttons don't work, I can't boot into recovery / anything else. No logos or text. It's like the battery is dead, but I can't power it on. Tried charging it, because the battery was around 10% when I tried restoring the backup, but I don't think that will help. Any other ideas? I think I lost this device for good.
Hi,
After coming from stock 8.0, I’ve got everything up and running which appears to run great.
However, I am struggling to get my PS4 controller working.
It will connect fine via Bluetooth, but no input is detected.
Any ideas?
{
"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"
}
Introduction
Welcome to TWRP for the Samsung Galaxy Tab S7+ 5G (T976B). This same image will also work for the wi-fi-only T970.
Installation
Only proceed if you are comfortable with low-level device management and are capable of recovering an unbootable device, should an unforeseen mishap occur.
Unlock your device's bootloader and then install the recovery image below. If you use Odin to flash it, remember to rename the image recovery.img and tar it before flashing. You will also need to flash a neutralised vbmeta.img image if you have not already disarmed verified boot.
Post-installation
The Tab S7+ 5G utilises proprietary file-based encryption (FBE) in its factory state for the user data partition. TWRP cannot decrypt this, however, so it must be removed. Otherwise, you will not be able to perform back-ups and restores.
To remove encryption from your device, please use TWRP to flash the Samsung multi-disabler and then format /data again. You must use at least v2.5 of the multi-disabler.
These builds are stable and known to perform well on many users' devices.
Latest releases
Android 12 (CULC firmware)
twrp-gts7xl-3.6.0_11-A12-1a7_ianmacd.img
Android 11 (BUA8 firmware)
twrp-gts7xl-3.5.0_10-A11_3_ianmacd.img
Android 10 (ATJ4 firmware)
twrp-gts7xl-3.5.0_10-2_ianmacd.img
Source
TWRP device tree for the Galaxy Tab S7+ 5G (T976B)
Kernel source code for the Galaxy Tab S7+ 5G (T976B)
TWRP source code
Support
For support or just to talk about the device amongst friends, please join our Telegram group dedicated to TWRP/root on Samsung devices.
XDA:DevDB Information
TWRP for the Samsung Galaxy Tab S7+ 5G, Tool/Utility for the Samsung Galaxy Tab S7 / S7 Plus
Contributors
ianmacd
Version Information
Status: Production
Current Production Version: 3.5.0-1_ianmacd
Production Release Date: 2020-12-29
Created 2020-09-16
Last Updated 2022-01-12
Changelog
2021-01-28 3.5.0_A11-3
First release with Android 11 kernel, built for BUA8 firmware.
Any file beginning with Magisk- is now considered flashable.
2021-01-25 3.5.0_A11-2
Fix device rebooting only to recovery.
Fix spurious attempt to perform digest authentication when flashing .apk file.
2021-01-25 3.5.0_A11-1
Report the device as running Android 11.
TWRP will now include files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files. This is to accommodate the new packaging of Magisk as a payload within the manager app.
2021-01-19 3.5.0-2
Merge post-3.5.0 release bug fixes.
2020-12-29 3.5.0-1
Update to TWRP 3.5.0.
2020-12-23 3.4.0-3
Fixed bug that causes unmounting of System when Advanced menu is entered.
2020-12-20 3.4.0-1
First production release.
Working MTP implementation.
2020-11-06 3.4.0-1a21
Fixed image back-up of Optics partition.
logcat is now enabled in recovery.
With kernel built for ATJ4 firmware.
2020-10-07 3.4.0-1a16
With kernel built for ATI3 firmware.
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
+1
+++++++++1 please doo pleasssseee
Come on Ian.... :angel: Get that T870 source code and give us 11 inch wi-fi guyz some luv...
ivanox1972 said:
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
Click to expand...
Click to collapse
+1 would really appreciate it if this could be done.
Would love twrp support for SM-T970 wifi. Will definitely buy you some coffee for the hard work.
Thanks. :good:
Please please please +1 +1 for T970 wifi model!!!
donation guarantee from me
Will chip in fora T970 tutorial.
Thank you.
FYI it does work on T970 but ADB is not working.. I was able to put the multi disabler and magisk zip onto my extsd card then flashed twrp, flashed multi disabler, formatted data, reboot recovery flash magisk then boot system. Keep in mind I already had my vbmeta disabled.
I then made a full backup in twrp which went just fine.
So T970 will work but adb isnt working so would need to have your files on a extsd .
EDIT: I spoke too soon.. it actually works including adb after disabling mtp.. i had something screwy with my messin with it lol.. multi disabler worked also
Got it flashed to my Tab S7+ (T970), but I don't see system as a flashable partition when trying to flash an img. Only see Boot, Recovery, Optics image, Prism image and super. I am looking to flash a a GSI
EDIT: It seems the S7+ has dynamic partitions where system.img is within super.img (which also contains other partition images). Flashing a system.img to the super partition won't do. Guess I'll have to research and wait for devs so i can figure out how to flash a GSI on this thing
Gilbot said:
Got it flashed to my Tab S7+ (T970), but I don't see system as a flashable partition when trying to flash an img. Only see Boot, Recovery, Optics image, Prism image and super. I am looking to flash a a GSI
EDIT: It seems the S7+ has dynamic partitions where system.img is within super.img (which also contains other partition images). Flashing a system.img to the super partition won't do. Guess I'll have to research and wait for devs so i can figure out how to flash a GSI on this thing
Click to expand...
Click to collapse
repack gsi into the super.img then flash super
Hello. One thing I wanted to ask. Might I use this TWRP Tree to compile SHRP?
Best Regards,
me
ivanox1972 said:
Super fast and superb news! Can you make it for t970, wifi only?
Thanks
Click to expand...
Click to collapse
mikedavo said:
+1
Click to expand...
Click to collapse
Huntyz said:
+1 would really appreciate it if this could be done.
Click to expand...
Click to collapse
vangry2020 said:
Would love twrp support for SM-T970 wifi. Will definitely buy you some coffee for the hard work.
Thanks. :good:
Click to expand...
Click to collapse
Speedy_Will said:
Please please please +1 +1 for T970 wifi model!!!
donation guarantee from me
Click to expand...
Click to collapse
Jalh said:
Will chip in fora T970 tutorial.
Thank you.
Click to expand...
Click to collapse
ssalkuwari said:
+++++++++1 please doo pleasssseee
Click to expand...
Click to collapse
The T976B image has since been verified to also work without issue on the T970..
3.4.0-1a16 released.
The image has been updated with the latest fixes from the head of the TWRP Android 10 branch, plus a kernel built to match ATI3 firmware.
ianmacd said:
The T976B image has since been verified to also work without issue on the T970..
Click to expand...
Click to collapse
Where can I send a donation to ?
ianmacd said:
The image has been updated with the latest fixes from the head of the TWRP Android 10 branch, plus a kernel built to match ATI3 firmware.
Click to expand...
Click to collapse
Can we update to this build without flashing through odin via a PC?
Also please provide a payment method so we can send money your way:good:
Edit: Just updated to the latest new build using the official twrp app works perfectly on T970.
thanks.
I have a new SM-T970 with now an unlocked bootloader. Is it save to flash this TWRP in "EUX_T970XXU1ATI2" (this is the current firmware on the tablet and no updates to "ATI3" are offered to me currently)?
One additional question: Where I can find a "neutralised vbmeta.img" for the SM-T970?
Edit2: Got it!
For everyone who is struggeling with the "neutralised vbmeta.img" as me here is the manual on how vbmeta can be "neutralised": https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
Click to expand...
Click to collapse
The file which must be flashed as "USERDATA" will be this (on bottom at the first post): vbmeta_disabled.tar
Now lets have a look if the TWRP is working on my ATI2-Firmware.
EDIT3:
Now I got everything to work:
- unlocked bootloader
- root with magisk
- "disabled vbmeta"
- flashed TWRP
- flashed "multidisabler-samsung-2.6.zip" and disabled with this the encryption
- Setup a last time and now I have TWRP and root via Magisk
Thanks everyone who helped to make the tab s7+ much more usable as it is out of the box.
Later I will try backup/restore in TWRP.
EDIT4:
So I just made a backup, wiped data and afterwards restored the backup: Success! The tablet is exact at the state where I backed it up.
So for others: I got a lot of information from this thread which are useful for the Tab S7+ also: https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
vangry2020 said:
Can we update to this build without flashing through odin via a PC?
Click to expand...
Click to collapse
Yes. If TWRP is already installed, just choose Install from the main menu, tap Image, select the new TWRP image file and flash it to Recovery. Reboot to recovery and you'll be in the new version.
Alternatively, any Android root app capable of flashing the recovery partition can be used. Or even just dd on the command line, using a terminal program or adb to spawn a shell.
Also please provide a payment method so we can send money your way:good:
Click to expand...
Click to collapse
I don't accept donations, but I appreciate the sentiment. Thank you.
{
"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 11 (R), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_htc_m8
Kernel source code: LineageOS/android_kernel_htc_msm8974
Working:
WiFi
Bluetooth
ANT+
Camera (including video recording)
FM Radio
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Broken / not yet supported:
MHL
NFC
Compatibility:
Single SIM variants:Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr).Dual SIM variants:Builds are compatible with all M8 Dual SIM variants (m8dug and m8dwg).In both cases, all builds are based off the HTC's Android 6.0.1 firmware and kernel with binaries from Android 6.0 GPe.
Downloads:
Single SIM variants:
lineage-18.0-20201109-UNOFFICIAL-m8.zip
Dual SIM variants:
lineage-18.0-20201109-UNOFFICIAL-m8d.zip
Installation:
Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
Wipe /system, /data and /cache
Install LineageOS zip package
[*]Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Credits & collaborations
This work is due to efforts from everyone involved in M8 development. The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Single SIM variants:
Official wiki link
Dual SIM variants:
Official wiki link
Please note that M8 GPe partition layout is no longer supported. The device must first be converted to Sense firmware, otherwise installation will fail.
Can not find Gapps for m8.
---------- Post added at 10:51 PM ---------- Previous post was at 10:28 PM ----------
BitGapps will this work? Any other option?
https://bitgapps.cf/
https://bitgapps.cf/arm/R/
Initial expression everything working. Nice job
Gapps Link: https://bitgapps.cf/arm/R/
had a few teething troubles, first the clicky bootloop (speaker popping) on the lineage animation, then an "entering recovery" loop (my twrp had disappeared (probably because I was using an out of date one), got back to fastboot and flashed twrp-3.4.0-1-m8.img and all is well until booting lineage, then powering off and entering recovery, at which point it's gone again and it just reboots normally. Reverting to a fresh 17.1 and the recovery remains intact.
works nicely with the Gapps above,
sadly my banking apps don't, Is this because it's signed with public keys?
Out of all the ROMS i've tried, only your variant of 17.1 worked correctly
In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid
fela4 said:
In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid
Click to expand...
Click to collapse
Same here. Furthermore, now I cannot install fastboot drivers and reinstall twrp recovery. Any solution? Can't even install gapps.
adem_7 said:
Same here. Furthermore, now I cannot install fastboot drivers and reinstall TWRP recovery. Any solution? Can't even install gapps.
Click to expand...
Click to collapse
The GApps at https://bitgapps.cf/arm/R work fine
You should be able to boot TWRP using fastboot
download the TWRP image and open a terminal in that directory
I use Linux so this came in handy
Code:
sudo $(which fastboot) boot twrpxxx.img
**replace twrpxxx with your TWRP image file name
Your device should boot TWRP and you can flash your zips
Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.
cexcells said:
Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.
Click to expand...
Click to collapse
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.
Dynamo_anik said:
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.
Click to expand...
Click to collapse
I also had the issue of a bootloop every time immediately after getting to the home screen.
cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
i did clean installation and i didn't face any issue.
Dynamo_anik said:
i did clean installation and i didn't face any issue.
Click to expand...
Click to collapse
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.
cexcells said:
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.
Click to expand...
Click to collapse
Use bitgapps
https://bitgapps.cf/arm/R/
there is no google account setting up at the starting.
Flashing this rom on my M8 worked perfectly fine.
Thanks a lot for your work!
took the plunge
cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
Followed your 3 step install and all great so far.
Skipped setting lock screen during set up as a precaution, is it OK to set one up?
Installing apps from an OTG USB is going great
Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?
text1 said:
Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?
Click to expand...
Click to collapse
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot
ainaz said:
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot
Click to expand...
Click to collapse
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452
Martoost said:
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452
Click to expand...
Click to collapse
Adb driver is not enough for that, you also have to install the HTC mobile driver. If it's still the same try changing the USB cable