Hi All,
I have a non-DE XT1060 with an unlocked bootloader. I am attempting to flash a custom recovery, but I am running into issues. When I go into fastboot, it shows the device is indeed unlocked, but says Status Code: 3, where it would normally say Status Code: 1.
I am guessing this is part of my issue, since when I run the command ADB DEVICES, my device does not appear on the list. However, when I run the command ADB FASTBOOT DEVICES, it will list my device out. Because of this, I am having trouble flashing a custom recovery and obtaining root.
If anyone knows what Status Code: 3 actually means or has other ideas what might be going on, I would appreciate your help. I did a fair amount of searching online already, but nothing seemed quite the same as the issue I was having. Thanks in advance for any help.
I recently unlocked my device with the same status code 3 and had difficulties flashing the recovery also... In the android development section theres a post called recovery unlocked they mention that the correct command to flash would be mfastboot instead of fastboot (i guess its a motorola thing) also Adb commands don't run while in fastboot...
I think I had a misunderstanding of what fastboot was, but your reply prompted me to read more and I get it now. That being said, when I attempt to flash the recovery via fastboot, I receive the error: (bootloader) Variable not supported!
For the record, it does respond to commands such as fastboot devices and fastboot reboot-bootloader
Never had that outcome but having the latest adb/fastboot files would make things easier... If it still occurs
Is your command prompt path correct to the same folder as your recovery.img and your fastboot and mfastboot.exe files?
Yeah, you beat me to it... I had the directory wrong... needed C:\adb\
D'oh!! Thanks for your help though.
i have status 3 its normal or not ?
Apparently its normal as it all worked fine for me once I had the correct directory.
JustROLLIN said:
Apparently its normal as it all worked fine for me once I had the correct directory.
Click to expand...
Click to collapse
sure ? all have unlock bootloader have status 3 ?
maxou88 said:
sure ? all have unlock bootloader have status 3 ?
Click to expand...
Click to collapse
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Oh ok thx my friend
my phone MOTO E stucks on warning bootloader unclocked.....plz help me...????
while doing fastboot its shows its not recognized by internal or external command...
samwathegreat said:
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Click to expand...
Click to collapse
If you relock the bootloader will the status code change and will the software status change from modified to whatever it says before it was unlocked?
HELP please
mine is the moto g turbo edition XT1557 running marshmellow 6.0
and i unlocked the bootlocker status code 3
while trying to boot the phone it vibrates once and gets stuck on the "warning boot locker unlocked screen"
tried the logo thing, the wipe data thing. Noting is working can anyone help me ???
Related
Hey guys
I noticed that many people are having problems to flash using fastboot. They report that fastboot says the bootloader would be locked, even if it's definitely unlocked.
so my question, who of you is able to flash (kernels for example) using
Code:
adb reboot bootloader
fastboot flash boot boot.img
and who can flash using
Code:
adb reboot oem-unlock
fastboot flash boot boot.img
I've been talking to LG about this problem, but all they said was to change a driver config for ADB. But due to the fact that I'm using Linux, it is impossible that it is a driver problem. I also tried their "solution", but guess what... it didn't work.
first one don't work by me
please use the poll, so that we've got all informations bundled
Hi
I've already voted.
So for me it does not work.Always comes back PERMISSION DENIED.
232.10 3At Austria.
I have rooted and bootloader unlocked.CWM recovery installed.CM 10.1 RC2 installed.
I can flash everything,rom,kernel...
Everything works just Reboot bootloader is not working.
Has an idea? Thanks
I can't really test adb due to idiot computer asking for disk to be inserted. But when I reboot to bootloader it says "now ready" which didn't happen when it was locked. Used the hacked method too, my odm_reserved reads:
0x000000000000000000000000000000000000fdffffffcafffffffdfffefeffed
As @laufersteppenwolf probably knows I am UK 234-000 user, unlocked with the original terminal hacked that blew all our fuses :thumbup:
Sent from my rooted P880
@non4 said:
I can't really test adb due to idiot computer asking for disk to be inserted. But when I reboot to bootloader it says "now ready" which didn't happen when it was locked. Used the hacked method too, my odm_reserved reads:
0x000000000000000000000000000000000000fdffffffcafffffffdfffefeffed
As @laufersteppenwolf probably knows I am UK 234-000 user, unlocked with the original terminal hacked that blew all our fuses :thumbup:
Sent from my rooted P880
Click to expand...
Click to collapse
it's not about the bootloader being locked, it's about the ability to use fastboot for flashing something (kernel for example)
laufersteppenwolf said:
it's not about the bootloader being locked, it's about the ability to use fastboot for flashing something (kernel for example)
Click to expand...
Click to collapse
I know, but does yours say "now ready"? If so then LG really did screw up, idiots
Also if I type "reboot oem-unlock" in terminal I get "welcome to fastboot mode "
Sent from my rooted P880
@non4 said:
I know, but does yours say "now ready"? If so then LG really did screw up, idiots
Also if I type "reboot oem-unlock" I get "welcome to fastboot mode "
Sent from my rooted P880
Click to expand...
Click to collapse
yeah, it says now ready, but fastboot says my bootloader is locked -.-
EDIT: @@non4 already knows LG's answer to this problem, but i think i can tell it y'all:
We are very sorry to say that there is no way to solve the problem you mentioned.
Click to expand...
Click to collapse
nice work LG -.-
laufersteppenwolf said:
yeah, it says now ready, but fastboot says my bootloader is locked -.-
Click to expand...
Click to collapse
You tried typing OEM unlock command? A few people have to do this to get to correct working fastboot mode. In fact I think the guy that got my BL unlocked with his echo odm method had this issue
Sent from my rooted P880
no, i can't ATM...
laufersteppenwolf said:
no, i can't ATM...
Click to expand...
Click to collapse
Reboot oem-unlock works in terminal emulator, that's the only way I can get into "welcome to fastboot" screen. When you can try it, if you can flash stuff through here then we have a solution for you unlucky fellows
Sent from my rooted P880
I'm sorry, but "reboot oem-unlock" does not work.
I just get black screen. :crying:
varadinum said:
I'm sorry, but "reboot oem-unlock" does not work.
I just get black screen. :crying:
Click to expand...
Click to collapse
Weird...
Sent from my rooted P880
Security error for reboot oem-unlock, but manual flash is possible. Normal fastboot says BL is locked, as usual.
Sent from my LG-P880 using Tapatalk 2
maybe you guys can contact LG, too. So they eventually can realize that they've f**ked up, regarding the bootloader...
varadinum said:
Hi
I've already voted.
So for me it does not work.Always comes back PERMISSION DENIED.
232.10 3At Austria.
I have rooted and bootloader unlocked.CWM recovery installed.CM 10.1 RC2 installed.
I can flash everything,rom,kernel...
Everything works just Reboot bootloader is not working.
Has an idea? Thanks
Click to expand...
Click to collapse
maybe my post here helps:
http://forum.xda-developers.com/showthread.php?t=2224020&page=46
adb reboot oem-unlock i got the fastboot welcome screen. i was hoping to see the unlock screen once more because i think something went wrong..
guys, I'm stuck at the CM10.1 boot animation, and after reading numerous posts I found some saying that I need to flash the boot.img through the fastboot. I've managed to go to the Welcome to LG Fastboot Mode though TWRP2.5.0.0 reboot -> bootloader. But when i try fastboot devices my device isn't listed... Any advice on what should I do? Is there any other way to solve the boot issue? I've waited like 15 mins with the phone not getting further than the CM10.1 Logo... :'(
PS: I'm using Minimalistic ADB and Fastboot from here
http://forum.xda-developers.com/showthread.php?p=42407269
both reboot commands "oem-unlock" and "bootloader" are defined in the kernel source code. "oem-unlock" sets an intern hardware flag for booting the unlocked mode and "bootloader" just sets the normal bootloader flag.
wondering why the reboot parameter "recovery" actually only does a normal reboot? (CM has an additional script they call before rebooting to recovery for setting the recovery boot flag)
right, no "recovery" command defined in the kernel source, but its only a few lines of code to add this
------
reboot
bootloader: locked fastboot
oem-unlock: unlocked fastboot
some time ago i messed around with these hardware flags and now oem-unlock doesnt work. it boots instead into recovery lol. no clue why
Gesendet von meinem LG-P880 mit Tapatalk 4 Beta
problem ( Please help quick )
Hi Every One
i have a question
i install new firmware to update hboot
first step to install was relocked bootloader and i did it
after installation i want to unlock my bootloader but my android does not up and freaze on htc one boot animation
how can i unlock my bootloader via fastboot ?? please help me quick
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
openbook said:
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
Click to expand...
Click to collapse
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Evolution_Tech said:
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Click to expand...
Click to collapse
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
openbook said:
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
Click to expand...
Click to collapse
As @Evolution_Tech told you, IF you have TWRP installed you can boot into recovery and move a flashable ROM.zip from your PC to your phone.
If you do not have TWRP Recovery installed, you are out of options. You will have to return it for repair or replacement.
You don't type $.
Anyway, as above, no TWRP recovery, nothing you can do
seems like you could flash a factory image in Wug's toolkit if you can into bootloader mode. (power off/ hold vol down + power button at the same time)
then flash a factory image in "soft brick" mode.
norwoodesteel said:
seems like you could flash a factory image in Wug's toolkit
Click to expand...
Click to collapse
No. Did you read the thread? Bootloader is locked.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
norwoodesteel said:
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
Click to expand...
Click to collapse
It does matter. It can only unlock the bootloader if the bootloader can be unlocked. It cannot unlock the bootloader if the bootloader cannot be unlocked, which is the case here.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
sorry, it's the sideload function where you don't have to be unlocked
norwoodesteel said:
sorry, it's the sideload function where you don't have to be unlocked
Click to expand...
Click to collapse
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
danarama said:
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
Click to expand...
Click to collapse
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
No! Stop clutching at straws. We've already told you what the only thing you can do is.
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
nothing can fix your phone unfortunately. only thing you can try to do is a RMA.
I have such operations
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
imtv said:
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
Click to expand...
Click to collapse
@ IMTV: Can you explain in detail.
openbook said:
@ IMTV: Can you explain in detail.
Click to expand...
Click to collapse
He isn't giving you a fix if that's what you're hoping, because there is no fix.
It looks like he is saying he has the same problem as you.
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
jamescable said:
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Only works if you have TWRP installed. And IF you have TWRP installed, there are other, easier solutions....
Every Software Lock should have an unlock procedure.
That is what i am searching for.
@ Danarama:I am noticing your reply's for a while now.where ever i post you respond saying RMA is the only option. Please don't make conclusions.If you don't know unlock procedure then ignore my posts.
I live in Kuwait and i bought the phone from UAE paying customs duty delivered to me via DHL no local warranty.
So i am trying all options.Let other's respond.
For people living in US,UK or few other countries RMA might be an easy procedure so they just use that option.
There are Nexus lovers everywhere so don't talk about RMA or Direct Play Store return procedures here after.
I am using Android since 2010 and i have played, rooted, reinstalled etc... with lots of android phones. I was shocked when i ended up with a dead lock like this that too on a nexus.
How stupid is this Google's Anti Theft Feature with out a back door option even for genuine owners like me.I am not a theif.I know my google account credentials which i used on my nexus 6.
Atleast Google should give an option to genuine owners to prove themselves by logging into their website with the gmail ID used on the phone to request for an unlock procedure.
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?
kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...
$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución
To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.
Hi there,
I just bought a pixel 5 phone and tried to unlock bootloader
After I made the steps described in that post for P5 ... after flasing the magisk img file I wanted to reboot the phone but it is stuck on the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device.
link..."
What can I do to fix that issue? I'm trying to root it and install lineageos after.
Regards,
LE: Most probably I run the command with fastboot installed with apt in ubuntu 20
Version from fastboot from ubuntu: fastboot version 1:8.1.0+r23-5ubuntu2
LEE:
Pfiu ... I was pretty scared ... fixed it with this link: https://flash.android.com/devices
Can somebody let me know please if the issue was because of the bad fastboot version?
Also ... I saw there is a kddi version and without it ... tried without kddi as I don't know exactly to verify if I'm having kddi
I wanted to try again to root the phone. Went to developer options and now oem unlocking is grayed, i cannot change id and it says:
"bootloader is already unlocked".
Click to expand...
Click to collapse
Then I said to go to fastboot mode but when I'm running the command:
Code:
fastboot devices
it cannot see my phone now, I'm seeing an empty output now.
Also ... when I want to start the phone I'm seeing:
"the bootloader is unlocked and the integrity ..."
Click to expand...
Click to collapse
Can somebody please help me? what should I do?
What's the problem? The message appears on some devices that had their bootloader unlocked. So the message alone does not matter.
The problem is that I don't have root access and I want to try again those steps for root
...
I want to make the steps described for how to unlock the bootloader and have root permissions as I want to install then lineageos on the phone
Thank you
LE: so the problem is described above in more details and what exactly I did before coming at this situation
So I was able to see again the device in fastboot (enabled stay awake)
When I tried command:
Code:
fastboot flashing unlock
it said it is already unlocked
Then I flashed magisk img but I can't see it on my phone
Any advice please?
dallas87 said:
So I was able to see again the device in fastboot (enabled stay awake)
When I tried command:
Code:
fastboot flashing unlock
it said it is already unlocked
Then I flashed magisk img but I can't see it on my phone
Any advice please?
Click to expand...
Click to collapse
Pull down your notifications and allow USB debugging after plugging in on your PC perhaps? Also check the box to always allow.
I don't try anymore to root my phone as I don't want to use lineageos custom rom. I already installed one that doesn't need root.
Thanks
LE: What I installed without root required had issue for me with sim manager
I finally rooted my phone and installed lineageos that is working well