Related
Root the M4 Aqua E2303 Locked Bootloader/Install TWRP on 2.167/3.92
Before we begin:
Make sure you have the following:
•A Windows PC
•Flashtool (https://drive.google.com/file/d/0B_d8uWGbkaetTnhWX0J5UG5hN28/view?pref=2&pli=1)
•The .128 firmware (https://drive.google.com/file/d/0BzVQf67OZ9NtMFotOXRycTZoSlk/view?pli=1)
•Patience
•A good internet connection
•15 to 20 minutes
• The M4 Aqua Root Toolkit (https://www.dropbox.com/s/edse0h6b02odzn1/rootkitXperia_E23xx.zip?dl=0)
•ADB Drivers (https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view?pref=2&pli=1)
•TWRP Toolkit (https://www.dropbox.com/s/yomdwq3p2le9hvi/M4Aqua-lockedTWRP-0.1-installer.zip?dl=0)
How are we going to do it:
The procedure is pretty straight forward, as the M4 Aqua is only on Android™ 5.0 we can take the kernel of the older versions of firmwares so we could root the device, while keeping the firmware version to the newest release (2.167/3.92). The method has been only tried on the E2303, there may be chances of it working for the E2306.
Let's begin! Part 1, Changing the Kernel:
First, we need to install the latest Flashtool version (link above), after you proceed with the installation of Flashtool, you need to install the Flashtool drivers, which can be found in C:/Flashtool/drivers or the path you selected flashtool to be installed. Once you open Flashtool drivers you want to select FLASHMODE DRIVERS, this is only so that the M4 will be recognised while in flashmode. After the drivers have been installed, you want to move the downloaded .128 firmware to C:/Users/*YourName*/.flashtool/firmwares or you can use the other method I will show later. Once you have done that you want to open Flashtool and wait for the Sync to finish. After that has finished, you will see a lighting icon in the top-left corner, you want to press the icon and select flashmode, now the second method, at the top you will see a path leading to the generic .tft folder in which Flashtool belives the .ftf files are located by default. You can change that by pressing the button on the right and lead the program to the path of the .128 ftf file. After you have selected your .tft file you will see on the right a lot of options *everything that the .ftf file contains*, if you want to keep the data on your device you can tick the first two options, a bit down on the right you will see a lot of options, including system.bin, you want to tick everything EXCEPT for the kernel.sin, this is the most crucial part. After that is done you want to let the program prepare the files, mean while you want to power off your M4 Aqua, after the process on Flashtool is done you want to press the VOLUME DOWN button while connecting the phone to the PC, once you see the green led light you can leave the button, if everything was done right the process of flashing should begin. If everything went well the kernel should be flashed and the phone should safely power on. Now we can proceed to the second part. Rooting the phone.
2ND METHOD
You can downgrade to .128 firmware and download the .167 or .92 firmware and update everything except for the kernel. You can do this by going into Flashtool, and doing the steps above but TICKING the kernel.sin. Try this if the first method doesn't work.
Part 2, Rooting the phone:
Now that we have changed the kernel we can use the root toolkit to root the device. Download the root toolkit from the link above, but before you do anything you want to go to Settings>About Phone, scroll down to Build number and press it 7 times, after that is done you want to go back to Developer options, and you want to tick USB Debugging, after you have done that you need to install the ADB Drivers from the link above, after that is done you can connect the phone to the computer, now you want to extract the toolkit and run install.bat *No administrator rights needed*, and then you should see a screen on your phone asking if you want to trust the computer, you want to tick the box saying always and you want to press yes, now the rooting process should begin and your phone to be rooted. After this is done we can proceed to the part 3, installing TWRP
Part 3,Installing TWRP:
Now, that we have root we can install TWRP using another toolkit. This part is optional but if you want any custom ROM's you need this. This part is the easiest, you need to download the toolkit from the link above and just run the script. We don't need any additional steps as we did them in Part 2.
If everything went well you should now be rooted and have TWRP with a locked bootloader and on the newest firmware.
In case of bricking you can use the Sony PC Companion tool and repair my phone/ tablet option. YOU WILL LOSE ANY DATA SAVED ON YOUR PHONE.
sir , can this apply to D2353?
I have only tried on E2303, but you use the right .ftf files the procedure should work
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
osman.by said:
im flashed 128 kernel on 3.92, phone not booted stuck boot animation..
fix this after root random reboots? im rooted on 128 and upgrade 3.92 by twrpreroot, phone randomly reboots..
edit: im flashed 128 kernel on 2.167, phone not booted
Click to expand...
Click to collapse
Root and flash stock kernel tft u use
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Clean install of .167 and .92. Flashing the .128 kernel causes the blue boot animation to hang (the start up sound cuts off half way). Flashing the previous kernel back over works.
Same happens when I flash .128 then everything but the kernel from .167 and .92.
Unsure what the FSC script option does, but yes or no makes no difference.
d0mokun said:
I'm having issues with this also. Downgrading the kernel only causes a boot loop animation. I can downgrade everything to 128 and it works. Going back up to latest with everything BUT kernel causes boot animation loops also.
EDIT!
Oh heck yes, I did it! For anyone stuck in a logo boot loop despite following the above, here is how I did it:
- Use Flashtool to completely flash my .167 E2303 to .128.
- Use above tools to root and install TWRP.
- Use Flashtool again, but this time in Fastboot mode. I extracted the system.sin file from a .167 ftf and then flashed system using Flashtool.
- Reboot the phone into TWRP. Clear cache, dalvik. I did NOT clear data.
- Install M4 extras. Install AOSGP. Clear cache, dalvik.
- Reboot took about 15 minutes, probably less.. and BINGO.
Thanks to all.
Click to expand...
Click to collapse
EDIT: Someone re-uploaded the M4 rootkit: http://forum.xda-developers.com/m4-aqua/general/guide-t3130092/post65486499#post65486499
bootloop on E2303 Tried both methods
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
drunkenlo said:
Hey all. Trying to root my E2353 on 26.1.A.1.112. Ran install.bat with all drivers installed, with adb, but all I'm getting is this. Any suggestions?
Click to expand...
Click to collapse
enable usb debugging and unlock the phone and accept the popup message when plugged in
Jevinruv said:
enable usb debugging and unlock the phone and accept the popup message when plugged in
Click to expand...
Click to collapse
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
drunkenlo said:
I have usb debbugging enabled and the phone unlocked but I don't get a popup message. Tried disabling and re-enabling usb debugging but still nothing.
Click to expand...
Click to collapse
Revoke USB Debugging authorization from developer Settings
Random Reboots
Any fix for the random reboots as of yet?
could u fix the dropbox link, it isnt working for me - Error (429)
This account's links are generating too much traffic and have been temporarily disabled!
I'm getting an error when installing the flashmode drivers, it just says failed after I tick the box and continue. Can anybody help me please? I've tried rebooting my PC, running as admin and even tried compatibility options but it doesn't help.
osman.by said:
When i upgraded from 128 to 167, phone works well but random reboots. Any fix this issue?
Click to expand...
Click to collapse
kgalv419 said:
Any fix for the random reboots as of yet?
Click to expand...
Click to collapse
If your random reboots usually happen while downloading or updating apps in the play store, you should try this. Make sure you backup your data first just in case.
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Hello. Please help. I got softreboot everytime I try to call someone
Sent from my E2303 using Tapatalk
Hello,
thank you for this guide. I have a question: why not extracting the old kernel and just flashing the kernel.sin?
Prefix: my xz1 died on me so I was forced to buy a new phone and therefore I won not be maintaining this thread any further. The guide should be relevant even without my help but I just won't be answering any questions regarding this thread or anything to do with the xz1.
YOU DO NEED TO UNLOCK YOUR BOOTLOADER AND THEREFORE WILL LOSE YOUR DRM KEYS!
NONE OF THIS IS MY ORIGINAL WORK BUT MY PROCESS IS ORIGINAL. YOU CAN THANK @modpunk FOR HIS PORT OF TWRP TO THE XZ1 AND YOU CAN THANK @janjan FOR HIS HARD WORK IN CREATING THE FIRST FULLY FUNCTIONAL KERNEL THAT SUPPORTS MAGISK AND STILL OFFERS A WORKING CAMERA AND SONY FEATURES
Here we go.....
1: Download modpunk's port of TWRP from this thread: https://forum.xda-developers.com/xperia-xz1/development/recovery-twrp-3-2-1-t3727602
Make sure to check the dates on the files and always download the latest version.
2: Download Janjan's kernel and DRM package here:
https://forum.xda-developers.com/xperia-xz1/development/kernel-sony-xz1-23-january-2018-t3739586
Make sure to check the dates on the files and always download the latest version.
3: Enable developer settings and enable ADB Debugging. I shouldn't have to say this part but something tells me if i don't then i'll get loads of questions about not being able to connect to the phone, lol.
4: Connect the phone to your pc and copy the 3 zip files contained in the janjan download to your phone. You don't need to copy the boot.img to your phone.
5: Open a cmd window on your pc and type the following:
adb reboot bootloader
6: Once the pc recognizes the phone in bootloader mode then type:
fastboot flash boot path/to/the/boot.img (I usually just type "fastboot flash boot " and then just drag and drop the boot image into the cmd window.
7: Once the boot image is flashed unplug the cable from the phone then reboot it. Once it's running then make sure the kernel info has changed to say "[email protected] #1
8: Once again, boot into bootloader by running the adb command
adb reboot bootloader
9: Once in the bootloader type into the cmd window:
fastboot flash recovery path/to/the/recovery.img
10: Reboot to system and then power off the phone.
11: Once it's off, boot into TWRP manually by holding the power button + the vol down button until the phone vibrates once, then let go and it'll boot into TWRP.
NOTE: It will ask you for your password to decrypt the data partition. This password is whatever your pin number or password you use on your phone lockscreen. If you don't use any lockscreen security then the password is: default_password.
12: Once in TWRP flash 2-Patching_drm_Su and 3-Magisk and then reboot to system and check that magisk is installed.
13: Finally open magisk and open the Modules section then tap the + icon and locate and flash the last zip 4-kernel_permissive and then reboot the phone and open magisk and check the modules section to ensure the Magisk SELinux Permissive Script is active.
Now you have a fully functional XZ1 with Magisk root and a properly functioning camera and Sony features.
Enjoy!
N1ghtr08d
Sorry.You forgot to flash SR5-SuperSU-v2.82-SR5-20171001224502.zip in TWRP recovery after step 13
Posting not relevant anymore!!!
1:st posting fixed by N1ghtr08d
Thanks bro. I had edited it and I must have missed putting that back in. Fixing it now
Any try to use Magisk instead of SuperSU ? I need to use some apps witch don't work with root phone.
If you turn the phone off, press and hold 'Volume Up' and attach a USB Cable from your PC it will boot into the bootloader. The LED will be blue then ...
Thanks modpunk, that is very true. I guess my preference is just to use ADB.
As far as magisk is concerned, I believe that none of the magisk releases work with this device. I would prefer to use magisk also so if anyone figures out how to install it successfully without putting the phone in a bootloop, please share it here and I will update this guide. I'd rather have SuperSU than no root at all.
Does anybody have any tips for installing Viper4android? I renamed the audioeffects file in System/Vendor/Etc and installed the Nougat test io fix version and when I opened the app and allowed it to update the drivers, everything went well and looked successful, however upon reboot and opening the app to set it up, it just tells me to update the drivers and reboot again and even doing that just lands me back at the same point.
Does anybody know how I can get it installed and running properly?
Coincidentally V4A installs and runs perfectly now that it can be installed through Magisk Manager!
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
trevorftard said:
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
Click to expand...
Click to collapse
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
pergoteborg said:
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
Click to expand...
Click to collapse
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
trevorftard said:
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
Click to expand...
Click to collapse
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Thank you for the help Pergoteborg. I thought the guide was fairly self explanatory.
I pointed out in the op that the one boot image I provided in the download is to be flashed to 2 different partitions.
If you follow my instructions as provided you will have success. It's really easy to follow along if you read it properly.
pergoteborg said:
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
Click to expand...
Click to collapse
I tested myself and answer is NO. Therefor no magisk for 47.1.A.8.49 yet since we do not have kernel support. Root achieved by SuperSU
So I :
Got phone in flash mode (Vol- when putting in computer USB cable, Green light). Ran NewFlasher with 47.1.A.8.49
Booted phone, turned it of and set it to fastboot mode (Vol+ when putting in computer USB cable, Blue light)
Flashed TWRP: fastboot flash recovery twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
Booted phone, Uninstalled Magisk manager, Installed SuperSU App from Google Play.
Turned off phone, booted into TWRP (Vol- and pwr, release pwr button when phone vibrates, hold on the Vol- button)
Installed Magisk-uninstaller-20171123.zip to get rid of Magisk. Installed SR5-SuperSU-v2.82-SR5-20171001224502.zip to get SU
HIPP!!!
pergoteborg said:
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Click to expand...
Click to collapse
Thanks for being actually helpful. I wasn't familiar with the FOTAKernel partition. I though it was a typo that was supposed to be the name of some boot.img. I'm familiar with everything else about fastboot. I'm still getting a glitchy display after flashing the boot.img to the boot and FOTAKernel partitions. I think I'll just check out and give up on this one.
Hi There
Thank's to my hero aledoom who ported XZ1 (G8342) FW47.1.A.8.49 to Androplus we can now enjou latest FW and Magisk
Download the patched kernel here (aledoom´s direct link here)
If you currently have root with SU, get rid of it by flasching UPDATE-unSU-signed.zip in TWRP
Then follow the OP, but use kernel from here instead of OP boot.img.
I currently testing MAGISK 15.0 and it's working fine except there is no modules ported to the new template just yet,
Hi all, do you think that TWRP, Androplus kernel et Magisk work on a XZ1 Dual ?
I don't know. To be honest, you'd need to check with modpunk and aledoom if their recovery and kernel are compatible
So this is actually my first official post as a new member on this site but have been a long time user of the guides here. I have a question but I want to root my xz1 to optimize the performance and what not and just cause haha. My question is about what's being lost. I noticed something called xreality or something won't be accessible. What is this? Reason I'm asking is that I playmobile legends and this phone and only this phone I've found has an in game option for. "high frame rate" mode.. I'm not interested in rooting it if all I'll do is make it perform less rather then the opisite anywho Sony's alot different then most android im finding so I figure what the hell better make an account finally and ask.
I have no idea what xreality is. Is it a Sony app?
As far as what's lost, you lose the DRM keys so the camera stops working correctly, as in when you take a photo it just turns out as a green image instead of the picture you intended.
Now with that being said, someone over on the root bounty thread apparently discovered a fix for this that allows the camera to function fully as before. I have tried flashing this fix on my personal device and it didn't work as expected however I'm using magisk for root instead of SuperSU like the poster stated so I'm waiting on a reply from him regarding the usage of magisk Vs SuperSU with his fix.
Here's the thread in question. He posted right at the end of the thread just before me.
https://forum.xda-developers.com/xp...z1-compact-lb-root-drm-backup-t3672176/page16
Hello. So basically my friend has a xperia Z5 Compact phone and he wants to get magisk 19.1 on it. I am new to the phone and do not know how to root it etc. so I need help on getting TWRP and magisk on it. The bootloader is already unlocked because I tried to get TWRP on it but it ended in frozen boot screen. I have since flashed the phone and now need help to actually do something with it.
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Alright Im going to try that in the next few days.
casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt
I_did_it_just_tmrrow said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt
Click to expand...
Click to collapse
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs
casouzaj said:
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
Code:
fastboot oem device-info
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with:
Code:
fastboot flash recovery the-name-of-the-twrp.img
With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot C:\Users\idijt\Downloads\twrp-3.0.2-0-E5823-20160417.img
downloading 'boot.img'...
OKAY [ 0.392s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.459s
I_did_it_just_tmrrow said:
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with: With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Click to expand...
Click to collapse
In your computer, run Flashtool and click on the XF icon (the last one in the line of icons on the top part). XperiFirm will be downloaded and run. On it, under : Smartphone 2015'', click on 'Xpetia Z5 Compact' and on the specific model. Now clock on 'Check All'. Select a ROM bearing 'Customized' in its name and with version 32.4.A.1.54, which is Android 7.1.1). The list of available files appear on the right. Click on the most updated one and on 'Download'. Wait until the ROM is downloaded and unpacked. When the progress bar gets blank and says 'Downloaded successfully', click on 'Close'. Then, click on the X in the XperiFirm window to kill it. Flashtool will resume its work, which will culminate with the creation of the ftf file in the right directory.
To flash the ROM, click on the bolt icon, in Flashtool , select 'Flashmode', click on the little arrow at the left of the model name. The same for the specific model and for the ROM name. Finally, click on the ROM to be flashed. Mark all the boxes in the upper 'Wipe' section and click on 'Flash'. While it is preparing the files, turn the phone off. When an animated window requesting connection comes up, hold the phone's volume down button whilst connecting it to the computer. Release the button when the animated window goes away. Wait for the process to completely finish. Disconnect the phone from the computer
The ftf is located in C:/Users/your_username/.flashTool/firmwares. Copy it to anywhere you wish and change the copy's extension to zip.. Double click on it and extract 'kernel.sin'. In Flashtool, click on Tools > Sin Editor, and click on the tree dots on the right. Navigate to the location of the kernel.sin file, select it and click on 'Extract data'. File kernel.elf has been created.
Do you know rootkernel? (https://forum.xda-developers.com/xp...t-automatic-repack-stock-kernel-dm-t3301605). Copy the kernel.elf and the phone's TA.img to the rootkernel directory. In a terminal window in that directory, enter:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
The TWRP I use is this one: https://forum.xda-developres.com/z5-compact/general/twrp-twrp-3-3-0-z5-compact-t3929320, which I fastboot'ed to the FOTAKernel partition.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs
casouzaj said:
In your computer, ........
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
EDIT:
I flashed Magisk v19.3 and it wokred... Yes, as you told me :/
Can I simply flash Berni LineageOS now and did I need to flash the new-boot.img, the DRM-Fix_System_Mode.zip and Magisk always after flashing a new rom?
I_did_it_just_tmrrow said:
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
Click to expand...
Click to collapse
At any state the phone is in, in order to turn it off, hold both the power and the volume up buttons, until it vibrates thrice.
Then, enter TWRP by holding both the power and the volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. Then, under TWRP, install the new-boot.img, the Magusk-V19.3.zip and the DRM-Fix.zip.
Sent from my Xperia Z5 Compact using XDA Labs
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
Regarding Berni's LineageOS builds, I'm running his 14.1 firmware. It has some issues. I don't go back to the stock ROM because I would have to wipe my data in the process, and, at the moment, it's not an option for me. The big advantage of the stock ROM is that you can have all your DRM keys active, although the bootloader is unlocked. The big disadvantage is to have outdated security updates. Berni's 15.1 build has more bugs than the 14.1 one,, and with his 16.0 build, the phone doesn't even boot up.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Sent from my Xperia Z5 Compact using XDA Labs
I too am trying to root my Z5 Compact E5823
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Click to expand...
Click to collapse
should I still answer these this way?
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
Click to expand...
Click to collapse
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
Click to expand...
Click to collapse
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
Click to expand...
Click to collapse
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as wells
Click to expand...
Click to collapse
One last thing as you mentioned above
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)
gnostisus said:
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
should I still answer these this way?
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
One last thing as you mentioned above
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)
Click to expand...
Click to collapse
Magisk modules are installed by the Magisk Manager app. Tap on the menu button (the 3 bars at the top left) and select 'Download'. Tap on the search button and type in at least part of the module's name, and tap on 'Install'. The only module that is installed differently is the systemless hosts one. Tap on 'Menu > Settings > Systemless hosts'. After all the modules you wanted get installed, reboot your phone.
By the way, in my Z5C phone I'm currently running the latest stable Magisk v20.4. In its Menu > Settings part, I turn on the 'Magisk Hide' key.
Regarding flashing the Dk.ftf file, I do it whenever I flash a full ftf, because I guess the alternative partition it is flashed to gets overwritten.
Sent from my Sony E5823 using XDA Labs
Berni's LineageOS
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
casouzaj said:
]Regarding Berni's LineageOS builds, I'm running his 14.1 firmware.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Click to expand...
Click to collapse
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.
gnostisus said:
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.
Click to expand...
Click to collapse
I've never used ANT+. I can't help you with that.
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP. .If you need the Google stuff, install a Gapps package, also from TWRP (I use to get the most updated mini one from opengappsI.com). Wipe all your data and caches. To get root access, install Magisk (the stable v20.4, I guess).
Good luck!
Sent from my Sony E5823 using XDA Labs
quick question about Berni's build
casouzaj said:
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP..
Click to expand...
Click to collapse
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
Wipe all your data and caches.
Click to expand...
Click to collapse
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again
gnostisus said:
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again
Click to expand...
Click to collapse
You can either copy the zip files to your phone (or SD card), select the storage where the files are located and tap on ' Install', or keep them on your PC and, in TWRP tap on 'Advanced > add sidelioad', slide the bar, connect your phone to your PC, launch a command window, navigate to the folder where the files are located and enter:
add sideload filename.zip
Wait until the sideload process is finished (TWRP returns to the normal adb interface).
To clear your data, tap on the 'Wipe' softbutton and slide the bottom bar to factory reset.
Sent from my Sony E5823 using XDA Labs
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to