Database Users

[Knowledge Base] Introduction to the Sony (-Ericsson) Xperia Galaxy

But... why?
Well, many people like and buy the Xperia line of devices currently on the market who previously owned a Samsung, LG or HTC. There are many differences in hardware, but most certainly in how Sony perceives the Android ecosystem and how it differs from the other major brands. This (noob) guide is meant to help people on the path to the Sony side I'm sure it contains lots of info which is even useful for the old timers
Things which differ a LOT from the other brands:
First and foremost: no recovery partition;
Second but not least: no download mode.
Sony has replaced the Android recovery partition with the FOTA kernel, which is meant to aid the device in rolling out OTA updates, which allow kernel updates without the risk of bricking the device. I hear you scream: "But wait, what about the recovery partition announcement by Sony themselves!?", well the answer is simple: that is meant for unlocked bootloader devices ONLY, as a part of their "Open Devices" program.
What is Flashmode, Flashtool and what are these FTF and SIN files I am reading about?
I'm going to quote @Androxyde here (it's a straight copy of his index page), as he is the maintainer of the tool:
Flashtool is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS/SUS or PC Companion.
Based on a command line tool written by @Bin4ry (Andreas Makris), I brought a user interface to sin files flashing.
We worked together to add more features to the tool such as rooting methods implementation or TA backup / restore.
Then I took the lead and got some advice and help from him occasionally on some features like rom cleaner or bootloader unlocking.
From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares) and more features have been implemented.
But flashing firmwares is still the core of Flashtool (that is updated at least to follow Sony improvements around sin files) and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable
The flashing feature as well as bootloader unlock feature are available whatever the phone is recognized or not by the application. What is only mandatory for flashing is to own the FTF file according to the device you want to flash it on.
Why should I use Flashtool?
Once bootloader unlocked, official sony tools do not work anymore.
Using official sony tools, you can only upgrade. No downgrade possible.
Using flashtool, you can choose what to flash and what not to flash. This said, many rooting scenarios are available implying kernel only downgrade to retrieve a patched rooting exploit and then flash back the right kernel.
You said unlocking bootloader?
This process gives you the opportunity to flash custom roms such as CyanogenMod ROMs.
I invite you to visit the FXP Project that brings CM and AOSP to xperia devices.
Click to expand...
Click to collapse
To complete this explanation, Sony devices know 2 bootloader based flash modes:
Flashmode (This is the S1 flash protocol @Androxyde wrote about)
Fastboot (This is the original, unmodified fastboot mode from Google)
In the past there was the Sony-Ericsson Update Software/Service (SEUS, later named SUS because Ericsson got removed from the name) which could update your device to the latest software or recover it from an inoperable state. PC Companion was less of a tool for updating and more of making backups, installing applications and managing the device storage. Sometime the past 3-4 years Sony merged the 2 programs, so if people on XDA or anywhere on the web talk about using PC Companion to restore their device, they are not wrong, they are simply using the latest version
Sony recently released their own package called 'flash tool' (to add to the confusion of noobs in the community), which deep down is a little easier to use and stripped down version of EMMA, which is a tool we mere mortals will probably never use as EMMA is the flash tool for Sony's repair shops and tech support. It's primary function is to allow owners of an unlocked bootloader device (or, 'open device' as Sony named it) to still use Sony firmwares and update their device, because as soon as you unlock the bootloader, the OTA updates will stop.
Things to remember on the files used by these tools:
An FTF file is basically not more then a ZIP archive containing multiple SIN files, you can open the FTF using 7z/WinZip/WinRar and look inside it.
A SIN file is a disk/partition image, which is encrypted by Sony. S1 (the bootloader) will check this encryption to make sure the image was not tampered with before it accepts it for flashing.
Fastboot flashing will always fail when the device is still in a locked bootloader state. For some models it is even disabled entirely or non-functional until you unlock the bootloader.
I am reading about the TA, what is it, why should I make a backup?
The TA partition (Trim Area) is a signed partition which holds various things which are unique to your device, like the device's IMEI, DRM keys and bootloader settings and configuration options. This partition can not be exchanged between devices, because it really is unique. If you would flash the TA backup from someone else it will cause a hard-brick rendering your device only useful as a paperweight...
When you unlock your bootloader you will lose all the DRM features on your device, this makes it valuable to have a backup of the unmodified version stowed away somewhere safe. You will need root level access to create that backup before unlocking. There is a tool called Backup TA which is widely used to create and restore backups of the TA partition. TWRP in XZDualRecovery can do the same.
When you restore the backup TA partition you made before unlocking the bootloader you will essentially re-lock the bootloader and restores the DRM keys. This process is (as far as we know up to now) undetectable by Sony's support staff, which makes it easy to restore the phone to stock for warranty driven support issues as unlocking your bootloader will void your warranty on the device (it is subject to local law though). That is why, for a lot of owners of a Sony device at least, it is considered to be the "Holy Grail" and is usually the reason for a lot of users to wait for a root exploit to be found before unlocking their bootloader.
Okay, I get it now. I would like to unlock my bootloader, how to proceed?
I'm not here to rewrite everything other people or Sony themselves can write just as well or even better, so I have a link for you:
http://developer.sonymobile.com/unlockbootloader/
Read it, it will teach you just about everything you need to know.
Once your bootloader is unlocked, your device will be much like a Nexus device when it comes to rooting, excluding the recovery partition, so that's why we flash or hotboot a custom kernel with a recovery, by using fastboot. If you are afraid of a terminal and typing commands, you can use a tool like QuickIMG or Flashtool to make your life easier.
Right, now I want root!
Well, if you have an 'open device', this is a lot easier then you think. Just remember that using root exploit kits is unnecessary and in some cases even risky as some packages do funky things or jeopardize your privacy.
Try to find a 'stock based' custom kernel. These are custom kernels built by the community to add features to the kernel but are meant to work with Sony's stock firmwares. I'm the maintainer of XZDualRecovery myself and created the Kernel Builder for the supported devices.
These custom kernels will NOT root your device (unless otherwise stated by the creator), but introduce a recovery to the boot process and with that you will be able to flash SuperSU to root your ROM.
But you just said Sony devices don't have a recovery partition, please... UN-confuse me!!
Yes, I did, and I'm right: there have been bright minds in the community who included a recovery in the boot image (the kernel partition) in the past and that way included a recovery on our Sony devices.
With the current 'open devices' policy from Sony, we now have:
Recovery stored inside the system partition, which is meant for locked bootloader devices (closed devices) because they can not run custom kernels;
Recovery stored in the boot image (for open devices);
Recovery stored on the FOTA partition, but with a trigger from the regular boot image at boot (also for open devices);
Recovery stored on the FOTA partition -renamed to recovery- together with an updated bootloader (for open devices, of course).
Hmm, okay... it's still confusing, but OK. My service menu says I'm rooted, but none of the root apps work properly, what gives?!
If you open the phone dialer app and on the keys see the letters below the digits, you can spell the word SERVICE. Type *#*#SERVICE#*#* and a service menu will pop up. Tap 'Service Info' and then 'Configuration'. Then you will see one of these lines there almost on the bottom of the list:
"Rooting status: unknown": it's probably unlocked, but it was unable to verify that;
"Rooting status: rooted": you have unlocked the bootloader;
"Unlock bootloader allowed: YES/NO": this tells you if the bootloader is (vendor-) locked or not, if it says NO, you're out of luck.
The rooting status there is not telling your system is rooted, it tells you your bootloader is and will allow custom rom/kernel flashing. Don't confuse these two.
I'm not allowed to unlock my bootloader But I still want root, can I?
In some cases you can. It depends on the bugs found in specific firmware versions which allow a root exploit to be developed.
From the 2015 range of Xperia devices Sony started using dm-verity, which causes a bootloop once the system partition is modified. This modification of the system partition will be required to include a SU binary in the system to obtain root, so until a dm-verity defeating option is found, locked bootloader root or recovery will not be possible.
For older models, check the device forums and the cross device development forums to check out the community rootkits available. Usually it will tell you what ROM version it is intended for. Be careful with rootkits/roottools though, some are also found to be introducing malware to your device or sending privacy sensitive data to the creators. Use common sense, if you have no valid use for the root user level, keep it off your phone. If you already have recovery, you can use that to modify or clean your device instead.
I have rooted my phone, but whenever I try to modify something on it it spontaneously reboots or I get a message 'Permission denied" when trying to remount the system partition R/W! Why is that?
Like all manufacturers, Sony tries to make it difficult (or downright impossible) to modify the Android base system they created. Because if you can, anyone or anything which obtains root access can. This is a serious security risk, because if it's malware which puts itself on the system partition and locks up your phone, the only way around this is to wipe your entire device and restore a stock ROM using PC Companion or Flashtool. Of course, they have their own proprietary software to protect as well, but security is the main objective here. The really sensitive bits are stored in the TA partition as I explained earlier.
Sony (-Ericsson) had a service called RIC, which in time moved partially in to a kernel feature. What it does is monitor if system is remounted writeable. This usually is a situation you want to avoid at all costs so RIC will deny you permission, cause a kernel panic OR simply reboots your device to get out of that state.
"Remount-Reboot fix", RICKiller, RICDefeat, and XZDualRecovery all (attempt to) disable this service or stop the kernel from acting on a remount of system.
Hard-bricks, Soft-bricks, bootloops??
They are simple to understand, really:
Hard-brick, TYPICALLY NOT RECOVERABLE: The bootloader stopped functioning, this can be caused by a bad flash/update or by restoring the wrong TA backup.
Soft-Brick, ALWAYS RECOVERABLE: the system partition is corrupted or just simply empty, this causes the device to stall at boot. A soft-brick can also make the screen remain off, because of a bad or missing kernel image.
Bootloops, ALWAYS RECOVERABLE: If the system gets powered up and then reboots during the start. This can be at the kernel splash screen or during the boot animation.
In case of a Soft-brick or Bootloop:
Use the installed recovery (if it still works), PC Companion, QuickIMG or Flashtool to restore your device to working order.
In case of a Hard-brick:
You can never recover from that state without physically opening your device and do some heavy duty engineering (JTagging) on it to flash back the correct bootloader/TA (read that link to see what it would take!). This is way too difficult for 98% of the community, which means that hard-bricking your device is typically the creation of a very expensive paper weight.
Please, be extremely careful when dealing with the TA partition.
*********************************************
I will be updating the above text for sure, if you feel anything is missing, please write a post in this thread with the text you wish to include. I want this to be a community driven guide and I know a lot, but I can't know everything
*********************************************
Extended the text some more to include ideas from:
@Klaos3000
@Yenkazu
Thanks for the suggestions/additions guys! :highfive:

As it concern the recovery, i think you can create a partition with EMMA.
Sent from Greece

kos25k said:
As it concern the recovery, i think you can create a partition with EMMA.
Sent from Greece
Click to expand...
Click to collapse
Please, re-read the first part...

Can I root my iPhone 6 with this guide?
That was a bad joke.
Very useful guide. We should probably educate people around here about what an unlocked bootloader actually means and what it let us do. I'm shocked by the number of people using Kingroot and other risky closed-sourced tools, especially the ones with an unlocked bootloader.
People of earth, if your bootloader is unlocked, it means that your device will be much like a Nexus device when it comes to rooting, sans the recovery partition, so that's why we flash or hotboot a custom kernel with a recovery, by using fastboot. If you're afraid of a terminal and commands, then you can use a tool like QuickIMG. After that, you simply flash SuperSU. That's it!

You can add something about TA Partition and RIC server. :3
Good thread btw

Yenkazu said:
You can add something about TA Partition and RIC server. :3
Good thread btw
Click to expand...
Click to collapse
I'd say, give me a piece of text on the subject for the OP and I'll include it :good:

[NUT] said:
I'd say, give me a piece of text on the subject for the OP and I'll include it :good:
Click to expand...
Click to collapse
RIC, from your thread :3
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
But, it's kinda useless if people already use your DualRec, since it's already integrated xD
But more info didn't hurt (?)
TA Partition
http://forum.xda-developers.com/xperia-z/help/ta-partition-t2451186
Not really details, but user should know the impact of unlocking bootloader

Updated the OP to include info on the TA partition and RIC protection. Also included a part of the post by @Klaos3000, because it contained some useful info
Thanks guys :highfive:

Very usefull! :good: But for me 2-3 Weeks to late. I'm still quite new on Z3C and I collect all those info the old style
Without this thread you would need days to catch all dependencies - With this you would need approx. 10 min!
Very helpfull and good to link new user to...
And yes - I came form the Sammy side (of the moon ) and was a bit shocked what sony did with "open source android".
Not because of SystemUI ( I love it...) but because of all this "anti modding" stuff they build in.
Sticky? Sure - must be!

Updated the OP to include info on Hard-bricks, Soft-bricks and bootloops.

Please people, if you have anything to add to the OP, let me know!
As I said, I know a lot, but I can't know everything there is to know about Sony devices...

Good work (...as usual from your side) :good:
Very useful tutorial.
No need to write long explanations to Sony beginners anymore - just add a link from here.

Really Helpful
Brilliant.....Really it deserves place at (Sticky Threads).I think if you add minimum One Custom Kernel(for stock firmware)
of every devices..That would b very helpful to recover from Soft bricks.Then this thread will be an "ALL IN 1" thread.Its my Opinion after all...Brilliant work.

Need a little advice.
Hi,
I have a ZL with Locked bootloader and your ZL-lockeddualrecovery2.8.22 installed
I am on stock 5.0.2 now Rooted thanks to your awesome recovery.
Question is now I have your dual recovery would I be able to simply flash crDroid CM zip Thread Here and others like it or would I still need to unlock the bootloader Edit OP of ROM says it is required
So if I flashed the above would it replace your recovery with the boot.img in the zip
Sorry for the noob questions but I am new to Sony devices and still taking baby steps with this phone
I can unlock the bootloader no problem but I am more concerned about your recovery been replaced.
Thanks in advance :good:

bigrammy said:
Hi,
I have a ZL with Locked bootloader and your ZL-lockeddualrecovery2.8.22 installed
I am on stock 5.0.2 now Rooted thanks to your awesome recovery.
Question is now I have your dual recovery would I be able to simply flash crDroid CM zip Thread Here and others like it or would I still need to unlock the bootloader Edit OP of ROM says it is required
So if I flashed the above would it replace your recovery with the boot.img in the zip
Sorry for the noob questions but I am new to Sony devices and still taking baby steps with this phone
I can unlock the bootloader no problem but I am more concerned about your recovery been replaced.
Thanks in advance :good:
Click to expand...
Click to collapse
As long as your phone is locked, you only can flash stockroms and stock-kernels.
You also have to use recovery for stockrom, because you kernel is "untouchable" and recovery have to put in /data and /system partition and can't be put in kernel.
All other roms/kernels will end in errors while flashing.
If you have unlocked your BL, you can flash any rom and kernel you want, as long as your phone is supporting it.
Yes, by flashing a zip, your kernel will be replaced and in most cases they have a recovery in it.
By flashing a rom from another version or changing from stock-based roms to i.e. CM-roms or Omni and vice versa, you have to unpack the kernel (boot.img) by hand and flash (fastboot) this first, before you flash (after a reboot in recovery) the whole zip.
Otherwise it could end in bootloop.
Because of (i most cases) wiping /system, /data while installation, your stock-recovery will deleted too. This depends of the work of the installer in the zip file.
Btw... before unlocking your phone, backup your TA ( with FlashTool). This TA is unique and you may use it to lock your phone again later.
And... if your phone is unlocked - no fear of losing recovery. You always can flash another one with fastboot again.
Someone correct me, if i was wrong or forgot something.

@bigrammi, you can always try yo repack the CM kernel using my kernel builder, that way you will still have XZDualRecovery but then included in the boot image, so no risk of losing it...

akkufix said:
As long as your phone is locked, you only can flash stockroms and stock-kernels.
You also have to use recovery for stockrom, because you kernel is "untouchable" and recovery have to put in /data and /system partition and can't be put in kernel.
All other roms/kernels will end in errors while flashing.
If you have unlocked your BL, you can flash any rom and kernel you want, as long as your phone is supporting it.
Yes, by flashing a zip, your kernel will be replaced and in most cases they have a recovery in it.
By flashing a rom from another version or changing from stock-based roms to i.e. CM-roms or Omni and vice versa, you have to unpack the kernel (boot.img) by hand and flash (fastboot) this first, before you flash (after a reboot in recovery) the whole zip.
Otherwise it could end in bootloop.
Because of (i most cases) wiping /system, /data while installation, your stock-recovery will deleted too. This depends of the work of the installer in the zip file.
Btw... before unlocking your phone, backup your TA ( with FlashTool). This TA is unique and you may use it to lock your phone again later.
And... if your phone is unlocked - no fear of losing recovery. You always can flash another one with fastboot again.
Someone correct me, if i was wrong or forgot something.
Click to expand...
Click to collapse
Thanks yet again bro :highfive:
Wow these Sony Xperia's take some figuring out :laugh:
I think I have just about got my head around it all now
I have managed to get the TA backed up with TWRP and Flashtool so I should be safe now
I will have to unlock the bootloader just to stop it nagging me to upgrade :laugh:
@Nut Thanks bro I will take a look at your suggestion it's a little more complicated than what I am used to or should I say different.

bigrammy said:
[...]
@Nut Thanks bro I will take a look at your suggestion it's a little more complicated than what I am used to or should I say different.
Click to expand...
Click to collapse
Well, i saw HTC M7 in your signature. If you were able to unlocked, s-off-ed, re-flashed firmware and rooted this beast - you don't need to have any fear about a Sony device.

[NUT] said:
@bigrammymi, you can always try yo repack the CM kernel using my kernel builder, that way you will still have XZDualRecovery but then included in the boot image, so no risk of losing it...
Click to expand...
Click to collapse
Hi @Nut,
I thought I would take your advice and expected to download a tool to unpack everything and pick through the files and start editing init.rc etc etc :silly:
I had no idea this was a fully automated Online tool
I still can't quite believe it you're a genius!! :angel:
A BIG THANKS to All the Xperia dev's helpful community members and especially the tool creators XZDualRecovery, Flashtool, XperiFirm and PRFCreator etc you're all Awesome :highfive:
I fear I will become lazy with such great dev's :laugh:

bigrammy said:
Hi @Nut,
I thought I would take your advice and expected to download a tool to unpack everything and pick through the files and start editing init.rc etc etc :silly:
I had no idea this was a fully automated Online tool
I still can't quite believe it you're a genius!! :angel:
A BIG THANKS to All the Xperia dev's helpful community members and especially the tool creators XZDualRecovery, Flashtool, XperiFirm and PRFCreator etc you're all Awesome :highfive:
I fear I will become lazy with such great dev's :laugh:
Click to expand...
Click to collapse
Thanks, glad to have been of help to you

Please Point Me to The Right Direction

Hello the Wonderful and Fantastic Members of the XDA Community,
I'm in the process of researching on how to unlock bootloader, install magix and ultimately root the phone, and I hope that someone can point me to the right guides to accomplish these steps. I have been trying to figure it out but would feel much better if someone can point me to the right guide as opposed to me blindly guessing which guide I should follow. This is what I know so far:
1. I believe that in order to use Magix, I need to have a "Custom Recovery" which requires I unlock phone's "bootloader". But before I can do that, I need to have a stock system, which DrakenFX had gracious posted but I'm not too sure how to find. Can someone point me to the right forum to obtain the stock system image from DrakenFX and the guide to unlocking the bootloader for this phone? What are some precautions I should take prior to attempting to unlock the bootloader? And what do I need to do with the stock system if everything goes south with my attempt? I'm currently on A2017UV1.0.0B27 (after the latest update). Will the stock system work with that?
2. I believe that after I unlock the bootloader, I have to install the Custom Recovery, which I think I should use TWRP - is it compatible with magix? After I install TWRP, I need to use TWRP to "flash" magix onto my phone? How can I install TWRP and use it to flash magix? What are some of the precautions I need to take before my attempt to complete step 2?
3. I think after I installed the customer recovery and flash magix, rooting "should" be easier for me, but please point me to the appropriate guide to accomplish that.
Extra Question: I read in one of the forums that after I unlock the bootloader, I will no longer able to receive On The Air updates, how can I continue to receive these updates after bootloader is unlocked and what happens when ZTE roll out Android N for the Axon 7? Will I be able to update to that version?
Here are all the facts about my phone:
Model: ZTE A2017U
Android Version: 6.0.1
Kernel Version: 3.18.20
Build Number: A2017UV1.0.0B27
Thank you all so very much for your patience, understanding, and kind help, I'm forever grateful!

First flash TWRP by following this guide: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Then unlock your bootloader by following this guide: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
I've never used Magisk before (I just stick with SuperSU), so I'll leave that part to someone else.
As for the extra question:
If you used ZTE's official bootloader unlock method (which required you to submit a form with your IMEI), you'll no longer get OTAs, but if you do it all unofficially (like these guides), you'll still get OTAs. HOWEVER, the OTAs will not install if you make changes to the device besides bootloader unlock. If you have a custom recovery it won't apply. If you have systemless root (which modifies the boot image) it won't apply. If you use Magisk (which modifies the boot image) it won't apply. If you make changes to /system it won't apply. So basically, besides having an unlocked bootloader, you have to be full and complete stock to install OTAs.
However, after an OTA comes out, I suspect that someone will make a TWRP-flashable version.

@xtermmin Thank you so much for your reply, I greatly appreciate it!
Quick question, Is there a way to install TWRP without having to root first? The reason I ask was according to Magix, it must be flashed prior to the system being rooted.

@xtermmin Thank you so much for your reply, I greatly appreciate it!
Quick question, Is there a way to install TWRP without having to root first? The reason I ask was according to Magix, it must be flashed prior to the system being rooted.
Click to expand...
Click to collapse
You don't need to root to flash TWRP.

[Help] Moto g4 plus root error..please help

Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please

Adarsh balu said:
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Click to expand...
Click to collapse
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
EDIT - I understand you're desperate for help resolving this, please don't post the same thing in 3 places if you can.

echo92 said:
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
Click to expand...
Click to collapse
Here it is
I did not use kernel
Oem done

twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643

All steps are followed until flashing of supersu..The error comes there..is there any xt 1643 users who could suggest a correct reliable and error free method for this

Adarsh balu said:
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
Click to expand...
Click to collapse
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.

echo92 said:
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
Click to expand...
Click to collapse
Thanks..let me test it....
Any way thnq for the suggestions...:good:

Tell me will i be able to update if android O comes for g4 plus..please reply fast

Adarsh balu said:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Click to expand...
Click to collapse
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?

echo92 said:
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
Click to expand...
Click to collapse
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share

Adarsh balu said:
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Click to expand...
Click to collapse
Again, Android O hasn't been formally announced yet...
I see you've already gotten an answer from tywinlannister regarding this question https://forum.xda-developers.com/showpost.php?p=71265934&postcount=249
I don't see much to add to his well thought out reply except if you're staying with stock (assuming you're using temporary TWRP):
1) Unroot completely using the SuperSU settings panel or follow the unrooting instructions for your superuser app.
2) Reboot into temporary TWRP, restore your boot.img (if you flashed ElementalX kernel) from within TWRP (if I recall, it's Restore >Select image and then assign it as a boot image). If you did not make a backup of your boot.img, there are images around (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/1643-indian-version-stock-boot-modem-t3460615 - i don't know if this is for nougat or marshmallow - download and extract the rar file, copy the extracted boot.img to your device and boot into temporary TWRP, then flash the boot.img).
3) Reboot and you should be fully stock - with stock kernel/boot.img, recovery and no root.
1a) As tywinlannister linked, you could just reflash the latest fastboot image which would remove root and give you a stock boot, which would be the best for reliability (which as of this post is this: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Thus, when/if Android O does arrive, you should be able to update via OTA. It's gonna be at least 6-12 months away for the update, if previous Android updates have been anything to go by.

Theoretical root for SM-J320VPP?

So it's been a while since discussion about this specific model, but I was wondering if it would be at all possible to root this with Magisk?
Since Magisk can apply root by patching boot image file, I figured it could technically be possible since in this thread:
https://forum.xda-developers.com/galaxy-j3-2016/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049
There is a link to a flashable ZIP to "access GSM" with this model phone, found here:
https://mega.nz/#!mtNEibLa!NmVJ7RM0fSDwXdD3CTKi0fVQgYdIMP6m8THRQLyJQRw
The interesting thing about it is that ZIP contains a boot.img file, so what I was wondering, would that the stock boot image file needed for Magisk?
There isn't much information about what's supplied in that ZIP nor have people mentioned it's use or anything, but I was wondering if it could at all be tested to possibly work. Or if whatever is in that ZIP is even the stock firmware.
I can't necessarily test it myself since I need my phone however, can anyone verify the contents of the ZIP or boot.img? It would be a pretty convenient if this was all it takes.

Without root I doubt you will be able to flash anything that isn't an official Samsung firmware update. And depending on which branding your device has,you may not even be able to flash firmware of any type whether it be an update or full firmware. Some carriers insist that Samsung fully lock down the bootloader thus completely crippling the device. U.S. carriers doing this are various. Especially if it is pre-paid. Best advice is to research any device before you purchase it. See if root has been achieved. If not and that device has been out for some time. Avoid it. Pick a device you know has gained root from among the choices offered by any carrier. It would seem you have one of the many locked bootloader turd phones put out by Verizon,Sprint,TRACTURD and so forth. Locked bootloader that won't recognize any flash that isn't signed. Odin or not the flash will fail. Time to flush that turd and find a better alternative.
Fivavoa said:
So it's been a while since discussion about this specific model, but I was wondering if it would be at all possible to root this with Magisk?
Since Magisk can apply root by patching boot image file, I figured it could technically be possible since in this thread:
https://forum.xda-developers.com/galaxy-j3-2016/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049
There is a link to a flashable ZIP to "access GSM" with this model phone, found here:
https://mega.nz/#!mtNEibLa!NmVJ7RM0fSDwXdD3CTKi0fVQgYdIMP6m8THRQLyJQRw
The interesting thing about it is that ZIP contains a boot.img file, so what I was wondering, would that the stock boot image file needed for Magisk?
There isn't much information about what's supplied in that ZIP nor have people mentioned it's use or anything, but I was wondering if it could at all be tested to possibly work. Or if whatever is in that ZIP is even the stock firmware.
I can't necessarily test it myself since I need my phone however, can anyone verify the contents of the ZIP or boot.img? It would be a pretty convenient if this was all it takes.
Click to expand...
Click to collapse

New!! [MTK-SU temp root] TA Backup BEFORE Unlocking your bootloader. MTK SoC Only!!

This works for MediaTek SoC ONLY!! XA XA1 and variants of C4/5's, M5's, L1, L2 and Maybe even L3's
Update: A Bootless/System only Root is now reported as working again thanks to diplomatic.
Can XA1 users who have benefited from mtk-su and the System only Root please report back their experience here also so other XA1 users will know what to expect. ​
Thanks to dev @diplomatic All Sony Mediatek devices should now be able to obtain a /ta partition backup before unlocking their bootloader. :victory:
It works by getting temporary "root" with a easy to use method which will then allow you to grab a /ta backup via the dd cmd
I did some testing for diplomatic and I can confirm this works with my locked bootloader XA1 on Android 8.0 lesser versions should also work.
I also tested this on my other Mediatek devices with the same successful results upto and including Android 8.1
Please visit diplomatic's Thread HERE for instructions and details also remember to Hit his Thanks Button or the :good: Thumbs Up Button if your using a phone app.
How do I backup the /ta ???
See this here.
Use MTK-SU to get temp root then use my dd backup helper script
Thread is HERE for instructions and info
https://github.com/bigrammy/dd-backup-helper-script/blob/master/dd-backup.sh
I am new to Sony whats all this stuff mean???
The below will help anyone new to Sony Gain a little insight into the slight differences over stock Android.
So take time to read it
New to Sony then read the info HERE it will save you a lot of head scratching and google time and I created the thread for just such as you. :good:
As a Footnote for the over enthusiastic:
You only need dd backup what is specific to your device so everything that is NOT included in the FlashTool/Xperifirm firmwares. Like the /TA, /Protect_f, /Protect_s, to name a few for example.
Backing up stock boot or fotakernel is kinda pointless because these are contained in the XperiFirm/FlashTool firmwares and can be easily restored using FlashTool or xflasher to flash those Stock ROM parts.

This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.

Ticklefish said:
This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.
Click to expand...
Click to collapse
Sure. But you will be able to temp root phone.

Ticklefish said:
This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.
Click to expand...
Click to collapse
Sorry for the super late reply but for some reason I don't get a notification when someone post's I guess I must have forgot to subscribe to my own thread. :silly:
Why cant you unlock your bootloader

bigrammy said:
Sorry for the super late reply but for some reason I don't get a notification when someone post's I guess I must have forgot to subscribe to my own thread. :silly:
Why cant you unlock your bootloader
Click to expand...
Click to collapse
I have the message "bootloader unlock allowed: no" so I'm stuck.
I was hoping to be able to install TWRP so I can start modding my system apps.
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I have the message "bootloader unlock allowed: no" so I'm stuck.
I was hoping to be able to install TWRP so I can start modding my system apps.
Sent from my Sony Xperia XA1 using XDA Labs
Click to expand...
Click to collapse
Hmm My XA1 is with a relative just now so can't check but we used to have this problem on the C4 and C5.
I just Ignored that and tried the unlock code anyway. It worked for me on the C4 and XA but but not tested it on the XA1 so no guarantee's.
The other option is to use xflasher which worked for me on my XA1 (BL Locked) and flash only the system, boot, recovery, oem and userdata of the earliest 7.0 you can get your hands on and see if it boots. :fingers-crossed: It may even work for the preloader lk etc but I did not want to risk bricking the XA1 so never tried to flash those sensitive area's
If it does let you flash a earlier version then just wait for the ota and install it. The OTA will flash the perloader and lk of the next 7.x update and hopefully that will allow you to unlock the BL unless your phone is locked to specific carrier then I am unsure about that.
Again this is the method used on the C4/5 for rolling back to 5.0 so we could unlock the bootloader.

bigrammy said:
Hmm My XA1 is with a relative just now so can't check but we used to have this problem on the C4 and C5.
I just Ignored that and tried the unlock code anyway. It worked for me on the C4 and XA but but not tested it on the XA1 so no guarantee's.
The other option is to use xflasher which worked for me on my XA1 (BL Locked) and flash only the system, boot, recovery, oem and userdata of the earliest 7.0 you can get your hands on and see if it boots. :fingers-crossed: It may even work for the preloader lk etc but I did not want to risk bricking the XA1 so never tried to flash those sensitive area's
If it does let you flash a earlier version then just wait for the ota and install it. The OTA will flash the perloader and lk of the next 7.x update and hopefully that will allow you to unlock the BL unless your phone is locked to specific carrier then I am unsure about that.
Again this is the method used on the C4/5 for rolling back to 5.0 so we could unlock the bootloader.
Click to expand...
Click to collapse
Interesting. I might try the unlock code just to see what it does. I think Vodafone may have locked my phone, which is understandable but annoying.
I can't afford a new handset and all my old ones are either broken or so underpowered that they're pretty useless, so I won't try flashing anything right now. Too risky.

Ticklefish said:
Interesting. I might try the unlock code just to see what it does. I think Vodafone may have locked my phone, which is understandable but annoying.
I can't afford a new handset and all my old ones are either broken or so underpowered that they're pretty useless, so I won't try flashing anything right now. Too risky.
Click to expand...
Click to collapse
Hmm I thought they could only really sim lock the device but maybe that's why your not been shown the Option to unlock the bootloader.
If you have the sim lock removed by fair or fowl means then the unlock option may become available to you. I have flashed full Vodafone Virgin O2 ROM's with FlashTool before now and none ever locked the bootloader I have only ever heard of people having problems who accidentally flash the sim.lock part of the firmware. :silly:
PS: I have used these before for sim unlocking and all was ok. HERE also cheaper than most.

New bootless/System Only Root
A Heads up for everyone!!!
Well @diplomatic has done it again with a New bootless Root for locked bootloaders it has been reported to be working on the XA1 which I am sure will be good news for many. :victory:
Remember to Hit the thanks button of diplomatic or better still buy him a Beer or Pizza for liberating your phone. :good:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
@Ticklefish

Bootless magisk root
Bootless magisk root working on XA1!!!
Updated tutorial: https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135

Wow, cool! You mean I don't have to unlock my phone to get root? Can't wait to try it on my XA1...
---------------------
But seriously, this bootless root may be a bigger headline than the temp root shell itself.

diplomatic said:
Wow, cool! You mean I don't have to unlock my phone to get root? Can't wait to try it on my XA1...
---------------------
But seriously, this bootless root may be a bigger headline than the temp root shell itself.
Click to expand...
Click to collapse
Awesome work all round and yes you are correct it may even warrant a thread of its own since itś not limited to MTK devices.
On a side note.
Safestrap recovery would be the next logical thing for the XA1 then the locked bootloader circle should be complete.
It will be like running the Fire Phone again :laugh:
https://github.com/bigrammy/android_bootable_recovery-safestrap

Yeah, you're right, I'll make a new thread eventually. Just wanted to start slow and see where it goes...
Unfortunately, safestrap recovery will be problematic because this method doesn't let you write to /system or boot. It doesn't do anything about dm-verity and all that.

diplomatic said:
Yeah, you're right, I'll make a new thread eventually. Just wanted to start slow and see where it goes...
Unfortunately, safestrap recovery will be problematic because this method doesn't let you write to /system or boot. It doesn't do anything about dm-verity and all that.
Click to expand...
Click to collapse
I need to get around to unpacking the boot of the XA1 and look at the lk too. If they moved the fstab to system/vendor then there maybe a way.
My thoughts are as yet untested and based off vague memories but if I manage to put them all together I will let you know.
Real busy just now with Work and ongoing home improvements so not got much time for playing

Read this before thinking about bootless recovery:
https://source.android.com/security/verifiedboot/dm-verity

Any method to root with magisk that allows modifying / system?

leonardo.teseyra said:
Any method to root with magisk that allows modifying / system?
Click to expand...
Click to collapse
Yes for sure but you need to be officially bootloader unlocked for that.
You use the mtk-su to gain temp root then make a couple of dd backups of your /ta and any other partition you think maybe useful which is basically
anything not contained in a firmware package using FlashTool/Xperifirm
EG:
ta
nvram
nvdata
protect_f
protect_s
When you have what you need Unlock the bootloader officially.
Convert your boot.elf to boot.img have Magisk patch the new boot.img and flash it via fastboot.
If you need more detail please provide more such as your device etc it make helping easier. :good:

bigrammy said:
Yes for sure but you need to be officially bootloader unlocked for that.
You use the mtk-su to gain temp root then make a couple of dd backups of your /ta and any other partition you think maybe useful which is basically
anything not contained in a firmware package using FlashTool/Xperifirm
EG:
ta
nvram
nvdata
protect_f
protect_s
When you have what you need Unlock the bootloader officially.
Convert your boot.elf to boot.img have Magisk patch the new boot.img and flash it via fastboot.
If you need more detail please provide more such as your device etc it make helping easier. :good:
Click to expand...
Click to collapse
Thanks for the help, I have a Sony Xperia XA1 with android 8.0. Do you know of any tutorial I can follow? I need to root with magisk to be able to hide the root.

leonardo.teseyra said:
Thanks for the help, I have a Sony Xperia XA1 with android 8.0. Do you know of any tutorial I can follow? I need to root with magisk to be able to hide the root.
Click to expand...
Click to collapse
Backup your ta partition then unlock your bootloader using Sonys official method.
Flash the boot and recovery for your device which are located in this thread HERE
Format your data again with TWRP and flash magisk thats it your done.
To revert your devices back to 100% stock dd back your ta backup and reflash the 100% stock ROM using FlashTool or maybe Sonys official tool.

bigrammy said:
Backup your ta partition then unlock your bootloader using Sonys official method.
Flash the boot and recovery for your device which are located in this thread HERE
Format your data again with TWRP and flash magisk thats it your done.
To revert your devices back to 100% stock dd back your ta backup and reflash the 100% stock ROM using FlashTool or maybe Sonys official tool.
Click to expand...
Click to collapse
How can I backup my TA partition?. I have root access but I can't find /ta any where