Related
Warning: crawrj mentioned this wouldn't flash in TWRP. I use CWM, so not sure whether it's compatible with TWRP (or any other recoveries) at the moment. So, if you're not using CWM... I would suggest waiting a bit.
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: http://d-h.st/Dkl
RogueSly said:
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: d-h.st/Dkl
Click to expand...
Click to collapse
Nice find
travisw0204 said:
Nice find
Click to expand...
Click to collapse
Thanks. It took a bit to find, but I couldn't live without root. My battery is GAWD with the CPU limited. :3
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
crawrj said:
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
Click to expand...
Click to collapse
Weird. Flashed for me on CWM when I used it.
RogueSly said:
Weird. Flashed for me on CWM when I used it.
Click to expand...
Click to collapse
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
crawrj said:
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
Click to expand...
Click to collapse
I've been using http://forum.xda-developers.com/showthread.php?t=2254323. I tend to stay away from touch recoveries when there are 4 dogs in the house.
Lol, too little too late for me. :facepalm:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Awesome! Glad to hear it's fixed. Not sure why the modem didn't install. I didn't get any errors on my device after taking out the patches for My Files and KNOXAgent, as both were missing on my system. I'll try restoring back to MDC and updating to SuperSU 1.3 to test it.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
I was going to ask an annoying question.... but decided it was annoying and did a search. here is what I found in the difference between SuperUser and SuperSU and SuperSU Pro ($2.49). Reference: http://android.stackexchange.com/qu...ruser-from-chainsdd-and-superuser-from-clockw
SuperSU improves everything about Superuser and adds more options. The free version offers faster notifications, there is possibility of disabling them for each app and a new interface, attractive and easy to handle. In addition, according to developer claims by using SuperSU you’ll enjoy higher speed from the apps that require root rights, especially on Android 4.0+. The paid version called SuperSU Pro provides the opportunity to keep root rights after a system update, which usually cancels these rights. Although the method is not guaranteed the option is very useful. We have password protection and advanced log configuration settings for each application.
You might also want to read SuperSU Brings Better SuperUser Root Permission Management to Android. Quoting from that article:
SuperSU is basically SuperUser on steroids. According to the developer, it “allows for advanced management of Superuser access rights for all the apps on your device that need root.”.
Edit: ::FacePalm:: What ever you do. Do not uninstall SuperUser after you install SuperSU. You will loose Root. LOL (Hey at least I can laugh at myself.) I am not worried about it yet... I know I will get it back eventually.
Edit 2: After reading the OP, all you have to do if you have TWRP Recovery installed is do the OTA, your update will install and you will automatically reboot into TWRP.
Go to Mount first and mount System.
Go to back to home and select Advanced.
Go to File Manager. NOTE: This can be very frustrating! Use BACK and Sort Options to reset Sorting if it keeps doing things you don't want it to do. Also (Up A Level) is handy. If you are on "/" directory, touch Sort Descending: Name and you will see System. Select Sysytem.
Now Sort Ascending you will see App. Select App.
Gentally and slowly Swipe down in the middle to reach Knox. I found 2 files. Select one at a time and delete them.
Reboot
Then rerun Motochopper Root method.
I am on Stock MDC still. So if you are on MDL I am not sure if this would work. Now follow the directions that I failed to see when you install SuperSU.
Install SuperSU. Open SuperSU and make sure SU binary is switched from SuperUser to SuperSU. Once you do that you can remove SuperUser.
Edit 3: Once you check to make sure SuperSU has Binary after a reboot... SuperSU will remove SuperUser for you. No need to do anything.
After all said and done... I am thinking that the TWRP stopped the OTA from installing. I have been extremely busy with work, so no time to read XDA lately has been stopping me from keeping up to date. I just need more time in the day.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
RogueSly said:
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
Click to expand...
Click to collapse
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
crawrj said:
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Well, that sucks. I guess I will give up trying to flash it for now. Already removed KNOXAgent again and dropped faux's kernel on here. It's showing my build as MDL, so at least I don't get pestered by the update message.
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
tones160 said:
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
Click to expand...
Click to collapse
I think there are a few posts in the development sections that will help out with getting root on MDL. If it were me, I would just pull the SuperSU apk and unzip it. Grab the su binary out of there, push it to /system/xbin/, and then install SuperSU on the phone once it restarted. Now, I can't confirm that works... because I haven't had to get that dirty with rooting my phone. Motochopper worked perfectly fine when KNOXAgent was removed, so it should work if you have KNOXAgent frozen too.
Cf autoroot
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
gershee said:
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
Click to expand...
Click to collapse
That's apparently right, for now. I'm working on figuring out why the MDM partition won't flash. I tried to patch the files manually, as mentioned previously and here, but it seems that it didn't flash as the baseband didn't change?
Hopefully figure it out soon.
Getting E:Error in /external_sd/OTA 5-13-2013 (No Knox Agent), Status 7. Any advice?
This isn't an issue, but I thought it was odd and I'm wondering if anyone else has seen this?
I got the OTA to upgrade my 6602 to .244 firmware (only 45.1 MB) so I bit the bullet and upgraded after reading DooMLoRD's method of rooting .244. I started Flashtool and plugged in my phone to start the whole process, only to see my phone screen show the SU message asking if I wanted to grant access. I'm looking under About phone and it says "Your device already has the latest available system updates" and the Build number is 10.3.1.A.0.244. Titanium works and SU says I have several apps that have SU access.
I'm certainly not complaining, but I thought the .244 upgrade broke root? Or am I completely missing something here?
when upgrading by OTA, keeping root is normal. you loose the root when upgrading with PC comp for example.
sensei_sai said:
when upgrading by OTA, keeping root is normal. you loose the root when upgrading with PC comp for example.
Click to expand...
Click to collapse
Ahh, OK, thanks!
As you know there are not many kernel options for ZR as in Z you have to unlock bootloader to root the phone to flash it with CWM or any other recovery.
So this is detailed Guide to root Xperia ZR & having Locked Bootloader
1) Don't upgrade your phone to 4.2.2_10.3.1.A.2.67 Firmware & If you already updated it to Downgrade it to 4.1.2_10.1.1.a.1.310 Firmware In Flash mode Using Flashtool 9.13 (Download Flashtool 9.11 install it After upgrade it with 9.12 & 9.13) don't unlock bootloader.
2)Now Root it Using DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit. to root just click runme.bat. Your phone will get root access & you will get Superuser app
3)Then use Backup-TA-9.8 to backup your TA.img & save it at any Safe location for further Use ( It Content DRM Data & must be saved throughout lifespan of your phone).
4)Now upgrade your phone to 10.3.1.A.2.67 either by OTA or Using Sony PC companion & if you are unable to get upgrade don't panic just use flashtool & flash the 4.1.2_10.1.1.a.1.310 again & try the OTA upgrade. (As i do have both for Indian region but attachments will be too big to Attach here).
5)Now install Vroot on your PC & root your phone with it. Now you can see that your bootloader got unlocked but don't panic install SuperSu from Playstore update binary for it reboot your phone. now freeze Superuser from Vroot using titanium backup then update binary for SuperSu. Now convert Superuser from Vroot into user app using Titanium Backup. Reboot Your phone update binary for SuperSu & uninstall superuser from Vroot.
6)Now Use BLU button From Flashtool. on pressing BLU button Flashtool it will prompt to start phone in flash mode to unlock bootloader just do as prompted but dont disconnect the phone after boot loader just hit the BLU button to re-lock bootloader. Reboot your phone.
7)Now just flash Back-up your TA Using Backup-TA-9.8.
8)Congratulation now you have rooted phone with locked bootloader with full functionality.
I wrote this because i just lost DRM data things cant be undone.
SO for all Niewbies this is guide to ROOT ZR with Locked BootLoader.
sasaengineeringworks said:
As you know there are not many kernel options for ZR as in Z you have to unlock bootloader to root the phone to flash it with CWM or any other recovery.
So this is detailed Guide to root Xperia ZR & having Locked Bootloader
1) Don't upgrade your phone to 4.2.2_10.3.1.A.2.67 Firmware & If you already updated it to Downgrade it to 4.1.2_10.1.1.a.1.310 Firmware In Flash mode Using Flashtool 9.13 (Download Flashtool 9.11 install it After upgrade it with 9.12 & 9.13) don't unlock bootloader.
2)Now Root it Using DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit. to root just click runme.bat. Your phone will get root access & you will get Superuser app
3)Then use Backup-TA-9.8 to backup your TA.img & save it at any Safe location for further Use ( It Content DRM Data & must be saved throughout lifespan of your phone).
4)Now upgrade your phone to 10.3.1.A.2.67 either by OTA or Using Sony PC companion & if you are unable to get upgrade don't panic just use flashtool & flash the 4.1.2_10.1.1.a.1.310 again & try the OTA upgrade. (As i do have both for Indian region but attachments will be too big to Attach here).
5)Now install Vroot on your PC & root your phone with it. Now you can see that your bootloader got unlocked but don't panic install SuperSu from Playstore update binary for it reboot your phone. now freeze Superuser from Vroot using titanium backup then update binary for SuperSu. Now convert Superuser from Vroot into user app using Titanium Backup. Reboot Your phone update binary for SuperSu & uninstall superuser from Vroot.
6)Now Use BLU button From Flashtool. on pressing BLU button Flashtool it will prompt to start phone in flash mode to unlock bootloader just do as prompted but dont disconnect the phone after boot loader just hit the BLU button to re-lock bootloader. Reboot your phone.
7)Now just flash Back-up your TA Using Backup-TA-9.8.
8)Congratulation now you have rooted phone with locked bootloader with full functionality.
I wrote this because i just lost DRM data things cant be undone.
SO for all Niewbies this is guide to ROOT ZR with Locked BootLoader.
Click to expand...
Click to collapse
May i know why DRM is important and what is it used for?
good guide. only problems are...
there are a LOT of exact same guides floating around for MONTHS already. why do u feel u need to make a new one?
also, where are your credits and permissions to share other ppls' work here?
and also, there are those easy 1-click solutions available for MONTHS already and most ppl use that now instead of this complicated method which is outdated and troublesome...
oh one more thing after i read thru it again...
sasaengineeringworks said:
5)Now install Vroot on your PC & root your phone with it. Now you can see that your bootloader got unlocked but don't panic install SuperSu from Playstore update binary for it reboot your phone. now freeze Superuser from Vroot using titanium backup then update binary for SuperSu. Now convert Superuser from Vroot into user app using Titanium Backup. Reboot Your phone update binary for SuperSu & uninstall superuser from Vroot.
Click to expand...
Click to collapse
ur this just made your entire post redundant... because... THAT is ALL you need to do. nothing else. and even that is inaccurate info...
so please, having just joined XDA only recently with 4 posts and you think ppl here don't know what inaccurate info you know? do a search first in future... don't make unnecessary posts, k?
Just a reply
chewdaniel said:
good guide. only problems are...
there are a LOT of exact same guides floating around for MONTHS already. why do u feel u need to make a new one?
also, where are your credits and permissions to share other ppls' work here?
and also, there are those easy 1-click solutions available for MONTHS already and most ppl use that now instead of this complicated method which is outdated and troublesome...
oh one more thing after i read thru it again...
ur this just made your entire post redundant... because... THAT is ALL you need to do. nothing else. and even that is inaccurate info...
so please, having just joined XDA only recently with 4 posts and you think ppl here don't know what inaccurate info you know? do a search first in future... don't make unnecessary posts, k?
Click to expand...
Click to collapse
OK i agree there are there are many guide for rooting but all are applicable to Z or Zl having many kernel options. not as Zr which has very few kernel option.
Try any Method except vroot on Zr & tell me which are more useful.
Even vroot unlocks bootloader so to get root with 4.1 without unlocking bootloader is precautionary because accidental wipe of Ta partition may void Warranty.
This is not for pro who can build kernel for those who knew very less about android, to avoid them all pain i suffered.
& again i joined this forum 4 days ago as you think but i used this subscribed it 4 years ago with my first X10 & used it Since then anonymously as i lost my password for cant retrieve it.
& Tell me What is inaccurate i will try it Myself.
If you think its ridiculous why you haven't posted how to Root Zr it would have saved me a lot of pain.
So as you done nothing before stay as you are at least i m trying to save pain of others.
DRM
Islamegy said:
May i know why DRM is important and what is it used for?
Click to expand...
Click to collapse
DRM data is Digital Rigths Management Data which links purchased data to your phone without which you cant use data u purchased. More Important without which warranty voids, Bravia Engine seizes to work properly as it works with DRM Data. & Track Id downloaded from Market will not integrate with walkman which are Sony proprietary software's.
"Even vroot unlocks bootloader..."
WRONG
Vroot on 4.2.2 works without any issue...
Sent from my C5503
chewdaniel said:
"Even vroot unlocks bootloader..."
WRONG
Vroot on 4.2.2 works without any issue...
Sent from my C5503
Click to expand...
Click to collapse
I support this, I have done it just today on my C5503 and I confirm that I STILL have BE2, I just uninstalled vRoot Immediately because of the first post in this Thread Page
Kratellismorru said:
I support this, I have done it just today on my C5503 and I confirm that I STILL have BE2, I just uninstalled vRoot Immediately because of the first post in this Thread Page
Click to expand...
Click to collapse
hmm... i don't get any sort of crap from that software on my PC... maybe cos i was smart enough not to just blindly click Next all the way. IE/reg/security settings are all fine (part of my job is IT security so i know when weird things come into my PC)
as for the screenshot of the superuser app "dialing home", well one of the first few things i did was to replace it with SuperSU...
what..?? I've never seen a rooting procedure which unlocks the BL... and that last one absolutely doesn't need to be unlocked for rooting ! Honestly, I've serious doubts about your intentions. Why the hell do you tell upgrading, flashing, flashing back and blabla... this is too complicated.
Get vroot or kingo root, that's all you need
> chewdaniel personally, I use Superuser by clockwormod, it's open source and a safe alternative as well.
chewdaniel said:
good guide. only problems are...
there are a LOT of exact same guides floating around for MONTHS already. why do u feel u need to make a new one?
also, where are your credits and permissions to share other ppls' work here?
and also, there are those easy 1-click solutions available for MONTHS already and most ppl use that now instead of this complicated method which is outdated and troublesome...
oh one more thing after i read thru it again...
ur this just made your entire post redundant... because... THAT is ALL you need to do. nothing else. and even that is inaccurate info...
so please, having just joined XDA only recently with 4 posts and you think ppl here don't know what inaccurate info you know? do a search first in future... don't make unnecessary posts, k?
Click to expand...
Click to collapse
This ^^^^^^^^
Thread closed
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
original post:
Last Friday the OTA arrived on my phone and I tried to update it and keep it rooted. But I failed.
Has anyone a clue how to do it or can it be assumed to be impossible?
What I tried so far:
I was rooted with chaindd's superuser on firmware version .141 as it arrived. I had just three apps in use witch required root, busybox, titanium backup and adfree.
Nevertheless my attempts to update failed at the second stage of the update.
After a few attempts I did a factory-reset, reflashed the .141 firmware and rerooted using flashtool. The update worked that time but root was lost. Even though the app and binary were still there...
Sent from my LT30p using xda app-developers app
There's been no OTA update over here what's your customization number ?
Sent from Shane's Xperia T LT30a
Have you tried using OTA root keeper ? I didn't need to use it before on my Xperia's but had to with the Motorola Razr and it worked .
Sent from my LT30p using xda app-developers app
MySpace customization number is 1266-2433. It is from the Austrian provider 3.
At my first attempts to update I also tried ota root keeper. But they all failed.
Afterwards, after the reset, I just tried it with superuser's and supersu's ota survival mode.
I have also read on other forums that if the update follows the Google update.zip format one can flash it through a custom-recovery and flash supersu.zip afterwards and keep root.
But Sony's update is probably not in that format because it's a .bin file(download_ platform.bin in /sdcard/recovery/).
By the way it's 450 mb big.
Sent from my LT30p using xda app-developers app
At the moment the only way to root is to flash THIS via recovery.
Instead if you want to keep your update with your customization number, you can unlock your bootloader (first do a TA backup)
istux said:
At the moment the only way to root is to flash THIS via recovery.
Instead if you want to keep your update with your customization number, you can unlock your bootloader (first do a TA backup)
Click to expand...
Click to collapse
How do I install CWM I can't find a compatible version and I came across a thread saying that I need an unlocked boot loader to do so ?
Sent from Shane's Xperia T LT30a
I have done it!
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
This is for Mac. Is it possible to make this script for Windows?
Dacha75 said:
This is for Mac. Is it possible to make this script for Windows?
Click to expand...
Click to collapse
Yes it was for mac and linux only, because i only use this two.
I have added a script for windows but I am not sure if it works, because i can't test it.
The file in my previous post has been updated.
thurin said:
Yes it was for mac and linux only, because i only use this two.
I have added a script for windows but I am not sure if it works, because i can't test it.
The file in my previous post has been updated.
Click to expand...
Click to collapse
Thank you. I'll try.
I can't root with flashtool. Which method in flashtool did you use for rooting?
Start flashtool.
Plug your phone with USB debugging on to your PC
Click on the sign of the open lock.
Then follow the instructions of flashtool
That should work for phones on a 4.1 Firmware
thurin said:
Start flashtool.
Plug your phone with USB debugging on to your PC
Click on the sign of the open lock.
Then follow the instructions of flashtool
That should work for phones on a 4.1 Firmware
Click to expand...
Click to collapse
I did that but flashtool won't root my phone.
[4.3] [T] Keep root with OTA-update
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
Your script for Windows works excellent. I have root on 4.3 after OTA-update.
Flashtool didn't wont to root my .141. I use [T/TX/V][ROOT] DooMLoRD Easy Rooting Toolkit (v17) {perf_event exploit}[20130717] for rooting.
THANK YOU !!!
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
I' ve tried your method (root with flashtools) but when I update from OTA I loose root (Supersu tells that couldn't find su binary) :crying:
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
hello friend this script work for xperia tx LT29i 4.1.2?
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
I Downloaded The Attached File from Post #7 but when I Run "runme.bat" I got this error! (Attached Pic)
Where is the problem??
I have Windows 7 64bit
Mahthenewgamer1998 said:
I Downloaded The Attached File from Post #7 but when I Run "runme.bat" I got this error! (Attached Pic)
Where is the problem??
I have Windows 7 64bit
Click to expand...
Click to collapse
You probably don't have ADB/Fastboot implemented in your system.
First do this Simple guide to ADB/Fastboot.
Then run file "runme.bat". This should work.
Link for downloading adb & fastboot on the page above is not working (for me).
View attachment adb_fastboot.zip
scrubs00 said:
hello friend this script work for xperia tx LT29i 4.1.2?
Click to expand...
Click to collapse
Yes
thurin said:
Ok I have managed to keep root with the OTA-update to 4.3!
As I have read the problem with updates to 4.3 from a <4.3 firmware is that root on 4.3 requires more than just the su binary as it was on <4.3 firmwares. So it has come to my mind(and at this point i am really confused that no one else has thought of this before) what if I install all the necessary files before I update? And guess what... It worked.
Here is what i have done:
Flash the latest 4.1 firmware with flashtool
Root using flashtool and supersu
Run the installing script that i have wrote
Load and install the OTA-update
I guess if you have used flashtool to root, steps one and two are not necessary. If you have used Bin4ry's rooting script it will not work and you will have to reflash(that's at least what i have experienced).
So what will this script to?
It will install all the files provided in the latest UPDATE-SuperSU-v1.93.zip from chainfire. And it is adapted from his update-binary.
I know it is not perfect as i have done it, but i am quite new to shell scripting. So any help to make it better is welcomed.
Thanks to the makers of flashtool and supersu for making this possible!
Click to expand...
Click to collapse
Thanks thurin. Your script worked for me too on my Xperia T. I was already rooted on JB 4.1.2 so went from step3 and now I'm still rooted on JB 4.3 firmware 9.2.A.1.199 (o2 UK). I'm surprised your post hasn't received more attention since I've seen a lot of queries about updating to JB 4.3 without losing root on bootloader locked phones.
Looking at the output in the CMD box when I ran the script it appears none of the file delete commands worked as I had lots of
"rm failed for -f, No such file or directory." errors, however I checked with ES Explorer that everything looked OK before running the OTA update.
I think it is that the android default 'rm' command doesn't support the '-f' switch, but if you amend your script to use the file delete from busybox then those errors shouldn't occur,
e.g. /system/xbin/busybox rm -f /system/bin/su
Hi,
I'm using Chainfire systemless root for Android 6. Can I install OTA updates without unrooting or is it better to unroot anyway? Do I habve to reinstall the boot image after an OTA Update?
You should be able to update, assuming nothing modified /system.
I am unsure whether you need to reflash SuperSU after updating. I would assume yes, but ???
You should really go read the threads in this forum. Asking questions about topics that are already answered is a forum faux pax. Don't be a noob.
Ok, I'll put myself out there as a noob then.
I've read everything that I can find about whether systemless SuperSU will allow OTA updates or not. I find no definitive answer. It's "maybe" (as above) or "You'll have to reinstall stock recovery" (which doesn't sound to me like a transparent simple OTA update) - all pretty vague and I see no answer from anyone who has actually seen it work on their own device.
So can some kind soul please point me to the apparently obvious definitive yes/no answer that they've found and I can't?
Or anyone who has systemless SuperSU installed and has seen ***with their own eyes*** the "System updated downloaded" and managed to press the button and update without any other actions?
Thank you...
I've had success with 2.63 (not out yet) using the "Full unroot" option in SuperSU, and OTA updating from 6.0 to 6.0.1 on volantis/flounder (Nexus 9 Wi-Fi). Most OTA's will not work without unrooting this way. After flashing the OTA, you will have to re-root.
The same should be possible on 2.62, assuming you are also running stock recovery.
Of course, this will only work if you have not modified /system, /vendor (if present) and /oem (if present) in any way.
Once I get FlashFire updated, it should all be much easier than that.
Thanks, Chainfire. At last a definitive explanation, and from The Master himself...
I've seen on one thread somewhere a comment about the writer using 2.63. Do you have any schedule for the release of 2.63? I'm currently unrooted, and I would want to root again only if I knew that the monthly disruption is minimal.
No great rush - I reckon it'll be another month at least before I have to do something about my current stock 6.0.1.
(Found your shirt yet? )
Not more than a few days I think. Nobody has 2.63 but me. I might skip that number though, as some are misnaming the 3rd release of 2.62 (2.62-3) as 2.63.
Note that those iterations with the same version numbers only include changes to the ZIP file scripts, not changes to the SuperSU GUI or binaries.
As for the shirt, I'm afraid it's still lost somewhere in the red light district. Long story!
Thanks again.
This is the thread that I mentioned:
http://forum.xda-developers.com/lg-g-pad-83/orig-development/v500-cyanogenmod-13-0-t3259135/page12
nytral - post #117:
"Oops, Secure booting error, boot certification verify. Supersu 2.63beta managed to generate a boot.img"
@Chainfire Does "Full unroot" restore the original boot.img ?
Because most OTA's nowadays verify the checksum of boot partition before continuing to update.
Assuming the backup hasn't gone missing, it will offer to restore the original boot image. I will also offer to attempt to restore recovery (also needed for most OTAs), though that requires a working install-recovery inside the firmware (TWRP is known for messing that up on install).
MM root could be nice, i cannot use titanium backup without the mobile rebooting when i try to do my backups, it can backup but not restore.
RichardEb said:
Hi,
I'm using Chainfire systemless root for Android 6. Can I install OTA updates
Click to expand...
Click to collapse
http://www.xda-developers.com/chainfire-systemless-root-now-supports-automated-boot-image-patching/
Just a clarification, meaning even if I have custom recovery(Since I flashed 2.65 with custom one) I can still receive OTA by using unroot option on my nexus 5? Let's say monthly security patches and I just need to reflash root?
Steps?
*Assuming I have custom recovery and rooted
1. Unroot using SuperSU
2. Install OTA using built-in
3. Reflash root