Database Info

[Tutorial][Root][Guide] Root Acer Liquid Zest 4G z528 (t07)

Hi, I will be showing you how to root this device, it's a pretty new (released last year) model from Acer (a company dev hates becauseof their no-release firmware).
I will not be held responsible for anything that will happen, proceed at your own risk
ABOUT (ME?):
ive had this device, i really wanted to root it, but turns out that no official or legit guide is available in the internet. But with the help of some other guides about previous tutorial, and a big thanks to smartmanvartan who provided the customized twrp port for my device.
PREREQUISITES
1. ADB and fastboot, here is a guide (Note: im using linux), if youre in windows, go to the acer webpage and download the usb driver for the device and install it.
2. the twrp port in here. Then unpack that zip file, you will be using the twrp-mod.img file.
3. download the supersu.zip here and put it in the external sdcard.
BACKUP!!! Make sure you also have a backup of the original firmware, so if something happens, it's easy to return to stock, you can download the firmware here
Process
Im assuming that you already has the required files. MAKE SURE YOURE DEVICE IS z528, there are two kinds of acer liquid zest 4g.
1. unlock the oem lock in the device, go to settings > about device > go to build number and repeatedly tap on it until you are notified that the developers option is enabled. After that, go to settings > developer option > turn on the enable the oem unlocking, enable usb debugging.
2. turn off your device then boot into fastboot mode (press the VOL UP button and the Power Button) it should boot into the prebootloader, use the VOL UP key to navigate, then VOL DOWN to select, you have 4 options: recovery, fastboot, normal, demo, choose fastboot.
2. while in fastboot mode, connect cable to the phone to the device, then open a terminal (command prompt if youre in windows) then type
Code:
fastboot devices
then enter, it should return a device on the list. (if youre device is not in the list,make sure you've followed the adb and fastboot install guide)
3. Once fastboot detects youre device, do
Code:
fastboot oem unlock
and there will be a prompt in your device, follow it.
4. check everything is okay with
Code:
fastboot getvar all
and look for the bootloader if its unlocked.
5. navigate to the place where the twrp image is located, then open terminal there (windows: shift + right click > open command prompt there) then do
Code:
fastboot boot <name of the twrp.img>
example :
Code:
fastboot boot twrp-mod.img
then wait for the device to restart and boot into the custom recovery.
6. While in the custom recovery, (you will see my name there HAHAHA) tap install, locate the supersu.zip, and wait for it to get flashed. You will see some important notice about not disturbing the process, the device should boot twice and, if everything is successful, voila! your device is rooted, after logging again like your device is fresh from the store, check the supersu app, it should not throw some error
6.5. if it's not working, try repeating the process, then before installing the supersu.zip, go to wipe first, then erase the cache (DO NOT ERASE ANY OTHER!, then go back, wipe swipe to do factory wipe.
EVERYTHING SHOULD WORK!
Just reply if you've encounter any problem.
NOTE:
it also works for the z628 (t08)

Hello,
Does it work for t08?

cartgen said:
Hello,
Does it work for t08?
Click to expand...
Click to collapse
Im afraid it doesnt, you have to provide/port a custom twrp suitable/compatible for your device.

Hello , but after rebooting the TWRP recovery is gone. Is there a way to replace the original with TWRP on the phone?

snakekiller said:
Hello , but after rebooting the TWRP recovery is gone. Is there a way to replace the original with TWRP on the phone?
Click to expand...
Click to collapse
The method ive showed you is booting only in twrp, not replacing to stock recovery. After using the command
fastboot boot twrp.img
You should wait for your device to boot into twrp.
If you want to replace the stock recovery, im warning you,google the possible problems that may happen, if you wish to proceed, use the command
fastboot flash recovery twrp.img

flamendless said:
The method ive showed you is booting only in twrp, not replacing to stock recovery. After using the command
fastboot boot twrp.img
You should wait for your device to boot into twrp.
If you want to replace the stock recovery, im warning you,google the possible problems that may happen, if you wish to proceed, use the command
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
ok from where did you take the twrp recovery.
did you changes some stuff , sow that its works on this device?
or did you make it yourself.
if i try and its not working . maybe bootloop or just a brick .
can i recover it with the linux terminal?

snakekiller said:
ok from where did you take the twrp recovery.
did you changes some stuff , sow that its works on this device?
or did you make it yourself.
if i try and its not working . maybe bootloop or just a brick .
can i recover it with the linux terminal?
Click to expand...
Click to collapse
I got the custom twrp from a person here on xda. To avoid bootloop, don't flash the TWRP, just do the fastboot boot twrp.img, that method will never cause bootloop. What is your device? What happened after you fastboot boot twrp.img?

Your tutorial works fine . But I just want want a custom recovery so that I can make a custom ROM for this device.

i have a question
i downloaded SP Flastool for linux but how put this phone to download mode.
sow that it's connect with the program.

snakekiller said:
Your tutorial works fine . But I just want want a custom recovery so that I can make a custom ROM for this device.
Click to expand...
Click to collapse
Is your device same as the device tutorial I've used in this post? If it is, I have provided the custom twrp that works on the specific device.

snakekiller said:
i have a question
i downloaded SP Flastool for linux but how put this phone to download mode.
sow that it's connect with the program.
Click to expand...
Click to collapse
You will only use the sp flash tool if your device is mediatek, also, you wont need it for the rooting process this tutorial is for, you will only need the sp flash tool when your device got soft bricked

ok guys i did the test.
you can safely flash this recovery to your device.
lets make some custom roms now.
all the credits go to flamendless

guys are u shure u mean the z628 not the 528? the 628 ist the liquid zest plus iirc... liquid zest 4g are 525 and 528 iirc... if u mean the 528 is the twrp working on this device? would be great it twrp works on this device...
best regards

numen said:
guys are u shure u mean the z628 not the 528? the 628 ist the liquid zest plus iirc... liquid zest 4g are 525 and 528 iirc... if u mean the 528 is the twrp working on this device? would be great it twrp works on this device...
best regards
Click to expand...
Click to collapse
My phone is the 528 or the T07. I flashed the recovery and works great on this device

snakekiller said:
ok guys i did the test.
you can safely flash this recovery to your device.
lets make some custom roms now.
all the credits go to flamendless
Click to expand...
Click to collapse
Thanks! I would also like to try a custom rom for it, i dont see any custom rom available for this device. update me if you already got one

numen said:
guys are u shure u mean the z628 not the 528? the 628 ist the liquid zest plus iirc... liquid zest 4g are 525 and 528 iirc... if u mean the 528 is the twrp working on this device? would be great it twrp works on this device...
best regards
Click to expand...
Click to collapse
oh, youre right, im truly sorry, my device is z528, idk why i messed up. im gonna update this thread. sorry.

flamendless said:
oh, youre right, im truly sorry, my device is z528, idk why i messed up. im gonna update this thread. sorry.
Click to expand...
Click to collapse
so the twrp should be able to flash on the z528 without any problems, right?
best regards

numen said:
so twrp should be able to flash on the z528 without any problems, right?
best regards
Click to expand...
Click to collapse
Absolutely ?

Yes, works 1000%

ok guys
i maked just a original rom from the latest firmware version 1.0.15.
what is different with the original stock rom!!!!
its now auto rooted in the system self.
removed all the bloatware.
init.d added so you can add scripts if you like.
changed the boot en shutdown animation.
tell me what you want also see changed in the rom. (launcher maybe?)
when its fully finish i upload it.
and BTW its flashable with twrp

[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1

Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27

So we can flash either through TWRP or Fastboot right?

Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%

Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.

Thank you very much.
Is there any userdata.img available?

alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.

sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.

alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe

alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.

Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs

A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found

I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?

Thanks. Both methods work fine. Don't ask how I found out.....

Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...

coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1

Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it

Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?

Does Nokia 1 support DT2W?

Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance

Can any please repost the firmware , the link isn't working

[AIO] [Guide] [Unlock bootloader] [TWRP[ROM Flashing] [Root]

Xiaomi Pocophone F1 [Beryllium]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are NOT risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Unlocking the bootloader​
You will have to apply for unlocking bootloader for that make sure you do have MI Account if not then create now, Once you are done with then visit here and make sure you use same mi account you have in your phone then wait for 2-3 days. After that download, the latest MI Unlock tool(Shared in download section) Run mi*.exe as admin and simply sign in there as well. Now move to your phone --> Settings app --> About phone --> Tap on MIUI for 6-7 times and you will see "you are a developer now", go back to main settings additional options --> Developer options --> Turn on OEM Unlocking and USB Debugging. Also allow USB Debugging from this PC If you still didn't get simply revoke all and connect usb then in adb type "adb devices", you will see a prompt on your mobile just tick and allow. You will also see an option called as "Mi Unlock status" click on it and click on "Add account and device" Now turn off your phone and go to fastboot mode for that press and hold volume down + power key. You will see "FASTBOOT MODE" on your phone now move to your PC and connect USB. Now once your phone appears in Mi Unlock Tool just click on "Unlock" "It will pop up some prompts" agree with them by clicking "Unlock anyway", It simply means your data will be wiped and warranty will be void! Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again. If it shows press any key to poweroff on your phone when you connect in fastboot then try changing the port or simply reset your device and redo changes that we did (Follow above process again as USB debugging will be off by default, reset ) Now you are done with unlocking the bootloader let's move to TWRP​
Flashing TWRP​This is one of easiest step, just open cmd in adb folder and type following codes :
Code:
adb reboot bootloader
Code:
fastboot flash recovery *your recovery name.img
Code:
fastboot boot recovery.img
We are done with flashing TWRP now let's move to encryption issues!​
DFE ​
Now this is most critical. If you skip you will have to flash stock ROM again so don't mess here!
Download vendor image, dfe, your favorite custom ROM, Gapps, Magisk(Everything mentioned in the download section
Boot into TWRP --> Wipe --> Format data! Reboot to recovery from TWRP menu and flash DFE. Now, go to system and setup MIUI and then come back to TWRP for flashing your favorite custom ROM. Now in TWRP --> Wipe --> Advance wipe choose system, data, dalvik & cache --> Swipe to wipe. Now copy those files to your Sdcard. Then go back to main TWRP page and choose --> Install, Now follow the order of flashing these files(most important)
* Flash vendor image i.e beryllium-9.4.8-9.0-vendor-firmware.zip(This is optional if you had latest MIUI ROM then you can skip this)
* Flash ROM & Gapps
* Flash DFE i.e DisableForceEncryption.zip
* Flash Magisk(up to you, only if you want root)
* Reboot
Enjoy! You are done with it. Yea.. ik Download section is mentioned below!
Here's a quick tip always flash DFE whenever you update ROM as the vendor might be changed, This will ensure the safe running of the device!
​

Download section :​
* Mi Unlock Tool
* TWRP(official)
* Vendor image
* DFE
Enjoy! ​

Which vendor image to use

dlas.dl said:
Which vendor image to use
Click to expand...
Click to collapse
I have mentioned that in OP i.e "beryllium-9.4.8-9.0-vendor-firmware.zip"

Hi if I want only root
What is the process to root with stock ROM
Thanks in advance

Rameshhreddy98 said:
Hi if I want only root
What is the process to root with stock ROM
Thanks in advance
Click to expand...
Click to collapse
Same, all i want is Magisk and twrp with global (or beta) miui ota and I am not sure what to do

Dearminder said:
Same, all i want is Magisk and twrp with global (or beta) miui ota and I am not sure what to do
Click to expand...
Click to collapse
You can't have the cake and eat it too!
By flashing Magisk, you modify /system and you lose the ability to receive and flash OTA.
AFAIK, there is no official TWRP version which can handle OTAs. The unofficial ones were created for specific purposes and so they fail in some other respect.

tnsmani said:
You can't have the cake and eat it too!
By flashing Magisk, you modify /system and you lose the ability to receive and flash OTA.
AFAIK, there is no official TWRP version which can handle OTAs. The unofficial ones were created for specific purposes and so they fail in some other respect.
Click to expand...
Click to collapse
How about the Orange fox recovery? Doesn't it support OTA?

Dearminder said:
How about the Orange fox recovery? Doesn't it support OTA?
Click to expand...
Click to collapse
It is supposed to support OTA but it may have other issues as I said above. Read its thread.

Hello,
Could you repost the DFE tool? The link is broken.
Thanks in advance

vinimdi said:
Hello,
Could you repost the DFE tool? The link is broken.
Thanks in advance
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1395089523397944356

Thanks. But I was looking for the DFE without magisk that was available on the OP.

vinimdi said:
Thanks. But I was looking for the DFE without magisk that was available on the OP.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1395089523397897352
There you go mate!

Tribes11 said:
https://androidfilehost.com/?fid=1395089523397897352
There you go mate!
Click to expand...
Click to collapse
Thank you very much bro

Why its so complicated on poco ? my last phone was mi a1 it was super easy to unlock bl , twrp and root
now i have poco and came here to check rooting and other stuff then shocked by these complications ?

I'm in MIUI stable now and whenever I try to connect my phone in fastboot mode to the mi unlock tool, it automatically exists fastboot mode and I get a black screen with a message, "press any key to shutdown".
Is that normal?
MI unlock has also not been able to detect my phone. I wonder what's wrong.

thapaavijeet said:
I'm in MIUI stable now and whenever I try to connect my phone in fastboot mode to the mi unlock tool, it automatically exists fastboot mode and I get a black screen with a message, "press any key to shutdown".
Is that normal?
MI unlock has also not been able to detect my phone. I wonder what's wrong.
Click to expand...
Click to collapse
Re-install the drivers available in the Unlock tool.

Help me
Bro I requested for bootloader unlock, they gave me 72 hours time, then by mistakenly in middle time I sign out my mi acc from my device and again sign in, then again 72 hours later I try to unlock but now it is showing couldn’t unlock, error -1, I tried with different computer, what to do now ?, how can I unlock bootloader now? With new Mi account? Or with this one? Please help , and sorry for my bad English

Its mentioned here as .... Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again.Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again. ...
DO i have to wait 72 hours to unlock ?? or its just a message and unlock done within secs/ mints

Moto G7 root and TWRP

This thread contains known working root and custom recovery, along with any other verified working mods for this device
Thanks to anyone who is willing to help out in advance. You are awesome
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you
* could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications of your own free will
THIS REQUIRES AN UNLOCKED BOOTLOADER!!! DO NOT ATTEMPT ON A LOCKED BOOTLOADER. YOU ALSO NEED APPROPRIATE DRIVERS AND ADB TOOLS. THIS GUIDE IS ONLY FOR THE MOTO G7 SERIES, DO NOT ATTEMPT ON ANY OTHER DEVICE
Also check under developer options USB debugging and OEM unlock is checked. Tap build number 7x under settings -> about phone to enable developer options. Please note that some carrier locked variants do not permit OEM unlocking and as such currently have no method to unlock the bootloader
Follow the instructions here to unlock your bootloader
Confirmed Magisk working with boot image, patched through Magisk app.
TWRP needs some work but basic functionality is up
Magisk
Download the appropriate firmware from here, making sure to match build number and variant, found under Settings -> System -> About Phone. Even if you use boot images given to you, I recommend you do this just in case something messed up
Extract the boot.img file
Copy it to the internal storage of your device
Install magisk manager app, found here and open it.
Make sure under advance setting both keep dm-verity and keep force encryption are checked, otherwise you may get stuck in a bootloop
Tap install beside "Magisk is not installed" on the first card
Tap patch boot image
Select your boot image
Once magisk creates the image, copy it to the folder that contains the adb tools
The output can be flashed via fastboot on an unlocked bootloader via
Code:
adb reboot bootloader
fastboot flash boot boot.img
After initial setup/first boot, reboot your device again. Magisk Manager stub should now show up under apps. If you have previously installed it, you'll still need to reboot after the initial boot with magisk for the app to recognize you have it
The stub will download the actual app (if necessary). Once that's installed, open it and tap yes when it asks you to set up environment. If that failed, just close the app and reopen, tapping yes on the prompt. Do that until it says setup done
We now have twrp so theoretically the magisk zip can be flashed. I personally have experienced a lot of problems with this method so I'd recommend against it, but if you want to here's how:
See below instructions to flash twrp if you haven't already
Download the latest magisk zip here and save it to your SD card if you have one
Reboot to TWRP via volume down + power, which will get you to bootloader. In bootloader, use the volume keys to scroll to recovery mode, then press power to select. I personally prefer adb via
Code:
adb reboot recovery
Type in you screen lock if prompted, then hit the check mark on keyboard when done
Tap install
Navigate to where you saved the zip and select it
Swipe to install
Follow the last two steps of the other method
TWRP
A beta version of TWRP is now available here. Credit to @Alberto97
Download the file and copy to your adb tools folder
Reboot to bootloader
Code:
adb reboot bootloader
Boot it with
Code:
fastboot boot twrp-version-build-river.img
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-version-build-river.img
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
Select Fix Recovery Bootloop from Advanced tab, and swipe to fix
In case of emergency (eg, soft brick), follow these instructions to get back to stock before reattempting. They may say for updating, but they work to get back to stock

I Have two G7 rooted with Magisk indeed

if you look at the full firmware there seems to be no stock recovery included in it. we definitely need twrp to even flash a custom gsi rom. id help but i have no time or idea how to build twrp.

mingkee said:
I Have two G7 rooted with Magisk indeed
Click to expand...
Click to collapse
Can you please provide evidence? A screenshot of the main page of Magisk app and a screenshot of root checker will do

fix-this! said:
if you look at the full firmware there seems to be no stock recovery included in it. we definitely need twrp to even flash a custom gsi rom. id help but i have no time or idea how to build twrp.
Click to expand...
Click to collapse
I know how, but I'd need the stock recovery

clcombs262 said:
Can you please provide evidence? A screenshot of the main page of Magisk app and a screenshot of root checker will do
Click to expand...
Click to collapse
OK
You asked for it

clcombs262 said:
I know how, but I'd need the stock recovery
Click to expand...
Click to collapse
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.

mingkee said:
OK
You asked for it
Click to expand...
Click to collapse
Can you share step by step how you did it?
Like patch boot img with magisk, flash magisk zip, use TWRP, etc?

mingkee said:
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.
Click to expand...
Click to collapse
Thanks for the effort!

clcombs262 said:
Can you share step by step how you did it?
Like patch boot img with magisk, flash magisk zip, use TWRP, etc?
Click to expand...
Click to collapse
He described it in
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084/page4
I'm trying to gather enough courage to root my G7. Scary. But I need it for things like titanium backup, AfWall, etc.
Besides I believe twrp is not yet available. Need it for the nandroid backup to restore if things go bad.

maybeme2 said:
He described it in
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084/page4
I'm trying to gather enough courage to root my G7. Scary. But I need it for things like titanium backup, AfWall, etc.
Besides I believe twrp is not yet available. Need it for the nandroid backup to restore if things go bad.
Click to expand...
Click to collapse
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting

clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
I have my Moto G7 xt1962-1 US Retail rooted with magisk. It works. You can use my patched boot image if your're running the same on ppo29.114-16-5 and don't want to do it yourself. Flash with:
Code:
fastboot flash boot patched_boot.img

mingkee said:
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.
Click to expand...
Click to collapse
Of course its merged. I did not realize this, but it is a arm64 A/B partition device. that means that recovery is merged into boot

clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
I can work on providing the steps I take with river_amz later today and document each step. Will edit this reply when I do so.

Ni
clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
cclombs, you are correct. ANY device that can be bootloader unlocked can be rooted with Magisk in this way. Magisk works by inserting itself into the boot image so you just need access to the boot image. However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
EDIT: Section removed. Access to read boot.img requires root. I was wrong!
And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.

zerogun said:
cclombs, you are correct. ANY device that can be bootloader unlocked can be rooted with Magisk in this way. Magisk works by inserting itself into the bootloader so you just need access to the bootloader image. However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
Theoretically, even if you did not have access to the stock ROM, you can enable ADB debug in Developer Options, go into an ADB shell, and then do this:
dd if=/dev/block/[boot location] of=/data/downloads/boot.img
This would do a full image backup of your boot.img and put into your downloads folder. And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.
Click to expand...
Click to collapse
I thought dd required root?
And I think you mean boot image, not bootloader. Bootloader is very different, and should NEVER be modified

You are correct. I meant to say boot image. I'll edit to not confuse people.
I'll have to check later on if dd requires root. I thought it only needed adb debig access.

Thank you zerogun. I'm trying to learn.
zerogun said:
However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
Click to expand...
Click to collapse
Where do they supply these stock ROMs?
zerogun said:
Theoretically, even if you did not have access to the stock ROM, you can enable ADB debug in Developer Options, go into an ADB shell, and then do this:
dd if=/dev/block/[boot location] of=/data/downloads/boot.img
This would do a full image backup of your boot.img and put into your downloads folder. And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.
Click to expand...
Click to collapse
When you 'go into an adb shell' do you mean use adb from a connected PC or is there an adb shell app on the phone itself?

Anybody interested in partially working TWRP? My plan was to release it once fully working but I'm stuck on decryption since days (I can't understand what keymaster 4 is still missing since it wants to upgrade the key) and I might change idea.
With broken decryption you can't use your internal storage but you will be still able to flash things from sdcard or usb otg.

Alberto97 said:
Anybody interested in partially working TWRP? My plan was to release it once fully working but I'm stuck on decryption since days (I can't understand what keymaster 4 is still missing since it wants to upgrade the key) and I might change idea.
With broken decryption you can't use your internal storage but you will be still able to flash things from sdcard or usb otg.
Click to expand...
Click to collapse
You can wipe with TWRP to remove encryption once, but you have to reboot in TWRP

[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June/July patch)
- Touch not working when installed
- Please report any other bugs
Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 03.08.2019
- Initial Release
Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing
XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus
Contributors
Schritti, MartinX3, Oshmoun, Marijn
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-08-03
Created 2019-08-03
Last Updated 2019-08-05

Reserved

Reserved

Woohooo!
First!

My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.

sickkside13 said:
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
Click to expand...
Click to collapse
All variants are supported

I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?

clothtalklp said:
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
Click to expand...
Click to collapse
It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.

I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.

I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.

So about unlocking - my device/version isn't supported to unlock. Any hints?

mad-murdock said:
So about unlocking - my device/version isn't supported to unlock. Any hints?
Click to expand...
Click to collapse
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.

Haxk20 said:
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Click to expand...
Click to collapse
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.

mad-murdock said:
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
Click to expand...
Click to collapse
Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.

Hi,
first off a big thank you!
I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:
1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.
Should I install latest magisk 20.1 or an earlier version?
Thank you.

Problem with TWRP
Why is the device memory data encrypted even though the device doesn 't have a password?

reintal said:
Why is the device memory data encrypted even though the device doesn 't have a password?
Click to expand...
Click to collapse
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.

Haxk20 said:
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Click to expand...
Click to collapse
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.

reintal said:
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
Click to expand...
Click to collapse
We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.