I have in my research not found any way to root this phone using any One Click Root type of thing, I am currently stuck because of my lack of knowledge using MTK Droid Tools (I can see the "root" button when I plug in the device, I know it reads "temporary root" but it is of any use since I can't even make a proper scatter file? (I have the "unknown rom" error))
I need someone to brighten me up on the subject!
Also does installing a custom recovery requires me to unlock my bootloader?
EDIT: I tried the root button and after failing to get temporary root MTK Droid Tools says that I should be able to root the phone using CWM
EDIT2: So I read a bit this evening and I now know that MT67xx chips can't get their scatter file dumped by MTK Droid, so now I am currently looking for a way to get that scatter file...
I am clueless as of now, I really need someone to help me!
I just unlocked my bootloader, I also discovered that in the stock recovery there was an option called "mount /system", what does it do?
I have been looking for more than 8 hours today and I'm kind of feeling hopeless...
So, for anyone who might get any info out of it here are the info of the device straight out of MTK Droid:
Hardware : MT6737
Model : KLIPAD_V355
Build number : Y376C12.DM.HN.V355.KLIPAD.V2.EU.CTS.8+1.7.0.V01.01.2017.07.22
Build date UTC : 20170722-122206
Android v : 7.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P3, 2017/06/06 15:58
Kernel v : 3.18.35 ([email protected]) (gcc version 4.8 (GCC) ) #2 SMP Sat Jul 22 20:23:02 CST 2017
If there's no stock ROM you're gonna need to make your own.
Get a scatter from another device with same chip platform, run 'cat /proc/partitions' and compare.
Dump/read back recovery [and ideally full ROM]
Modify recovery [create twrp]
Flash twrp
Unlocking boorloader might be needed for the above - OEM unlock in dev settings and fastboot
Related
Hey Guys hope someone can help me,
I was following this guide "How to Unlock + Recovery + Root the HTC One M8" from youtube and managed to get into the bootloader atleast thats what I think it is and followed the guide into the fastboot menu, then I had to install the htc file fastboot, well after installing them "android-tools" which fastboot asked for, I went and opened a terminal and after the fastboot oem get_identifier_token:
[[email protected] ~]$ fastboot oem get_identifier_token
< waiting for device >
...
Just gonna normally reboot the device to give you the information from what I already did in settings and some OS info, as for settings its quick: I turned USB debugging: ON, then I made sure I had developer access on the phone I also had to make sure fastboot setting was disabled.
Then for OS info:
Android version:
5.0.1
HTC Sense-version:
6.0
Software number:
4.16.401.10
HTC SDK API-niveau:
Unknown
Kernel version:
3.4.0-g6af28ec
[email protected] #1
SMP PREEMPT
Smallband version: [This is a long one so I am gonna include the first 3 numbers]
1.25 [req for the rest if you think you need it]
Build number:
4.16.401.10 CL448934
So the main problem is what have I missed to do, that my device cant successfully connect to the Android SDK-tools, and I now remember I had the same problem on Windows 7 months ago on my first attempt.
Thanks for any support.
And plz if you point me to a guide also point me to the step that might help me in this process.
Hi Everyone,
Well I have an OBI SJ-1-5 SmartPhone which is not working now as I was trying to Flash a Stock ROM via SP Flash Tool.
I was trying to unlock the bootloader via "fastboot oem unlock" command in fastboot mode. The result was "ok". This device also has "allow bootloader to be unlocked" feature in developer options which was set to "on" while I was doing it. During the process of unlocking it shows some warning message that whole device would be reset, I agree and continue. After which it got stuck and I've to use "fastboot reboot" command, which result in continuous boot loop. Then i was not able to go into recovery or do anything.
I then do some google fu and found Stock ROM which aren't compatible to the device as it was showing the error "PMT has changed for the ROM". Which i sort out somehow. In the mean time I forget to unchecked the "Preloader" option, and unfortunately the new Stock ROM* has incompatible preloader with my Device. Resulting in a Complete Brick of my SmartPhone giving me "BROM ERROR: S_FT_ENABLE_DRAM_FAIL (0xFC0)" error both while doing "Format whole Flash" and "Format whole flash except Bootloader", even "Download" option gives me the same error.
Fortunately I have another pair of same Model so I thought to Dump the Stock ROM including the preloader files and Update my brick cellphone with it. I know the procedure of "Readback", so to grab the "scatter" file I used "MTKdroidTools" which again unfortunately unable to create the "root shell" for my device neither I was able to save the scatter file(the save button was disabled) because my device is MediaTek 6580 which is unsupported to use with "MTKdroidTools". My other cellphone is not Rooted and Rooting is the whole reason I now have a Brick Cellphone so I am not gonna take risk again doing something with that new device .
Which leave me the last option of Using a Hardware Device like "Magic Box" or "Volcano Box" to DUMP firmware. And that I don't have and neither I can somehow get my hands onto it.
But I "think" I can get my cellphone back to life if I would find a ROM of a device with Similar board id and Flash its ROM using (Format+Download). After that it would allow me to use "Auto Format except Bootloader". After which I could flash the ROM that was giving me (0xFC0) error (without ticking the preloader).
Details of SJ1-5
Chipset: MediaTek 6580
Root : No
Build Number : Obi_SJ1-5_B1B8_Ver3.6
Kernal Version : 3.10.72
Android Version : 5.1
Android Security Patch Level : 2016-01-01
*The ROM I tried : Obi_SJ1.5_MT6580_5.1_v1.7.1_151014_144940
I hope someone can provide me the DUMPed Stock ROM from a working Device. I would really appreciate that. And please let me know if there is any other Method that I missed. Sorry for my bad English.
Thank you all in Advance.
Same problem here. As always with mtk phones it is problematic and very risky to find working/compatable scatter and rom. Same story, flashed wrong preloader and now the phone in boot loop. Thinking to connect directly to a serial but i need a correct rom for a start. If anyone has a dumb of this phone please contact me at [email protected]
Hi All,
I would appreciate a little help please?
I have a Samsung Galaxy Xcover4ltexx SM G390F
Bootloader Version: G390FXXU2ARA4
PDA Version: G390FXXU2ARA4
CSC Version G390FXXU2ARA4
BaseBand Version: G390FXXU2ARA1
Android Version 7.0 / SDK 24 (Nougat)
Build date Fri, 26 Jan 2018
I am trying to root this phone.
On the phone Settings in the developer options I have
Turned on OEM unlock
USB debugging is ON
I went with what I thought would have been the quickest and easiest option
And ran KingRoot on the PC. This failed me at 98%
I retried several times to no avail.
I then tried other quick root programs. None would root the phone.
I downloaded Odin3_v3.10.6_plus_CF_Auto_Root.
CF-Auto-Root-xcover4lte-xcover4ltexx-smg390f.tar.md5
I followed the instructions step by step and this failed to root my phone
I tried using all the ODIN PROGRAMS up to Odin3_v3.13.1.
All I have manage to do is wipe my phone and put it back to Factory default settings
3 times. I am sick of rebuilding my phone with all my apps and data.
Can anyone give me a step by step guide in how to root this phone successfully.
Thanks, in anticipation of some good advice.
Flourgrader.
Thanks
Flourgrader said:
Hi All,
I would appreciate a little help please?
I have a Samsung Galaxy Xcover4ltexx SM G390F
Bootloader Version: G390FXXU2ARA4
PDA Version: G390FXXU2ARA4
CSC Version G390FXXU2ARA4
BaseBand Version: G390FXXU2ARA1
Android Version 7.0 / SDK 24 (Nougat)
Build date Fri, 26 Jan 2018
I am trying to root this phone.
On the phone Settings in the developer options I have
Turned on OEM unlock
USB debugging is ON
I went with what I thought would have been the quickest and easiest option
And ran KingRoot on the PC. This failed me at 98%
I retried several times to no avail.
I then tried other quick root programs. None would root the phone.
I downloaded Odin3_v3.10.6_plus_CF_Auto_Root.
CF-Auto-Root-xcover4lte-xcover4ltexx-smg390f.tar.md5
I followed the instructions step by step and this failed to root my phone
I tried using all the ODIN PROGRAMS up to Odin3_v3.13.1.
All I have manage to do is wipe my phone and put it back to Factory default settings
3 times. I am sick of rebuilding my phone with all my apps and data.
Can anyone give me a step by step guide in how to root this phone successfully.
Thanks, in anticipation of some good advice.
Flourgrader.
Click to expand...
Click to collapse
Try Magisk root solution instead !
Hello,
Thought I might help for reference.
If you can find:
CF-Auto-Root-xcover4lte-xcover4ltexx-smg390f.zip
You may need to downgrade to Android 7.0, as some incompatabilities have been reported.
Bye!
Phone Specs :
Model : A250DL (also referred to as TCL LX)
Android : 8.1.0
Arch : armv7
Kernel : 4.4.95+ (gcc version
6.3.1 20170404)
([email protected] #1)
Build Number : vG7a
Custom build version :
alps-mp-o1.mp1-V1.112_k39tv1.bsp_P15
Baseband Version :
MOLY.LR12A.R3.MP.V10.3.P24
Bootloader : U5G7A0A0CT00
(edit)
Seems the device has a mediatek processor, MT6739
I found a twrp build for this processor, however it does not cooperate with SP Flash Tool, the phone comes up then reboots
almost immediately
OEM Unlocking is available in developer settings, however i can't boot the phone into any other mode besides recovery mode. I've tried a number of button combos as well as 'adb reboot fastboot'. If anyone knows how to enter fastboot mode / know of a TWRP build for this device that'd be great. Thanks
Hi I also that the tcl lx I was wondering if you were ever able to get the phone rooted because I've wanted to root my phone but I haven't found a root for it yet if you could get back to my i would appreciate it
steine said:
Hi I also that the tcl lx I was wondering if you were ever able to get the phone rooted because I've wanted to root my phone but I haven't found a root for it yet if you could get back to my i would appreciate it
Click to expand...
Click to collapse
Hey sorry for the late reply I forgot about this thread if im being honest sadly I never made any progress and ended up bricking the device after trying to install twrp with sp flash tool (the scatter file I used wasn't valid). I'll check my history and see if I can find relevant links but there was a twrp build for this somewhere. The problem for me was getting a scatter file which lead me to bricking. However there is a new exploit for mediatek cpu's (mtk-su) its only been tested on a couple Amazon devices (it was developed as a software root exploit for some Kindle's) but it may work for this as well. I will warn you now though if you end up bricking this it's impossible (to my knowledge) to restore it. Best of luck !
Has anyone made any progress or seen any threads that have gotten further? Just got this phone myself to replace my last as it ended up being same price as said last phone but its an upgrade to boot.
crazypwn said:
Has anyone made any progress or seen any threads that have gotten further? Just got this phone myself to replace my last as it ended up being same price as said last phone but its an upgrade to boot.
Click to expand...
Click to collapse
Also looking for help on rooting this phone. Has anyone found it yet?
There are three major obstacles with rooting this device. First, there doesn't appear to be any type of exploit or official support for unlocking the bootloader. Second, the boot chain is secured with AVB 2.0 signing. Third, the kernel is coded with dm-verity. So, even if SP Flash Tool could be used to flash the boot partition with a patched boot image (systemless root), the secure boot chain will detect the modification and fail to boot the OS. Likewise, if SP Flash Tool could be used to push a pre-rooted system image (system-wide root), device mapping will detect the change to /system and fail to boot into the OS. Like many TCL devices running more recent Android versions, it appears that the Alcatel A250DL cannot be rooted.
Mtk-su seems to work fine
Mtke-su seems to work fine:
github -> /JunioJsv/mediatek-easy-root/blob/master/app/src/main/assets/mtk-su
Log:
param1: 0x1000, param2: 0x8040, type: 13
Building symbol table
kallsyms_addresses pa 0x40eda580
kallsyms_num_syms 51245, addr_count 51245
kallsyms_names pa 0x40f0c650, size 671079
kallsyms_markers pa 0x40fb03c0
kallsyms_token_table pa 0x40fb06f0
kallsyms_token_index pa 0x40fb0a70
Patching credentials
Parsing current_is_single_threaded
c04e5d58: LDR Rt, [PC, #128] ; 0xc04e5de0
init_task VA: 0xc140c578
Potential list_head tasks at offset 0x2b0
comm swapper/0 at offset 0x454
Found own task_struct at node 1
cred VA: 0xd7cf8b80
thread_info flags VA: 0xcd2de000
seccomp mode VA: 0xc3fc4930+20c
Parsing avc_denied
c0485bbc: LDR Rt, [PC, #84] ; 0xc0485c18
selinux_enforcing VA: 0xc15a56d4
Setting selinux_enforcing
Switched selinux to permissivearmv7l machine
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
returned 0
---------- Post added at 10:46 AM ---------- Previous post was at 10:23 AM ----------
Nevermind....no super app binary installed
Viva La Android said:
There are three major obstacles with rooting this device. First, there doesn't appear to be any type of exploit or official support for unlocking the bootloader. Second, the boot chain is secured with AVB 2.0 signing. Third, the kernel is coded with dm-verity. So, even if SP Flash Tool could be used to flash the boot partition with a patched boot image (systemless root), the secure boot chain will detect the modification and fail to boot the OS. Likewise, if SP Flash Tool could be used to push a pre-rooted system image (system-wide root), device mapping will detect the change to /system and fail to boot into the OS. Like many TCL devices running more recent Android versions, it appears that the Alcatel A250DL cannot be rooted.
Click to expand...
Click to collapse
yeah after much research I was just going to make this phone a youtube/remote for my older tv . . . .I found no options either. .
Magisk Rooting
Unlocked Galaxy A10e(SM-A102W/Canada)No OEM Unlock OptionDevice Details
Hardware
Model: Samsung Galaxy A10e(SM-A102W/Canada)
Android version: Android 9(Pie)
System Partition Type: A-Only System Partition
Chipset: Exynos 7884
CPU Architecture: ARM 32-bit(NOT ARM64)
System-as-root: Supported
Software
Baseband version: A102WVLS3ATB1
Kernel version: 4.4.111-16763710
#1 Fri Feb 28 18:33:54 KST 2020
Build number: PPR1.180610.011.A102WVLS3ATB1
SE for Android status: Enforcing
SEPF_SM-A102W_9_0009
Fri Feb 28 18:21:51 2020
Knox Version: Knox 3.3
Knox API level 28
TIMA 4.1.0
Service provider SW version: SAOMC_SM-A102W_OYV_SOL_PP_0008
RF8N20K9RSJ
SOL/SOL/XAC
I've recently purchased an unlocked Samsung Galaxy A10e(SM-A102W) from Walmart and had it set up with Lucky Mobile, I purchased this device with intentions to root/modify after a quick Google search before I took off. I had asked the salesperson who had sold me the phone if it could be done, he told me yes and so far I've spent the last 5 days fixated on trying to get this phone rooted.
So far I've tried,
Enabling Developer Options
Enabling OEM Unlock | No option in Developer tools even after removing Google/Samsung accounts, Auto Updates > Off, playing with date/time settings, Auto Updates > On and re-flashing stock firmware
Enabling USB Debugging
Downloading stock firmware with frija and SamFirm *DEPRECATED applications.
Extracting AP file from stock firmware, copying to Internal Storage on Galaxy A10e Device
Downloading and installing MagiskManager.apk(7.5.1)
Patching AP file from stock firmware with Magisk Manager app on Galaxy A10e Device
(I have tried multiple patched AP files, from ones containing just /Meta-data/, boot.img, recovery.img and vbmeta.img to ones containing every .img)
Copying Patched AP file(magisk_patched.tar) from Internal Storage onto PC
Booting into stock recovery, Download/Bootloader mode | Is Bootloader already unlocked?
Flashing Patched AP file with Odin3B PatcheD/ModdeD v3.14.1 | Options set are "F. Reset Time", although I've tried "DeviceInfo", "Flash Lock", and "Decompress Data"
(I've heard with this model not to use "Auto Reboot"; using "Nand Erase" or "Re-Partition" will most likely damage your device!)
Galaxy A10e device returns message "SECURE CHECK FAIL : (BOOT)", "SECURE CHECK FAIL : (VBMETA)" and depending on the nature of the Patched AP file I used, I may or may not have to re-flash the stock firmware
In short, I'd really like to figure out if I can and/or how to root this device as of now.
Is there a reason my OEM unlock option isn't showing up in the developer tools?
Is going through the stock recovery(Pwr + Vol. UP, release Pwr on logo) and selecting Bootloader, proceeding to go into Download mode, mean my Bootloader is unlocked?
Tools and Resources
Patching/Flashing Software
- MagiskManager
- Odin
Official Samsung Stock firmware Applications
- frija
- SamFirm | *DEPRECATED
Official Samsung Stock firmware
- A102WVLS3ATB1
I also need to unblock the bootloader of this Samsung A10E to try to root.
I have tried to enable oem unlock with some manuals but this model has resisted.
Any luck?
Well, i also need help on that. I've successfully modded phones in the past, but i can't seem to find the hang of that particular model.
Any help appreciated. Thanks !