Related
This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Dude, quit being so amazing. It's getting ridiculous.
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Yes!!! Glad to see you!
@WugFresh
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.
I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.
bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.
Can confirm a working flash. Everything looks great! Thanks for all the hard work
no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Edit
Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)
OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.
dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks
Yes it seems Google decided to remove the backup confirmation dialog from TcSettings
So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2
DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.
Hi!
I recently bought a Mi Mix and want to flash it with Lineage OS.
I followed all relevant instructions - did unlock the bootloader and so on - but I am not able to install TWRP using ADB and fastboot.
The phone is connecting well in ADB - even the "fastboot flash recovery twrp.img" gets a positive response - all seems to work fine. But after rebooting, I am always confronted with the stock recovery - the flashing so seems not to work out of some reason - TWRP gets removed during the reboot process.
I also tried to first flash and then use the "fastboot boot twrp.img" command. This command starts TWRP, but only in a frozen state - TWRP then starts in a way that you are not able to interact with the interface. Also here - after rebooting the stock recovery is there again. Can someone give me a hint, how to solve this problem?
I am running ADB on a Linux Computer (Debian 9) - dont think, that this might cause issues, but maybe....
The phone runs the MIUI-Version "MIUI Global 9.1 Stable"
It would be great, if someone here could help me out. I am somehow stuck and dont know how to proceed..
Thanks for taking the time!
Best
You can find two compatible versions of TWRP here.
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
H0707 said:
Thanks Gavin!
Just out of curiosity - can you explain me, why the official TWRP Versions are not working and the ones you did post are good?
Best
Heiko
Click to expand...
Click to collapse
Touch has never worked on the official versions to my knowledge. Even the latest 3.2.1.0 build still has broken touch. It is still usable if you use a USB adapter/mouse, but not via touch.
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
H0707 said:
Dear Gavin! Your TWRP file worked great.
But I have no another issue that seems to be common with the Mi Mix - the media sound is not working anymore. Notification and phone works fine but music and video is gone. I just was reading that you should update the firmware. Are the other files added in the link you did send by chance the relevant firmware files?
Best
Click to expand...
Click to collapse
Use 8.1.4 and wipe caches
https://redirect.viglink.com/?forma...://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
H0707 said:
Thanks - do I have to wipe cache and dalvik in TWRP before installing?
Click to expand...
Click to collapse
After
I use thishttps://androidfilehost.com/?fid=673368273298927160 TWRP Modified by MrRaines (Highly recommended) and this how to show install twrp on mi mix
gavin19 said:
You can find two compatible versions of TWRP here.
Click to expand...
Click to collapse
I was looking for that as well! Thanks for sharing. I can confirm that this TWRP version works well with the Mi Mix.
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
Are you encrypted, or maybe you missed a stage when installing,
H0707 said:
Thanks guys - the device works fine now. You saved my day!
There is one thing left. I still cannot initiate TWRP manually - have to use ADB for this. Once TWRP is started, I cannot reach the devices harddisk anymore from my computer. Thats no issue now, but might cause issues in the future. Any idea how to solve this?
Best
Click to expand...
Click to collapse
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
james1089 said:
Are you encrypted, or maybe you missed a stage when installing,
Click to expand...
Click to collapse
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
malimt said:
No. It happened with my device as well. You cannot mount your internal storage on your PC. I've tried many different versions of TWRP and none have allowed access. I'm not quite sure why ... I had other devices in the past and it always worked. On the Mi mix however, it does not. So just turn on your phone and transfer what you need to or adb sideload it.
No. I don't believe that he did James. Does it work for you? because it never worked for me either. I've tried all the different versions of TWRP and it didn't do a thing. Also I have no passwords or encryption. I'm sure of this. Maybe I'm also doing something wrong and that's why I can't Mount my internal storage while in TWRP recovery?
I don't use the official TWRP because for some reason the official versions of TWRP offered for the Mi Mix are broken. The touchscreen never works and I don't have an external controller or anything else to make it work other than the phones screen. So I've used the custom versions that have been fixed and re-released on XDA.
Click to expand...
Click to collapse
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
james1089 said:
Well its strange cause there are thousands using it for over a year now. Maybe you have always been encrypted. Which ROM are you using, I mean you haven't still got the vendor fake ROM, any updates?
Click to expand...
Click to collapse
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
malimt said:
That's very odd. I'm not quite sure what to tell you. I know for a fact though that my device is not encrypted. I'm currently running RR without any password/pattern. Before installing RR I was on stock OS and still no password/pattern. I live alone and so I don't feel the need to use a password on my phone. So ever since I've purchased this phone I've never had a password on it.
No updates as far as I'm aware on the RR.
Does it Mount for you? If so, what TWRP are you using on your device?
Click to expand...
Click to collapse
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
james1089 said:
I've used the same 1 from the beginning, smarty, I just followed the guide in the guide section how to remove vendor ROM. I use Linux it works fine. Everyone thought they had official ROM in the beginning only to find out it was vendor ROM. What about using mtp to send files, maybe that's what I did, can't even remember.
Click to expand...
Click to collapse
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
malimt said:
Wow. Well you're lucky tbh. I can't seem to figure out why mine doesn't connect. I'm not sure what the difference is between the vendor (ROM) and the "stock" (ROM) - I know I was using the global stable (ROM) that's what my phone first came with and it was running 6.0 MM.
Yes, I have tried to use MTP while in TWRP and it doesn't do anything. My computer does detect something but doesn't show the phone to be connected or anything. I have even tried to mount it in the options but nothing. I know I have all drivers installed and does not make a difference. I'm running Windows 10 not Linux.
Click to expand...
Click to collapse
So does it show up when phone is booted?
james1089 said:
So does it show up when phone is booted?
Click to expand...
Click to collapse
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
malimt said:
Yes, when it is booted it shows up perfectly, after I switch from "charging to file transfer (MTP)" in the status bar.
Click to expand...
Click to collapse
I'm going to try when I get home, it's been do long since I tried something like that, have you ticked and then unticked mount in read only. Then reboot to recovery again.
October security patch.
You MUST be on Android 12 to use this!!!!!
If your already on Android 13, you can not go back to Android 12, so don't try flashing this!!!
Your bootloader must also be unlocked to install custom firmware.
To do this, reboot to bootloader and type the following: fastboot flashing unlock
The custom kernel of this ROM hides the unlocked bootloader. The device will pass Safetynet and the Play Store will report the device as certified. Based on this, root, magisk and the modules are not needed to pass device certification.
This is based on the Android Open Source Project. It includes various proprietary hardware-specific code.
All the source code is available in the Github repo here.
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Thanks go to Github and Pixel Experience for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the Pixel Experience source code, device specific code. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated every week with minor changes.
GAPPS ARE ALSO INCLUDED WITH THIS ROM
DO NOT DOWNLOAD OR FLASH GAPPS ON THIS ROM!!!!!
DOWNLOAD RECOVERY FLASHER HERE
DOWNLOAD ROM HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 Have all the recovery flasher files in the same folder
Simply double click on flash.bat to install recovery
#4 REBOOT TO RECOVERY THEN ADB SIDELOAD
adb sideload PixelExperience_barbet-13-20221107-BETA-UNOFFICIAL.zip
#5 REBOOT TO SYSTEM
#6 REBOOT TO RECOVERY AGAIN IF YOU WISH TO ROOT AND ADB SIDELOAD
adb sideload magisk.apk
#7 REBOOT TO SYSTEM
Screen call and Google assistant works.
If you are already on this ROM, you can dirty flash updates without wiping data. Simply set to inactive slot in bootloader. Reboot to bootloader then
fastboot --set-active=other
Then repeat all steps except #2
YOU MUST WIPE WHEN COMING TO THIS ROM THE FIRST TIME!!!
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
[email protected] said:
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
Click to expand...
Click to collapse
Thank you.
Installed this rom with gapps and magisk, everything working fine.
[email protected] said:
Installed this rom with gapps and magisk, everything working fine.
Click to expand...
Click to collapse
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.
predragiPredrag said:
how is the FP sensor, does phone have slow unlock when you are not using AOD? Google introduced that stupid bug in March, and they still didn't fix it.
Click to expand...
Click to collapse
Works very quick, much more quicker than latest stock
[email protected] said:
Thank you.
Click to expand...
Click to collapse
Thanks for the info. Any bugs let me know.
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set-active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
[email protected] said:
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
Click to expand...
Click to collapse
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
TheSayaMan said:
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
Click to expand...
Click to collapse
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
TheSayaMan said:
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Click to expand...
Click to collapse
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
[email protected] said:
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
Click to expand...
Click to collapse
Great, thanks!!!
[email protected] said:
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
Click to expand...
Click to collapse
This is 12.1. If you look in System, it will show Lineage 19.1
TheSayaMan said:
This is 12.1. If you look in System, it will show Lineage 19.1
Click to expand...
Click to collapse
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet
[email protected] said:
No, for me it says, Android version 12
Lineage version 19-20220504-UNOFFICIAL-barbet
Click to expand...
Click to collapse
The file name is irrelevant. Look in System, updater.
I didn't install latest your update, maybe because of it, it using Android 12?
TheSayaMan said:
The file name is irrelevant. Look in System, updater.
Click to expand...
Click to collapse
So you see, there Android is 12
[email protected] said:
So you see, there Android is 12
Click to expand...
Click to collapse
Lineage 19.1 is same as Android 12.1
Install LineageOS 20 on SM-T290 and SM-T295 with Google Apps (MindTheGapps)
* Your warranty is now void. (It might already been)
* I am not responsible for any damage that it may do to your device. I WARNED YOU
* It's your choice to do it. Not mine. I just made it as I wanted to do it, but you have the choice to do so. If you choose to do it, you know that it may have consequences.
Click to expand...
Click to collapse
WARNING! This won't work on a bootloader with version U4! Flashing won't work and so you will not be able to use this guide. Unfortunately, you can also currently not downgrade the bootloader, making it impossible to get any custom stuff (custom recovery, custom ROM, etc.) on your device...
Hello there! This is another guide from me here on XDA Developers! Today, I will show you how to install LineageOS 20 on an SM-T290 and SM-T295, and yes, it works on both! Let's get started:
PrerequisitesBut first, make sure you have all of this:
An SM-T290 or SM-T295 tablet
TWRP (v3.7.0 recommended for SM-T290 and v3.5.2 for SM-T295)
Unlocked bootloader
1. Download LineageOS 20 ZIP from here (There stands it is for gtowifi, but it also works on the LTE model).
2. Choose the nightly build for the ZIP, it is very stable even though it is nightly.
3. OPTIONAL BUT I DO NOT RECOMMEND: You could also choose the recovery, but that's more like the stock recovery and I recommend you to keep TWRP as it has better features.
4. Download the ZIP that has the format 'lineage-20.0-YYYYMMDD-nightly-gtowifi-signed.zip'
- OPTIONAL: Download the recovery image for LineageOS 20 with the format 'lineage-20.0-YYYYMMDD-recovery-gtowifi.img'.
5. Download MindTheGapps from here.
6. Choose the one with the format 'MindTheGapps-13.0.0-arm64-YYYYMMDD_BBBBBB.zip'
7. Follow the links to download the ZIP file.
8. Place the LineageOS and MindTheGapps ZIP to an SD card or USB drive. If you choose to also take LineageOS recovery, you will also need to place the .IMG to an SD card or USB drive.
9. Insert the SD card or USB drive into your tablet.
10. Boot the device into TWRP.
11. Go to 'Wipe' > 'Swipe to Wipe'.
12. Then go once again to 'Wipe' > 'Format data' > 'Swipe to format'.
13. Go to install, make sure that it is not install image but as flash ZIP!
14. Use the select storage button to choose the storage where the ZIPs are saved.
15. Choose the LineageOS 20 ZIP and swipe to install.
16. Wait until it is done and now install MindTheGapps.
17. Optional step (depending on whether you have the following things):
- Install Magisk (root) ZIP if you have it. You could also do this later on.
- Install LineageOS recovery ZIP if you have chosen to use it. This can also be done later.
17. Click on 'Reboot system' or go to 'Reboot' > 'System'.
18. Wait until the boot is done.
19. Go through the setup, but WAIT! First read the step below.
20. Depending on whether you have LineageOS recovery or TWRP, you need to enable the option 'Auto-update LineageOS Recovery/LOS Recovery' in the setup if you have LineageOS/LOS Recovery and disable that if you have TWRP.
21. Once the setup completed, you are done!
That was easy to follow. Thank you.
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
No problem!
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
Nice. Guess you have LineageOS 20 right now.
Minionguyjpro said:
Nice. Guess you have LineageOS 20 right now.
Click to expand...
Click to collapse
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Heeni said:
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Click to expand...
Click to collapse
It does work with TWRP. It uses an OpenRecoveryScript. If you have Gapps (which you don't have), you need to reflash them afterwards. Also Magisk needs to be reflashed, but it is much easier to do than the stock!
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
dequadim said:
How does this tablet with LineageOS work now? Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
I'm not sure, but it has some good features though. Some parts are a bit buggy, but most are not. It's also much faster.
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
SGX22 said:
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
Click to expand...
Click to collapse
Hello there! LTE will not be included, but you have 2 workarounds:
Make a hotspot over Wi-Fi with your phone or any other SIM device
Use the GSI ROM, which may have support
Well, LTE doesn't work, because of this: LineageOS is made on base of the drivers and packages of the device. And, they are almost the same I think, that's why the other stuff will or should work. But, the SM-T295 also has a driver and/or package for the SIM, LTE and so. And because it was originally made for the SM-T290, instead of an SM-T295, it will not include those drivers and so the support for it. You could try a GSI, although I had issues with it. But I may have done it wrong or so.., I always say: if there is an official custom ROM, use that over GSI, because it was really made for the device and includes the drivers and packages for the device. Although I don't really know whether GSI is bad, it may also work correctly..., if you try GSI, and it doesn't work, you could take a look at this: https://forum.xda-developers.com/t/gsi-lte-fix.3925151/
dequadim said:
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
In my opinion it is much faster and very responsive. It is really an improvement!
SGX22 said:
In my opinion it is much faster and very responsive. It is really an improvement!
Click to expand...
Click to collapse
Well, I will install it as soon as I can.
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Minionguyjpro said:
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Click to expand...
Click to collapse
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Note: as i experienced you cant install Twrp on android 10 bootloader 3
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
You can repair it quickly. Please search on youtube.
Deleted, need to search some further to make sure it is correct...
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
SGX22 said:
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
Click to expand...
Click to collapse
Well, an old Samsung Galaxy Tab 4 with LineageOS 18.1 (Android 11). I helped someone today to get it on his device! It was very easy to do, so.