I always have an error notification, that the last system-update cannot be verified and therefore I cannot install it.
I unlocked the bootloader and rooted the z3 according the how-to in xda-developers forum.
How can I install that lastest system-update and get rid of that notification?
Thanks!
Questions belong in the Q&A section
Thread moved
PS
Taken straight from the sony website here
Q:Are there any known issues when unlocking the boot loader?
A: Yes. When you select a device, any known issues for that device will be displayed. In addition, the following generic issues have been reported:
•Some users have experienced problems when they are accepting over the air upgrades. Therefore we do not recommend users to accept over the air upgrades, after having unlocked the boot loader. For additional information, check out the XDA Forums for hints and tips from the community.
Click to expand...
Click to collapse
You cannot install it until someone produces a FTF file for it. Then you can flash it via flashtool.
Turn off notifications in settings.
Thanks very much.
So if I flash a ftf from here:
http://forum.xda-developers.com/z3/general/ftf-stock-firmwares-xperia-z3-models-t2886061
I will lose all my data and also root. Is that correct?
Thanks!
bill340 said:
Thanks very much.
So if I flash a ftf from here:
http://forum.xda-developers.com/z3/general/ftf-stock-firmwares-xperia-z3-models-t2886061
I will lose all my data and also root. Is that correct?
Thanks!
Click to expand...
Click to collapse
Not if you exclude "Data" when you flash.
You will lose root, but you can quickly get it back by flashing a root package.
Flashing a FTF does not relock your bootloader
Thanks!
So you mean the supersu update.zip via recovery?
Or do I need to reflash a kernel via fastboot?
bill340 said:
Thanks!
So you mean the supersu update.zip via recovery?
Or do I need to reflash a kernel via fastboot?
Click to expand...
Click to collapse
The kernel
I recently have an update for my Xperia Z3 D6616 but it says couldn't verify. I had it rooted but then i erased the root premissions and the app (KingRoot). Should i update with the computer?
Related
Check the device firmware type by going to Setting - about tablet - built number
Download the right firmware pack for your device.
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Now extract the zip file and you will have another zip file.
Rename that zip file as "EP201_768_SDUPDATE" and place it to an external sd card if you do not have a custom recovery. If you are rooted and unlocked plus you have a custom recovery you don't need to rename it you can place it in internal sd is well.
Now turn off your device. Hold power button including the volume down button and enter custom recovery. For stock recovery it should detect it automatically and will install. once in custom recovery clear your cache and install the file with the name above or whatever name you have. once installation is complete. reboot the system be patient and you have the latest update.
You can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/show....php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
Make sure you have USB debugging on.
To get custom recovery. Download goomanager from playstore and you can install TWRP recovery from the option list. which is Option - install OpenRecoveryScript.
I am not responsible if you mess up your device. do these at your own risk. Nonetheless these steps work perfectly for me.
Renaming is not needed.
lafester said:
Renaming is not needed.
Click to expand...
Click to collapse
Exactly thats for people without custom recovery
Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium
rizanx said:
Exactly thats for people without custom recovery
Click to expand...
Click to collapse
does the update push the stock recovery as well?
and root is lost right?
Yes and yes.
Sent from my HTC One X using xda premium
odeccacccp said:
does the update push the stock recovery as well?
and root is lost right?
Click to expand...
Click to collapse
Yes you will lose root.
But you can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/showthread.php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
oh and make sure you have USB debugging on.
sorry for the mix up. yes you do lose recovery. Download goomanager from playstore and you can install TWRP recovery from the option list.
rizanx said:
Through custom recovery stock recovery is not pushed! you will still have custom recovery. You will only lose root.
Click to expand...
Click to collapse
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
+1 You WILL lose custom recovery with this method. This has all been covered before...
Sent from my EVO using xda premium
Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
Thanks for clear up.
MysticMgcn said:
Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks
I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?
GRIM1337 said:
I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?
Click to expand...
Click to collapse
No. when you unlocked it clearly stated no more ota updates for you.
Yes. of course you can flash manually just like any other rom.
odeccacccp said:
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks
Click to expand...
Click to collapse
You don't need to have stock rom. As long as you have the stock kernel your ok. You will of course lose custom recovery but its easy to download again as i have mentioned in my first post.
There is a lengthy way to do this. But why do that when it takes you literally 2 minute to root it with DebugfsRoot .
Hope it went well for you.
Ok so I just recently got my hands on a Nexus 5 which I rooted with CF Auto Root and relocked the bootloader with Bootunlocker for security (I'm guessing I should unlock before the update). I see reports surfacing of a possible 4.4.3 update in the near future. So before that happens I want to figure out the best practice for updating a N5 with CF Auto Root. It stands to reason I'll do a full backup so that's a given.
I'm not new to rooting. Done it a few times. Just haven't had a device that gets regular OTAs in my country so it hasn't come up.
Is there a way to update so that root is preserved? Obviously I'd like to keep the process as simple as possible but if I have to work from scratch it's not the end of the world.
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Or perhaps it's better to ask what the best procedure for updating a stock Nexus 5 with CF Auto Root.
Everything that you have ever wanted to know about OTA can be found here http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Ah thanks. Appreciate it.
generally no, after ota you lose root. but there are apps that will save your root so that you keep root after an update.
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Reaper1242 said:
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Click to expand...
Click to collapse
ive never used any since i dont ota, i update my custom rom as soon as its updated, but ive heard of success with rootkeeper. but it doesnt matter, it literally takes 3 minutes to root a nexus the right way(via fastboot).
Yea, I should use fastboot in future.
Reaper1242 said:
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Click to expand...
Click to collapse
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
jj14 said:
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
Click to expand...
Click to collapse
you would need to flash a custom recovery first, then supersu in your custom recovery.
Thanks everyone for the responses.You've made everything much clearer.
simms22 said:
you would need to flash a custom recovery first, then supersu in your custom recovery.
Click to expand...
Click to collapse
Good point. I assumed that op had installed a custom recovery when he rooted, but that is not always the case.
Ok so I'm going to sideload myself. Been a while so I just want to confirm the process so I don't screw up.
I'm using TWRP
Obviously I'll do a NANdroid and probably Titanium as well.
1) Unlock bootloader with Bootunlocker
2) Connect device to PC
3) Boot into TWRP recovery and go to Advanced > ADB Sideload
4) type adb sideload update.zip (or whatever I call the file)
5) reboot device and check if it's working
6) reboot to recovery and reflash superuser.zip
I think that's it. Is there anything else I need to be aware of? If I'm right it should then be updated, rooted and in the same state before I updated.
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash stock system.img and flash recovery.img and then do the update.zip from the stock recovery..
If you don't want to flash, then make sure you have removed all the modifications you have done to system apps. If you don't remember then I would certainly recommend flashing stock images...
Sent from my Nexus 5 using Tapatalk
Q&A for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
UK Root?
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
DazEB said:
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
Click to expand...
Click to collapse
If it is the WiFi Only model it should work, but no promises. If it is LTE please PM the link to the boot.img
Cwm and future ota
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Sweet, I followed the "Locked bootloader" method step by step and it working perfectly, no problem whatsoever. Thank you very much!!
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
Cwm had not prevented any OTAs on the shield tablet for me yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
Thanks for the instructions. I followed the unlocked bootloader one, but now I cant boot. I flashed the modified LTE boot img and now everytime I boot it keeps going into fastboot mode.
Unlocked bootloader
flashed CWM
Booted into CWM and flashed SuperSU Beta
Selected Yes to fix Root
Reboot system
Boot back into fastboot and flash the modified boot.img
Reboot system...............now keeps booting into fastboot.
Please help.
EDIT: I'm an idiot. Unzip the boot.img before you flash it. Problem solved.
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
You can also restore stock recovery afterward by flashing this
SuperPichu said:
You can also restore stock recovery afterward by flashing this
Click to expand...
Click to collapse
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
layanto said:
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
Click to expand...
Click to collapse
You can definitely restore it if you make a backup. I'm actually not sure if they are the same.
Can this be done without a computer?
Jaybenosa said:
Can this be done without a computer?
Click to expand...
Click to collapse
No
Sent from my SHIELD Tablet using XDA Free mobile app
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
So I failed miserably, accidentally hit reboot system after step 4 so now I'm on lollipop not rooted and no unlocked boot loader nor have a recovery ??
Jaybenosa said:
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
Click to expand...
Click to collapse
This is how to unlock the bootloader. It will erase all your userdata.
https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
KentuckyHouse said:
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
Click to expand...
Click to collapse
You will have to unlock. You can restore the stock recovery afterward if you wish
Sent from my SHIELD Tablet using XDA Free mobile app
Does towelroot still work for the LTE devices when moving to lolli?
OK, so I had to unlock my bootloader since I'd already taken the OTA.
Now I'm at this point. I can't seem to get recovery to stick. I've flashed it multiple times in fastboot and it just won't stick. Now, over in the other thread, someone has asked if I've done the "fastboot flash boot boot-root.img" step yet. This confuses me, as that step comes AFTER you flash recovery, then flash SuperSU with CWM. But seeing as how I can't get recovery to stick, I can't flash SuperSU, and that means I can't move on to that step.
So I guess what I'm asking is, can I run "fastboot flash boot boot-root.img" before "fastboot flash recovery recovery.img"? Will that make a difference? Will it brick my tablet?
I'm all out of ideas here.
Locked bootloader and updated to ver 2.0 lollipop.
Hi there.
I have downloaded and installed version 2 lollipop and I would like root to store my games on SD. When checking the root guide it informed me to download update but not install. I have already installed the update and was wandering if they is a way to root my device still.
Kind regards
Hi,
TL-DR; I rooted my phone, and want to update with minimal loss of data.
Sorry for this newbie question but I really couldn't figure out everything and wanted to confirm before proceeding.
I have MHA-L29C185B138 and rooted step-by-step via the instructions on this link:
HOW TO ROOT YOUR MATE 9 with Decrypted Data in TWRP without needing a patched Boot.img
I want to update. What should I do? I isntalled Firmware Finder and downloaded MHA-L29C185B172 FULLOTA-MF. (downloaded all 3 files)
I couldn't find a complete tutorial for rooted roms. Read different and partial recommendations on different threads. Somewhere I read that I need to restore my boot and recovery partition before update. I backed my boot partition as it was a step in rooting guide but I didn't back up my recovery partition.
So could you please point me a beginner friendly guide that explains step by step updating rooted mate 9?
Thanks in advance.
I bump up this question as I'm interested in that answer also
Sent from my MHA-L29 using Tapatalk
Updating and keeping root is basically not possible, as far as I know.
Regardless of installation method, your phone will be re-locked and wiped when new firmware is installed on a rooted phone.
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
vipivj said:
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
Click to expand...
Click to collapse
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Sent from my MHA-L29 using XDA-Developers Legacy app
jr313 said:
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Click to expand...
Click to collapse
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
vipivj said:
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
Click to expand...
Click to collapse
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
jr313 said:
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, you want to use the RECOVERY.img not recovery2. You fastboot that img and you will have stick recovery, and it will place it in the correct spot so need to worry about where you would need to flash it to. Hope that helps
sent from my rotary phone
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
TENN3R said:
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
Click to expand...
Click to collapse
Just old bootloader afterwards
Great, works for me.
Can you post specific instructions I really would like to unlock and root my phone
Any side effect of using old bootloader? Thank you.
[email protected] said:
Can you post specific instructions I really would like to unlock and root my phone
Click to expand...
Click to collapse
In fact, there are a lot of articles teaching you that.
For example, you can click here to know how to root.
vibranze said:
Any side effect of using old bootloader? Thank you.
Click to expand...
Click to collapse
No more side effects than not verifying the system image found yet.
Steven_Yang said:
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
Click to expand...
Click to collapse
THANK YOU!! i have the bootloop issue that was driving me crazy and was unable to root properly, until i flashed the old bootloader
Read here. There is a fix that does not require downgrading the BL.
https://forum.xda-developers.com/showthread.php?t=3600606