I have an AT&T Galaxy Tab E (SM-T377A) and I need to root it, but I haven't been able to find any guides or .tar files to flash. I have found guides for the sprint version (SM-T377P), but I'm afraid that will screw something up if I try it.
Is it even possible?
Thanks for the help.
https://forum.xda-developers.com/galaxy-tab/help/question-tab-e-att-sma-6-0-1-mm-root-t3578171
Same question I'm assuming the AT&T (A) and T-mobile (T) variants are Exynos CPU while the Sprint (P) is Qualcomm. We need a confirmation of a root method.
SM-T377A Hardware / Software Details From "Phone Info" App
Here is all the info from my AT&T Samsung Galaxy Tab E 8.0 that I just received today (brand new and shipped from AT&T).
Manufacturer / Brand: samsung
Phone Model: SAMSUNG-SM-T377A
Device Type: gteslteatt
Product Name: gteslteuc
Country of Origin: MADE IN VIETNAM
Manufacturing Date: 2017.05.23
Knox Warrant Void: 0x0
Colour / Internal Storage: Black / 16 GB
Product Code: SM-T377AZKAATT
Original CSC Code:
Firmware's CSC Code: ATT
Active CSC Code: ATT
Available CSC Codes:
CSC Country: USA / US
Mobile Operator: AT&T / 310410
Bootloader Version: T377AUCU2APJ2
PDA Version: T377AUCU2APJ2
CSC Version: T377AATT2APJ2
Baseband Version: T377AUCU2APJ2
Latest Firmware: Not Found
Kernel Version: 3.10.9-8864257 [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
Root Existence: No
Android Version: 6.0.1
Build Number: MMB29K.T377AUCU2APJ2
Build Fingerprint: samsung/gteslteuc/gteslteatt:6.0.1/MMB29K/T377AUCU2APJ2:user/release-keys
Build Description: gteslteuc-user 6.0.1 MMB29K T377AUCU2APJ2 release-keys
Build Date: Mon Oct 17 18:03:29 KST 2016
Changelist: 8864257
Hardware / Board: universal3475 [32-bit]
Platform / Chip: exynos3 / exynos3475
GPU (Graphics Processing Unit): ARM Mali-T720
Modem Board: SHANNON308
Hardware Revision: REV0.3
Total RAM: 1.36 GB
Screen: 7.96 inches, 1280 x 800 pixels, 189 ppi, 213 dpi
Sound Card: Universal3475-I2S
Camera (Rear): 5MP / SLSI_S5K4EC_FIMC_IS
Camera (Front): 1.9MP / DB_DB8221A_FIMC_IS
Sensors: K2HH Acceleration (Accelerometer) - STM, SX9500 Grip Sensor - SEMTECH, SX9500 Grip Sensor for wifi - SEMTECH, Screen Orientation Sensor - Samsung Electronics
Related
Hello
what is the negative wire to connect the car to watch the video when the car is moving.
Thank you for your help
Number model: S07
Versio MCU: MTCB KLD2 V2.77 aug 26 2015
Version android: 4.4.4 10082015
Kernel version 3.0.36+ @ chun roo-book # 817
Build Number: RK3188 eng 4.4.4 10082015
CPU: 1.6 GHz armv7 (X4)
Memory: 1024 MB
ango81 said:
Hello
what is the negative wire to connect the car to watch the video when the car is moving.
Thank you for your help
Number model: S07
Versio MCU: MTCB KLD2 V2.77 aug 26 2015
Version android: 4.4.4 10082015
Kernel version 3.0.36+ @ chun roo-book # 817
Build Number: RK3188 eng 4.4.4 10082015
CPU: 1.6 GHz armv7 (X4)
Memory: 1024 MB
Click to expand...
Click to collapse
Leave the wire open. Go into settings and turn on watch video when driving. Settings/driving settings.
Hello
thank you it works very well
You are in the wrong forum section...
Correct:
http://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa
Hello people have a question have this autoradio with android 4.4.2 from the company Allwinner that is Allwinner T3_P1 model gerootet and busybox is also installed but I do not find any Rome I will times list with the specficationen and would ask you to clarify
ERNEL: Linux version 3.10.65 ([email protected]) (gcc version 4.6.3 20120201 (prerelease) (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) ) #203 SMP PREEMPT Wed Aug 10 00:26:03 CST 2016
CODENAME: REL
Mainboard: exdroid
BRAND: Allwinner
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: t3-p1
DISPLAY: t3_p1-eng 4.4.2 KOT49H 20160810 test-keys
FINGERPRINT: Allwinner/t3_p1/t3-p1:4.4.2/KOT49H/20160810:eng/test-keys
HARDWARE: sun8iw11p1
ID: KOT49H
TAGS: test-keys
General Specifications
Manufacturer Allwinner
Model t3
Android version 4.4.2; 20160810; SDK19
CPU 4 cores; rev 5 (v7l) t3; Max: 1200,0 MHz; Min: 480,0 MHz
Display 800 x 480; DPI: 240; Evaluated Size: 3,9"
Touch screen NOT multitouch 1 point
GPU Mali-400 MP; ARM; OpenGL ES-CM 1.1; OpenGL ES 2.0
RAM 1024 MB
Flash 0.125 GB; 16 GB (14.924 GB actual) (see memory map tab)
Communications
Phone None
WiFi 8188eu; IEEE 802.11 b/g/n; Realtek RTL8188E; AP Mode
USB Host Yes
Bluetooth Yes
GPS Yes
How did you root this device? No one succeeded rooting it.
Did you manage to find a suitable ROM for this device? Not only that i couldn't find a suitable rom, or even a way to flash it, but also unable to root after numerous tries with different version of kingroot, kingoroot, baidu root.
I am dumping device info for XT1774 below for reference. There is little info about unlocking, flashing, rooting, stock ROMs, and custom recovery at this time. Hopefully this will help anyone who is working on these things for this model. If there is additional device not displayed here, request it below and I'll attempt to update it.
DEVICE
Model: Moto E (4) Plus (owens_verizon)
Manufacturer: motorola
Baseband Version: M8920_02.02.06.71R OWENS_NA_CUST
RIL Version: Qualcomm RIL 1.0
Build Number: NDR26.58-21
Build Fingerprint: motorola/owens_verizon/owens:7.1.1/NDR26.58-21/21:user/release-keys
Bootloader: 0xBD06
Java VM: ART 2.1.0
OS Version: N MR1 (7.1.1)
SDK: 25
DISPLAY
Resolution: HD, 720x1280 pixels
Software Density: 320 dpi (xhdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 4 (v7l)
Board: msm8937
Chipset: Qualcomm Technologies, Inc MSM8920
Cores: 4
Clock Speed: 960 MHz - 1401 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm aes pmull sha1 sha2 crc32
CPU Governor: interactive
Kernel Version: 3.18.31-perf-g0a8b4dc-00004-gfdbc9d2
Kernel Architecture: armv7l
GRAPHICS
Renderer: Adreno (TM) 308
Vendor: Qualcomm
OpenGL Version: OpenGL ES 3.0
RAM
Total: 1848 MB
Java Heap: 192 MB
STORAGE
Internal: 10 GB
EXTERNAL: Not Detected
PRIMARY CAMERA
Resolution: 13 MP
Flash: Yes
Video Resolution: Full HD, 1920x1080
Supported Resolutions:
Image:
4160x3120
4160x2340
3840x2160
3264x2448
3264x1836
2592x1944
2592x1458
1920x1080
1440x1080
1280x960
1280x720
720x480
640x480
352x288
320x240
Video:
1920x1080 (Full HD)
1280x720 (HD)
960x540 (qHD)
864x480
720x480
640x480 (VGA)
352x288
320x240
176x144
SECONDARY CAMERA
Resolution: 5 MP
Video Resolution: Full HD, 1920x1080
Supported Resolutions:
Image:
2592x1944
2592x1458
1920x1080
1440x1080
1280x960
1280x720
720x480
640x480
352x288
320x240
Video:
1920x1080 (Full HD)
1280x720 (HD)
960x540 (qHD)
864x480
720x480
640x480 (VGA)
352x288
320x240
176x144
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
3-axis Accelerometer
Compass
Orientation
Ambient Light sensor
Proximity sensor
Flat Up
Flat Down
Stowed
Moto Glance Gesture
sx9310-cap
GeoMag Rotation Vector Sensor
Created by Droid Info
you said "custom recovery" in first post.
can you please share the download link for custom recovery
Francesco Franz said:
you said "custom recovery" in first post.
can you please share the download link for custom recovery
Click to expand...
Click to collapse
Yes I meant something like twrp and so far the only thing close that I've seen for Qualcomm was your post. Unfortunately, @w0rdie did not seem to have any luck and has not updates us since.
So I'm hoping that device details may help anyone and will be glad to post whatever details I can pull from the phone if requested. It would be great to get this device unlocked, rooted, twrp, and stock Android. I am apprehensive about trying anything right now because I will be on the road soon with no ability to mess with my phone at the computer. Another thing that bothers me is that you can't remove the battery from this device without a set of tiny star screwdrivers and breaking the warranty sticker.
The firmware for this device appears to be the same firmware labeled for the Moto G4 Play. The build/version info is exactly the same. The only info I don't have for my device to compare is the "Subsidy Lock Config" and "FSG Version", but everything else is identical. Anybody know where to find these on my device and what they are for?
https://androidfilehost.com/?fid=817550096634801571
BUILD REQUEST INFO:
SW Version: owens_verizon-user 7.1.1 NDR26.58-21 21 release-keysM8920_02.02.06.71R
MBM Version: B8.12
Modem Version: M8920_02.02.06.71R
FSG Version: FSG-8953-10.38
Build Fingerprint: motorola/owens_verizon/owens:7.1.1/NDR26.58-21/21:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 26.11.21.owens_verizon.verizon.en.US
Model number: Moto G Play
Android Version: 7.1.1
Baseband Version: M8920_02.02.06.71R
Build Number: owens_verizon-user 7.1.1 NDR26.58-21 21 release-keys
Build Date: Mon Jun 19 18:58:07 CDT 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_vzw_shrt_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.26.11.21.owens_verizon.verizon.en.US
Version when read from CPV: owens_verizon-user 7.1.1 NDR26.58-21 21 release-keys
Click to expand...
Click to collapse
so are people working on root or a bootloader unlock for this model? if soo ill donate.
S7 frp
I been reading just about every where possible on this unit but I've seen mostly joying has a similar unit as this is not a joying unit. Any help would be appreciated*
DEVICE
Model: Sofia 3GR Car (sofia3gr_car_64)
Manufacturer: Rockchip
Baseband Version: SF3GR_M-26.3_cpeg_rk-r2p_bc2-20160629_111639
RIL Version: IMC RPC-RIL 1.0
Build Number: sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.build.20170904.114911 release-keys
Build Fingerprint: Android/sofia3gr_car_64/sofia3gr_car:6.0.1/MMB29M/build09041150:userdebug/release-keys
Bootloader: BOOTCORE_VER
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 58.62 Hz
PROCESSOR
CPU Architecture: x86
Board: rk30sdk
Chipset: SOFIABOARD
Cores: 4
Clock Speed: 416 MHz - 1200 MHz
If someone could help me with a stock firmware or a custom rom
I would be most grateful
PLEASE HELP A MEMBER OUT !
Sent from my SM-G935R4 using Tapatalk
Here what the mcu.txt says
****************MCU LIST************************************************** 1<2017.06.24 09:53:38>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_1_(1_10)" 2<2017.06.24 09:53:38>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_2_(11_20)" 3<2017.06.24 09:53:38>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_3_(21_30)" 4<2017.06.24 09:53:38>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_4_(31_40)" 5<2017.06.24 09:53:38>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_5_(41_50)" 6<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_6_(51_60)" 7<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_7_(61_70)" 8<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_8_(71_80)" 9<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_9_(81_90)" 10<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_10_(91_100)" 11<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_11_(101_110)" 12<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_12_(111_120)" 13<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_13_(121_130)" 14<2017.06.24 09:53:39>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_14_(131_140)" 15<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_15_(141_150)" 16<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_16_(151_160)" 17<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_17_(161_170)" 18<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_18_(171_180)" 19<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_19_(181_190)" 20<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_20_(191_200)" 21<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_21_(201_210)" 22<2017.06.24 09:53:40>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_22_(211_220)" 23<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_23_(221_228)" 24<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_24_(229_238)" 25<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_25_(239_248)" 26<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_26_(249_254)" 27<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_27_(255_264)" 28<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_28_(265_272)" 29<2017.06.24 09:53:41>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_29_(273_282)" 30<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_30_(283_292)" 31<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_31_(293_302)" 32<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_32_(303_312)" 33<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_33_(313_322)" 34<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_34_(323_332)" 35<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_35_(333_342)" 36<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_36_(343_352)" 37<2017.06.24 09:53:42>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_37_(353_362)" 38<2017.06.24 09:53:43>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_38_(363_370)" 39<2017.06.24 09:53:43>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_39_(371_378)" 40<2017.06.24 09:53:43>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_40_(379_388)" 41<2017.06.24 09:53:43>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_41_(389_394)" 42<2017.06.24 09:53:44>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_42_(395_404)" 43<2017.06.24 09:53:44>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_43_(405_414)" 44<2017.06.24 09:53:44>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_44_(415_424)" 45<2017.06.24 09:53:44>"K_MCU_5009_nodisc_7706_RDS_KEY1_20170624_093212_432_45_(425_432)"
Sent from my SM-G935R4 using Tapatalk
Hello guys, i need help with china music...
I have such a radio
ANDROID YT9216B_00002_V004_20190729
SYSTEM : 9.1 XYAUTO: 3,0 (8227L) CAN BUS: 3;0 (8227L)
DDR:4G RASH: 32G cpu: A71.3GHz x 4
DISPLAY 1024*600
MCU1: 3.1 (8227L)
i think this fake.
but i have good prog - AIDA
and that's what she showed
android 8.1 GO
API 23
Android id 343e65327412ca49b
ID assembly YT9216B_00002_V004_20190729
ID MRA58K
version core 3.18.12 ([email protected]) (gcc version 4.8 (GCC)) #5 SMR PREEMPT Mon Jul 29 11 14:39 2019
manufacturer alps
model 8227L_demo
equipment ac8227l
platform ac8227L
product full_8227L_demo
4xARM Cortex A7 @ 1118Mhz
32bit ARMv7