[OFFICIAL][RECOVERY] TWRP 3.1.x for Samsung Galaxy Tab E [SM-T377P/SM-T560NU] - Samsung Galaxy Tab E Guides, News, & Discussion

Code:
** Disclaimer
I am not responsible if flashing this recovery bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Recovery Information
Recovery Target Device: Samsung Galaxy Tab E [ SM-T560NU | SM-T377P ]
Recovery Status: Stable
Recovery OS: TWRP 3.1.1-0
Maintainers: [ vince2678 ]
Project GitHub Repositories: https://github.com/TeamWin
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]
[B]SM-T377P[/B] - [COLOR="DarkSlateBlue"][B]gtesqltespr[/B][/COLOR]
Click to expand...
Click to collapse
Download
Official Builds:
Code:
[B]SM-T560NU:[/B] [url]https://twrp.me/devices/gtelwifiue.html[/url]
[B]SM-T377P:[/B] [url]https://twrp.me/devices/gtesqltespr.html[/url]
Click to expand...
Click to collapse
Instructions
Installation using Odin
Installation using the App
Code:
* Download the Official TWRP App from the Play Store.
* Locate your device using the codename for your device.
* Download and flash TWRP (may require root).
Code:
* [B]Enable Developer Mode on your phone and unlock the bootloader from the
Settings, if not done already. [/B]
* Download a recent [B].tar[/B] archive from the links above for your device.
* Reboot into Download Mode [Press Power+Volume Down+Home].
* Flash the [I][B]tar[/B][/I] archive using ODIN by clicking [I][B]AP[/B][/I] and selecting
the [I][B].tar[/B][/I] file you just downloaded.
Click to expand...
Click to collapse
Changelog
Code:
[B][U]29/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated to 3.1.1-0.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Mouse cursor is now hidden from recovery screen.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP now has F2FS filesystem support [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP has USB OTG support integrated for external usb peripherals
(should work for vfat, exfat, ext4 or f2fs-format peripherals).[/B]
Code:
[B][U]07/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Fixed reboot-to-system issue [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] adb shell now works [/B]
Code:
[B][U]07/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Build recovery image for SM-T560NU [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Create forum thread. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]
[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Unknown. You tell me. [/B]
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL][RECOVERY] TWRP 3.1.x for Samsung Galaxy Tab E [SM-T377P/SM-T560NU], Tool/Utility for the Android General
Contributors
vince2678
Version Information
Status: Stable
Created 2017-05-08
Last Updated 2017-06-21

I would like to know if compatible with model T560.

bira792 said:
I would like to know if compatible with model T560.
Click to expand...
Click to collapse
Nope.

Will this work on Galaxy Tab E SM-T560NZ?

deplorablemichael said:
Will this work on Galaxy Tab E SM-T560NZ?
Click to expand...
Click to collapse
If it's not a Qualcomm Snapdragon device, no, it will not work.

any way to do this if FRP is blocking it?

the TWRP versions linked in the OP doesn't work on my SM-T377P
I tried flashing both of the linked version 3's with Odin and Heimdall and all I get is boot loops. TWRP 2.8.7 installs fine using either method.
What else can I try?

mobilemischief said:
any way to do this if FRP is blocking it?[/QUOTE]
Go to developer settings and enable OEM unlock. Now try to flash it now. That's what I did. Also I had USB debugging on too.
Click to expand...
Click to collapse

The TWRP links are dead.
Any way someone could upload the t560 file?
Edit: NVM, just had to actually search for it. Thanks for pointing me in the right direction.

vince2678 said:
Nope.
Click to expand...
Click to collapse
Hi, I got SM-t377p with Nougat running, when I tired to flash these TWRPs it just boots back into System. I downloaded from here
https://dl.twrp.me/gtesqltespr/
I flashed this TWRP and it worked
https://androidfilehost.com/?fid=24385658843825618
its older model

Related

[RECOVERY][GT-I9060] PhilZ v6.58.7 [UNOFFICIAL][UPDATE-20141022]

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Orignal thread - there are features, screenshots and other.
Please click thanks for Phil3759 :good:
SOURCES
Device-specific source code for the Samsung Galaxy Grand Neo [GT-I9060] are available from:
https://github.com/baran0119/android_device_samsung_baffinlite
https://github.com/baran0119/kernel_samsung_baffinlitexx
https://github.com/baran0119/android_vendor_samsung_baffinlite
CHANGELOG
- v6.58.7 (20141022)
like in original thread
- v6.57.9 (20140922):
initial release
HOW TO FLASH IT?
If you have not custom recovery or you bricked your device:
So you have to flash it via odin.
You need PC, a USB cabel, ADB drivers, appropriate recovery and ODIN
Open ODIN and click on AP
Select appropriate recovery
Untick auto reboot
Click on start
Done
Click to expand...
Click to collapse
If you already have custom recovery
You can also flash via ODIN but you don't need PC using custom recovery.
Dowload appropriate recovery
Reboot into recovery mode (POWER+VOL-UP+HOME)
Install zip package
Done
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DOWNLOAD
v6.58.7 (20141022):
Recovery image 20141022
Recovery flashable via ODIN 20141022
Recovery flashable zip package 20141022
v6.57.9 (20140922):
Recovery flashable via ODIN 20140922
Recovery flashable zip package 20140922
Recovery image 20140922
Other:
Odin v3.09
ADB Tool
Please do not mirror.
CREDITS
CM team
samsung
contributors
XDA:DevDB Information
[RECOVERY] PhilZ for Samsung Galaxy Grand Neo (GT-I9060), Tool/Utility for all devices (see above for details)
Contributors
baran0119, luk1337, rutvikrvr
Version Information
Status: Stable
Current Stable Version: 6.57.9
Stable Release Date: 2014-09-22
Created 2014-09-23
Last Updated 2014-09-23
Reserved
KNOWN BUGS
I don't see any...
if you'll find any please tell me
nice one...gonna give it a try..thanks buddy :good:
works fine, thanks
Thanks for this recovery :good:
newer release uploaded:
v6.58.7 (20141022)
baran0119 said:
newer release uploaded:
v6.58.7 (20141022)
Click to expand...
Click to collapse
How can update from a previous version
hanafi2009 said:
How can update from a previous version
Click to expand...
Click to collapse
Flash zip package via recovery
Baran sen türkmüsün ?
Mod Edit: Translation added: "Baran are you Turkish?"
kakic said:
Baran sen türkmüsün ?
Mod Edit: Translation added: "Baran are you Turkish?"
Click to expand...
Click to collapse
I don't have anything in connection with Turkey.

[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU]

Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy Tab E [SM-T560NU ]
ROM Status: Stable
ROM OS: LineageOS 14.1
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Bug reports: https://bugs.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-T560NU[/B] - [COLOR="DarkSlateBlue"][B]gtelwifiue[/B][/COLOR]
Click to expand...
Click to collapse
Download
All Jenkins builds are testing builds, and as such, are likely to be extremely unstable or
unusable.
Code:
[B]All builds:[/B] [url]https://download.msm8916.com/[/url]
[B]Jenkins Builds Builds:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/[/url]
[B]TWRP Builds:[/B] [url]https://jenkins.msm8916.com/job/TWRP_Builds/[/url]
[B]GApps:[/B] [url]http://opengapps.org/?arch=arm&variant=micro&api=7.1[/url]
[B]RSS:[/B] [url]https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_Tab_E/rssLatest[/url]
Click to expand...
Click to collapse
Instructions
If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).
You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.
Click to expand...
Click to collapse
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Features
Code:
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS for Galaxy Tab E [SM-T560NU], ROM for the Android General
Contributors
vince2678, deadman96385, minz1
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-06-08
Created 2017-02-03
Last Updated 2018-06-24
Reserved
Changelog
NOTE: gtesqltespr (SM-T377P) builds have been disabled until someone steps up for testing to resolve the issue in recent builds.
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
from the touch screen, this means that the virtual Nav Bar
can be enabled in the Settings. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Both cameras should now be working [/B]
Code:
[B][U]01/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] LineageOS updater can reboot to recovery properly.[/B]
Code:
[B][U]11/03/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T377PSPT2BPJ1 (6.0.1) to T377PVPU1AOJ5 (5.1.1)[/B]
Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high,
and could quickly cook your phone and kill power on mobile devices.
Lowering to 200Mhz should significantly extend batery life
on the stock scheduler. [/B]
[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]
[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]
There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.
Code:
[B][U]29/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Switched to LineageOS sources. [/B]
[B][U]20/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Made some substantial changes to our build
infrastructure, which should make my life substantially easier
and using Jenkins and all a more pleasant experience. [/B]
[B][U]17/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed [/B]
[COLOR="RoyalBlue"][B]gtesqltespr[/B][/COLOR]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Wifi should be working (build >= 4) [/B]
Code:
[B][U]16/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]
Code:
[B][U]15/01/2017[/U][/B]
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Started builds for SM-T377P [/B]
* [B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Set maximum cpu frequency to 1209Mhz [/B]
[COLOR="RoyalBlue"][B]gtelwifiue[/B][/COLOR]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Rear camera is working [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] LiveDisplay feature is working [/B]
Code:
[B][U]11/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Switched binary blob base from
T560NUUEU1BPI3 (6.0.1) to T560NUUEU1AOK1 (5.1.1)[/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Audio and wifi now work proper. [/B]
Code:
[B][U]08/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created forum thread [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] First build completed. [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None [/B]
nice work! maybe this would work on the t377p
That good ... there is the possibility of cooking something for the T560: C
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
I'm aware of the bug. For now, you'll have to flash the latest CyanogenModRecovery to update the device until twrp works proper.
I'm hoping you might know what I need to do here, but I installed a theme recently and it worked fine. But I ended up having to redo my tablet for a different reason, and ever since then whenever I try to use the same theme my system UI fails.
Finally custom rom for our device. :good: Can we hope to see CM13 on T560 also?
ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
You can try the recoveries below, fully tested and working.
https://forum.xda-developers.com/showthread.php?t=3302935
gapps
hey guys does this require gapps?
You can install Gapps after flashing the rom, Yes.
im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?
42o247 said:
im wondering if anyone knows the device name for the t377p, to edit in the updater script to try flashing this on a sm-t377p?
Click to expand...
Click to collapse
wont work needs another kernel
parrotgeek1 said:
wont work needs another kernel
Click to expand...
Click to collapse
cool cool. good to know.
ElsaReyes said:
I don't know if anyone else has had this problem, but I believe I may of found a bug. Whenever I install or update CM using Twrp I get sent into a never ending TWRP Boot Loop. Not sure if it's just me, or if it's even something fixable, but I figured maybe you would want to know. If you want to know about bugs. :3 Thanks again for the CM. :3
Click to expand...
Click to collapse
The reboot issue for recovery is now fixed.
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device
42o247 said:
i got my t377p to boot all the way to the cm head logo by deleting the first line in the updater script and clean flashing the zip.
clean flash
restore boot partition from stock mm rom
boot
hangs at cm boot logo
ive begun reading how to make a custom kernel and the sources are available for the t377p. so if i dont get too frustrated i can try to compile one to make this rom work with my device
Click to expand...
Click to collapse
A lot of things would not work, for example, the touchscreen. As similar as devices may seem there will still be hardware differences between variants and I don't recommend cross flashing.
Just flashed the 1/15 build and everything went well. I'm in the process of setting my Sm-t560nu up. I will report back after I'm finished. Thanks a lot for this Rom.
vince2678 said:
The reboot issue for recovery is now fixed.
Click to expand...
Click to collapse
Awesome. Thank you for all your work on this. Downloading the build now. :3
And just to keep you updated, it might not be in the newest build but I tried playing some of the videos I have saved on my sd card last night, and while the audio moves along just fine, the video plays all choppy and slow.
Hello, i'm glad to see a rom for TAB E, great work, but if you have time pls do something for T560, many users will be happy to see a CM on theyr tablets imcluding me, thanks allot for any answers
Sent from my SM-G935F using XDA-Developers Legacy app

[Latest][MT6582]TWRP 3.1.1-0 For Micromax Unite 2 (Stable)

HTML:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Changelog :-
Based On Omni Sources
Fixed Invert Touch & Invert Screen
Fixed Late Wipe Cache
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Downloads :-
TWRP 3.1.1-0 (Flashable Zip)
Flashing instructions :-
Reboot Into you installed Custom Recovery.(for e.g TWRP,CTR,CWM,PHILZ)
Select "TWRP_3.1.1_Compiled_Fixed_.zip" and Flash.
Reboot into Recovery to see newly Installed TWRP Recovery
Done .
Device Tree :- https://github.com/EndLess728/TWRP_Miromax_Unite_2.git
XDA:DevDB Information
TWRP 3.1.1-0 For Micromax Unite 2 (A106)
Contributors
EndLess, manjot.gni, Anurag D'Cruz ,Divyrajsinh Jadeja
Source Code: https://github.com/omnirom/android_bootable_recovery
Kernel Special Features: Fixed Invert Touch & Invert Screen
Version Information
Status: Stable
Current Stable Version: TWRP 3.1.1-0
Stable Release Date: 2017-07-01
Created 2017-07-01
Last Updated 2017-07-01
Awesome Bro
Thanks, found an issue - there is no option to boot into bootloader
mGforCe said:
Thanks, found an issue - there is no option to boot into bootloader
Click to expand...
Click to collapse
our device dont have bootloader thats why i removed it
EndLess said:
our device dont have bootloader thats why i removed it
Click to expand...
Click to collapse
But other recoveries have same and using that we can boot into fastboot mode!
mGforCe said:
But other recoveries have same and using that we can boot into fastboot mode!
Click to expand...
Click to collapse
i removed that option to reboot in to bootloader beacause in this device it doesnt support
After flashing and booting into recovery the screen goes black and reboot to system
Mukesh kalaga said:
After flashing and booting into recovery the screen goes black and reboot to system
Click to expand...
Click to collapse
Same here , i even tried Flashify which shows Error and Rashr showed Success , but after rebooting to recovery , it boots back to system.
its working fine on me. but could you please update to latest version with otg support.

[Rom] Viper OS for Motorola Moto C (namath)

​
Code:
* Your warranty is voided.
*
* We are not responsible for bricked devices, dead SD cards,
* Third World 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.
Code:
If you are having problems and want to send a report (Logcat), make sure that you are reporting from the default kernel, not a modified one. Modified kernels can break or fix, even make things better. It depends. I cannot get a full hint of the problem when you're not running the original kernel.
Features:
Status bar Customization
- Customizable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- Header customization
System
- Power menu customization​
Working:
- Almost everything
Bugs:
- Video recording
ChangeLog
First build:
Code:
* Intial build for Moto C
Second build:
Code:
* Semi fix for video recording
* Used Camu instead of snap camera temporary
Instructions:
1. Download the ROM and move it to your phone storage.
2. Reboot phone to TWRP recovery.
3. Wipe everything execpt SDcard (Internal memory is optional).
4. Flash the ROM and Gapps.
5. Reboot.
DOWNLOADS:
- First Build: Download from here
- Second Build: Download from here
TWRP recovery
- Tutorial for locked bootloader
- Compiled recovery
Source
- Device tree
- Vendor
- kernel source
Base
LineAge OS
Credits
- crDroid Android
- CypherOS
- AICP
- PureNexus
- AOKP
- Dirty Unicorns
- Paranoid Android
- and more..
@iykeDROID™
@Nonta72
@nasreirma
@Zormax
@darklord4822
- Other developers mentioned in my device tree
~ Happy flashing ~​
XDA:DevDB Information
The first Viper OS for Moto C, ROM for the Android General
Contributors
Mysteryagr
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: N/A
Based On: LineAge
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-12-06
Created 2017-12-07
Last Updated 2017-12-06
reserved
rom :v
What model? moto c
Enjoy
NexxHud said:
What model? moto c
Click to expand...
Click to collapse
Motorola Moto C 4G - XT1754 - namath
Motoc
would serve for the xt1757 is double sim variant of 4G
NexxHud said:
would serve for the xt1757 is double sim variant of 4G
Click to expand...
Click to collapse
If it is namath, then yea
My roms are for Moto C 4G, codenamed namath
gapps which to use ..?
chetan180 said:
gapps which to use ..?
Click to expand...
Click to collapse
Use the gapps you like, I am using Aroma open gapps
help donor NVRAM not to find it anywhere Moto C 4G 1754
Do not register your IMEI in Maui META
thank you in advance
волков алексей said:
помогите донорским NVRAM нигде не найти его Moto C 4G 1754
не прописать свой IMEI в Maui META
заранее спасибо
Click to expand...
Click to collapse
Kindly reply in English, I can't understand this, if you don't know English, then use Google translate.
Mysteryagr said:
Kindly reply in English, I can't understand this, if you don't know English, then use Google translate.
Click to expand...
Click to collapse
I need a donor NVRAM I can not find it anywhere. or NVRAM calibration for xt1754.
волков алексей said:
I need a donor NVRAM I can not find it anywhere. or NVRAM calibration for xt1754.
Click to expand...
Click to collapse
Just reflash stock firmware and it will be fine.
Note: choose download mode
Mysteryagr said:
Just reflash stock firmware and it will be fine.
Note: choose download mode
Click to expand...
Click to collapse
at Maui META not restore imei need calibration imei 000000000000
---------- Post added at 12:13 AM ---------- Previous post was at 12:07 AM ----------
Mysteryagr said:
​
Code:
* Your warranty is voided.
*
* We are not responsible for bricked devices, dead SD cards,
* Third World 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.
Code:
If you are having problems and want to send a report (Logcat), make sure that you are reporting from the default kernel, not a modified one. Modified kernels can break or fix, even make things better. It depends. I cannot get a full hint of the problem when you're not running the original kernel.
Features:
Status bar Customization
- Customizable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- Header customization
System
- Power menu customization​
Working:
- Almost everything
Bugs:
- Video recording
ChangeLog
First build:
Code:
* Intial build for Moto C
Second build:
Code:
* Semi fix for video recording
* Used Camu instead of snap camera temporary
Instructions:
1. Download the ROM and move it to your phone storage.
2. Reboot phone to TWRP recovery.
3. Wipe everything execpt SDcard (Internal memory is optional).
4. Flash the ROM and Gapps.
5. Reboot.
DOWNLOADS:
- First Build: Download from here
- Second Build: Download from here
TWRP recovery
- Tutorial for locked bootloader
- Compiled recovery
Source
- Device tree
- Vendor
- kernel source
Base
LineAge OS
Credits
- crDroid Android
- CypherOS
- AICP
- PureNexus
- AOKP
- Dirty Unicorns
- Paranoid Android
- and more..
@iykeDROID™
@Nonta72
@nasreirma
@Zormax
@darklord4822
- Other developers mentioned in my device tree
~ Happy flashing ~​
XDA:DevDB Information
The first Viper OS for Moto C, ROM for the Android General
Contributors
Mysteryagr
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: N/A
Based On: LineAge
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-12-06
Created 2017-12-07
Last Updated 2017-12-06
Click to expand...
Click to collapse
hi, do work it on moto c XT1754 model? must Unlock boot loader (enable OEM Unlock) before Flash this custom rom?
thanks
javad490 said:
hi, do work it on moto c XT1754 model? must Unlock boot loader (enable OEM Unlock) before Flash this custom rom?
thanks
Click to expand...
Click to collapse
No need to unlook bootloader. use this method:
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184
After install custom recovery, DO a backup of your actual rom, so if something goes wrong, you can always go back to your original firmware.
Tried factory reset from within this rom now phone only boots in twrp mode even after reflashing this rom or resurection remix
Vasko01 said:
Tried factory reset from within this rom now phone only boots in twrp mode even after reflashing this rom or resurection remix
Click to expand...
Click to collapse
What moto c variant do you have?
You can restore your twrp backup. If you didn't make any backup, search for your original firmware and flash system and boot images.
jhonatann989 said:
What moto c variant do you have?
You can restore your twrp backup. If you didn't make any backup, search for your original firmware and flash system and boot images.
Click to expand...
Click to collapse
xt1754
i did make a twrp backup but it doesnt show up at all in restore section for some reason
Vasko01 said:
xt1754
i did make a twrp backup but it doesnt show up at all in restore section for some reason
Click to expand...
Click to collapse
Where did you make your backup? Internal o external storage?

Development [ROM][13] Modded crDroid 9 [UNOFFICIAL][Gapps and adreno driver v530 included]

Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features:
* Based from Latest Crdroid 9 Android 13
* Encrypted build
* Gapps Build
* Selinux enforcing and Safety net passes by default
* Updated to adreno v530
* More info - Click here
First Time Installation:
* Backup before you begin
* Reboot to provided or TWRP based recovery.
* Format Data , even coming from crDroid 7.x
(otherwise you may not able to boot ROM due to encryption complexities)
* Flash ROM via adb sideload
* Reboot and profit!
Update Installation:
* Backup before you begin
* Ensure you are on provided 12/13 recovery
* Use Updater app to download update and flash
(or download update separately and use Updater app with Local update option)
* No need to flash gapps if already flashed.
Download:
Click Here
Known issues:
* None.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_sm8150-common
Kernel link: https://github.com/crdroidandroid/android_kernel_xiaomi_sm8150
Crdroid official vayu ROM: https://forum.xda-developers.com/t/rom-13-0-crdroid-9-official.4516191/
-------------------------------------------------------------------------------------------------------
Liked my Modified ROM? click the liked button !
If your experiencing a performance problem it is due to some of my tweaks ill upload a update today
Update: Uploaded! Kindly install the new rom

Categories

Resources