Related
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
rootSU said:
You could read the guide in general (sticky thread) which answers all these questions
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Android.Addiction said:
Thanks, however the guide seems to use a separate flash step to reset tamper, I was specifically interested in using the app instead if possible.
Click to expand...
Click to collapse
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Aerowinder said:
Your steps look good to me. There are a couple ways to flash the stock firmware, make sure your userdata gets wiped. You could also go into stock recovery when you're finished and factory reset.
Click to expand...
Click to collapse
So far I've just been running the steps inside ./flash-all.sh manually:
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-kot49h.zip
I can add this extra step before the above commands if needed:
fastboot erase userdata
Thanks man!
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Lanchon said:
for the record: don't do this! it DANGEROUS to oem-lock without a working stock recovery corresponding to your bootloader version! its not mentioned often, but fastboot oem unlock uses the stock recovery to do the wipe plus unlock. this means: no stock recovery, no unlock!
yes, you can manually unlock THIS DEVICE because we know how to, IF YOU CAN BOOT AND BE ROOT. if you cant get root from android or recovery (say, recovery doesnt boot and android is not rooted) then you CANT UNLOCK EVER AGAIN.
Click to expand...
Click to collapse
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
The steps the last guy quoted did flash factory images before locking.
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
rootSU said:
The steps the last guy quoted did flash factory images before locking.
Click to expand...
Click to collapse
lol yes he did, sorry! i thought he run the toggle-lock/reset-tamper script. my bad.
EddyOS said:
Yeah, but the guy I was quoting was on about the issues present in the OPO where there are issues with the bootloader getting stuck locked if not using a stock recovery
Click to expand...
Click to collapse
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
rootSU said:
Sorry, to clarify -
Poster 1 - Outlines correct steps
Poster 2 - Don't do this this it's dangerous
You - yeah but its not dangerous. You're thinking of opo
Me - Actually the steps highlighted originally are correct and would work even on Opo!
Click to expand...
Click to collapse
In a nutshell, although the guide in my signature covers all bases with the OPO as I wrote it when I had one!
EddyOS said:
It's not the same as the OPO, but I'd agree that it's best to get to stock first then relock using the script as opposed to an app
Click to expand...
Click to collapse
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Android.Addiction said:
I'm returning my Nexus 5 for replacement and I was going to do the following:
- boot into Android and run BootUnlocker to reset Tamper flag
- Go to bootloader, use fastboot to flash factory images
- fastboot oem lock
Would this put the phone in factory state, without triggering tamper flag? I'm worried about step 2... would flashing factory images trip the tamper flag?
Click to expand...
Click to collapse
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Lanchon said:
what makes you think its not the same? any source to that info? i have a nexus 5 with me here, and i remember that fastboot oem unlock ran something that looked liked a recovery. do you mean to tell me that the bootloader has its own independent recovery image built into part of its partition to boot to and do the unlocking? because otherwise i dont see how it would do it. please explain.
Click to expand...
Click to collapse
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
all N5 have tamper flag. it was introduced mid life of the N4 via a bootloader upgrade. i had an N4 at the time and thought that move was sh*tty.
gee2012 said:
Just reflash a factory image in fastboot with the`flash-all`command in cmd and relock the bootloader afterwards and its completely stock. Nexus 5 doesn`t have a tamper flag afaik anyway.
Click to expand...
Click to collapse
Yes it does
EddyOS said:
Yes it does
Click to expand...
Click to collapse
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
EddyOS said:
What I mean is there's an issue with the OPO where you relock the bootloader without the stock recovery and you then can't unlock it again. It's not been documented that the same fault happens in the Nexus range, but if the OP follows the guides available on here it'll all be OK
Click to expand...
Click to collapse
yes, we've established the steps are ok and it was my misreading.
but regarding my warning about locking with non working stock recovery: its not been documented, but im sure it happens all the same! the bootloader uses a recovery (presumably the one recovery we know and not an image embedded in the bootloader itself) to wipe data. and it would be a mistake to unlock before wiping. so the bootloader does the wipe-then-unlock by delegating everything to the recovery. no recovery, no unlock.
gee2012 said:
Where can you see it? Not in the bootloader menu as i see. So its reset tampered flag (BootUnlocker), flash the factory image and afterwards lock the bootloader in fastbooot?
Click to expand...
Click to collapse
When connected in fastboot, type
fastboot oem device-info
And it'll show device tampered true or false
To get it all back to stock, flash the factory image completely then boot TWRP (don't flash it) and run the bootunlocker script found in the Nexus 5 unroot thread
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
zephiK said:
Did you type fastboot oem unlock?
Your bootloader is locked and needs to be unlocked.
If fastboot oem unlock does not unlock it, then you need to fastboot boot into recovery.
Flash tamper, unlock, and then afterwords, adb sideload SuperSU.
Click to expand...
Click to collapse
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Yeah, I'm in the same boat as you. Unfortunately after all my reading, it seems impossible as CM did it as a preventative measure to secure your data.
I'm going to do a back up of everything and then a reflash to 25R where battery life was best, then unlock and reboot.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
Well thats the whole point, the OnePlus One is a very developer friendly phone indeed. Thats why you get the "keys" to unlock the phone with a simple command instead of using a exploit to flash a custom recovery.
On 25R bootloader, it was possible but as of now there isn't a way to root without unlocking the bootloader. You can read the thread here, http://forum.xda-developers.com/oneplus-one/help/root-unlocking-bootloader-t2820628
This is why when people just now get a phone that has the ability to fastboot oem unlock, I suggest them to unlock their bootloaders as the first thing to do.
Backup all of your data and move forward. Best of luck.
therightperson_630 said:
Umm thanks, I could have, but I really don't want to wipe everything, I got everything set up how I want with lots of data..I was looking for a way *without* wiping everything.. fastboot oem unlock will be my last resort tbh.
I thought with such a developer friendly phone there might be a way to overcome this problem
Click to expand...
Click to collapse
if you truly want to restore everything there are apps that will zip up all your data and you can flash in one session after wiping your phone. If you are reloading the exact same software it should not be an issue. check google and playstore for such apps like app2zip
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
therightperson_630 said:
app2zip requires root, which I can't get if I've not unlocked the bootloader, which means wiping everything...app2zip won't help here but thanks for the suggestion
Click to expand...
Click to collapse
oh yea my bad I forgot about the root part. I usually root right away so my bad..
Sorry, but the only way is to unlock the bootloader. You could use Helium backup, also some Apps themselves have great backup functionality.
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
timmaaa said:
Yep. Gotta unlock it. No idea why people don't just do that in the first place.
Transmitted via Bacon
Click to expand...
Click to collapse
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
therightperson_630 said:
Because most people set up their phone before getting stuck into rooting and the like. Just as I did. I think locking the bootloader is good in theory, but the average user wouldn't know how to brick their phone even if the bootloader was already unlocked, so why do it?
Click to expand...
Click to collapse
The difference between having a locked and unlocked bootloader is simply flashing custom recoveries or radios/etc. Theres no harm in doing leaving your bootloader unlocked.
The bootloader has to be locked out of the box, I believe its one of the criterias needed to be fulfilled in order to be approved for Google Apps (Play Store,etc). Also, it doesn't make sense to have a bootloader unlocked for average users.
Just unlock the bootloader and learn from your lesson.... either that or stick with stock ROM without root. Yeah it'll set you back because you'll have to redo your phone apps/settings but on the bright side you won't have to do it again because ur bootloader is already unlocked.
You need your bootloader unlocked to obtain root. See http://forum.xda-developers.com/showthread.php?t=2788632 on instructions on how to do so if you're unfamiliar. After once its unlocked, fastboot flash a custom recovery and flash supersu.
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
therightperson_630 said:
Trust me I'm familiar...had none of this trouble on the G1. Out of 5 android devices this is the second time I've had to unlock the bootloader...and the average user doesn't even know what a bootloader is, so not sure they'd be able to mess about with the radios.
Click to expand...
Click to collapse
Thats because the G1 had a locked bootloader and the only way to flash a custom recovery was to gain a exploit to push a custom recovery. For the OnePlus/Nexus/HTC, we don't need a exploit because we have the ability to unlock our bootloaders. Think of it as Apple's iOS, in order to gain jailbreak you need a exploit to jailbreak your phone which can take a long time for it to happen. Whereas, on Nexus/OnePlus/HTC, we can simply just obtain access to do changes to the phone without having to wait for a exploit.
You keep mentioning average user but a average user wouldn't be attempting to obtain root access for their phone. The average user would just be using his/her phone as a phone and not tinkering with the deeper innings of the Operating System and if the average user wants to tinker with the deeper innings then they should really do their research and learn. There are a lot of good guides on XDA.
Couldn't agree more. There is no need for any exploit with this phone because you've been handed the keys.
Transmitted via Bacon
therightperson_630 said:
Hello,
trying to get root by unlocking the bootloader first (using preload recovery TWRP lastest + tamper bit mod) but I keep getting this error:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.406s
So I can't preload the custom recovery, is there any way of rooting on this oneplus firmware without wiping the whole device?
Any help would be much appreciated..
Edit: This isn't a reroot, this is first time root/unlock
Click to expand...
Click to collapse
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
ondoy1943 said:
have you considered the exploit devised in the following thread?:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
But then again,
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to fastboot oem unlock command.
Click to expand...
Click to collapse
A little off topic but I unlock my boot loader and root as soon as I get the phone so I don't have to loose anything.
zephiK said:
That doesn't allow you to root while having a unlocked bootloader. It just changes the bits on whether or not your device has been tampered.
Click to expand...
Click to collapse
that's what you think, but in my case i was able to unlock the bootloader using the mod, hence rooting was a matter of course. the casual "fastboot oem unlock" command was not effective with my device. so.....
edit: then again, i unlocked the bootloader and rooted my phone while it was still at 30O firmware. i have no idea if the 33R firmware's bootloader is different from that of the 30O or not, that will render the mod ineffective.
It's fine, problem solved, went through the gruelling task of trying to back everything up without root = 40gb of stuff..
Already tried the tamper bit mod...it was stated in the first post (tamper bit mod) and the command screenshot was one of the steps when trying to boot the recovery, it still wouldn't boot because the bootloader wasn't unlocked..so, useless in my case.
Still lost some stuff but I got most of it back. I didn't have this problem on my xperia SP when unlocking the bootloader..if I remember correctly you could root, get recovery and custom rom all without unlocking bootloader. Unlocking the bootloader didn't erase the internal sd either..sure it might have been through an exploit rather than the proper way, but tbh I think I'd rather have that.
I'm not liking this "you've been given the keys" analogy...It's more like you've already settled into your new house and you're given the keys to unlock the front door when you're already inside...it's hassle more than anything.
Like the title says. Im selling my N5 to someone and they don't want cm11s. If i flash back to my stock+root+unlocked bootloader, then factory reset to wipe all my data will they be able to get the OTA? I dont care if the bootloader is still unlocked i just want them to get updates.
Thanks for all the help guys
prophet of doom said:
Like the title says. Im selling my N5 to someone and they don't want cm11s. If i flash back to my stock+root+unlocked bootloader, then factory reset to wipe all my data will they be able to get the OTA? I dont care if the bootloader is still unlocked i just want them to get updates.
Thanks for all the help guys
Click to expand...
Click to collapse
Flash a system image.. It'll wipe phone too..all in 1 easy step. Stock kernel, system and recovery when finished...Boot loader unlock I don't think matters.
prophet of doom said:
Like the title says. Im selling my N5 to someone and they don't want cm11s. If i flash back to my stock+root+unlocked bootloader, then factory reset to wipe all my data will they be able to get the OTA? I dont care if the bootloader is still unlocked i just want them to get updates.
Thanks for all the help guys
Click to expand...
Click to collapse
Yes, as long as you don't make any changes to /system you will still receive OTAs.
_MetalHead_ said:
Yes, as long as you don't make any changes to /system you will still receive OTAs.
Click to expand...
Click to collapse
thanks guys but i came across a great video on how to unroot and lock the bootloader.
Please post questions in the Q&A section
Thread moved
Hello,
Is it possible to Root my Sony Xperia Z3 D6603 which is currently running Android 5.0.2 without losing the DRM keys?
I don't want to have to roll back to 4.4.4, or lose any of my files.
I have a pretty slow internet so i'm not a big fan of downloading stuff, I'm just psyched to check out Xposed if it exists.
No, you must roll back to a FW ending in .93 which is KK, then root, then install recovery, then update via a pre-rooted flashable zip
I would not hold my breath for a lollipop exploit. The main reason to find one has gone (i.e there already is a way to get root on lollipop with a locked bootloader)
Hussain_Salam said:
Hello,
Is it possible to Root my Sony Xperia Z3 D6603 which is currently running Android 5.0.2 without losing the DRM keys?
I don't want to have to roll back to 4.4.4, or lose any of my files.
I have a pretty slow internet so i'm not a big fan of downloading stuff, I'm just psyched to check out Xposed if it exists.
Click to expand...
Click to collapse
rooting has nothing to do with the DRM keys
you have to downgrade.
you will lose your data.
you have to download a kitkat stock rom.
No way around this if you want root.
android404 said:
rooting has nothing to do with the DRM keys
Click to expand...
Click to collapse
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
you will lose your data.
Click to expand...
Click to collapse
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
gregbradley said:
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
Click to expand...
Click to collapse
Of course... Thanks for correcting me.
gregbradley said:
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
Click to expand...
Click to collapse
But why revert if he is unlocking?
If he is unlocking he can flash a kernel with recovery and root via TWRP.
Before back up TA.
And after restore the DRM keys.
Easy.
TheTeslaCoil said:
But why revert if he is unlocking?
If he is unlocking he can flash a kernel with recovery and root via TWRP.
Click to expand...
Click to collapse
Please read the OP, he does not want to lose DRM keys, hence he needs to root without unlocking the bootloader first.
Also, if you have a custom kernel installed you cannot have DRM keys running, once you restore them using a TA partition restore you relock the bootloader and cannot boot on a custom kernel.
gregbradley said:
Please read the OP, he does not want to lose DRM keys, hence he needs to root without unlocking the bootloader first.
Also, if you have a custom kernel installed you cannot have DRM keys running, once you restore them using a TA partition restore you relock the bootloader and cannot boot on a custom kernel.
Click to expand...
Click to collapse
The DRM can be restored.
I rest my case.
TheTeslaCoil said:
The DRM can be restored.
I rest my case.
Click to expand...
Click to collapse
sigh,,,
No they cannot unless you have taken a backup before unlocking the bootloader.
There is a thread about restoring some functionality but it does not restore to 100% stock compared to when people have a stock ROM with DRM keys installed, and like I said, READ THE OP, he asked for a way not to lose his DRM keys, not to have the functions associated with them.
If you unlock without backing them up, you cannot restore them, FACT!
I really do not want to get into an online fracas with you, but this is the second time today you are jumping in and not giving exactly 100% correct answers to the questions asked.
android404 said:
Of course... Thanks for correcting me.
Click to expand...
Click to collapse
No worries
gregbradley said:
sigh,,,
No they cannot unless you have taken a backup before unlocking the bootloader.
There is a thread about restoring some functionality but it does not restore to 100% stock compared to when people have a stock ROM with DRM keys installed, and like I said, READ THE OP, he asked for a way not to lose his DRM keys, not to have the functions associated with them.
If you unlock without backing them up, you cannot restore them, FACT!
I really do not want to get into an online fracas with you, but this is the second time today you are jumping in and not giving exactly 100% correct answers to the questions asked.
Click to expand...
Click to collapse
But I already said, if you back up TA.
Check again.
And you appear to be a person that doesn' t like to be contradicted.
So...see you later.
TheTeslaCoil said:
But I already said, if you back up TA.
Check again.
And you appear to be a person that doesn' t like to be contradicted.
So...see you later.
Click to expand...
Click to collapse
Please tell the user how to back up his TA then without rooting first...
You need to back it up before unlocking the bootloader and you need root to back it up....
From now on I think me and you should only talk via PM.
Regards.
Root, backup TA. Save it on your laptop.
Unlock bootloader.
Enjoy a rooted unlocked device with endless possibilities.
If you ever want to have your phone as it was when you bought it, restore TA, unroot etc.
Easy peasy japanesey.
TheTeslaCoil said:
Root, backup TA. Save it on your laptop.
Unlock bootloader.
Enjoy a rooted unlocked device with endless possibilities.
If you ever want to have your phone as it was when you bought it, restore TA, unroot etc.
Easy peasy japanesey.
Click to expand...
Click to collapse
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
gregbradley said:
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
Click to expand...
Click to collapse
Just to follow up with this discussion. I am currently on a locked bootloader but rooted and installed recovery using the method mentioned in the other thread. How can I back up my TA partition? I can't find a tutorial link on TA partition backup.
mf1tym said:
Just to follow up with this discussion. I am currently on a locked bootloader but rooted and installed recovery using the method mentioned in the other thread. How can I back up my TA partition? I can't find a tutorial link on TA partition backup.
Click to expand...
Click to collapse
You have already done the "hard" part. Do some reading on this thread http://forum.xda-developers.com/showthread.php?t=2292598 ,will be short , download zip within OP ,extract and run. After you created backup store it safely I think I have mine on 4 locations (cloud and local) although I doubt I will be unlocking bootloader anytime soon.
gregbradley said:
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
Click to expand...
Click to collapse
I said backup TA.
So...I' m right.
schetz said:
You have already done the "hard" part. Do some reading on this thread http://forum.xda-developers.com/showthread.php?t=2292598 ,will be short , download zip within OP ,extract and run. After you created backup store it safely I think I have mine on 4 locations (cloud and local) although I doubt I will be unlocking bootloader anytime soon.
Click to expand...
Click to collapse
Schetz, thanks mate. I saw this link before. It said it's unmaintained and the devices capatable is only to Z2 so I thought it did not work on the Z3. But I will re-read it again.
TheTeslaCoil said:
I said backup TA.
So...I' m right.
Click to expand...
Click to collapse
You said to root by unlocking the bootloader first, then backup the TA so you are wrong. Editing your post after the fact does not change this, adding the line "Before backup TA" does not make you correct as you have to root to backup the TA.. so when you say "why revert when he can just unlock", that's why.
And finally, restoring the DRM keys after unlocking means you get a locked bootloader, so you cannot boot a custom kernel so you lose root...
The point is now moot, and you need to remember my advice on this, keep it in PM's
If you're asking if we have Marshmallow, yes we do, in the form of Resurrection Remix 6 (WIP) and CM13 (WIP).
You said with locked bootloader it doesn't boot. Did you mean UNLocked bootloader? When you unlocked your bootloader, did you install TWRP?
When you installed TWRP did you wipe EVERYTHING?
If wiped everything then you have no ROM to boot. (You should have done a factory re-set instead.)
You have to go back into TWRP and drag over a ROM from your computer... install that in TWRP and then it will boot.
I'm only guessing at what you did, so that's my best answer.
_______
Oh, wait, looking at your other posts, you're the guy who re-locked his Droid Turbo bootloader and bricked it:
http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081
So, that's your issue. Still not sure why you did that. You paid for Sunshine, it was a one-time deal, can't be done again, and you still re-locked your bootloader. An unlocked bootloader is FREEDOM. You can screw up and still recover from mistakes. A locked bootloader is slavery, and if you mess up, much harder -- sometimes impossible -- to recover from mistakes...
IF that's still your issue, the only thing you can try to do is re-install stock 5.1 Droid Turbo Lollipop image via fastboot. Good luck.
This post by @TheSt33v in the other thread where you posted gave you the only possible answer. If you have TWRP still installed you have to overwrite everything, including the recovery partition. But you have to follow the steps exactly.
http://forum.xda-developers.com/showpost.php?p=65095391&postcount=5
TheSt33v said:
With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader.
See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse