Related
Im taking my silver HTC One back because my camera is jacked up along with some signal issues. So im getting the black version But I need to return it back to stock. I'm guessing i start off by flashing my original nandroid back up. Im guessing next would be relocking the bootloader?
Mr.Muscles said:
Im taking my silver HTC One back because my camera is jacked up along with some signal issues. So im getting the black version But I need to return it back to stock. I'm guessing i start off by flashing my original nandroid back up. Im guessing next would be relocking the bootloader?
Click to expand...
Click to collapse
put it into fastboot, run the command prompt "fastboot oem lock" and then the bootloader should then say "relocked" and will still say "tampered" too, then run the RUU that OMJ has posted in the development thread and then you will be back to stock, your "tampered" flag will be gone but the "relocked" will still be present
make sure you have USB debugging on.
Download the AIO Tool Kit and extract. anywhere
Hasoons AIO Toolkit
Download the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM.zip and rename it to something short such as lol.zip(that's what I used, just rename it lol, not lol.zip, if you rename to lol.zip it will show up as lol.zip.zip.) and place it at the root of your c:/ drive, so c:/lol.zip
Navigate to the AIO toolkit folder you extracted, Open the One.exe. At the bottom, click reboot into bootloader and then do command.
Hold shift and right click then click Open Command Window Here.
when the command line opens up type
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip c:/lol.zip
If you get a message about flushing, then retype the last command, "fastboot flash zip c:/lol.zip"and it should work
Thank you so much guys. At work right now and will do as soon as I get home.
Will you still have the relocked if you do it this way? If you send a phone back that says relocked will sprint charge you or will they even notice.
youkosnake said:
make sure you have USB debugging on.
Download the AIO Tool Kit and extract. anywhere
Hasoons AIO Toolkit
Download the Sprint_HTC_One_m7wls_1.29.651.7_encrypted_ROM.zip and rename it to something short such as lol.zip(that's what I used, just rename it lol, not lol.zip, if you rename to lol.zip it will show up as lol.zip.zip.) and place it at the root of your c:/ drive, so c:/lol.zip
Navigate to the AIO toolkit folder you extracted, Open the One.exe. At the bottom, click reboot into bootloader and then do command.
Hold shift and right click then click Open Command Window Here.
when the command line opens up type
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip c:/lol.zip
If you get a message about flushing, then retype the last command, "fastboot flash zip c:/lol.zip"and it should work
Click to expand...
Click to collapse
toadkiller said:
Will you still have the relocked if you do it this way? If you send a phone back that says relocked will sprint charge you or will they even notice.
Click to expand...
Click to collapse
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones
Yeah mine is going back because of the speakers, they crackle. The replacement doesnt. Oh well Ill see what happens.
LymeWire said:
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones
Click to expand...
Click to collapse
LymeWire said:
yes it will still say relocked in the bootloader but most of the time sprint doesnt look unless you are returning it bc its defective, if you are returning it just to return it and will pay the $35 restocking fee then they shouldnt look, i never do and im a tech who deals with the returned phones
Click to expand...
Click to collapse
I couldn't get it to stock so I said f it. I hope they don't look at it. I'm sure I'll be paying for it later though.
Sent from my HTCONE using xda app-developers app
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Welcome to the club!
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
https://www.xda-developers.com/motorola-moto-g7-plus-t-mobile/
It has NFC and B71 which G7 doesn't have.
Hopefully bootloader will be unlockable. If so, I may get one and paid in full and have it SIM unlocked, and flash RETAIL ROM
Any update on this? Been holding out on upgrading for this if it's true
If this is right it could be the revvl 3 or 3 plus as product sku is tmo revvl this is from wifi alliance
It's the g7 plus and g7 play https://www.tmonews.com/2019/07/t-mobile-revvlry-official-specs-price/
Can we root it using g7 plus method and unlock bootloader same way I currently have the phone
You can try to get bootloader unlock code it won't hurt nothing but as far as rooting I don't know but should be the same
krazy_smokezalot said:
Can we root it using g7 plus method and unlock bootloader same way I currently have the phone
Click to expand...
Click to collapse
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.
Jleeblanch said:
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.
Click to expand...
Click to collapse
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola
krazy_smokezalot said:
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola
Click to expand...
Click to collapse
Knowing they (as in T-Mo) doesn't offer codes, which I figured they didn't, then I'd at least try to paste your unlock code on Moto's site. Worst that'll happen is a message will pop up saying you device doesn't qualify.
t mobile g7 plus bootloader unlock
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.
REVVLRY+ is indeed G7 plus
Jimhackthorn said:
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should0 all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.
Click to expand...
Click to collapse
Ok I'll try it cause it got it for free and it's paid off. Got it from my job as a gift. So I'll definitely check it out then I'm even more interested. But I kinda doubt it cause the bootloader has the name revvl in it in CPU Z. Bootloader goes by MBM-3.0lake_revvl-43c7c77-190517
Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone
unlock instructions
krazy_smokezalot said:
Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone
Click to expand...
Click to collapse
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.
Jimhackthorn said:
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.
Click to expand...
Click to collapse
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings
krazy_smokezalot said:
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings
Click to expand...
Click to collapse
This is a common method to unlock Motorola smartphone bootloader.
Hopefully you will be lucky to get the code, but you may wait up to 2 weeks after initial release.
I can confirm that Motorola will give you the unlock code.
Findings
UNLOCKING AND LOCKING BOOTLOADER WILL WIPE YOUR DEVICE> BACKUP PERSONAL DATA IF YOU WANT TO KEEP IT.
I unlocked the bootloader and flashed the moto G7 plus RETAIL firmware. Everything worked fine except google pay, and verity being disabled.
Installing TWRP would always give me a recovery boot loop, so I stopped trying, instead just booting into TWRP with fastboot.
I cannot get verity enabled, even after flashing stock and locking the bootloader, so that means no Google Pay, no Google Fi, no whatever else requires verity.
Looking at
Code:
fastboot getvar all
Shows a flag that verity is disabled and another flag that warranty is void, even after flashing stock.
The stock firmware I found in a firmware repo, because I failed to do a full backup of my system (I only backed up boot, system, and data).
Would anyone be willing to unlock their bootloader, boot into TWRP, do a full backup, and share it, to see if I can get back to stock with verity enabled? I'd love Google Pay back.
BanterJSmoke said:
I can confirm that Motorola will give you the unlock code.
Click to expand...
Click to collapse
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown
mingkee said:
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown
Click to expand...
Click to collapse
Except it's nearly $100 less expensive to just buy an unlocked g7+
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 DisabledFor 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 DisabledFor 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