[Q] General questions about ROMs and the rooting how-to - Xperia Z3 Compact Q&A, Help & Troubleshooting

Hi, many thanks for the great and detailed how-to. However, I think it may lack some answers to a few important questions that people who come from other phones could ask. Until now, I've been used to rooting and flashing my Galaxy Nexus which appears to be rather different from the methods on this phone. Anyway here goes: I just got my Z3 Compact. I'm willing to give the stock UI a try, especially because it has some very nice features (noise removal on camera, STAMINA mode) and a clean enough look, however I need root and don't want to put up with some of the preinstalled apps. I can then either create my own pre-rooted image or flash a custom, stock-based ROM w/ root such as SLiM. Here are my questions:
Based on the how-to, if I want to install a custom ROM such as SLiM, at which step do I need to flash it? In particular, that ROM requires "root and recovery", does that really mean that I first have to root a stock ROM and install a new pre-rooted ROM + recovery, and only then flash SLiM from recovery, or can I install it during the various stages of the how-to?
I was used to TWRP recovery remaining on my Galaxy Nexus for pretty much all its life. I don't understand: why are there so many different recoveries for the Xperia phones and why do you apparently need to flash them so often? Can't you put one there and never touch it again? Why do they sometimes come with the ROM?
Why do some custom ROMs have requirements to be running a specific version of the firmware to be installed? Can't they just be flashed from recovery? Oh and btw, is there a difference between a ROM and a "firmware" as far as Xperia-specific vocabulary goes?
Putting those questions into words, I realize I may be missing something crucial about these phones that ties recovery, ROM and kernel together in a way I'm not used to. If there is any documentation about how these general concepts work on Sony phones, I'd be happy to read it!
Thanks in advance.

Answering myself, hoping it can be helpful to people who are new to the Z3C and wondering about the same questions:
SLiM is a complete ROM, it only requires "Root and Recovery" to mean that it must be flashed from recovery -- and recovery must be installed from root anyway.
If you want to install SLiM on your first root, you must follow the how-to down to the point where you've downgraded, rooted and installed XZDualRecovery. After that you're good to go, you can wipe everything (or not) and flash SLiM.
There aren't in fact that many recoveries. Basically, the CWM recovery and its derivatives (PhilZ Touch) and TWRP. Both have different UIs and a few different extras in the way they manage backups, but they really serve the same purpose.
And then, there are things like XZDualRecovery, which includes both standard recoveries and allows to choose between them. Why include both? I don't know -- it may be related to CM ROMs needing their own recovery or just user preference --. Anyway, I suppose what makes XZDualRecovery the standard on Z2+ Xperia phones is its ease of install and the fact that it works out of the box.
Now, you need to reflash XZDualRecovery after installing a new ROM. There's a part of it that resides in the system partition and you'll lose it when you flash a new ROM; that's a big difference from what I was used to on the GNex, and many custom ROMs already include the necessary files. Be sure to check that before you flash, though.
I was mistaken, no ROM comes with a "previous ROM" requirement. Some packages (debloat releases such as serajr's for example) require an already present and rooted ROM to be installed, as they don't contain the whole system + data. They are not complete ROMs and must be flashed onto an existing, rooted ROM of the same version.
There is no real difference between ROM and "firmware", the latter is mostly what Sony uses to describe their flashable tool format releases while the former is more often used to describe custom releases. As a consequence, you'll more often see Sony's stock .FTF files described as "firmwares", and custom flashable .zip files as "ROMs".
In the end, here is what I ended up doing yesterday to my new Orange FR Z3C:
Follow the how-to to:
install the PC drivers;
downgrade to 23.0.A.2.93 stock firmware;
root the phone;
install XZDualRecovery;
Download Pandemic's pre-rooted stock 5.1.1 rom (23.4.A.0.546), reboot to recovery and flash it;
Download serajr's debloated, pre-rooted system and flash it;
Download and flash RICDefeat just to be safe;
Download and flash/install the Xposed framework and serajr's Xperia Xposed, although right now I only use it for its ability to load custom icon packs.
Huge thanks to everyone involved in the development of these tools, apps and ROMs.

Related

[Q] What do I lose when I switch to custom ROMs from stock ROMs?

I'm currently running my Note on a stock XLA4 and AbyssNote kernel and I'm considering flashing RocketROM in the hopes of improving performance and battery...
What features do I lose, if any, when I switch to a custom ROM?
I am most concerned with the following:
1. My access to Android market and being able to download the same apps as if I were on stock ROM (because I don't know how Market checks devices. )
2. Access to Samsung Apps (I would normally check all new apps offered there.)
3. The apps that originally come with the Note. (I use S Planner and S Memo a lot!)
4. Others I may not be aware of. (?)
THANK YOU IN ADVANCE, GUYS! :O
I just finished backing up mostly everything in my phone but I'm putting off wiping and flashing before I'm sure of what comes next.
It really depends on the ROM you choose. You should be able to use all the functions with most of them, but some ROMs remove Samsung stuff, some don't, some remove most and leave others (like s-memo), and some remove stuff but let you choose to install it back (like CheckROM).
Just read the ROM description post thoroughly - it should list all the stuff that was added or removed. Unless it specifically says that samsung apps/widgets were removed, or that it is AOSP, all the functions should be available.
P.S. don't forget to make a full backup in CWM Recovery before wiping/flashing in case you don't like the result or something doesn't work, so you can go back to your stock ROM.
edit: as for market, it should work with all ROMs. There are some slight problems in some ROMs, which usually means that a custom ROM will have the previous version of market (which works fine) and, to update to new market, you have to install any app from the market and then apply a fix which updates the version to the new market. Method of applying the fix can differ, but it will probably either be a one-click-fix, or you will have to reboot into recovery and choose "flash zip from (internal) sd card" and install it like you installed the ROM.

[Q] does rooting modify the original firmware?

Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Rooting itself doesn't modify anything besides installing an app called Superuser.
You deleting/disabling apps that were not meant to be disabled does.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
smoza said:
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
Click to expand...
Click to collapse
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
dr.pythagora said:
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
Click to expand...
Click to collapse
- As far as I know, you can receive updates but you cannot apply them. It will show in the notifications "Software Update, Click to download" when you download it, it will reboot to recovery and stop there. Again, I'm not 100% sure about this but this happened to me once.
- If you flash a custom kernel like Prometheus Kernel, then you will have to flash the stock boot.img if you wanna go back to stock completely. But if you never changed your kernel from stock, then you don't need to do anything. I have provided the link to stock kernel and stock recovery as well, in the Index thread. (Link in my signature)
PS - As far as Custom ROMs go, you should try the Sense Roms. All of them are based on the stock ROM so all of them are completely stable. You can always put the 'Stock theme' on these roms to make them look like the Stock ROM and you will end up with a ROM that looks exactly like Stock but performs much better and has increased functionality
Hope this was helpful. I'll be glad to answer any further questions.
It will not definitely modify your system it will add a folder to your system to access the system... and also it adds app called Superuser or SuperSU ....
Features of Rooting:
Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem.
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Most of the time,[citation needed] rooting a device voids its warranty.
From Wikipedia ...

Got new One+ 3T Some questions

I have received today my new mobile 1+ 3t a3010
oxygen 4.1.3
where should i start ?
tweaking kernel, roms...
please refer me to the right threads
thanks in advance.
- Unlock bootloader first: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
- Flash OOS 4.1.5 or the newest Openbeta (or Freedom OS if you understand what you do)
- if you need root: flash supersu or magisk
- if you want: Flash Kernel (ElementalX, Franco, Blu, Flash, etc)
- very optional: https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589
How one decides to mod the phone (custom ROMs, kernels, etc.) is completely up to personal preferences and tastes. Everyone will give you a different answer to your questions, and many owners of this phone will never mod it at all, and be completely happy. Read up on existing threads, and you'll figure out what are the best options for you. There are also plenty of existing threads with suggestions and favorites regarding ROMs, etc. so no need to start another such discussion.
So really, my advice on where to start, is to read read read. Understand the methods and steps before you begin (and that goes with any of these devices). The previous answer had some good resources, for a start. And you'll find many more useful threads in the "Guides" forum section. My additional suggestion would be to know how to return to stock with the full zips: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Along similar lines (and in agreement with the prevous answer) I would recommend updating to latest OOS 4.1.5 or Open Beta, to ensure you are on the latest firmware and modem, before doing other mods.
Thank you both for great answers,
i did successfully bootloader unlocked and twrp flashed
Now which is oos 4.1.5 you talking about ?
like https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
and this https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
is ok to flash now ?
You posted the same thread twice. But yes, that is correct. You'll want the full zip from Post #2 of that thread. Then follow the instructions in Post #3, using second method, for users with TWRP. It also says for root users, but it's irrelevant whether you are rooted or not, as long as you have TWRP installed you'll need to use the full zip; as stated at the bottom of Post #3, if you use the OTA with TWRP, it will fail or you will soft brick!
Also, if you root, TWRP will stick (this is what I always do after flashing the updates). If you choose not to root after installing 4.1.5, you might find that TWRP is removed. But you might be able to avoid this by booting back to TWRP after installing 4.1.5, butbefore rebooting to OS. Otherwise, if you find TWRP is gone, just flash again using fastboot.
Tell me please,
can i flash custom kernel being on stock 3.1.5 with stock recovery?
Just stick with stock. LineageOS is kind of awful. Theres a million bugs that affect daily usage even on a perfect install and setup. Its just not worth it. I'd go with freedomOS CE 2.10. Very solid rom with nice extra options to remove useless google apps like photos and google music youtube and the like. It even allows magisk which is a fantastic rooting systemless method. I would also add the adblocked youtube module or app from a thread by Master_T. Just stick with basic rooting function and your experience will be superb. The more advanced you go with this phone the more prone to breaking something you get.
You were already advised how to mod the phone, back up in Post #2 above. I assume you mean locked bootloader along with stock recovery. I believe what you suggest won't work, and the stock recovery will not let you flash an unsigned zip. You need to unlock your bootloader and flash custom recovery TWRP. Then you can flash a custom kernel. But again, it's already been described by another back up on Post #2.
Also, I'm pretty sure you mean 4.1.5 (not 3.1.5), as you already stated the phone came with 4.1.3 (so 3.1.5 wouldn't make much sense). So please proofread before posting, to avoid confusion (and I was really confused by the number 3.1.5 at first).

How to upgrade rooted SM-T719 from Android 6.0.1 to Android 7 or 8

Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!
There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data
Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted

Multiple problems with custom roms - URGENT

Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.

Categories

Resources