I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM on AT&T
WIFI A/B/G/N 2.4ghz
Bluetooth 4.2 LE
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
USB 2.0 port, 3.5mm jack
Root
clcombs262 said:
I have an Alcatel Tetra running Android 8.1, June 2018 update, and I would like to root it. It was only released in September 2018, though, so there seems to be no common solution.
Some specs are:
480x854 resolution on 5" screen @ 70hz
1.1ghz MediaTek MT6739WM CPU
2gb ram
4G LTE GSM
WIFI A/B/G/N 2.4ghz
Android 8.1, June 2018 update
16gb internal storage with support for 128gb sd card
GE8100 GPU
5MP front camera & 2MP back
Click to expand...
Click to collapse
I have one also id like to root
I also have this phone. Almost cobbled together a twrp but just need the correct recovery-kernel & offset file to repack it. As it stands right now the twrp build will boot loop, but I know all the other pieces are solid ( correct resolution set, correct prop.default, fstab files, .rc files and so on) unfortunately so flash tools is useless until we can get a custom DA file that works with the Tetra. This whole process has been quite a pain lol but I'm close. If I can get it figured out I'll make a thread here upload all relevant files
Update: I'm currently using a few different RATs to pull any and all files possible while also trying to see what exploits (if any) I may be able to leverage with them. currently still lacking the recovery.fstab, but all other files needed for the ramdisk folder section of the recovery.img is set (put together the prop.default from scratch as I can't pull it from the phone). Still need all files outside of the ramdisk folder though (mostly just a proper recovery-kernel and offset, think I may be able to substitute the other files from a similar Alcatel MT6739 phone, the 3x/5058, which I have a stock firmware for). I also have the source code for the 4.4.95+ kernel that's on the Tetra, digging through it to see if I can use anything from it. If anyone has any thoughts about what could be done with all this stuff I have please feel free to share, as I could use some fresh eyes on this.
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro??
Click to expand...
Click to collapse
#1. There is no publicly available fw for this device as of this moment to patch with Magisk.
#2. Sp flash tool cannot currently readback or download to this phone, as the necessary DA file is unavailable. That means no way to get the boot.img or recovery.img to make magisk root/port TWRP
#3. NO ROOTING APPS WHETHER THEY BE APK OR PC BASED, WORK WHATSOEVER ON THIS PHONE, AND 80% OF THEM ARE BORDERLINE MALICIOUS (HERE'S LOOKING AT YOU KINGROOT)
#4 please kindly ****post elsewhere.
Root Alcatel Tetra
MICHAEL(SMHOS.ORG) said:
Just use magisk to root ,or ONE click root for PC is easy bro
Click to expand...
Click to collapse
I know for a fact One Click Root has no support, and Magisk is unreliable in my experience. I think I may have a way to apply a root patch, but obviously I need the patch first. I believe I can exploit the "apply update from sd card" function but haven't really tested it.
MICHAEL(SMHOS.ORG) said:
OK try it and check if any patch or so,because I use Flashing tools like Gsm alladin cracked or android adb multi tool since it support adb function for root
Click to expand...
Click to collapse
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
cthulu_rises said:
There is currently no adb exploit to gain root that works on this device. Trust me, I've tried. There is not an easy fix for this phone. The only options I see, is for someone who has access to the most recent NCK box, or Miracle thunder MT2 ( which added support for the mt6739 chip set) to dump the firmware and share It with the public, or for the Download Assistant file for this phone to be released, at which point SP flashtools can be used to dump the firmware, at which point a custom TWRP can be ported, root can be gained, and bob's your uncle. I've spent the last month going over every possible way to crack this phone open, and aside from finding/developing an as of yet unknown exploit, the only options available require a firmware dump (which currently can only be made with the 2 aforementioned box tools). I've been using every method I can think of to get a functioning TWRP without the stock recovery, with no luck yet. Ive taken every possible amount of info and files accessable from the phone using adb shells, mtk based tools, and RATs. I've got ahold of pretty much all publicly available firmwares and TWRPs for other Mt6739 phones that are already cracked, to see if I could take the files/Info and modify them to fill in the gaps and get a functional TWRP. Hasn't worked yet and while I've narrowed the reasons why down, those reasons seem to be hard blocks that could only be overcome through root access/access to the Tetras specific firmware. Which as you see is a catch 22 where you would need root to get root. I've even tried to get ahold of an ota update directly from AT&Ts cdn to try and exploit. I have the dl address but am not sure how to use it, as trying to connect to it from phone browser or PC just returns as forbidden. I'm honestly a little burnt out with it at the moment and am gonna go mess with some other phones I have and come back to this later when/if hopefully some new resources become available.
Tlr ; the easy and common solutions aren't gonna cut it, so save your breath
Click to expand...
Click to collapse
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu, or if you have an activity launcher.... exploitable, maybe?
Also, you must remember that those people are just people like you and me, with more experience. Since this phone was released September of this year, it may be awhile. So we may be on our own since the Tetra is a lower end device. I got a system dump, which I know can be used ro make firmware, but am not sure how to do so
clcombs262 said:
/
+1 on the no easy solutions. In theory, there is a utility built in to flash an update from an sd card from fastboot menu.
I got a system dump
Click to expand...
Click to collapse
Only way to use stock sideload would require you to sign the zip with the manufacturer private keys. I did pull some keys & certs from the phone but never got a chance to see if they were the proper ones.
And pls upload your system dump
Dont use this, see next post
Last post was the wrong file.
Here you'll find:
*DA file
*Auth file
*Preloader
*.mbn
*.sca
All specific for the 5041c, direct from Alcatel
https://drive.google.com/file/d/1FS0MFuoFSRlSncuUUtsZM808fqypUmue/view?usp=drivesdk
Yo OP what's up with that system dump?
cthulu_rises said:
Yo OP what's up with that system dump?
Click to expand...
Click to collapse
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
clcombs262 said:
It ll be awhile. My ssd took a dump and died last night and I don't get paid for 2 weeks, so can't afford a new one.
That zip wasn't backed up unfortunately. So right now I have no pc
Click to expand...
Click to collapse
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
See next post
cthulu_rises said:
Dang sorry to hear that brotha. Do you remember what method you used to get the system dump? I can try my hand at it
Click to expand...
Click to collapse
The primary code I used was
Code:
adb pull /system
adb pull /data
I may have used other code; I don't remember. It's been awhile.
Also, so my friends will stop asking, will you post how to root/flash recovery with what you provided? It'll be easier to link to the post then explain it 500 times, since I end up their IT guy a lot. Thanks in advance
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
cthulu_rises said:
Take the Da file, auth file, and scatter file provided and load them in the latest version of SP Flash Tool, use the readback function to dump the recovery img. If memory serves me correctly, mmcblk0p18 is the location for it. (use the scatter file to locate the begining address and the length for it). Once you have the stock recovery img, manually port twrp to it using carliv image kitchen. Then fastboot to flash twrp. If you did it right then you can boot into twrp and flash supersu or magisk for root. Make sure to boot directly into recovery after flashing, because the recovery gets replaced by stock after a normal boot
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
I would have posted more already but have no access to PC for a while. I haven't even had a chance to do this for myself yet
Click to expand...
Click to collapse
I have access to a library pc, but youre not allowed to install anything. No adb or sp flash tool. Though i do have a theory about using stock recovery...
Probably wont work, but hey. YOLO. Still waiting for my ssd to be in stock
Well here's the stock ROM. Cut SP flash Tool and all its hassles out and use this. Just extract the recovery.img and port twrp, or extract boot.img and patch with magisk. Am gonna do this when I get home, I have a beater laptop I can use but no internet there, so I'll post my work the next time I can come to town and get cell service.
https://mega.nz/#!dpFmBIgI!4FXN0VYjTYSyMp608BCCDOtEVABHqOwoJPBx_OkaKrE
This zip contains the magisk patched boot.img, happy rooting!
Related
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
I want to port TWRP to the 5044T which I believe is a Alcatel U5 which was sold as an Optus X Spirit
I want to create a backup of the device using MTK Tools before I start destroying my IMEI etc.
The MTK Tools 2.5.3 when run on this phone using USB debugging reveals the following:
Hardware : MT6737M
Model : 5044T
Build number : MRA58K release-keys
Build date UTC : 20171103-051806
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V81.6.P59, 2017/11/03 13:15
Kernel v : 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP Fri Oct 27 10:41:26 CST 2017
But it also stops there saying the following on the right:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I think I need a scatter file or to understand how to build one in order to continue? Can anyone with experience help me? I can follow instructions so long as their windows 7 64 or ubuntu compatible? I would still need help with the porting process for TWRP, I read a few guides, one didn't tell explicitly what to do but gave a general overview and up to you to learn the steps individually. The other guide I read was specific but didn't tell you what the specific command entered would do.
Please help, I'd like to backup and root this device and i'm willing to by a couple more of them for testing/rooting/porting purposes.
ID10T_Error said:
I want to port TWRP to the 5044T which I believe is a Alcatel U5 which was sold as an Optus X Spirit
I want to create a backup of the device using MTK Tools before I start destroying my IMEI etc.
The MTK Tools 2.5.3 when run on this phone using USB debugging reveals the following:
Hardware : MT6737M
Model : 5044T
Build number : MRA58K release-keys
Build date UTC : 20171103-051806
Android v : 6.0
Baseband v: MOLY.LR9.W1444.MD.LWTG.MP.V81.6.P59, 2017/11/03 13:15
Kernel v : 3.18.19 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP Fri Oct 27 10:41:26 CST 2017
But it also stops there saying the following on the right:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I think I need a scatter file or to understand how to build one in order to continue? Can anyone with experience help me? I can follow instructions so long as their windows 7 64 or ubuntu compatible? I would still need help with the porting process for TWRP, I read a few guides, one didn't tell explicitly what to do but gave a general overview and up to you to learn the steps individually. The other guide I read was specific but didn't tell you what the specific command entered would do.
Please help, I'd like to backup and root this device and i'm willing to by a couple more of them for testing/rooting/porting purposes.
Click to expand...
Click to collapse
Well for starters is your device 64bit?
Pretty sure MTK root tools does not support x64 bit architecture
Also generating a scatter file is not an easy task(nor safe)
Ricky Divjakovski said:
Well for starters is your device 64bit?
Pretty sure MTK root tools does not support x64 bit architecture
Also generating a scatter file is not an easy task(nor safe)
Click to expand...
Click to collapse
Yes I believe the device is 64bit, 6.06gb used of 8gb so cpu must be 64bit? Also chipset MT6737M is 64bit capable.
So I now understand that MTK Tools incompatible with 64bit? Who wrote MTK Tools and how do I influence them to them to update it?(prolly somthing I should use search to figure out, and I will. And search yeilds that MTK tools thread is under new managment)
scatter file is listing of start memory addresses for the system images? Yeah I can see how finding them in memory without the actual pointers would be difficult but if I may ask for a brief overview of how this kind of dev is done? Do they search memory for partition table or ext2,3,4 innode or somthing? If ya don't have the time please disregard this request.
Also if I buy another Optus X Spirit and mail it to you will you join the fight to free the image from the manufacturers control?(Prolly gonna be white, never seen a black one yet. But i'll put it in a black case as consolation. (BYO SDCard, and you will need one because it starts out with 1gb free!)
ID10T_Error said:
Yes I believe the device is 64bit, 6.06gb used of 8gb so cpu must be 64bit? Also chipset MT6737M is 64bit capable.
So I now understand that MTK Tools incompatible with 64bit? Who wrote MTK Tools and how do I influence them to them to update it?(prolly somthing I should use search to figure out, and I will. And search yeilds that MTK tools thread is under new managment)
scatter file is listing of start memory addresses for the system images? Yeah I can see how finding them in memory without the actual pointers would be difficult but if I may ask for a brief overview of how this kind of dev is done? Do they search memory for partition table or ext2,3,4 innode or somthing? If ya don't have the time please disregard this request.
Also if I buy another Optus X Spirit and mail it to you will you join the fight to free the image from the manufacturers control?(Prolly gonna be white, never seen a black one yet. But i'll put it in a black case as consolation. (BYO SDCard, and you will need one because it starts out with 1gb free!)
Click to expand...
Click to collapse
There is a 64bit MTK tools thats experimental from my understanding, but last time i attempted use out of it, the tool failed miserably when trying to detect the device.
I have no idea, i havent looked into it, but im pretty sure i rooted a 64bit mtk device before with dirtycow(check out my github root repo for drammer), the tool provides a console output so you can see exactly whats being done, however it also depends on the kernel patch level as this was recently fixed finally after decades without even being heard of.
If your willing to donate a device then sure, im willing to give it a shot.
Ok will try and pick one up tomob i'll send you a pm when I get one to get an address to send it to.
Will probably take a week or so, i'm behind cash wise so I need a little time to catch up.
twrp for alcatel u5
I am looking for working twrp for alcatel u5? anyone can help
I am also interested in this; however, I can't even get the device to fastboot mode. Is it Power + Volume down? Because that just leads me to the battery charging screen. adb does not recognise the device.
Dont think you can
I think this is what your looking for. Never use to be there. so someone has discovered it hardreset.info/devices/alcatel/alcatel-optus-x-smart/fastboot-mode/
Che0063 said:
I am also interested in this; however, I can't even get the device to fastboot mode. Is it Power + Volume down? Because that just leads me to the battery charging screen. adb does not recognise the device.
Click to expand...
Click to collapse
Pajuatu said:
I think this is what your looking for. Never use to be there. so someone has discovered it hardreset.info/devices/alcatel/alcatel-optus-x-smart/fastboot-mode/
Click to expand...
Click to collapse
Is there no fastboot method? Because otherwise I will not know another way to flash a custom recovery.
Use NCK dongle to backup your rom and imei, i personally have done it,
But using nck dongle you will not get the pre loader and 1 or 2 other files also will be missing, but it backs up the main system etc and also give you a scatter file,
Dont try to flash U5 firmware to it either it will give you chip error mismatched,
Alternatively you can obtain a full backup of each partition with SP flash tools read back option,
To do this use NCK dongle, open it once open select chip type as MT6737 then on the same page click "boot info" now plug the device in switched off and it will read all of your partition adresses and save them in a txt file,
From the txt file enter each address into SP flash tools readback option and it will backup each partition perfectly including the preloader,
As for flashing TWRP you can use SP flasht tool just click on the recovery tab and select the TWRP image when available,
I havent had a full chance to have a look at if it has fastboot or not but it definitely does not have Meta connection to it only flash so far ive found,
With entering fastboot also have yous tried through adb,
Adb reboot bootloader
? Does that not work i have a chinaphone MT6572 that has no visual fastboot only a black screen but i can issue fastboot commands such as getvar and what not maybe worth a try ill be doing the same when i get some time to look at it only just got it to day
Hey all managed to have a look at it today,
Turns out the optus X spirit is not actually 5044T vit rather 5044D but flashing U5 firmware has been prohibited as optus have added something to it to prevent it from flashing,
As for fastboot mode thats a no go it dosent have it,
Dev options has OEM unlock but what goods that when nothing can be done with it and as its a production build it cannot be remounted to add SU binary or Magisk binary for root, and cant remount with adb insecure as it requires root to run,
All my other rooting apps have failed but ill keep delving into it to see if something can be done about it as fastboot can after all be added to it as its within the firmware and is more than likely disabled within the build.prop im thinking.
Es file explorer can access /system and all contents within aswell as copy from but nothing can be deleted or copied to /system without root privledge,
Matty1993 said:
Hey all managed to have a look at it today,
Turns out the optus X spirit is not actually 5044T vit rather 5044D but flashing U5 firmware has been prohibited as optus have added something to it to prevent it from flashing,
As for fastboot mode thats a no go it dosent have it,
Dev options has OEM unlock but what goods that when nothing can be done with it and as its a production build it cannot be remounted to add SU binary or Magisk binary for root, and cant remount with adb insecure as it requires root to run,
All my other rooting apps have failed but ill keep delving into it to see if something can be done about it as fastboot can after all be added to it as its within the firmware and is more than likely disabled within the build.prop im thinking.
Es file explorer can access /system and all contents within aswell as copy from but nothing can be deleted or copied to /system without root privledge,
Click to expand...
Click to collapse
Do you have any stock ROMs for Alcatel 5044r? If you do I am looking for stock rom Android 6.0 or 7.0 thank you.
Skrappy187 said:
Do you have any stock ROMs for Alcatel 5044r? If you do I am looking for stock rom Android 6.0 or 7.0 thank you.
Click to expand...
Click to collapse
5044r is at&t alcatel idealXCITE correct ?
Matty1993 said:
5044r is at&t alcatel idealXCITE correct ?
Click to expand...
Click to collapse
Yes it is it is also officialy called Element5 or Element 5 (I don't know if that space between the T and 5 changes anything) plus I see it called as you posted and also called something with a C. Can't remember. I will post device info by CPU Z screen shot will that help?
Skrappy187 said:
Yes it is it is also officialy called Element5 or Element 5 (I don't know if that space between the T and 5 changes anything) plus I see it called as you posted and also called something with a C. Can't remember. I will post device info by CPU Z screen shot will that help?
Click to expand...
Click to collapse
Hope this helps....my device is not a MTK device rt?
Skrappy187 said:
Hope this helps....my device is not a MTK device rt?
Click to expand...
Click to collapse
Hey mate,
Your right out of luck there unfortunately i cant find firmware anywhere for it which is very unusual theres no reference to the model number anywhere for firmware
Wow these phones are absolute peices of ****,
So there's OEM unlock in developer options, BUT
Theres no fastboot at all, and also when pulling a backup of the friggen firmware it cant be flashed back optus have done something to it so it wont pull the preloader and a few other files, and what files it does pull wont flash back with SP Flash tool anyway gives an error & when trying to load the scatter file after the failed flash it cant be loaded again gives alot of errors with the file and nothing can be loaded to be flashed,
Also with the model number these are actually 5044T as SP flash tool confirmed this but also compatible with 5044D firmware as i used the .exe for 5044D to try and flash it and it would have if optus didnt block the international code to block the flash from happening,
Ill keep stabbing at it but im thinking the OEM unlock is purely there for asthetic purposes only unfortunately so without being able to flash anything back to it its not even worth editing the recovery and packing it with TWRP ramdisk as it cant even be flashed
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Skrappy187 said:
Hope this helps....my device is not a MTK device rt?
Click to expand...
Click to collapse
Look for other versions of firmware for it that sre qualcomm and not mediatek,
These mediatek can traditionally use T & D firmwsee if it wasnt for the flash block,
Just make sure they are qualcomm worth a try as i still cant find a firmware for your model but if i do find one ill get the link to you here
Matty1993 said:
Wow these phones are absolute peices of ****,
So there's OEM unlock in developer options, BUT
Theres no fastboot at all, and also when pulling a backup of the friggen firmware it cant be flashed back optus have done something to it so it wont pull the preloader and a few other files, and what files it does pull wont flash back with SP Flash tool anyway gives an error & when trying to load the scatter file after the failed flash it cant be loaded again gives alot of errors with the file and nothing can be loaded to be flashed,
Also with the model number these are actually 5044T as SP flash tool confirmed this but also compatible with 5044D firmware as i used the .exe for 5044D to try and flash it and it would have if optus didnt block the international code to block the flash from happening,
Ill keep stabbing at it but im thinking the OEM unlock is purely there for asthetic purposes only unfortunately so without being able to flash anything back to it its not even worth editing the recovery and packing it with TWRP ramdisk as it cant even be flashed
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Look for other versions of firmware for it that sre qualcomm and not mediatek,
These mediatek can traditionally use T & D firmwsee if it wasnt for the flash block,
Just make sure they are qualcomm worth a try as i still cant find a firmware for your model but if i do find one ill get the link to you here
Click to expand...
Click to collapse
Thank you bro....it looks like you gave it your all....thank you again.
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Matty1993 said:
Hey mate,
Your right out of luck there unfortunately i cant find firmware anywhere for it which is very unusual theres no reference to the model number anywhere for firmware
Click to expand...
Click to collapse
I did find a PC root method for this device do that help? If so let me know. Also the Linux to Dos explot do reboot my device if a home brewed root needs to be done.
Skrappy187 said:
Thank you bro....it looks like you gave it your all....thank you again.
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
I did find a PC root method for this device do that help? If so let me know. Also the Linux to Dos explot do reboot my device if a home brewed root needs to be done.
Click to expand...
Click to collapse
Yeah go on ill get details and give it a whirl if i can get root shell access i can push my TWRP i made to it through ADB shell thats all thats stopping me from trying that,
Also made a philz_recovery.img for it but cant test it as the scatter wont load to flash the recovery im trying to build a scatter as i found it wont load due to illegal information within the scatter.file itself through some investigation, i just have to find the illegal info & remove it to allow flash hopefully
But if i can get root & root shell i can just push it and if all works i can just upload the method here on how to do it until i work the scatter out
Had a bit of success,
Ive finally managed to pull the preloader and all other missing files,
Now i can make a scatter file that will work for it hopefully and i can port a recovery to it for rooting,
Ill update progress as i go
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Enough. Seriously.....
Keep it clean, and on-topic... The rules are there for a reason. Don't remember them? HERE you go.
Adromir said:
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Click to expand...
Click to collapse
If you want the files
Then can you please update your Sheild tv to the latest firmware for us 7.2.2
An back up the recovery.img
An back up your build.prob
Because I can't help you! I refuse!
Thx again have a great day
i hope you can port the twrp to nvidia sheild tv thx
Foster_e (Shield TV 2015 16GB) - 7.2.2 (30.7.130.7)
recovery.img + build.prop
https://drive.google.com/open?id=18E_u8as1E9dstmRtRwPb97hALdmsrdsc
The recovery is dumped directly from
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS -> /dev/block/mmcblk0p16
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Downunder35m said:
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Click to expand...
Click to collapse
So if I understand you correctly the only way that a recent version of TWRP would work on 7.21 and above are if you have a "rooted" developer image? I have stayed with 7.1 (rooted with a flashed TWRP recovery) My expectation is that Ill stay with it until a stable version is released.
Odd thing is every OTA notification I get refuses to install. It just boots to TWRP without updating. I even opted in for the 7.2.2 beta updates and the shield refuses to update. Kinda thankful as others seem to have so many issues, just not worth it until 7.3 is released perhaps?
Any decent update is worth applying.
But if you ask if it is worth it for those really needing full root access then the answer is no.
The cummunity behind the shield might not be as big as behing Samsung devices but I am sure something will be figured out sooner or later.
@Downunder35m : As I mentioned in a deleted Post, I know how to get these Files from the recovery images. But they are Still 7.2.1 and as 7.2.2 already I didn't see a point in starting with already Outdated Files.
What kind of Things have you been trying already? My Approach was, that maybe TWRP hangs itself, because it can't find the Vendor and system Partition. After unpacking the recovery.img i found out, that the partitions still get mounted, but not over over the fstab anymore but single commands in some init scripts. So my Idea was to patch the kernel of the recovery image with a proper fstab and then use that to build a twrp around it, with the modified boot image. But sadly the resulting TWRP exceeded the Partitionsize. But i didn't set up the Source Tree to compile correctly, because I assumed that with such a breaking approach nvidia did at least moved onward to Android 8.1 ..
A real life job sadly limits my time far more than what I would like.
So maybe my failures are of use to you...
Lets start with the basics:
(All for the 2017 model!)
Firstly, the bootloader has changed and now enforces basically everything Google has on offer.
This means you can not just boot into a custom recovery because the bootloader does not accept it as genuine.
Lets say you get around this problem by, dor example, compiling TWRP from source and with the not yet realesed NVidia 7.2 sources.
There might be other ways but right now I think we can't get around compiling it from scratch.
Once you are able to somehow properly boot into TWRP there is more problems:
A lot if not all special rights and permissions are now handled almost exclusively by the DTB, or to be precise the DTS, which is compiled during boot.
By default TWRP does not make any use of the DTB but instead relies only on the FSTAB configuration.
And since TWRP is not an authorised service, task or app the bootloader won't provide the required rights.
The system partition stays invisible, the vendor part locked and since TWRP is required to copy or store at least some things somewhere this is detected as a possible intrusion.
As that the bootloader now marks the entire system as compromised - the dreaded corrupted system message appears and the system fails to boot.
You could tweak the init files, get the complete FSTAB info from the plat - and nonplat_file_contexts and even fiddle with the rest.
Then you get this happy feeling of a booting TWRP, pull a backup and think all is fine.
That it until you try to reboot and nothing works anymore.
The backup is useless as firstly you can not write it back and secondly it will be encrypted or otherwise corrupt.
To be able to use TWRP ADBD must be able to run in root mode, this is not possible by default on a user or release build, which NVidia now provides as a "developer" firmware.
A bootloader set to enforce all SeLinux and DM-Verity funtions will not allow any vital modifications to any vital part of the system.
In theory you must first at least free the bootloader (we can not do that) or destroy the safety, like by using a modified DTB.
Then you must make sure that you modifiy the prop files so full ADB and ADBD rights are available where they are needed.
After that TRWP will run just fine but it creates a cricle that first needs to be broken somehow
No root rights means no TWRP, no TWRP means no mods to the system.
Magisk currently fails to help us as it does not make use of DTB features at this stage.
And if you ask me then messing with the DTB can backfire badly.
Unlike normal firmwares we won't get a DTB partition included in the boot image or kernel image.
So once the dTB is stuffed too much it will be hard to impossible to install a genuine or custom firmware.
Once Pie comes out this will be worse.
Here the DTB too will be protected and generated/checked during boot.
Unless NVidia wakes up and removes these restrictions from the developer firmwares we will be locked out until someone finds a way to restore full root rights.
Right now I am hopin they will still release the full sources one day.
With a massive effors one could then just compile a normal userdebug firmware and all is fine once more.
Any luck yet? I upgraded one of my Shield TV to 7.2.2 from 7.2.1 dev root and want to install Magisk....
Thanks!
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
UPDATE: Boots but not working correctly so removed links
leezaal said:
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
Click to expand...
Click to collapse
Every time i open recovery it works, but after trying to reboot it bootloops at nvidia. I flash-all and it works again until i enter recovery (then botloops again on reboot). Am i missing something? (shield 2017 7.2.3 dev edition)
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1BCfXg9pUpFm_3sPXp_nEwBlkNU9nelkg/view?usp=sharing
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
there is always the bug for 4k screen display?
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
Many thanks i renamed this to recovery.img and renamed magisk boot img to boot.img reflashed both as part of the whole 7.2.3 dev OS shield tv 2017 image.
booted into TWRP via adb from my pc it loads up fine on my LG 43" 4k tv no problem rebooted and got back into 7.2.3 also without any issues
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
twrp seems complicated to be functional lately, the same on my mi max 3, but orange Fox might be better on Shield
leezaal said:
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
Click to expand...
Click to collapse
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
rootfan said:
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
Click to expand...
Click to collapse
Thanks for the great feedback will DL the updated TWRP and give it a go will report back shortly
UPDATE: 100% working ! Amazing work all partitions mount etc no problem FULLY working TWRP on my 4k TV too
After many searches for the best help on my new Asus ZenFone V V520KL, I have no way to unlock the bootloader. Asus doesn't provide any support for this 2017 model, nor does Verizon, the company the phone was made for.
It comes stock with Nougat 7.0 OS, 32 GB ROM & 4 GB RAM. It's got a decent size screen and runs not too too bad.
I'm wondering if one of the tech people here would be so kind as to help me with not only unlocking the bootloader so I can then install a custom recovery image, preferrably TWRP, since I have used this type of program before on my other ZenFone 3 Zoom.
I already have ADB tools on my Windows 7 notebook (32-bit). I used it to install the last root on my other aforementioned phone so it will work.
What I'm wondering about is the bootloader unlock tool, custom recovery image (TWRP), and a way to root the bastard. Hopefully we can relock the bootloader after the job's done because it's annoying on my other phone to always have to bypass the "Can't check for corruption." screen before the phone actually boots. Again this is for the Asus ZenFone V V520KL model. There is really no information anywhere right now I know of that gets this job done.
Having a custom Pie 9.0 ROM upgrade would be the best if possible once we root the device.
My name is Andrew, S.D. from Canada.
Thanks and blessings.
Root
Did you find a way to root it?
No, I still need help with the original post. I can root the ZenFone 3 Zoom ZE553KL but they already tell us how to do that in another forum.
the Bootloader for v520kl is already unlock by ENG Firmware
Just serch it in forums
You're talking to a noob. Give me the location of ENG firmware.
Hi friend, in the other post de link for downloading de ENG Firmware is broken
[email protected] said:
Hi friend, in the other post de link for downloading de ENG Firmware is broken
Click to expand...
Click to collapse
This is the link
http://www.mediafire.com/file/lc17b75qbvy018z/Asus_Zenfone_V_V520KL_All_WW_ENG_T3.3.15.zip
I tried to flash it did not work for me..
---------- Post added at 10:55 PM ---------- Previous post was at 10:43 PM ----------
Doctor Andrew said:
You're talking to a noob. Give me the location of ENG firmware.
Click to expand...
Click to collapse
Here is the link:
https://forum.xda-developers.com/showpost.php?p=78833735&postcount=52
Hi friend,
It's de the same rom for this page
https:
www
hardreset.info/devices/asus/asus-v520kl/faq/firmware/ because, the size of this rom is 813MB
and the size of the rom of the link that you provide is 775.53 MB and the files is the same name.
or this rom has been updated.
someone know what version of android have this rom
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Doctor Andrew said:
Okay so we now have a link to just the ROM it looks like. Do we have a way to unlock the bootloader yet and install TWRP first? What about the TWRP image file, do we have one of those as well?
Click to expand...
Click to collapse
To flash the ENG rom, you do not need to unlock the bootloader. Just the Asus flash tool.
Once you flash it, you can reboot to fastboot mode(adb reboot bootloader) and use fastboot oem unlock to unlock bootloader. Be warned though the ENG firmware is very basic. No web browser, no google play, you can't pull down the notification bar etc. (Great battery life though with about 7-10 days since I am not using it at all).
As of right now, there is no TWRP for it that i know of. In fact, I can't even boot into recovery atm. I also am unable to get boot.img file form the .raw file so the various methods to root it seem to be out of reach for the moment.
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Doctor Andrew said:
I've absolutely no interest in the ENG firmware. Still looking for a solution to the original post that people can understand and use easily.
Click to expand...
Click to collapse
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
oh my god - rooooot
faericia said:
Well, ENG is the only way i could figure it out but I finally manged to get root on the phone with magisk. Still have some work to do to get play store and everything else running properly, but for now, hardest part is done.
Click to expand...
Click to collapse
Good time of day, Faericia, this is just great news. You can share the experience of getting root with magisk?
Regarding Google Play and all that, where you need Google, using a bunch of microG and Aurora store.
MicroG is the core of Google services, which allows you to pass authorization through Google, synchronize and do it all without any garbage code, according to my observations, the expense is not much spent.
Aurora shop, as an analogue of Google Play, the application, the ability to save apk.
Due to the lack of binding to your Google account.
I think this connection may be relevant and rooted.
The initial partition should appear as root, it intends to resolve all the problems that I have in my phone. for asus applications, after I have done my best, several attempts have already been made.
It was possible to look in read mode using root explorer.
Perhaps you can somehow remove the protection of verizon on the bootloader.
PS the most hardcore variation of raw firmware, a hex editor, search in that between code, boot, recovery, system, etc. Very large empty spaces. previously there were 100 miles earlier.
I think this is part of verizon jokes.
This article should be cut and placed in img.
Thanks so much in advance.
hello when you finish you could share through a tutorial what you did I have my asus v with verizon rom and only data but if I can make it functional with the rom eng then better
Okay, Here are the steps. Before anything else though, I should warn you that I have not been able to get safetynet to pass. So if you have apps that require safetynet to pass, this may not be the way to go.
First you will need the ENG firmware:
https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/
Also Asus Flash tools v 1.0.0.72:
https://drive.google.com/file/d/11rcjOgdpJhpK97GzbhYK6cYEIWOtzKE9/view
I am assuming you know adb and such. If not, search the forums and get the adb tools.
Using adb, Reboot to bootloader. ( adb reboot bootloader )
Load the .raw file in the asus flash tool, select v520KL and flash.
Once flash is done, unlock bootloader by going into bootloader (adb reboot bootloader) then type (fastboot oem unlock.)
Here is the patched_boot.img I used if you want to just try to flash that and see if it will work. This is for the eng firmware.
https://drive.google.com/file/d/1fUxGc27lrodR3ro9MIspde73G8Xg9VlW/view?usp=sharing
Go into bootloader and flash. (fastboot flash boot patched_boot.img)
Install magisk manager and test it out.
If you wish to patch the img yourself, the steps are below (still working on it):
So now we have the phone unlocked, and the software is very basic. We also need the boot.img file to patch since we do not have TWRP. Since I couldn't get it from the raw file (the extracted file is invalid with a size of 0 bytes) I decided to extract it from the phone. But to extract from the phone we need root. So for this next step, temporary root will have to do.
You can get temp root by using KingoRoot. Use the PC version and you will get root. This is just so we can extract the files from the phone itself.
I need to find the steps for the next steps again, but the basics is, extract boot.img from the phone. Patch it using magisk manager and then flash the patched_boot.img in bootloader mode. I had google play working(chinese version) but once i removed kingoroot it kept crashing. I currently have magisk and it gives me the root permissions but safetynet fails. I will retry this tomorrow and see if I can fix the safetynet issue and update this post with the steps.
Also I seem to have borken recovery mode on my phone. That may be because I tried flashing bunch of other stuff before I managed to root it so I do not know if it will be the same situation to you or not. I believe after I flashed ENG firmware, i had access to recovery mode at one point, but I may have just messed it up. Either way, Expect updates in the near future.
asus recovery
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Daniel.Sim said:
A huge over many thanks.
I also tried to get a temporary root, via the kingoroot pc version, it did not work, I suspect it because I installed eng, but did not oem unloock, when I did unlock, I somehow managed to get the boot out of the firmware, the user from 4pda was patched, but said that this boot is from 8 android, I thought that I had schizophrenia because later on trying to get boot I also got 0mb, this was due to the unexpected end of the archive.
In general, by flashing this boot, I also found a recovery mode and even a recovery mode, but going into recovery a message from Verizon was displayed, standard, when you roll the eng firmware for 5 seconds, hold something, etc. Well, you understand. And the whole laugh is that it was in a circle.
I suspect that asus had any plans for this device or for this amount of components. In other words, it was some kind of blank that was abandoned, maybe asus thought that this exclusive for verizon will make a trap, and then they say on the basis of v520kl we will make a non-exclusive open device, but alas, a huge member between two rolls.
Therefore, fortunately or unfortunately, recovery was not broken by you, most likely it was not working initially, but this is only a guess.
Click to expand...
Click to collapse
I know recovery mode was working with VZW firmware. I know this because I tried installing using adb sideload several times. I might be mistaken on getting there once i flashed eng firmware but again, it has been a month or two since I tried it and all I know is, it won't go into the recovery screen now. Oh well, not my main phone so irrelevant.
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
game #1 said:
I have installed patched boot img with fastboot. Now have root. But there a lot of apps not working. No Google apps at all. And no way to install them.
---------- Post added at 06:23 PM ---------- Previous post was at 06:15 PM ----------
Have installed patched boot img by faericia. Now I got root. But eng version doesn't have Google apps, so no play store, no Google pay, no accounts, no Gmail. And I don't know how to install it.
Click to expand...
Click to collapse
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
faericia said:
The only time I had Google apps was when I had kingoroot root still int he system. I then downloaded the Chinese google apps installer and used that to get it. Once i removed kingoroot google framwork kept crashing making it unusable.. If you don't need to pass safetynet, that might be the way. Othewise, I am still trying to work on it.
Click to expand...
Click to collapse
I found out how to stop frameworks from crashing. Just make it a system app. I use link2sd for this.
Now all gapps work nice.