Related
Hi there guys!
I want to root my Z1 c6906, unlock the bootloader and flash custom roms, but im kind of confused right now because i have read a lot of different guides and im not pretty sure which one to follow now. I also learned on one thread that i should do a TA and DRM Keys backup because they can be lost forever if i don't do a backup. Also the IMEI. So im not pretty sure how to do that. Also saw a thread about bricking the device, and kind of got scared. Btw, i have plenty of experience working on Android devices, unlocking, rooting, flashing roms, etc. I have used Android since the G1, but im kind of confused right now about how to proceed on this device because this is my first Sony and my last phone was a Nexus 4, which was virtually unbrickable. Can anyone help me out here?
djluis48 said:
Hi there guys!
I want to root my Z1 c6906, unlock the bootloader and flash custom roms, but im kind of confused right now because i have read a lot of different guides and im not pretty sure which one to follow now. I also learned on one thread that i should do a TA and DRM Keys backup because they can be lost forever if i don't do a backup. Also the IMEI. So im not pretty sure how to do that. Also saw a thread about bricking the device, and kind of got scared. Btw, i have plenty of experience working on Android devices, unlocking, rooting, flashing roms, etc. I have used Android since the G1, but im kind of confused right now about how to proceed on this device because this is my first Sony and my last phone was a Nexus 4, which was virtually unbrickable. Can anyone help me out here?
Click to expand...
Click to collapse
Quite simple process actually, just flash .534 ftf with flashtool and root with bin4ry or use nuts dual recovery installer. To backup your ta before unlocking bootloader, simply use the Backup TA tool
Ahki767 said:
Quite simple process actually, just flash .534 ftf with flashtool and root with bin4ry or use nuts dual recovery installer. To backup your ta before unlocking bootloader, simply use the Backup TA tool
Click to expand...
Click to collapse
Thanks. And what about the DRM keys?
djluis48 said:
Thanks. And what about the DRM keys?
Click to expand...
Click to collapse
The DRM keys are in the Ta partition
Ahki767 said:
The DRM keys are in the Ta partition
Click to expand...
Click to collapse
I see. Another question, i see that for my devices the only .534 TFT available is for Rogers. There is no problem if i flash using Flashtool?
djluis48 said:
I see. Another question, i see that for my devices the only .534 TFT available is for Rogers. There is no problem if i flash using Flashtool?
Click to expand...
Click to collapse
Yes, I'm sure there'll be no problems
Ahki767 said:
Yes, I'm sure there'll be no problems
Click to expand...
Click to collapse
Sorry for bringing back this thread. Now i got time to start trying to unlock the phone and flash custom roms, was extremely busy before with work.
New problem: After i downgraded to FTF .534, rooted and made the TA Backup, i check if the phone was "allowed" to be unlocked and surprise, it says it can't be unlocked. Tried unlocking with Flashtool and it said the same thing. Can the phone be unlocked or is there a way to flash roms without unlocking?
Right now im feeling really depressed with this phone. If i can't unlock it, i most likely will sell it and get something that can be unlocked.
One of the reasons i want to unlock is because on 4.4, Google prohibited the phone to write on the Ext.SD and i want a way to overcome that prohibition and use it like i was able to on 4.3.
If it says it cannot be unlocked then it cannot be unlocked
However, you can still sort out the issue of writing to the ext SDcard by rooting and following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2687966
In order to do that, you only need root, not to be unlocked
gregbradley said:
If it says it cannot be unlocked then it cannot be unlocked
However, you can still sort out the issue of writing to the ext SDcard by rooting and following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2687966
In order to do that, you only need root, not to be unlocked
Click to expand...
Click to collapse
Ok. That sucks. Thanks for the link.
Another question: How i root.757? I was able to root .534, but not sure how i need to proceed now. Do i need to download generic .757 and apply any root method? Or the root will still be there if i flash it over my current rooted .534?
1) Flash a stock 534 FTF (Ignore if you are already on 534)
2) Install dual recovery (Find files and instructions in the XZ dual recovery thread in the cross device development section)
3) Flash a prerooted 757 rom (Find files and instructions in the development section)
Done, 3 easy steps
gregbradley said:
1) Flash a stock 534 FTF (Ignore if you are already on 534)
2) Install dual recovery (Find files and instructions in the XZ dual recovery thread in the cross device development section)
3) Flash a prerooted 757 rom (Find files and instructions in the development section)
Done, 3 easy steps
Click to expand...
Click to collapse
So i can flash any rom now with that recovery? Even if my bootloader is still unlocked? Or only stock based roms?
djluis48 said:
So i can flash any rom now with that recovery? Even if my bootloader is still unlocked? Or only stock based roms?
Click to expand...
Click to collapse
If your bootloader is unlocked you can flash any rom from the development sections or the original development section
But if your bootloader is unlocked you do not need to do any of this to root.
Just flash DooMKerneL or [NUT]s XZDR kernel
If your bootloader is locked, you have to downgrade and root that way. Then you can flash any stock based rom, look in the development section for them
gregbradley said:
If your bootloader is unlocked you can flash any rom from the development sections or the original development section
But if your bootloader is unlocked you do not need to do any of this to root.
Just flash DooMKerneL or [NUT]s XZDR kernel
If your bootloader is locked, you have to downgrade and root that way. Then you can flash any stock based rom, look in the development section for them
Click to expand...
Click to collapse
Oops. Im sorry. I meant locked. Was doing something else and wrote that fast. Thanks for the answer. Will check. Got the DualRecovery installed now and will try to install a prerooted .757 later.
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Thanks..
ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
Follow the NUMEROUS instructions already posted. There are some in my signature
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No, that's why every guide says to downgrade
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Yes, messing with the bootloader can lead to a hard brick, yes you need root to backup the TA
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Follow the link in my signature to get that done
ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
Click to expand...
Click to collapse
The answare are spread over here, why do not take some more time to read?
ro xl123 said:
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
ro xl123 said:
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No way! You have to downgrade then upgrade to pre-rooted version.
ro xl123 said:
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
ro xl123 said:
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..
Thanks all. Thank you for your help.
eclyptos said:
The answare are spread over here, why do not take some more time to read?
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
No way! You have to downgrade then upgrade to pre-rooted version.
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..
Click to expand...
Click to collapse
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct
gregbradley said:
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct
Click to expand...
Click to collapse
So what is usb flash mode then?
when asked to enter flashmode hold the volume down button on your (Turned off) phone and attach the usb cable
ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.
eclyptos said:
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.
Click to expand...
Click to collapse
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!
ro xl123 said:
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!
Click to expand...
Click to collapse
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.
eclyptos said:
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.
Click to expand...
Click to collapse
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy
ro xl123 said:
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy
Click to expand...
Click to collapse
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.
eclyptos said:
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.
Click to expand...
Click to collapse
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?
ro xl123 said:
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?
Click to expand...
Click to collapse
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley
eclyptos said:
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley
Click to expand...
Click to collapse
No, I understood but kinda didn't wanted to.. :/
I already downgraded, rooted and installed recovery. Then I updated to stock rom 757 back, thinking that I could simply root using recovery. Anyways, after I updated, I couldn't get in to recovery mode, because the one I installed was without unlocking bootloader, I simply installed firmware based recovery. I don't really think about unlocking bootloader, the TA codes and stuff kinda scares me.. I did took backup of my TA tough. I just need to have root in OFW Kitkat. I can do without recovery (which i can't install because of bootloader). But root is essential. :/
ro xl123 said:
No, I understood but kinda didn't wanted to.. :/
Click to expand...
Click to collapse
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.
eclyptos said:
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.
Click to expand...
Click to collapse
OHHHHHHH... I'm so sorry, really. Now I understood it. Thanks alot man.. !! I love you :laugh:
ro xl123 said:
I love you :laugh:
Click to expand...
Click to collapse
I love you too.
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Deivid85 said:
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Click to expand...
Click to collapse
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
samwathegreat said:
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
Click to expand...
Click to collapse
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Deivid85 said:
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Click to expand...
Click to collapse
You are correct. Nothing in the PIE thread is relevant to us with unlocked bootloaders.
Worked like a charm!
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
NameLessThugZero said:
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
Click to expand...
Click to collapse
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
samwathegreat said:
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
Click to expand...
Click to collapse
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
samwathegreat said:
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
Click to expand...
Click to collapse
Sweet, thanks for your help. Ill check on the TB thing. Ill update if I need any other help.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Keep in mind, that PIE itself isn't as good of root as using SlapMyMoto & MotoWpNoMo together.
On the X there are two parts needed for effective Root. 1. Root Exploit, and 2. Write Protection Dis-abler.
PIE is a root Exploit. It exploits a vulnerability to grant root access. It does not address Write Protection.
Write Protection on the X prevents proper access to /system or the like. Some apps wont be able to create new files in the protected folders, and any changes made to existing files (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. This is also why PIE root is lost at power off/on.
In the past (4.4 and below days) SlapMyMoto was the Root Exploit, and MotoWpNoMo was the write protection dis-abler. Once thought to be permanent, the exploit used by MotoWpNoMo was plugged in 4.4.2 making it not work. Write protection becomes re-enabled, and there is no new exploit to disable it.
Why do I mention this? In reading the various threads, especially the Pie thread, there appear to be special instructions to install XPosed when write protection is enabled that you'll need to keep in mind, as well as info on how to re-root and get Xposed working again if you do power off/on. Because write protection is enabled, there are some apps and hacks that may not work. Some of the Tethering tricks for example.
Unlocking the bootloader gets around this. Once you unlock the bootloader, you can always install a custom recovery (like TWRP) and root from there. In the process, write protection becomes disabled. There is no need to wait on a vulnerability in the code to be exploited to gain root and disable write protection.
Hello all,
Im totally confused as to how to go about rooting my device c6902. Ive owned a couple of android devices and Ive rooted them all, however....with this device and there seem to be different ways people have rooted from reading the threads and im totally confused, So far I have unlocked the bootloader, and upgraded the device OTA to lollipop .242 (before the bootloader was unlocked), I dont intend installing any custom firmware, just want root so I can use TB and maybe delete a few bloatwares with root explorer and use xposed.
Im confused as to whether:
1. I have to downgrade firmware to kitkat, just to get root, then upgrade back to official firmware?
2. Ive been under the impression that a custom recovery and supersu, is enough to get root. It doesnt work that way on this device?
3. I saw some oneclick root programs that worked on the z1 compact would any work here
Just trying to know more about the phone and understand, so any help is appreciated. Thanks in advance.
bigmeech084 said:
Hello all,
Im totally confused as to how to go about rooting my device c6902. Ive owned a couple of android devices and Ive rooted them all, however....with this device and there seem to be different ways people have rooted from reading the threads and im totally confused, So far I have unlocked the bootloader, and upgraded the device OTA to lollipop .242 (before the bootloader was unlocked), I dont intend installing any custom firmware, just want root so I can use TB and maybe delete a few bloatwares with root explorer and use xposed.
Im confused as to whether:
1. I have to downgrade firmware to kitkat, just to get root, then upgrade back to official firmware?
2. Ive been under the impression that a custom recovery and supersu, is enough to get root. It doesnt work that way on this device?
3. I saw some oneclick root programs that worked on the z1 compact would any work here
Just trying to know more about the phone and understand, so any help is appreciated. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631291
Using the guide on the link I just posted, you are not required to unlock the bootloader, unlocking the bootloader without backing up the TA partition can cause problems with your phone.
You need to downgrade to KitKat 4.4.4 with kernel 108, then root it with easyroot install supersu and rootchecker to make sure your phone is rooted, the use NUTs recovery to create a recovery partition, after that search XDA forums for a pre-rooted lollipop flashable zip and install that, and voila you should be on lollipop with root and recovery.
I am not sure about one-click root programs.
demon148 said:
http://forum.xda-developers.com/showthread.php?t=2631291
Using the guide on the link I just posted, you are not required to unlock the bootloader, unlocking the bootloader without backing up the TA partition can cause problems with your phone.
You need to downgrade to KitKat 4.4.4 with kernel 108, then root it with easyroot install supersu and rootchecker to make sure your phone is rooted, the use NUTs recovery to create a recovery partition, after that search XDA forums for a pre-rooted lollipop flashable zip and install that, and voila you should be on lollipop with root and recovery.
I am not sure about one-click root programs.
Click to expand...
Click to collapse
Thanks for your help.
I already unlocked the bootloader though. Do I need to downgrade the whole kitkat rom or flash just the kernel? thanks
Figured out. Thanks
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.