hey guys,
why do you have to downgrade the fw to 4.4.4 if you could easily flash a new firmware with root included already?
guide I used: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
also, where are the DRM keys in the file system? I use Linux and I can't use the mentioned Windows bat file tool to back them up. And I don't want to rewrite the batch files into a shell script...
The DRM keys are raw data inside seperate partitions as far as I have understood it correctly. Maybe someone can comment on the details but you should be able to dump them using dd if you identify the correct partitions.. On the first question, I would be interested in this too.
Why would you downgrade and root if you can flash a pre-rooted image?
How come you can flash a pre-rooted image with locked BL? Doesn't the phone check CRC before flashing a firmware with locked BL? Doesn't it refuse to flash if tampered with? How does that work?
Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.
faxd said:
Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.
Click to expand...
Click to collapse
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
I have this question too.
Maybe because pre root images can have something installed that could hazardous?
I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.
pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff?
Click to expand...
Click to collapse
To quote someone else:
twisteroid said:
Well, because you need a recovery to flash the pre-rooted zip, and to have a recovery you have to root first. The pre-rooted SYSTEM partition cannot be flashed using Flashtool because it would not pass signature check. The only way to flash it is to use root access and a working recovery.
Click to expand...
Click to collapse
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
pakjebakmeel said:
Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH
faxd said:
To quote someone else:
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH
Click to expand...
Click to collapse
No, no, I think I got it now but my wording is a bit off I guess. Here are my understandings:
- Flashtool flashes through Sony firmware flash mode, this mode only flashes official tft files that pass signature check. When you add root to an image it fails signature check because of the mismatching hash and it will refuse to flash.
- To flash a 'tampered' image you need to use a custom recovery as it does not refuse.
- To get a custom recovery you need to get root to be able to flash the recovery partition.
- To get root you need to downgrade and use the exploit to get the su binary on.
Correct right?
Just one more question, how does the signature check work? I would understand it if you could download images from Sony like OTA's, they'd be signed and sealed by Sony. Just like driver signing based on RSA keys and such. If you modify them they fail the signature check obviously.
But I've seen people create FTF files from their own phones and it seems to pass the signature check, how is the file signed then? What is the 'signature' check based upon? Or is the image signature included on the phone and pulled into the FTF file when the image is pulled from the phone?
So basically the question is: "Where does the signature come from if one would create an FTF file from a working phone?"
Sorry, sorry, many questions. I'm just trying to understand all details, can't stand not knowing how stuff works.. :silly: I think I at least understand the root/bootloader/recovery part now. :victory:
phre5k said:
I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.
Click to expand...
Click to collapse
Restore goes well with this simpler method as well?
PantsDownJedi said:
Restore goes well with this simpler method as well?
Click to expand...
Click to collapse
Windows script does the exact same thing after looking at it, it does some logic for looking at the partitions a bit better is all. Hopefully nothing has changed since newer versions of Andriod.
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.
Hey,
I have a rooted Z3 Compact (D5803) with locked bootloader (via the gfrieroot hack).
However now I still have this old fw and I want to update to the latest KitKat FW, 23.0.1.A.5.77, according to this list:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
So now I'm wondering how can I do this, with keeping root?
TY
PS:
Before you ask, I want to stay with KitKat until Lollipop is more mainstream -> less problems.
According to the topic that you linked, it is written in the FAQ :
My current firmware is already rooted, will I need to root again after flashing?
Yes you will, as every time you flash you erase the system partition entirely (root included).
Click to expand...
Click to collapse
spookyneo said:
According to the topic that you linked, it is written in the FAQ :
Click to expand...
Click to collapse
Maybe, but I don't know how. Especially since I used a hack/exploit to obtain root w locked bootloader, which only works in that old FW (so I can't just update and do it again).
However from what I read there are ppl who have root, locked bootloader and a recent FW... So I guess there must be a way...
You have to find the original FTF for the version you want (23.0.1.A.5.77), and either make or download a pre-rooted flashable.zip for that version. Then just follow the last part "Install latest firwmare with root, DRM keys, recovery" from the rooting guide again: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
If you want to keep your data partition and internal storage, remember to check "DATA" and "CACHE" in addition to "SYSTEM" in Step 43.
twisteroid said:
You have to find the original FTF for the version you want (23.0.1.A.5.77), and either make or download a pre-rooted flashable.zip for that version. Then just follow the last part "Install latest firwmare with root, DRM keys, recovery" from the rooting guide again: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
If you want to keep your data partition and internal storage, remember to check "DATA" and "CACHE" in addition to "SYSTEM" in Step 43.
Click to expand...
Click to collapse
Thanks, this looks very promising - too bad there is only a US pre-rooted version...
Ah, well so I will now know all the steps...
twisteroid said:
You have to find the original FTF for the version you want (23.0.1.A.5.77), and either make or download a pre-rooted flashable.zip for that version. Then just follow the last part "Install latest firwmare with root, DRM keys, recovery" from the rooting guide again: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 .
Click to expand...
Click to collapse
Also, looking at that tutorial it doesn't seem to be necessary to have a rooted phone for that...
Why did I went then through the hassle of downgrading fw, gfrieroot hack and so on? *aaargh*
faxd said:
Also, looking at that tutorial it doesn't seem to be necessary to have a rooted phone for that...
Why did I went then through the hassle of downgrading fw, gfrieroot hack and so on? *aaargh*
Click to expand...
Click to collapse
Well, because you need a recovery to flash the pre-rooted zip, and to have a recovery you have to root first. The pre-rooted SYSTEM partition cannot be flashed using Flashtool because it would not pass signature check. The only way to flash it is to use root access and a working recovery.
Edit: and that reminds me, if you have root but no recovery yet, install NUT's dual recovery first.
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.
So I've tried to do my due diligence researching but as a noob a lot of this is very confusing. My main goal is to have verizon unlimited tethering (currently ota 5.0) I installed and ran Kingroot thinking I could just edit the system/build.prop file and be on my way, that doesn't appear to work. So anyways I was wondering if I buy sunshine unlock my bootloader would I need to buy mofo to enable use of TWRP or would the KingRoot temp root work for that? Don't have much money at the moment and am trying to see if I can just pay for the Sunshine. Any thoughts or help would be greatly appreciated?
Root with Kingroot and unlock with Sunshine. Mofo not needed. Install a recovery to your liking.
Sorry if this is really basic but I'm just really nervous about missing something. So I ran sunshine unlocked my bootloader and have root, installed busybox and TWRP. I'm currently on 5.0 verizon OTA and want to flash this stock rom http://forum.xda-developers.com/showpost.php?p=62785699&postcount=781 with G-apps. Don't I need to update my bootloader to 5.1? I'm assuming I do but most of the directions I've found are for doing that through mofo. Do you know where there is a bootloader img for 5.1 that I can flash through TWRP? Again sorry if this is really basic and thanks for any help. Also is there anything else I'm missing/forgetting that I would need to flash?
bengeo31 said:
Sorry if this is really basic but I'm just really nervous about missing something. So I ran sunshine unlocked my bootloader and have root, installed busybox and TWRP. I'm currently on 5.0 verizon OTA and want to flash this stock rom http://forum.xda-developers.com/showpost.php?p=62785699&postcount=781 with G-apps. Don't I need to update my bootloader to 5.1? I'm assuming I do but most of the directions I've found are for doing that through mofo. Do you know where there is a bootloader img for 5.1 that I can flash through TWRP? Again sorry if this is really basic and thanks for any help. Also is there anything else I'm missing/forgetting that I would need to flash?
Click to expand...
Click to collapse
You absolutely do not want to upload your partition table (the gpt.bin file). Your Sunshine unlock is based in part on the original partition table in your phone and you may/will lose root if you update to the 5.1 gpt.bin. The post you are referencing is to upgrade the first release of 5.1 to 5.1 with the stagefright patch. You need to follow the upgrade instructions in the first post of that thread to be on 5.1 v23.32-25-3 before using the info in post 781 to patch that version to 23.32-25-5.
The short version of the process is to download this file: 5.1bins.7z Extract the files from the archive and then use these commands:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
You will not flash the recovery.img file because you already have TWRP as your recovery.
After you do the above steps then select the option to go into recovery, when TWRP launches flash this file: xt1096-5.1-stock-20150820.zip After it flashes use the clear cache/dalvik button and then reboot the phone into 5.1 v23.32-25-3
Then you can use the instructions in post 781 to upgrade to 23.32-25-5, the current version. You have to do the first one, because the files in post 781 are patch files that only work with the -3 version. Clear as mud?
mikeoswego said:
You absolutely do not want to upload your bootloader (the gpt.bin file). Your Sunshine unlock is based in part on the original bootloader file in your phone and you will lose root if you update to the 5.1 bootloader. All the bootloader does is start up the phone, tell it to load the kernel and then it exits. It also handles fastboot flashing but there is no functional difference in the newer bootloader except to stop you from having root.
Click to expand...
Click to collapse
Are you absolutely certain about this? I'm under the impression that once your bootloader is unlocked root is a simple matter of installing TWRP and SUPERSU.
mbkintner said:
Are you absolutely certain about this? I'm under the impression that once your bootloader is unlocked root is a simple matter of installing TWRP and SUPERSU.
Click to expand...
Click to collapse
You're correct that your bootloader must be unlocked to install TWRP and SuperSU which is all that is needed for root.
Unless you've gotten an unlock code from Motorola, you paid money to get your bootloader unlocked. If you flash a new bootloader, the verification bypass that allows you to run TWRP will no longer work. If you fastboot flash the new bootloader before upgrading the rom you would lose root because you would no longer be able to use TWRP to flash SuperSU for the new ROM. If you waited to flash the bootloader after flashing the new ROM, you could keep root but still not have TWRP to flash future updates. IF there becomes a way to unlock the new bootloader, then you can pay again to unlock that one to regain the ability to run TWRP. I've never tried to go backward on bootloader versions, there seem to be a lot of warnings about bricking phones by doing that.
If you have an unlock code from Motorola, lucky you, don't worry about any of this.
bengeo31 said:
Don't I need to update my bootloader to 5.1?
Click to expand...
Click to collapse
You can run 5.1 ROMs and kernels while staying on the 5.0 bootloader and partition table.
mikeoswego said:
You're correct that your bootloader must be unlocked to install TWRP and SuperSU which is all that is needed for root.
Unless you've gotten an unlock code from Motorola, you paid money to get your bootloader unlocked. If you flash a new bootloader, the verification bypass that allows you to run TWRP will no longer work. If you fastboot flash the new bootloader before upgrading the rom you would lose root because you would no longer be able to use TWRP to flash SuperSU for the new ROM. If you waited to flash the bootloader after flashing the new ROM, you could keep root but still not have TWRP to flash future updates. IF there becomes a way to unlock the new bootloader, then you can pay again to unlock that one to regain the ability to run TWRP. I've never tried to go backward on bootloader versions, there seem to be a lot of warnings about bricking phones by doing that.
If you have an unlock code from Motorola, lucky you, don't worry about any of this.
Click to expand...
Click to collapse
I double checked with jcase and others in the official Sunshine thread and can confirm that upgrading to the latest release, to include your bootloader, will not cause your bootloader to relock. Sunshine is not a bootloader bypass, it is a permanent unlock. You will lose root but as stated, simply install TWRP and SuperSu to regain it.
Start reading here to see the discussion. http://forum.xda-developers.com/showthread.php?p=62893130
mbkintner said:
I double checked with jcase and others in the official Sunshine thread and can confirm that upgrading to the latest release, to include your bootloader, will not cause your bootloader to relock. Sunshine is not a bootloader bypass, it is a permanent unlock. You will lose root but as stated, simply install TWRP and SuperSu to regain it.
Start reading here to see the discussion. http://forum.xda-developers.com/showthread.php?p=62893130
Click to expand...
Click to collapse
Another bit of internet lore shot down. Thanks for the info!
Closed because of no webspace ... sorry!
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
Update: Newest kernel from (E5823_32.1.A.1.185 (central europe))
This version includes TWRP 3.0.2 and SuperSU-2.65
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
arhangel78ru said:
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
Click to expand...
Click to collapse
you need to have an unlocked bootloader!
DRM-keys will be lost, but functions can be restored with the DRM patch!
I added "the unlocked boot loader required" info to the first post.
Thorstenk said:
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
kernel that was used is: E5823_32.1.A.1.163 (central europe)
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
The kernel includes TWRP 3.0, just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
for root flash SuperSU-v2.71 (thats the only one that is working for me at the moment)
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
bro could you helpme I tried to use the script rootkernel but i always got rootkernel.sh not found aborting what i missing?
i have extracted kernel.elf in the same folder it contains the tools for rooting.
i want to know how to do this.
Thanks in advanced!
acabreram said:
bro could you helpme I tried to use the script rootkernel but i always got rootkernel.sh not found aborting what i missing?
i have extracted kernel.elf in the same folder it contains the tools for rooting.
i want to know how to do this.
Thanks in advanced!
Click to expand...
Click to collapse
In linux simply run
Code:
./rootkernel.sh kernel.elf boot.img
output should look like that:
Code:
./rootkernel.sh kernel.elf boot.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- Disabling dm-verity
- Disabling SONY RIC
- Adding tools
- Adding TWRP image
- Installing init script
- Renaming init to init.bin
- 64-bit platfrom detected
- Configuring keyprovd
- Configuring secd
- Installing library
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
kernel.elf is your original kernel extracted with flashtool, boot.img is your modified kernel that you can now flash using fastboot.
arhangel78ru said:
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
Click to expand...
Click to collapse
Now you can a backup of you TA Partition
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
Until now there is no way to get root on locked bootloaders.
Can I flash this over my Lollipop (rooted) rom, to get the newest official software?
(why is this such a smal file?)
BR
Sopur
Sopur said:
Can I flash this over my Lollipop (rooted) rom, to get the newest official software?
(why is this such a smal file?)
BR
Sopur
Click to expand...
Click to collapse
To get update throug OTA your bootloaders must be locked if not you can update with flashtool.
Thorstenk said:
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
kernel that was used is: E5823_32.1.A.1.163 (central europe)
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
The kernel includes TWRP 3.0, just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
for root flash SuperSU-v2.71 (thats the only one that is working for me at the moment)
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
is it possible to repack this boot.img with my own drm keys following tobias.waldvogel's guide in order to avoid flashing of DRM patch and thus using my own DRM keys?
albenex said:
is it possible to repack this boot.img with my own drm keys following tobias.waldvogel's guide in order to avoid flashing of DRM patch and thus using my own DRM keys?
Click to expand...
Click to collapse
Yes with the new tool versión!
Can someone explain it, pls?
ok, got it. ^^
So i currently have the E528 MM with androplus kernel and supersu 2.69, i assume that i need to re-flash the stock version through Flashtool and then flash this . Am i missing something? Do i have to re-lock my Bootloader when i flash back to stock or can i immediately dive in?
And is it me or....well i expected this file to be way heavier
DayMK said:
So i currently have the E528 MM with androplus kernel and supersu 2.69, i assume that i need to re-flash the stock version through Flashtool and then flash this . Am i missing something? Do i have to re-lock my Bootloader when i flash back to stock or can i immediately dive in?
And is it me or....well i expected this file to be way heavier
Click to expand...
Click to collapse
i´m not sure but i think it´s no necesary flash a clean intallation but it´s recomendable
if you have done a back up of your drm keys before unlock your bootloader this tool active fully again your drm
and no you don´t have to relock your bootloader, when you do a clean installation and you opened your bootloader this remaning opening and you can check on your dial *#*#7378423#*#* service test/Security
MARLIN [Key Ok] [Active] meaning your drm are Ok
Has anyone tried this yet? I really want to install this but i'm kind of scared....
Sent from my E5823 using XDA-Developers mobile app
DayMK said:
Has anyone tried this yet? I really want to install this but i'm kind of scared....
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
if yo do right things it works
At least working fine for me
Drm keys active & Root & xposed working
acabreram said:
if yo do right things it works
At least working fine for me
Drm keys active & Root & xposed working
Click to expand...
Click to collapse
Ok thanks for your answer, i think i'll do a clean install, re-flashing the international Australia and then flash this and supersu, wish me luck ?
Sent from my E5823 using XDA-Developers mobile app
DayMK said:
Ok thanks for your answer, i think i'll do a clean install, re-flashing the international Australia and then flash this and supersu, wish me luck ?
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
And here http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
It works pretty well, thanks!
Sent from my E5823 using XDA-Developers mobile app
Can I flash this, and I do not loose my data?
BR
Sopur
--