Related
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
First check here... http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Get the sdk tools and once set up, see if you can do adb devices and have the phone show up on the PC, if so, do adb push (name of rom file) then boot to twrp and install. If that doesn't work, check the same page above (since you don't have an OS not sure what would happen) try the unlock instructions for fastboot ( I would wait for someone else to comment before trying this). You might want to message this user http://forum.xda-developers.com/member.php?u=2872010 rootSU and see if he can give guidance, he has lots of experience.
Locked Bootloader
I still can't seem to get past the fact that my bootloader is locked...
Thanks though.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexu...tboot-t3066052.
Flashing
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
SidedX said:
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
Click to expand...
Click to collapse
Sorry my bad, here it is http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Follow the instructions as i posted, place the download rom in the /android-sdk/platform-tools/ folder and boot in bootloader and select recovery, select adb sideload there and type in cmd: adb sideload name.zip.
Unlocked Bootloader
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
SidedX said:
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
Click to expand...
Click to collapse
It worked for other users, but hey if you have a better option try that.
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
SidedX said:
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
Click to expand...
Click to collapse
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Thanks
I see, I was able to adb push /sdcard/. a factory image to get back in with a locked bootloader, thank you.
gee2012 said:
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Click to expand...
Click to collapse
hallelujah!
cam30era said:
hallelujah!
Click to expand...
Click to collapse
That covered the spiritual moment of the day
Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.
May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095
I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.
Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095
Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?
Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..
The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png
Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.
Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!
brockwitting said:
Hey XDA,
I was rooted, unlocked and TWRP'd on I think 6.4? I realized I wanted to go back to locked and stock after seeing some of the security stuff come out. I used SPFT to flash the 6.1 Prime Rom, and everything was working great. Phone booted no problem, and seemed to work fine. I then tried to use the Wireless Update to update the phone. It looked liked it downloaded fine, but now I'm in a reboot loop, and recovery does absolutely nothing but reboot loop as well. I CAN get the phone into Fastboot mode, but fastboot flash recovery gives me a "failed to get permission" error.
I ran a getvar all, and here is what I have:
unlocked: yes
secure: yes
kernel 1k
bootloader: version-preloader 0.0.00
Version: 0.5
I've tried the SPFT tools again, but it gives me ERROR: S_BROM_DOWNLOAD_DA_FAIL.
ANY clue what I can try next to just get the dang thing to be bootable? I don't care root or recovery or what, I just want a working phone, and I'm running out of ideas.
Thanks!
Click to expand...
Click to collapse
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.
You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.
brockwitting said:
You rock. I thought since it said unlocked I didn't need to do it again, but that did the trick. Now I just need to figure out what to do with the phone. I wouldn't mind keeping root, but I want the B12 update.
Click to expand...
Click to collapse
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241
kal250 said:
Here...
http://forum.xda-developers.com/r1-...om-6-5-flashed-via-twrp-t3455532/post68543624
Though if you have already updated, you're probably stuck, unless the dirtycow hack still works with newest OTA....
http://forum.xda-developers.com/r1-...irtycowed-f-amazon-root-t3490882/post69387241
Click to expand...
Click to collapse
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?
mrmazak said:
The dirtycow thing was only needed to get to the unlocked point. He is already there, so his only issue should be the lack of sp flash tool. Until/ if he does the bootloader rollback.
Shouldn't be problem with the modded v7 to roll back either.
Because in order to install the modded version , you need to be unlocked and twrp anyway, right.?
Click to expand...
Click to collapse
Yes.... See what happens when you loose your R1, I'm out of touch lol.... I do miss the phone.....
mrmazak said:
don't panic. everything is as is should be in your situation.
you see when you did getvar all , it said
secure: yes.
that means it only wants to boot signed and secured partitions. Just get into fastboot and do "oem unlock".
you really cant (safely) relock the bootloader. If your boot loader was relock now, you wold be in a perminent boot loop condition not able to recover.
But you can save it with "oem unlock" from where you at now.
Click to expand...
Click to collapse
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?
kfn said:
I presume he flashed factory original 6.1 from Colton's site.
I thought flashing original rom with SPFT should result in safely relocked bootloader, why not?
What if he relocked bootloader with 'fastboot oem relock' command after flashing 6.1 but before taking 7.4.2 OTA update? This would also leave him with:
unlocked: yes
secure: yes?
There must be some way to bring phone to original factory state with bootloader locked (meaning unlocked: no secure: yes).
BLU support also cannot do this?
Click to expand...
Click to collapse
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly
mrmazak said:
There is and I did it few times while testing my unlock script. Bit the chances of making a brick were so very high I cannot recommend doing it.
There are two other partitions that store the unlock state and they need to restored to really relock bootloader.
OEM relock does not work properly
Click to expand...
Click to collapse
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled back booloader, installed 6.1 from ColtonDRG site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this
kfn said:
Can you tell what steps you did to relock?
I really want to bring device to original factory state because encryption does not work when bootloader is unlocked. I did first dirty cow method on original 6.6 ROM (one with newer preloader), then rolled booloader, installed 6.1 from Coltron site with SPFT and finally installed vampireinfo's 7.4.2 thru TWRP.
However when I encrypted phone, in settings it says encrypted but I can browse device on PC without entering PIN.
On factory state encrypted device (with locked bootloader) I was not able to this
Click to expand...
Click to collapse
This will brick your phone, if you are not careful, and also if you are carefull. You can browse for help in encryption with unlocked bootloader before doing this, I'm sure there is a solution.
If you replace Seccfg.bin and Secro.bin from a backup from before unlocking bootloader you should be set to locked but I do not know of your phone will boot. You will be doing g that at your own risk.
But if you download the repair solution under the hidden tag(click to show content) in the roll back thread.
In that file it will restore you to 6.1 and it will be locked bootloader. I do not know about keeping v7 and relocked
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening