Hey guys I'm so bummed.
So I unlocked my phone with Sunshine some time ago. Verizon recently pushed the marshmallow update to my droid turbo original. All good no problems. Anyways I'm now returning it to Verizon but I wanted to lock the bootloader first.
So I locked the bootloader with fastboot then rebooted the phone and got the pink failed to validate system image.
I had a freak out and so I tried to flash a stock rom (after locking the bootloader). I saw some messages saying downgrading. which makes sense because I used this:
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
which I assume is old.
I got a lot of fail messages as I was flashing. And since the bootloader is locked, I don't see how this could work anyways.
I have two days before my new phone arrives and I have to send this back. How screwed am I?
Any help would be ridiculously appreciated.
Related
I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader
yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)
Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
vapor100LL said:
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
Click to expand...
Click to collapse
There was absolutely no reason whatsoever to "relock" your bootloader. In fact, it was very foolish to do this.
Glad you got it solved, but for future reference, there IS NO REASON TO EVER RE-LOCK THE BOOTLOADER.
Having an unlocked BL does NOT prevent you from taking OTAs.
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
droidfun1 said:
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
Click to expand...
Click to collapse
This might not work with a locked bootloader, but you can give it a shot.
Download the boot logo from this thread that looks like the original one: https://forum.xda-developers.com/mo...o-maxx-droid-turbo-x-style-logos-bin-t3407046
Double click on the .exe file while your phone is in bootloader mode and plugged into your computer.
Thanks ya, I have seen that logo fix floating around for the Droid Turbo but I didn't want to try until I had at least one confirmation that it could work on a relocked bootloader. Anyone have a guess/idea/or success story?
Hey guys, so my mom was using the Turbo yesterday when she was prompted to an update. Now according to a few searches there was a soak test out or something? Not sure, since I have the Turbo 2. But regardless, she went to apply the update and now that phone won't boot up. It lights up with the M logo screen and then goes to andy where he's got the rotating box in his belly, and underneath it says "Erasing...". I can't get to any of the other options from the screen where you hold Volume Down while powering up. All of the options lead to the same erasing screen. The phone will reboot after two or three minutes and go back to the same thing. Been doing this for hours. I have it sitting on a charger and will take a look at it when I come back from work but I'm wondering how to remedy this? I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use. Not familiar with ADB so if that's the route I have to go, I'd appreciate a write up on how to use it. Willing to install custom firmware if I have to as well. I just need to get the phone working asap. My mom works nights and she is currently phoneless, so this is a safety concern of mine.
Also that screen where you hold Volume Down, it says battery okay and all that but it says the phone software is modified. Not sure why, I know that she completely incapable of doing that. And I didn't modify anything when I had the phone. Not that is matters though, it's out of warranty so Verizon or Moto probably won't be too useful.
Any and all help appreciated. Currently not in the position to buy a new phone so I'd prefer fixing this one up if I can. Thanks!
Xelios029 said:
I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use.
Click to expand...
Click to collapse
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Never, which is why I'm confused why it says software status modified. The sunshine and mofo mods were released after I upgraded to the turbo 2 so I never even had a chance. But thank you though! Really appreciate it, I was scared that some part of the memory had failed or something. My only question from here is how do I get the phone into the mode to required to RSD it? Because even if I select the bootloader option from that screen where you hold volume down while powering up, it goes to that erasing screen no matter what.
EDIT: Got home from work and downloaded all the files. RSD 6.1.5, Motorola Device Manager for the drivers, and the FXZ file. No dice. It won't recognize the device in RSD even though windows is making that sound when a device is connected. No luck on RSDLite 6.2.4 either.
EDIT2: Okay ugh, now I don't know what to do. Turns out RSD didnt detect it because the cable was not directly plugged into the motherboard. Took me a while to figure that out. So I got it detected and I flashed that file you put above and I'm still having the same problem. It reboots once everything is finished flashing and then goes back to the "Erasing..." screen.
EDIT3: SUCCESS!!! Thank you so much! I swear I was thinking I was going to have to replace the phone. Let it sit at the Erasing screen after flashing it for a bit and it eventually rebooted itself and started the Droid splash screen. What a huge relief! Hopefully these updates help with someone else who may run into the same problem.
Glad it worked for you!
And it helped you were persistent.
ChazzMatt said:
Glad it worked for you!
And it helped you were persistent.
Click to expand...
Click to collapse
Thanks again, much appreciated!
ChazzMatt said:
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Click to expand...
Click to collapse
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
KARIM9377 said:
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You have to ask them. I don't know. But we've been surprised before by their talent.
ChazzMatt said:
you have to ask them. I don't know. But we've been stories surprised before by their talent.
Click to expand...
Click to collapse
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
KARIM9377 said:
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
Click to expand...
Click to collapse
Every time Sunshine released an update to force unlock the Droid Turbo bootloader, Verizon releases an OTA "security update" to block it.
This next rant is not towards you but to other longtime Droid Turbo owners... (Like anyone who has owned a Droid Turbo for over two months. Anywhere from 2 months - 2 years.)
People just need to UNLOCK their bootloaders before taking any updates. NEVER, NEVER, NEVER take an OTA update. If there's anything worthwhile it will be posted HERE on XDA and you can flash it manually. Just unlock your bootloader and you don't have to worry about Verizon "blocking" Sunshine because your bootloader will already be unlocked!
ALright, my previous m7 is sitting dead in forever bootloops... it's on the back burner until further notice.
so i got another one. stock all around. used. took the OTA for latest firmware and radios, exactly the same revision as the previous m7....
unlocked bootloader, flashed twrp, flashed good old cm11. worked good for a few weeks.
then i decided to try lineage 14/15. cm13, back and forth, over and a bout...
then running stabile in lineage14.1, i noticed i couldnt' make phone calls.
so i flashed back to cm11, LTE/4g shows up, data is good, but cannot make calls, cannot receive calls, same with text messages.
flashed back to the stock nandroid that the phone came with, same thing! only data, no voice/text.
so, in attempt to bring it back in for repair, i needed to relock the bootloader.
that's where it went ugly. it said relocked, tampered, and security warning, and i was unable to boot into anything else.
luckily i kept the unlock token ,and reissued an unlock, and it would let me boot into the rom again and the recovery, but i don't want to attempt to continue the RUU until i know exactly what steps are required.
i read the bootloader must be relocked before RUU, i also read if i was stuck where i was, in fastboot mode the RUU would still work, which it didnt..
help please!
thanks
Well, no one replied in time.
Asurion said it was covered under manufactures warranty. Zero deductible and a new HTC 10. And the old m7 was accepted tampered /unlocked.
Sent from my 2PS64 using Tapatalk
Wow, nice. I tried to help, but you got outside of my knowledge level. I'm really glad you got a 10. It's a really nice device.