XA2 Plus H4413 beginner questions - Root, Stock, Recovery etc.

XA2 Plus H4413 beginner questions - Root, Stock, Recovery etc. - Sony Xperia XA2 Questions & Answers

Hey out there,
I've got an almost brandnew XA2 Plus and want to use it with Custom Rom but rooted.
Root:
I guess the root of choice will be Magisk.
Bootloader unlock:
So of course I know yet, that I have to bootloader unlock the device before anything else.
Does the process wipe Userdata/factory Reset?
Recovery:
Well the recovery of choice will be twrp. I already saw, that there is a flash zip for the XA2 (non Plus) Variant "pioneer".
Why not for the xa2 plus h4413 "voyager" variant? Aren't the phones so similar that this will be possible?
Updates:
After I got a rooted phone and a new update gets released, what happens? Does it still inform me and fail updating?
I already know about the flash tool and xperifirm. Will an update with that tools successful without wiping data?
Thank you in advance.
Dennis

Related

[Q] Installation of custom ROM with DualRecovery without unlocking?

Hi,
I want to install a custom Rom on my Sony Xperia Z1 compact, either CyanogenMod or a Rom from Free Xperia. I wondered if I still have to unlock the bootloader after installation of [NUT]'s DualRecovery.
First the specs of my phone:
Andoroid 4.4.2
Z1C D5503
Build# 14.3.A.0.757
The phone is already rooted using, EasyRootTool v12.4 and SuperSu. Also I installed [NUT]'s DualRecovery:
Z1C-lockeddualrecovery 2.8.14-RELEASE.installer.zip
I also made a backup of the Trim Area and all other partitions using TWRP.
According to the installation instruction for CyanogenMod I'd need to unlock the bootloader and then install ClockworkMod Recovery. And then use CWM to install CyanogenMod (I prefer the sideload method).
I understand the instruction in a way that I have to unlock the device to install CWM.
But after the installation of DualRecovery I already have CWM on the phone. Can I directly boot into CWM to install CyanogenMod without unlocking the device first? I mean CWM is already there to install an image of a different Rom.
Would be great if somebody could tell me if this works. Otherwise I'll get an unlock code and perform the normal steps listed in the Wiki of CyanogenMod. I think I could use those steps to install Free Xperia also.
Thanks!

If you will install cm without unlock bootloader your phone will stuck at Sony logo or get bootloop or soft brick so I recommend to unlock bootloader firstly and after that install any cm roms or custom kernel
Sent from my D5503 using Tapatalk

Thanks a lot for your answer! That probably saved me from some trouble.
So the boot loader will simply not accept booting a non Sony Firmware without unlocking. Do I understand that correctly?
Will it be possible to install CM after unlocking the bootloader simply by booting to the already installed CWM?

Best way to root,unlock BL and install custom recovery

I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one

bolcna said:
I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6

levone1 said:
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
Click to expand...
Click to collapse
Do i have to be rooted to backup TA partition

bolcna said:
Do i have to be rooted to backup TA partition
Click to expand...
Click to collapse
I don't think so. Just need adb...

I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
bolcna said:
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps
Click to expand...
Click to collapse
I would go with unlock bl method. You can restore TA after rooting so you done lose drm, and it's easy to root with unlocked bl - https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6

OTA Update without data loss from 5.0.2 to 5.0.3 and Unlocked Bootloader

I have an important question.
I'm currently in stock 5.0.2, with unlocked bootloader, no custom recovery, and no root.
Now I'm getting this screen in the Update menú: "OEM unlock is detected, system will begin downloading the full upgrade package. To ensure your data integrity please perform a backup" (see attached image).
Can anybody confirm if it is safe to update (from 5.0.2 to 5.0.3, in my case) with an unlocked bootloader (with stock recovery, and no root)?
I read in some post of OP5 forums (not 5T) that upgrading from Nougat to Oreo with an open bootloader could result in a bootloop, forcing to "wipe data" for getting the device to boot, and hence losing all data... I know that if I lock the bootloader again, it will wipe my data, and I don't want to.
I also know that a modified system (with custom recovery or root) could result in a bootloop after update, but I want to emphasize that my OP5T has just an unlocked bootloader, but it has stock recovery and it is not rooted.
So, is it possible to update to 5.0.3 with an unlocked bootloader (stock recovery, no root) without any issues or data loss?
The strangest thing is that I hadn't any warning like that when I upgraded from 4.7.6 (Nougat) to 5.0.2 (Oreo)...
Thanks in advance.

I upgraded my phone with a custom recovery installed and had no issues at all, so having the OEM recovery shouldn't give you trouble at all.
The warning is there because 1+ is probably aware that people who unlock their bootloaders do so in order to install custom ROM's and kernels and hence they need a custom recovery installed. That's probably why it downloaded the full size zip instead of the smaller OTA.

HueleSnaiL said:
I upgraded my phone with a custom recovery installed and had no issues at all, so having the OEM recovery shouldn't give you trouble at all.
The warning is there because 1+ is probably aware that people who unlock their bootloaders do so in order to install custom ROM's and kernels and hence they need a custom recovery installed. That's probably why it downloaded the full size zip instead of the smaller OTA.
Click to expand...
Click to collapse
Well, thank you for your answer.
Finally, I did the update. It downloaded the full size zip (1.6 GB), and upgraded the device from 5.0.2 to 5.0.3 with no trouble at all. So, at least in my case, having an unlocked bootloader didn't make any problem to update my OP5T.

Installing Pie OTA while rooted.

Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.

Uses the Lenovo Moto Assistant. Remembering that the G6 Play stock rom will be installed on your device. That way, there will be no more root (however you can install later) and the memory will be formatted
https:// support.lenovo.com/br/pt/downloads/ds101291
Remove space after two bars

synaethe said:
Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.
Click to expand...
Click to collapse
Just reflash stock firmware and don't root. You cannot install updates from ota once you root

synaethe said:
Hi I have a virgin mobile Moto g6 play. I recently rooted it with magisk and installed twrp. I just got a notification that pie OTA is ready however I know it might brick if I install the OTA. What is the best way to go about installing it. Do I have to manually reflash stock Oreo in order to update or is there another way? Thanks for your help.
Click to expand...
Click to collapse
I just downloaded the full pie firmware from mirrors, flashed with RSDlite (servicefile). Rebooted bootloader, flashed TWRP. Boot to TWRP, flash encryption disabler and magisk.
Still unencrypted, all is well.

Just download the updated firmware from Lolinet and Flash it without erasing data

Root magisk questions

Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.

Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks

Develop Bugs

welcome