Hi all,
Just got my Xperia S and really love the phone with fantastic design and awesome screen. I really intend to gain root access for my phone to troubleshoot the battery drain issue further (and using some app for better control over the setting). Here's a few queries I have (and some partially answered by some of my searches on the forum):
Will I get any OTA or official firmware update shall I just root my phone with locked bootloader? (I won't mess with custom recovery or ROM)
I suppose I could still claim my warranty. But is there anyway to remove any traces completely to prevent them from finding out? Just removing the superuser app?
If in the future I would like to have access to custom recovery so that I could flash ROM, I suppose I must unlock the bootloader right? (at least until someone gets a workaround for locked bootloader)
The tool I will use for rooting is by Bin4ry. I am on the latest ICS firmware.
tanjinjack said:
Hi all,
Just got my Xperia S and really love the phone with fantastic design and awesome screen. I really intend to gain root access for my phone to troubleshoot the battery drain issue further (and using some app for better control over the setting). Here's a few queries I have (and some partially answered by some of my searches on the forum):
Will I get any OTA or official firmware update shall I just root my phone with locked bootloader? (I won't mess with custom recovery or ROM)
I suppose I could still claim my warranty. But is there anyway to remove any traces completely to prevent them from finding out? Just removing the superuser app?
If in the future I would like to have access to custom recovery so that I could flash ROM, I suppose I must unlock the bootloader right? (at least until someone gets a workaround for locked bootloader)
The tool I will use for rooting is by Bin4ry. I am on the latest ICS firmware.
Click to expand...
Click to collapse
Yes you'll definitely get official update
To remove trace completely just flash an official ROM via flashtool (official fw can be obtained at dev section)
No can install some stock based Custom Rom and CWM in locked bootloader
Eg : XTX,dualcore,Xcream,etc
What you can't do is flash a kernel. You'll need to flash a kernel to install Cyanogen Mod or Paranoid based rom
Sent from my Xperia S using xda premium
Theonlyzii said:
Yes you'll definitely get official update
To remove trace completely just flash an official ROM via flashtool (official fw can be obtained at dev section)
No can install some stock based Custom Rom and CWM in locked bootloader
Eg : XTX,dualcore,Xcream,etc
What you can't do is flash a kernel. You'll need to flash a kernel to install Cyanogen Mod or Paranoid based rom
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
Hmm, I guess I could get official update, just worry that I would lose root during the update. I think I could still try to retain my root using some app right? (LOL, I am a bit outdated about all these stuff - was using a HTC Desire where 2.3 is the best we could go)
I am observing that my screen is a bit yellowish throughout, perhaps I will send in for a warranty before I do anything.
Thanks for the reply. Really appreciate it and clear off some doubts.
Related
Hello
Since this will be my first nexus device , I have some questions regarding rooting and recoveries and what they affect on nexus devices specifically this nexus.
What affects the ability to receive official google updates?
If you are rooted do you always loose root if a new update comes? Does root affect the ability to receive updates?
If you have a custom recovery is it possible to receive official updates from google?
Thanks
Sent from my A500 using Tapatalk
I also have one quick question about rooting. I am totally new to this, I used android on my HD2 but it was always SD card version.
Does rooting affect warranty? I don't think it matters, but I'm with O2.
Official Updates
I think you can, however if you do you can lose root
Custom Recovery
Yes its possible. I believe koush is working on a stable CWM
Warranty
Yes, you will lose it and the Nexus will tell you before it lets you confirm you want to do it.
Im currently trying to get my Nexus back to unrooted status so I can send it back and get it on PAYG. I'll write up a tutorial once I've figured it out
TulpiX said:
Hello
Since this will be my first nexus device , I have some questions regarding rooting and recoveries and what they affect on nexus devices specifically this nexus.
What affects the ability to receive official google updates?
If you are rooted do you always loose root if a new update comes? Does root affect the ability to receive updates?
If you have a custom recovery is it possible to receive official updates from google?
Thanks
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
1. Rooting your device wont affect your ability to receive updates, Custom ROMs do.
2. when you receive a new OTA you WILL lose root, this is the reason custom ROMs dont accept OTA updates.
3 As far as custom recoveries, I dont think that affects your ability to receive updates, Even then you can still flash an official update.zip via a custom recovery.
rokfor2000 said:
I also have one quick question about rooting. I am totally new to this, I used android on my HD2 but it was always SD card version.
Does rooting affect warranty? I don't think it matters, but I'm with O2.
Click to expand...
Click to collapse
1. Eh grey area. Rooting doesnt void your warranty, but unlocking the bootloader does. As of yet there is no way to re-lock the bootloader.
slowz3r said:
1. Rooting your device wont affect your ability to receive updates, Custom ROMs do.
2. when you receive a new OTA you WILL lose root, this is the reason custom ROMs dont accept OTA updates.
3 As far as custom recoveries, I dont think that affects your ability to receive updates, Even then you can still flash an official update.zip via a custom recovery.
1. Eh grey area. Rooting doesnt void your warranty, but unlocking the bootloader does. As of yet there is no way to re-lock the bootloader.
Click to expand...
Click to collapse
fastboot oem lock does
Evostance said:
fastboot oem lock does
Click to expand...
Click to collapse
does it actually re lock your bootloader..... its been a while since I last used my NS, Since i switched to VZW
If thats the case then dont worry about warranty
Apparently it's works. But I think I've bricked my phone flashing a system.img...
Sent from my iPad 2 using Tapatalk
Ok thanks
I thought ota updates would also sometimes update stock recovery which would fail with custom recoveries and therefore no ota updates then.
So i was mistaken there?
Sent from my A500 using Tapatalk
So to be clear. I could do the following:
Get my phone
Unlock bootloader
Root it
Install cwm recovery
And this would NOT affect my ability to get ota updates?
TulpiX said:
So to be clear. I could do the following:
Get my phone
Unlock bootloader
Root it
Install cwm recovery
And this would NOT affect my ability to get ota updates?
Click to expand...
Click to collapse
pretty much, but remember an OTA will remove root/recovery
TulpiX said:
So to be clear. I could do the following:
Get my phone
Unlock bootloader
Root it
Install cwm recovery
And this would NOT affect my ability to get ota updates?
Click to expand...
Click to collapse
You will get ota updates but it will not install it coz the cmw recovery, then you will need to update your rom that incloded the update via cmw recovery
Hmm ok
So you loose recovery too? I thought you would only loose root?
But arent the last two posts exact opposites? One says you would get ota and it would install but you would loose root and recovery and the other says you would get ota but cannot install it. Or am i missing some point here?
liorra3 said:
You will get ota updates but it will not install it coz the cmw recovery, then you will need to update your rom that incloded the update via cmw recovery
Click to expand...
Click to collapse
OTA updates install fine with CWM and have for some time. The only reason it would fail is if it is trying to patch recovery and does an assert.
TulpiX said:
Hmm ok
So you loose recovery too? I thought you would only loose root?
But arent the last two posts exact opposites? One says you would get ota and it would install but you would loose root and recovery and the other says you would get ota but cannot install it. Or am i missing some point here?
Click to expand...
Click to collapse
You will lose root on incremental updates only because it does a recursive chmod on /system - so it just changes the permissions on the su binary.
You will lose your custom recovery because it will restore /etc/install-recovery.sh which restores the stock recovery on boot.
not to smash your topic to bits but SINCE WHEN has an ota update been available before aosp code? Welcome to nexus device people running stock is for chumps you won't need ota updates because you will already be on a custom rom that has it
Sent from my Nexus S using XDA App
Goat_For_Sale said:
not to smash your topic to bits but SINCE WHEN has an ota update been available before aosp code?
Click to expand...
Click to collapse
The Froyo source did not push to AOSP until after the OTA to the Nexus One.
Slightly different but also held from AOSP until out on a device:
Eclair (2.1) was not in AOSP in a form that would build for a device until post Nexus One being available.
Gingerbread did not push to AOSP until after the Nexus S was available.
The other hold up is when new binaries are needed for the build. The early AOSP Gingerbread builds for the Nexus One were BUGGY.
The ICS builds for the Nexus S needed some "shady, leaked" binaries to get things up and running well (wifi, bluetooth, GPS, etc).
Typically the new binaries are not posted until it OTA's.
Goat_For_Sale said:
Welcome to nexus device people running stock is for chumps you won't need ota updates because you will already be on a custom from that has it
Click to expand...
Click to collapse
You can say this all you want - I've run stock rooted roms on both the Nexus One and the Nexus S without any issues. The Nexus S forums are filled with people with issues with spontaneous reboots, poor battery life, FC's and 95% of the time it tracks back to a custom kernel that has been "tweaked" or the ROM they are running.
If you are looking for the added features of some custom roms then go for it. But thus far pure AOSP builds have been anything but "for chumps" with the Nexus One and Nexus S.
krohnjw said:
If you are looking for the added features of some custom roms then go for it. But thus far pure AOSP builds have been anything but "for chumps" with the Nexus One and Nexus S.
Click to expand...
Click to collapse
I'm pretty sure but "custom roms" he also included builds made from AOSP. The point is that AOSP is often newer between bigger releases and the times an OTA build is newer you could always just flash that if you really want.
Ok thank you guys
I learnt much from this
So in fact if i go cwm and root my best option is to forget ota and go custom rom. Even if its a stock + root custom rom.
Sent from my A500 using Tapatalk
TulpiX said:
Hello
Since this will be my first nexus device , I have some questions regarding rooting and recoveries and what they affect on nexus devices specifically this nexus.
What affects the ability to receive official google updates?
If you are rooted do you always loose root if a new update comes? Does root affect the ability to receive updates?
If you have a custom recovery is it possible to receive official updates from google?
Thanks
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
You can't receive OTA when your device is rooted. Why? Every OTA checks system consistence. If some different files or the same files with different checksums will be detected, OTA will be canceled.
Hello,
I'm one of those lucky guys who got the 2.55 build number.
Wandered around the forum for some time, seeking for a way to root my phone, but don't want to risk before being 99% sure that this may work.
As I understood, Bin4ry's method won't work with my phone, which results in need of unlocking the bootloader.
I checked its status and it shows that its Unlockable = Yes.
Now, let's say I unlock the bootloader, what should I do next? Flash a prerooted ROM?
All I could've found on forums was "UNLOCK YOUR BOOTLOADER" and "BIN4RY'S METHOD" stuff. Maybe because people were posting about this 2.55 thing alot. Maybe not.
All I need is a n00b friendly tutorial.
Btw, I'm on 4.0.4 ICS, which is pretty obvious.
Thank you, in advance.
Sent from my LT26i using xda app-developers app
Unlock your bootloader and just flash an auto rooting kernel.
But if you're unlocking the bootloader you may as well flash a Jellybean rom anyway
Sent from my Jellybean Xperia S
Hi, I hope the OP doesn't mind, but I'm kinda in the same situation and I need some help from you guys, because I am currently a Samsung owner (please don't throw rocks ) and I don't really know much about flashing ROM's on Sony.
So... I have with me my brother-in-law's Xperia S with 6.1.A.0.453 (ICS 4.0.4), never been tampered with, just bought, updated to ICS and rooted with Bin4ry's method.
All great, but I was hoping to flash 6.1.A.2.55, because I heard it is the latest.
But now the hard part comes, the phone has Locked Bootloader and I can't unlock it because "Service info > Configuration > Rooting Status > Bootloader unlock allowed" says NO.
That being said, if I flash the .55, how do I root it?
I updated and rooted an Xperia U a while back, using a method of changing the kernels, something like this:
Flashing the ROM I want (the one that can't be rooted)
Flashing an older kernel from a stock Rom witch was rootable
Root it
Flash the kernel of the last ROM, and root remains.
Do you guys thing that this method will work on Xperia S?
Flashing .55
Flashing an old kernel (from 6.1.A.2.45 or other that can be rooted)
Root it
Flashing the kernel of .55 again, and hoping that the Root remains.
Also, where could I find those kernels?
Ben36 said:
Unlock your bootloader and just flash an auto rooting kernel.
But if you're unlocking the bootloader you may as well flash a Jellybean rom anyway
Sent from my Jellybean Xperia S
Click to expand...
Click to collapse
bro
please tell me how to root xperia s 6.1.A.2.55, I already unlock the boot loader , but i dont know how to root. so i relock again. Please tell me how to root and can you send the ftf file for jelly bean rom. And i want to know what is kernel . i cant find it.
Ok, here's the thing.
I'm about to get a S4 mini, and I have a doubt, how can I root, bootloader unlocking and flash CyanogenMod 10.2.
I know how to flash by command with adb but, I no have an idea how to root.
I know the basics, I already got a Xperia Sola and I have done all that things, so, what should I do?
Thank you very much!
Sent from my Xperia Sola using xda premium
You can use the information taken from this thread:
http://forum.xda-developers.com/showthread.php?t=2364980
OK. Got it, it's easy.
But I need to unlock the bootloader to flash cyanogen, how I can do that?
Sent from my Xperia Sola using xda premium
manudo said:
OK. Got it, it's easy.
But I need to unlock the bootloader to flash cyanogen, how I can do that?
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Hello Manudo,
Why should you be willing to unlock the bootloader?
There is no need for that on a Samsung phone if you want to root your phone and flash custom roms.
Simply follow the instructions in the OP of the abovementioned thread.
After that you have root and CWM and you can flash whatever custom rom you want if that is suitable for the S4 I9195.
Please be aware of the firmware you have.
With XXUBMJ7 or XXUAMJ7 (both released a few days ago) and later your phone has the so called Knox flag/counter and after rooting, flashing custom rom or flash back an older firmware you will loose your warranty and ain't able (at this moment) to use your phone in an easy way.
Success.
hansare said:
Hello Manudo,
Why should you be willing to unlock the bootloader?
There is no need for that on a Samsung phone if you want to root your phone and flash custom roms.
Simply follow the instructions in the OP of the abovementioned thread.
After that you have root and CWM and you can flash whatever custom rom you want if that is suitable for the S4 I9195.
Please be aware of the firmware you have.
With XXUBMJ7 or XXUAMJ7 (both released a few days ago) and later your phone has the so called Knox flag/counter and after rooting, flashing custom rom or flash back an older firmware you will loose your warranty and ain't able (at this moment) to use your phone in an easy way.
Success.
Click to expand...
Click to collapse
Um, sorry. It's just that in Xperia, the phone I already got, it's needed to unlock the bootloader when it comes to flash custom roms. Didn't know that in Samsung doesn't matter, nice!
XXUBMJ7 and XXUAMJ7, what are these things? Firmware versions? And knox, what is that?
Should use Google more often, haha.
Thanks, dude!
My Z1 compact is running and i am trying to unlock the bootloader. I have entered *#*#7378423#*# which says i cant unlock the bootloader.
Is there any other method to unlock the bootloader?
Anyone know if its possible?
The reason I want to do this is to install custom Roms.
Instead of unlocking, I believe its possible to root using root and then install dual recovery.
Is this possible and will it let me install custom Roms?
Your device seems to be branded by your carrier and there is no workaround.
Sent from my D5503 using xda premium
325i. said:
The reason I want to do this is to install custom Roms.
Instead of unlocking, I believe its possible to root using root and then install dual recovery.
Is this possible and will it let me install custom Roms?
Click to expand...
Click to collapse
Yes, but only stock based. CM based roms require a different kernel which can only be flashed with an unlocked bootloader. So your choices are quite limited. The good news: Sonys roms are pretty good. The only question is how long their support will last in the future.
Sorry mate, but with a Bootloader unlocked allowed status set to :NO you cannot install any custom ROMs. You may however still root the phone if getting rid of bloatware or installing apps that require root is what you are after
Klucznik1 said:
Sorry mate, but with a Bootloader unlocked allowed status set to :NO you cannot install any custom ROMs. You may however still root the phone if getting rid of bloatware or installing apps that require root is what you are after
Click to expand...
Click to collapse
Not completely accurate, he can still install cooked roms based on stock, as long as they do not modify boot partition as he can only run stock kernels.
Iam requesting for developers can someone please keep provide on root for lgh815 for locked boot loader on 6.0 instead digging for unofficial boot loader unlock,that will be thankful.
i dream ,i hope so much too...
i have already asked what happen if we flash a zip MM rooted firmware (or imperium) with Chainfire's flashfire ....when we have a rooted Lollipop firmware and an eventual factory-reset with physical buttons...
but never have had answers ...
Loulou-13 said:
i dream ,i hope so much too...
i have already asked what happen if we flash a zip MM rooted firmware (or imperium) with Chainfire's flashfire ....when we have a rooted Lollipop firmware and an eventual factory-reset with physical buttons...
but never have had answers ...
Click to expand...
Click to collapse
Its not possible because on the rooted rom, the kernel its modified and when a locked bootloader phone tries to load it on boot...it will fail...
But i believe , in time, someone are going to find a hack/exploit to achieve root on locked phones
I already tried that it leads to bootloop...
i knew about this kernel problem....
but the main question is : why flashfire seem incapable to flash a "full" firmware (kernel included) like lgup/bridge/ota.... ?
And Chainfire have anounced that his flashfire is "the future" for to flash roms and firmwares ...
@xoxey it's nice to have tried
there are options that you have missed ? eventualy...
Root on 6.0 without unlocking bootloader is literally impossible because in Marshmallow Google changed their policy and now to root it you have to have modified boot.img flashed onto your device, original boot image will not allow you to have a root access or use custom recovery. It would be easy to just grab a boot.img of random kernel like SimpleGX or Imperium and flash it via fastboot, but there is a problem - bootloader basically loads your boot and if it locked it will load it only if the boot is signed, unmodified, although it leads to a bootloop. Only way to do this is to unlock it officially, and then, if you don't want to downgrade to 5.1, grab a boot.img of a kernel, flash it via fastboot (because stock boot will not allow you to flash recovery due to causes I have mentioned above), flash the recovery via fastboot, then to void bugs flash the full kernel (any of them, can be different than the one you used before, it just has to be full package) and then simply flash SuperSU v2.67. There is no different possible way to root it on 6.0.
Have you guys tried this guy's method to get temp root using kingroot? http://forum.xda-developers.com/showthread.php?t=3314927
fates13 said:
Have you guys tried this guy's method to get temp root using kingroot? http://forum.xda-developers.com/showthread.php?t=3314927
Click to expand...
Click to collapse
Guys u can try it,i will bet it doesn't work too&waste of time.
Loulou-13 said:
i knew about this kernel problem....
but the main question is : why flashfire seem incapable to flash a "full" firmware (kernel included) like lgup/bridge/ota.... ?
And Chainfire have anounced that his flashfire is "the future" for to flash roms and firmwares ...
@xoxey it's nice to have tried
there are options that you have missed ? eventualy...
Click to expand...
Click to collapse
Yh i tierd all possible ways to root my lg g4 on 6.0..i dont care of bootloops becoz i know how to fix them??