So I picked up a nexus 6 that was said to be bricked. It was cheap so I figured what the hell. Anyway it's stuck in fastboot. No matters options it goes back to the fastboot screen. In logs it says "invalid boot image header." device is locked status code 2. What chances do I have of getting this back up and running?
Sent from my D6708 using Tapatalk
Locked code status 2 = bootloader locked right?
Paperweight.
So there is nothing possible to do? I was under the impression is was almost impossible to hard brick a nexus 6. I guess i was ignorant. lol
the N6 and N9 was when they started having the oem unlock enabler in developer settings menu and without the ability to boot and enable that setting its just as screwed as any other locked phone.
Are you talking about bootloader mode?
Locked bootloader+stock recovery (no TWRP) =bricked.
I've read where others have typed "fastboot erase bootloader" which has removed the bootloader so the phone won't even start.
If you have an unlocked bootloader and TWRP then you can recover from most issues. I've formatted my phone with no OS before. You can adb pull a zip in or flash via OTG. Locking the bootloader with no custom recovery or ROM prevents you from installing anything
Add me to the list of people who's G4 decided it wants to join the bootloop party. I plan on sending it in to LG for warranty replacement but the problem is my bootloader is unlocked which is visible on the boot screen.
Clearly this issue has nothing to do with an unlocked bootloader but I'd hate to have repairs refused because of the fact it's unlocked. I am able to boot the phone into download mode and perform a software update through the LG Bridge tool. I can also do a hard reset which I have already done.
Is there any way to issue a "fastboot oem lock" command utilizing download mode? I did see this link but have no idea if that would help me. Any input would be appreciated.
njskins21 said:
Add me to the list of people who's G4 decided it wants to join the bootloop party. I plan on sending it in to LG for warranty replacement but the problem is my bootloader is unlocked which is visible on the boot screen.
Clearly this issue has nothing to do with an unlocked bootloader but I'd hate to have repairs refused because of the fact it's unlocked. I am able to boot the phone into download mode and perform a software update through the LG Bridge tool. I can also do a hard reset which I have already done.
Is there any way to issue a "fastboot oem lock" command utilizing download mode? I did see this link but have no idea if that would help me. Any input would be appreciated.
Click to expand...
Click to collapse
no.. you must boot phone .. so best way is to use the freezer method.. boot into fastboot relock it . then flash stock firmware and send it.
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?
Hello, I rooted, and installed custom recovery on my 1+3t. And the new update came out. I decided to give it a shot. Long story short. I locked my bootloader. And when I try to boot it up. It shows logo for one second, vibrates, and is stuck in that bootloop. I can get into recovery, and fastboot, but bootloader is locked. Any ideas?
Use recovery unbrick tool.
And don't lock your bootloader when you're going to flash any kind of mod, like Magisk.
You can unlock bootloader if you have activated oem unlock and usb debugging in the developer option. Then you are good to go for custom recovery..
You should never re-lock your bootloader after you flash anything not signed by OnePlus. Your device can never be booted up and only can be fixed if you use the unbrick tool by Qualcomm.
thes3usa said:
You should never re-lock your bootloader after you flash anything not signed by OnePlus.
Click to expand...
Click to collapse
My thoughts exactly.
To the OP, you don't need to lock the bootloader to update this device. And you should never lock the bootloader with mods on the phone (TWRP, root, etc.).
Good rule of thumb, is to read up before doing an update like this. Would have saved you a lot of hardship, as all the info is here on XDA for those that care to search and read.
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Weltraumpenner said:
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Click to expand...
Click to collapse
Try fastbooting the newest ota instead of the full factory image. Also, try going to Android recovery and hitting the factory reset inside the menu there. I believe to access the recovery through fastboot you wait for the dead Android guy and then press volume up and power at the same time.
Sent from my Pixel 4a using Tapatalk
Did you ever figure this out? Google had a chrome extension flag tool. Instead of cmd/cli adb.