Database Develop

[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 ...

[Q] Kexec for locked bootloader

Someone have studies "Kexec" solution for locked bootloader ?
Kexec : http://en.wikipedia.org/wiki/Kexec
We keep our stock kernel with bootloader locked (not unlocked allowed), but at start (early), we run the kexec process witch kill in memory the stock kernel, and run custom kernel and custom rom
It's elegant, and like CWM process.
Someone have informations ?

Well, i answer myself.
Kexec need 2 parts to run.
1/ A patched stock kernel, or a patch for stock to be flashed by recovery.
This patch is needed to reinitialize CPU without a full memory scratch.
This is necessary to keep kexec alive in memory and finish to load new kernel.
A example of patch here : https://gist.github.com/Tasssadar/6687647
and here : https://gist.github.com/4558647
These patch are for S4Pro APQ8064 CPU
Config Option :
•CONFIG_KEXEC=y
•CONFIG_KEXEC_HARDBOOT=y
•CONFIG_ATAGS_PROC=y
•CONFIG_GROUPER_HARDBOOT_RECOVERY=n
2/ Kernel loader
It is a userspace binary.
The command to boot is :
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
This binary "kexec" drop the memory from current stock kernel (even with a locked bootloader),
and load new kernel "initrd.img" to boot.
The command interpreter is called by command-line
To work, we need to dev a patch for stock current kernel.
The rest is easy... "just" modify a CWM to create userspace for kernels and roms on sdcard1, and the load option to boot onto
Please help us to found documentations

I think the devs will be more interested in making the camera work after an unlock.
DooMLoRD is working hard (As he always does for xperia devices) on making a recovery for LB, then I think he will spend time updating DooMKerneL to the same level as it is for other devices, then if he gets time he will work on Kexec, but he has said its low down on his todo list...

I'm waiting for a long time when you are able to load other kernel on my phone locked, if you find a solution I would be very grateful, I'm even willing donate for it
Google translator

I have the same Situation, and i would donate too

?'s about Safe Strap Roms

I'm new to flashing SafeStrap Roms and I have a couple questions
1.) Do/Can SS Roms run there own kernels say if its not in the stock rom slot
The reason I ask is I would like to enable UMS but through my research it can only be done if you are running a patched kernel to enable UMS?
2.) "Mostly seeking verification on this one" Is it true that there is currently no way to run a modded kernel on our variant because of the locked BL?
3.) Are there any Roms, &/or, Kernels currently allowing for UMS for our variant?
4.) Is Over/Under - Clocking/Volting Possible with SS Roms, with/without init.d support also With/Without Kernel Patching
5.) What is and is not possible with init.d support on our variant and could UMS be enable through the use of init.d script to change the build.prop persist.UMS.Enabled=True
Really I'm just trying to get my bearings I'm not new to Android Modding but definately new to Safestrap Roms and there ins & Outs
Any Knowledge on the subject will be greatly appreciated and may help others coming from devices that previously did not require knowledge of SafeStrap do to Non-Locked BootLoaders.
Thanks in advance

[Q] General questions about ROMs and the rooting how-to

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.

ROM with Root + Encryption + Stock Camera?

Hi,
I'm currently using a Magisk patched stock ROM for my G-973F with encryption enabled.
Is there any custom ROM that supports root and encryption (don't care if Samsung or AOSP, if FBE or FDE) while fully supporting the cameras?
It would be ideal if I can use TWRP with it.
Of course, it should ship updates regularly.
There are plenty of ROMs that have many features, but most of them don't mention encryption.
I hope someone can help me, or tell me if there isn't such a ROM.