Related
My phone tells me there is a software update. I accept, it goes through the whole process but then says unable to update. I assume its due to me being rooted via gingerbreak?
Is there a way to update?
Is there a way to un-root my phone?
Thanks in advance.
Flipfoot said:
My phone tells me there is a software update. I accept, it goes through the whole process but then says unable to update. I assume its due to me being rooted via gingerbreak?
Is there a way to update?
Is there a way to un-root my phone?
Thanks in advance.
Click to expand...
Click to collapse
Are you try to update via ota? Are you already on 2.3.3? Have you uninstalled any of the preinstalled apps?
If you are on 2.3.3 already there is no new update out for the phone. If you are still on 2.3.2 and are trying update via ota you will need all the preinstalled apps still on the phone, if you have uninstalled anything you will either need to reinstall the apks from here or redo the process of flashing 2.3.2 (to regain the uninstalled apps) then rooting and then doing the ota to update to 2.3.3.
Rooting will not stop you from getting an ota update as long as the bloat is still present. So it would be better to freeze the apps instead of uninstalling (if you plan to do the ota update in october to 2.3.4). If you want to un-root your phone you can reinstall gingerbreak and when you open gingerbreak click unroot, but it is not required to unroot to update.
Thankyou! I cant remember what bloat I deleted, how do I flash 2.2.3? Im a complete noob at all this, but im trying to learn.
Read these threads for how to:
Flashing with flashtool:
http://forum.xda-developers.com/showthread.php?t=1048422
Updating and keeping root on 2.3.3:
http://forum.xda-developers.com/showthread.php?t=1119074
Regards Dousan...
If you dont want to keep root and you have a locked bootloader you can just use SEUS (google it) and it will install 2.3.3 on your phone even if you have uninstalled something. But as said you will loose root.
Or follow the links in Dousan's post to update while keeping root. Just flash the uk 2.3.2, then root, then do the ota update without removing anything and you will be on 2.3.3 with root. There is another guide here diff poster but the same guide really. http://forum.xda-developers.com/showthread.php?t=1116090
I am looking into rooting my Nexus S so I can install an ICS ROM. This is my first time rooting so got a question.
How will OTA updates work for me? Will the ICS update just work or will I have to in root to get the official OTA update?
Sry if this has been asked before couldn't find a clear answer.
Sent from my Nexus S using XDA App
Don't do OTAs. Any update released by Google or your manufacturer will be released here, rooted, within hours.
If you take an OTA you will lose root and could even find your phone locked again (as unlikely as that is with the NS, better safe than sorry. Ask the EVO users who took the GB OTA )
Sent from my Nexus S 4G using Tapatalk
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Alright, thanks alot for the quick responses guys.
Sent from my Nexus S using XDA App
Once the ota is downloaded.....
* Put the zip on sdcard
* Reboot into custom recovery
* Manually flash it
* Directly after that, in the same recovery session, flash latest superuser zip
* Wipe cache
* Reboot
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
OTA's will work with CWM installed (The OTA will however remove CWM and needs to be manually applied)
OTA's will remove root access (the permissions on the binary get changed)
I have never seen an OTA on XDA that was pre-rooted. i have seen ROM packages that incorporate the OTA that are pre-rooted (installing these usually means a wipe of the device is needed)
if you replace the ROM on the phone, you will not get OTA updated. you must remain mostly stock to obtain them.
Custom kernels or custom google apps on stock roms will cause the OTA update to fail, however you will notified that the update is available.
I hope this answers your questions.
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
snandlal said:
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
Click to expand...
Click to collapse
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Matridom said:
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
I hope this answers your questions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
onthecouchagain said:
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Click to expand...
Click to collapse
OK, let's clear a few things up here.
CWM or ClockWorkMod is a custom recover that can be installed on the phones. This step is needed because the default recovery on the nexus does not allow for updates to be installed that are unsigned. CWM does, so it's a necessary step to installing the SU binary (aka root your phone) or installing custom ROMs
The bootloader is the basic system on your phone that reacts to the power on and hands over operations to Android. The equivalent in the PC world would be a BIOS.
fastboot is a utility that is provided by google that allows you to send commands to the bootloader and direct it's operations. It's needed to unlock the bootloader (so you can replace parts of it.. like recovery with CWM)
Interestingly enough, you can boot your phone to a custom recovery WITHOUT replacing your existing stock recovery by using fastboot.
Rooting your phone is simply installing and providing the proper rights to the SU binary to allow you to have full administrative rights to the phone, the superuser application is almost always bundled with it as it allows for a form of control as to what applications can use root access. Rooting your phone allows you to install some very interesting application, most popular are titanium backup (let's you back up app data and restore them after a reset) and removing advertising (adfree/adaway or it's like) Root can also be used by some applications that allow you to "cheat" at games.
rooting your phone is reversable, though not always the easiest to do. With the stock ROMS, it's fairly easy, you just re-apply the latest OTA and it will kill Root access on your device.
When it comes to custom ROMs the vast majority come pre-rooted to save you the hassel of doing it yourself.
On other phones where the bootloader remains locked, you have to use an exploit to gain root access, this then allows you to modify the OS and install custom roms and CWM while keeping the bootloader locked. Since the Nexus line can be unlocked, it's not needed.
Please note, root access is NOT required to install a custom ROM.
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
MaxCarnage said:
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
Click to expand...
Click to collapse
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Matridom said:
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Click to expand...
Click to collapse
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The key here is that SPRINT released an OTA for a SPRINT branded device. This has zero relevance to updates provided by Google for Nexus devices.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The issue at heart here is that fact that the OTA for the nexus line of phones comes straight from google and are not "tweaked" in any way by the carriers. (exception nexus 4g has additional applications required for CDMA support)
One of the selling features of the nexus phones is the fact that unlocking the bootloader is officially supported.
In regards to other phones getting their bootloader locked, I've experienced first hand the pains of that, having a galaxy S and the 2.3 installing a new bootloader and really screwing things up for me. In those cases, i agree with you whole heartily and to wait for pre-cracked roms that can be installed.
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
onthecouchagain said:
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Click to expand...
Click to collapse
All you would need to do is to unlock the bootloader, install CWM, then apply the .zip associated with the ROM you wish to install. I would however carefully read the installation instructions for the rom as in some cases, it might be a multi-step process (such as going from a 2.2 rom to a 2.3).
Many ROMS also do not come with the google apps and secondary zip file needs to be applied to get those running (cyanogenMod does this)
I wanted to add, that the process of unlocking your bootloader will erase EVERYTHING on the phone, including the SDcard partition. So make sure you back up anything of importance.
Matridom said:
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
Click to expand...
Click to collapse
I can't provide an example because, as I have already stated, this was a precautionary suggestion only.
I'm not going to get into a debate with you over this; I've made my point and you've made yours. Thanks.
Matridom said:
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
Click to expand...
Click to collapse
Good point again but the trick is to put your apps in /system/framework
Along with framework-res.apk.
This will add a dex file to /data/dalvik-cache, which is needed for saving upon reboot
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
suksit said:
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Click to expand...
Click to collapse
Rooting doesn't require flashing custom recovery.
iboj007 said:
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
Click to expand...
Click to collapse
No. It doesnt
Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?
Since you have flashed a custom recovery, you'll have to flash back the original recovery in order to do a ota.
It doesn't matter if your rooted or if you have a unlocked boot loader.
BTW, You will loose root if you don't use ota keeper from the market.
Sent from my Xperia Arc
mazlano27 said:
Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?
Click to expand...
Click to collapse
First question is why would you care? Its not like there are OTA's happening all the time. there has been basically one OTA since the device first came out and most people got it as soon as they started to use their device.
Second, if you have a custom recovery, that will stop it from working.
IF you put the recovery back, the question of if you will lose Root or not really depends on the OTA type. Most OTA's are incremental, meaning they only contain the changes of the system, not the whole system. If it is an incremental, unless there is something in the OTA that seeks out and removes root, it most likely will not affect it. However, if you have made any real changes to the system (removed system programs) the OTA may fail to run as it assumes everything in a normal system is there.
IF the OTA is a full system update like what the Kindle Fire was doing for a long time, it will flush the complete system area and load a new one, that effectively removes root since when it is done, it is no longer physically there. OTA Root keeper won't help you in those cases since the entire system area get wiped. Getting root back is trivial though as hard as it was originally.
I'd tend to think that the OTA's will be incremental... and I see little need or desire by Google to be hunting down root since it is a Nexus device and it is designed to allow for that. Its not like it is a phone like device where the Wireless operator is having a cow as to whether or not you gained access... its supposed to have that kind of access.
However, it really doesn't matter. When the next OTA comes out, there will be a number of devs which will take it apart and release an update you can use with the recovery you currently have and root and will keep root just fine. these typically get released within hours that someone notices a new OTA in the wild and sometimes you can get it before you actually even have a chance to get the real OTA over the wire.
So not a real big deal. I'd just stay where you are and when one comes out watch to see what gets released to mimic it.
Note changing the state of the bootloader will wipe your device. Unlocking will wipe it and locking it will wipe it. You are best off, unlocking it and just leaving it that way.
Hi all,
I am kinda new here and would like to put a question, hoping it's not a repetition (I have been browsing though this forum thoroughly, but apparently couldn't find a proper answer). This is the situation:
- bought a used Z2
- Z2 was from UK O2 operator and it had operator lock and unlockable bootloader
- network operator lock has been cleared with unlock code
- O2 customized firmware has been wiped away by flashing a recent 5.0.2 stock lollipop
- unlockable bootloader still exists so cannot upload any customized/rooted .zip system
Clearly, the only thing I can do to modify this phone is to upload .FTF firmares to it, due to unlockable bootloader. Right now, I see available online only unmodified stock .FTF firmwares.
THE QUESTION: is there ANY way to create a pre-rooted .FTF file (modding not strictly necessay but rooting essential) so that I can upload it to the phone?
Thanks for all your precious advice!!!
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
ptmaniac said:
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
Click to expand...
Click to collapse
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
derjaeger said:
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
Click to expand...
Click to collapse
Kingroot works fine on 5.0.2 but by itself will not disable sony RIC and you won't get a writable system. Nut's dual recovery will disable RIC on boot, just install it after rooting and you should be good to go.
I suggested flashing a preroot zip just because i don't like kingroot app to manage root permissions and it's hard to replace it with supersu. flash a preroot zip and you'll end with a clean stock rom+supersu+nut's dual recovery and fully writable system
Thanks a lot buddy!
I will try kingroot+nut recovery and see how I find myself.
I will always be one step away from uploading a custom .zip in case I need supersu.
You really made my day!!! )))
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Thanks for your answer!
But isn't this procedure including downgrade somewhat longer than the previous suggested one?
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
ptmaniac said:
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Click to expand...
Click to collapse
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
derjaeger said:
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
Click to expand...
Click to collapse
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
gazza35 said:
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
Click to expand...
Click to collapse
Sure, i also don't like kingroot. Like i said before it does root fine but doesn't disable ric, flashing nut's recovery after solves this.
And if you flash a preroot zip after there will be no traces of kingroot on the phone. Downgrade to kk and flashtool is still not necessary...
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
ptmaniac said:
derjaeger said:
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
It's all part of the experience of learning what's best, I always only use dual recovery because windows can install it directly and root at same time, there used to be plenty of rooting apps like kingroot but you don't see so many anymore, but I'm glad you're sorted, when ya get 5.1.1 just use prfcreater to make it into flashable zip then you don't lose root and have to go through the process all over again.
All the best
---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
Thanks a lot!
Yes, it really goes this way, now waiting for an unbranded fw, as this night the first branded ones have started to roll out...
I am really happy: for a couple of months I thought I was buried behind that nasty unlockable bootloader, and now i discovered it's even better, as rooting it without touching bootloader allows the software to work at 100% of it specs
Coming from Samsung to Sony is kinda rough at first for nibbling but when the right instruments are present and clear it's worth dealing with superior hardware.
Also, must say that Sony is lately improving its behaviour, after so many years of mafia attitudes towards buyers
Inviato dal mio X500U utilizzando Tapatalk
I've had Samsung, HTC, Apple, blackberry and finally stuck with Sony, I guess they all have pros and cons, Samsung phones are the easiest to mod and flash, Sony is quite daunting for newcomers very much like HTC. Can be tricky to learn.
Horses for courses and all that, I much prefer a rooted phone with locked boot, no particular reason except the drm keys etc, I do think camera is better on lb, than the quality on ul, although there is a drm restore mod on cross Dev, for ul, it does make xreality work, but it doesn't remove the missing key error in security tests.
I read on a page that once drm keys are gone, Sony won't honour the warranty, very much like Samsung and the knox counter, I'm not sure tho, but I do know I'll always remain Lb and stock based rom.
Only problem I have is getting wifi tethering working properly, it's doing my head in, 4 weeks of decompiling and editing and still can't get my phone to broadcast on any other channel except 1.
GGGRRRRRR @ SONY.
#whattheheckhaveyoudonesony
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
derjaeger said:
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
Click to expand...
Click to collapse
Looks like a cheap option of unb
randed HTC, but no, I don't think a HTC section would help.
I think it's an Italian release, dual simply phone, simply Google pointed to an Italian forum androidiani androidiani, run the link through a webpage translator and you may be in luck for root and rom, I think towelroot may root it.
Actually framaroot already offered rooting at the price of a horrible hack (3-4 reboots before device is ready when turning on or rebooting, plus device instability on heavy loads), never tried towelroot on it.
But problem is not about rooting rather than getting rid of horrible stock firmware. The latest fw edition by Mediacom was a total disaster (forums cry loud) and I thought it would be great to try to put some mod on the phones: this is why I had in mind to ask you if there is a general toolkit for HTC phones (like flashtool for Sony) which I could use to try to take care of it and experiment....
Inviato dal mio X500U utilizzando Tapatalk
I wanted to share two things with you guys here in Tablet z forum:
1- First of all, @zxz0O0 has developed a code based on the CVE-2015-1805 vulnerability that gives temporary root access to a select range of devices (including Tablet Z4). Let me try to explain in my words what that means. A full blown root gives permanent read/write access to /system and /data partitions. On an unrooted Tablet Z4 you only have read access to /system and no access to /data. With this root, you will be able to have a temporary terminal or adb session that gives you read access to /system and read/write access to /data. Why not write access to /system? Because Sony runs a service called RIC on Xperia devices that makes it impossible to mount /system as writable. In the past this would be patched by modifying the system partition. But in the recent Kernels sony has implemented a mechanism (dm-verity) which checks /system and if it is modified the device does not boot. So even if this (or any other) root method gave you the ability to write in /system you could not use it because your device would not restart the next time you turn it off. The solution would be to patch the kernel which requires an unlocked bootloader. IF you unlock your bootloader you lose your TA partition permanently which includes some of the Xperia features and licenses that have to do with image processing and some DRM. So a lot of us do not want to unlock the bootloader.
Then what good is this new root method? Since it gives you read access to the system partitions you can use this method to back up your TA partition. The idea is that if you ever unlock your bootloader you may be able to use this TA back up to return the system to its original state if you ever decide to relock it. Another benefit is that tools like Titanium back up which require access to the /data partition can now function (in a limited sense) although someone has to work out the details of that.
To download the pack that allows backup and restore of the TA partition go to http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
After you create the backup, you can unlock the bootloader, and use your TA backup and the procedure outlined here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 to create a csutom kernel that uses all the good stuff in the TA backup and emulates an environment where your tablet behaves like one with an unlocked bootloader. The camera denoising algorithm and all other Sony proprietary software which would be disabled after unlocking the bootloader should work.
If you want to return the tablet to its unlocked condition you will need this TA backup. Some explanation about retrieving the TA partition from this backup, if you unlock the bootloader and decide to relock it, is given here http://forum.xda-developers.com/showpost.php?p=66142823&postcount=16 and methods to do so are outlined at: http://forum.xda-developers.com/showpost.php?p=66158970&postcount=68
Note that to use this root you need to downgrade to lollipop (preferably version 28.0.A.8.260)
I have explained procedures to use the above tools here http://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 at length.
2- Now, here is the use I have found for this temporary root: I was always bothered by the fact that not only I could not (easily) get the 17 hour advertised on-screen use out of my tablet, the standby power consumption was always too much. Whereas I could optimize my other (rooted) devices to only drain 1-2% a day in standby, tablet Z4 seems to settle for nothing less that 5-10% a day in standby. This is what you can do to get excellent standby power from your tablet:
A) Say goodbye to your google apps (with the exception of Chrome and Maps) and other marginally advantageous apps. They wake your device up all the time when it is supposed be sleeping and endlessly chat with google servers even if you turn all the communications off in the google settings. So disable all of the apps listed in the attached pictures , plus lifelog,via settings. Don't complain about not being able to use the gmail or youtube apps. Other great replacements exist. Leave "Google App" active if you use the voice search or voice typing feature. Also uninstall the pre-loaded apps that you aren't using like facebook (which is cancer for any phone), Lifelog, Privilege, spotify, etc.
B) In settings under wifi open the advance menu turn off both "network notification" and "scanning always available", and change "keep wifi on" to "only when plugged in"
C) Under "power management" in settings, activate stamina mode and extended standby (no need to activate extended usage).
D) Finally (and here is where the temp root becomes useful) extract the file "iovyroot" from the file in the above link and put it in your adb directory. Open a command terminal and type:
Code:
adb push root\iovyroot /data/local/tmp/iovyroot
adb shell chmod 777 /data/local/tmp/iovyroot
adb shell
This gives you an android terminal shell. Continue with the following:
Code:
/data/local/tmp/iovyroot
pm disable com.sonyericsson.idd.agent
pm disable com.sonymobile.entrance
pm disable com.sonyericsson.updatecenter
pm disable com.sonymobile.anondata
pm disable com.dsi.ant.server
pm disable com.sonymobile.gmailreaderservice
pm disable com.sonymobile.googleanalyticsproxy
pm disable com.sonymobile.mx.android
pm disable com.sonymobile.enterprise.service
pm disable com.sonymobile.synchub
pm disable com.sonymobile.phoneusage
That is it. You just disabled the update service and a bunch of other things and extended your standby battery life. These settings will survive a reboot.
Let me know how it works out for you. If you find other creative uses for this temp root share here.
This is the BEST and probably the most right to the real point post ive ever readed in this particular forum since I joined....
Forgive me if I say I have had lost the faith on sony's z4t development here... It's a real pleasure to know there's still ppl working on what I think should be the right development direction on gettin' control of our loved devices, instead of breaking them and throw a lot of expensive features to the flush.
Thanks again mate to share it.
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Stevethegreat said:
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Click to expand...
Click to collapse
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Hmm, but if you can also temp root then you can backup everything using TitaniumBackup anyway before unlocking.
So if I understand this right, if you can back up TA we can infact unlock the bootloader now with no loss of DRM ?
So can now actually get full root based on that ?
najoor said:
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Click to expand...
Click to collapse
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Stevethegreat said:
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Click to expand...
Click to collapse
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
najoor said:
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
Click to expand...
Click to collapse
Mostly to save time as I have too much data. I though to do it like this
Downgrade to Lollipop -> Use the Exploit -> TA Backup -> Upgrade back to Marshmallow.
In principle everything should have had worked as by the end of it I would be back to Marshmallow (I would not linger into Lollipop). But now that you're telling me that lollipop may corrupt my data permanently I have second thoughts.
I thought, that my data would not work well on Lollipop, but that wouldn't matter to me; but now you're telling me that they won't work when I'll back in Marshmallow too, which is a totally different beast. Am I understanding you correctly?
Does everyone need to downgrade tho?
Once we have the TA partition available to restore, once its made available online surely everyone else can just restore the same one?
Or is the key unique?
Kinda assuming here that all the stuff that needs the TA partition will work with an unlocked bootloader, or does it have to be locked to be usable again?
Edit: Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader.
Bugger
Ultimately never rooted my device for fear of losing something (that I will never use anyway!)
DRM Keys are unique, in fact that's the whole point of TA backups.
Also there's a talk (on the other thread) of a tool that would merge your particular keys with a particular custom kernel.
That way you'd keep all Sony Exclusive features, but also be able to make use of root apps. It would be great if such a tool becomes usable with AndroPlus Kernel...
Nice, had all but given up hope of being able to unlock my Z4 so that sounds promising!
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
D0MINO said:
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
Click to expand...
Click to collapse
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
I unlocked the bootloader and rooted the device SGP771.
Bevor that, i backed up the TA.
Then i flashed the androplus kernel.
Everything works great.
But you cannot modify androplus kernel with that tool. That means DRM restore is only possible on stock rom.
When you restore TA to stock rom, your bootloader will be in a lockes status again and there is no more root. Too bad
odicamillo said:
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
Click to expand...
Click to collapse
Can ta be restored on any fw like marshmallow or can it only be restored on the fw that you backed it up from?
This looks very promising, thanks OP.
Has anyone else managed to get it to work as described?
Thanks in advance
najoor said:
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Click to expand...
Click to collapse
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
retikulatus said:
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
Click to expand...
Click to collapse
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
najoor said:
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
Click to expand...
Click to collapse
Thanks for the fast reply even if you ruined my hopes
no, i don't think i have myXperia , i checked on my apps and find nothing.
Since i had display issues with my tab s (sm-t800), i tried the z4 tablet for its LCD screen instead of the super amoled of samsung...
My bootloader was already locked when i purchased it, i updated it thinking it will change that but unfortunatly that did nothing.
It wasn't a new one though, perhaps the previews owner messed up with it and got its bootloader locked :/
Because it is some kind of lotery to have a bootloader unlockable with sony, i will wait patiently until samsumg release its 16:9/10 tab s4: imho, the tab s3 actual 4:3 format is a nonsense....
Thank you again
Kind regards from France