I am not able to flash anything via fastboot.
i tried every way to flash via fastboot mode but nothing works.
I am on 9.2.7.0 rom.'
I really need any solution.
looks like my fastboot is broken.
while trying to work fastboot, I mistakely locked my bootloader
and now when i go to fastboot mode.
my pc shows its fastboot but in miunlock tool
itdoesnt show my device.
If anyone one can help or experienced this issue , kindle please help
I have same sitauation like this:
https://forum.xda-developers.com/redmi-note-5-pro/help/error-flashing-twrp-pc-t3786357
so if this issued is solved tell me the solution
Rohan_sadhwani said:
I am not able to flash anything via fastboot.
i tried every way to flash via fastboot mode but nothing works.
I am on 9.2.7.0 rom.'
I really need any solution.
looks like my fastboot is broken.
while trying to work fastboot, I mistakely locked my bootloader
and now when i go to fastboot mode.
my pc shows its fastboot but in miunlock tool
itdoesnt show my device.
If anyone one can help or experienced this issue , kindle please help
I have same sitauation like this:
https://forum.xda-developers.com/redmi-note-5-pro/help/error-flashing-twrp-pc-t3786357
so if this issued is solved tell me the solution
Click to expand...
Click to collapse
Did you try a different PC/ USB cable? seems like driver issue to me.
while trying to work fastboot, I mistakely locked my bootloader
Click to expand...
Click to collapse
Did you unlock it again with the Mi Unlock tool?
Make sure to enable USB debug in developer options again.
And did you turn on OEM unlock in developer options again also.
ecrum said:
Did you try a different PC/ USB cable? seems like driver issue to me.
Click to expand...
Click to collapse
Yes i tried all. But no luck. Even now it doesn't unlocking. I am traped
corkiejp said:
Did you unlock it again with the Mi Unlock tool?
Make sure to enable USB debug in developer options again.
And did you turn on OEM unlock in developer options again also.
Click to expand...
Click to collapse
Yes, i did all the steps properly. But it even not showing anything
Rohan_sadhwani said:
Yes, i did all the steps properly. But it even not showing anything
Click to expand...
Click to collapse
I know you probably enabled the options when you first unlocked. But did you enable them again after your device was wipe from the unlocking process?
Can you boot the current rom on your device?
If the rom is not booting, you may need to try and flash stock fastboot rom in EDL Mode (If that is still an option for this device).
Edit: - As you locked the bootloader with fastboot command, have you tried the fastboot unlock command
Code:
fastboot oem unlock
What response are you getting from "fastboot devices" while in fastboot.
also what is "fastboot oem device-info" reporting?
Related
So guys, my AFTv is semi bricked since last year. I tried the USB keyboard recovery stuff and it didn't work. Now I'm using a USB Cable A-A to get into fastboot and I sucessfully entered into fastboot mode. The thing is, the fastboot seems to be locked and I can't flash anything and the recovery seems to be messed up as well.
Is there anything I can do now? Or just throw the box to the garbage?
I understand that the fastboot should be fully unlocked in order to flash anything, but is it possible to unlock through fastboot mode (since it's the only mode that works for me). Making it work again even without root or custom ROM would be great.
gabsporto said:
So guys, my AFTv is semi bricked since last year. I tried the USB keyboard recovery stuff and it didn't work. Now I'm using a USB Cable A-A to get into fastboot and I sucessfully entered into fastboot mode. The thing is, the fastboot seems to be locked and I can't flash anything and the recovery seems to be messed up as well.
Is there anything I can do now? Or just throw the box to the garbage?
I understand that the fastboot should be fully unlocked in order to flash anything, but is it possible to unlock through fastboot mode (since it's the only mode that works for me). Making it work again even without root or custom ROM would be great.
Click to expand...
Click to collapse
You know... thinking about it. You could unlock it using the method the Fire HDX guys use with generating the unlock file and unlocking through fastboot. I belive the command to get the emmc info is fastboot oem emmc-info.
rbox said:
You know... thinking about it. You could unlock it using the method the Fire HDX guys use with generating the unlock file and unlocking through fastboot. I belive the command to get the emmc info is fastboot oem emmc-info.
Click to expand...
Click to collapse
I'll check on that one when I get in home. Thanks rbox.
So that anyone coming across this knows, the "fastboot oem emmc-info" command works to get the values necessary to unlock the bootloader. I'll have a guide up for it soon.
AFTVnews.com said:
So that anyone coming across this knows, the "fastboot oem emmc-info" command works to get the values necessary to unlock the bootloader. I'll have a guide up for it soon.
Click to expand...
Click to collapse
Thanks! Hope you post that soon.
gabsporto said:
Thanks! Hope you post that soon.
Click to expand...
Click to collapse
I've been a bit busy, but I haven't forgotten. I expect to have it up this week.
Is this guide online? Haven't found it. Please help.
veeroohre said:
Is this guide online? Haven't found it. Please help.
Click to expand...
Click to collapse
Not yet.
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
Solution to Lock Bootloader:- Go to Fastboot Mode,
Type :
fastboot oem relock (Bootloader unlock code without bracket)
I finally submitted my device to service centre
Needed a help in locking bootloader of Honor 8 Pro Indian Variant DUK- L09 C675.
I flashed Latest Oreo update through TWRP with the help of DUK_FullOTA_ROM_flasher method but the bootloader is still unlocked....
If anyone could help me with this as I have to visit service centre related to mic issue.
Connect to your computer, restart to fastboot mode and use "fastboot oem lock". Make sure you have a stock recovery and ROM on it, because the locked bootloader will not boot anything else.
aserraric said:
Connect to your computer, restart to fastboot mode and use "fastboot oem lock". Make sure you have a stock recovery and ROM on it, because the locked bootloader will not boot anything else.
Click to expand...
Click to collapse
Relocking bootloader by this method will erase all data?
arunpkrt said:
Relocking bootloader by this method will erase all data?
Click to expand...
Click to collapse
No, it won't. But you should still have a backup whenever you mess with fastboot.
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
RenaldiDroidXDA said:
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
Click to expand...
Click to collapse
I think your problem is you used 'fastboot oem unlock' instead of 'fastboot flashing unlock.'
Well, now I see the problem.
Now I need to know how to fix it .-.
RenaldiDroidXDA said:
Well, now I see the problem.
Now I need to know how to fix it .-.
Click to expand...
Click to collapse
did you enable usb debugging in developer options?
lucky_strike33 said:
did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I did. adb works quite well enough, but fastboot detects nothing.
Hello everybody, i have a Moto One Action (XT2013-1) . It's stuck in fastboot mode and only when its plugged. I tryed to install stock rom but i can't flash i think i need to unlock the bootloader but it requires to OEM Unlocking on developers options.
My question is:
If i can't enter to devs options because i don't have system how i can unlock the bootloader without enter devs option.
Im from Argentina and so sorry for my bad english.
THANKS U
Matiasmora said:
Hello everybody, i have a Moto One Action (XT2013-1) . It's stuck in fastboot mode and only when its plugged. I tryed to install stock rom but i can't flash i think i need to unlock the bootloader but it requires to OEM Unlocking on developers options.
My question is:
If i can't enter to devs options because i don't have system how i can unlock the bootloader without enter devs option.
Im from Argentina and so sorry for my bad english.
THANKS U
Click to expand...
Click to collapse
Flashing stock firmware doesn't require unlocking the bootloader. Try LMSA.
georg3_ said:
Flashing stock firmware doesn't require unlocking the bootloader. Try LMSA.
Click to expand...
Click to collapse
Yeah...however, I think you do need USB debugging enabled.
This is a vicious circle. You need USB Debugging to flash the ROM, but you can't enable that, cause your ROM is currently not bootable.
So...you need to do things in order.
First, you need a bootable ROM. Any bootable ROM. Just so you can get that damn pop-up to show up, so you can allow fingerprinting for ADB.
After that, you can flash stock ROM or whatever.
arsradu said:
Yeah...however, I think you do need USB debugging enabled.
This is a vicious circle. You need USB Debugging to flash the ROM, but you can't enable that, cause your ROM is currently not bootable.
So...you need to do things in order.
First, you need a bootable ROM. Any bootable ROM. Just so you can get that damn pop-up to show up, so you can allow fingerprinting for ADB.
After that, you can flash stock ROM or whatever.
Click to expand...
Click to collapse
USB debugging wasn't needed only for adb?
I remember booting in fastboot before trusting any key from my computer.
georg3_ said:
USB debugging wasn't needed only for adb?
I remember booting in fastboot before trusting any key from my computer.
Click to expand...
Click to collapse
To be honest, I'm not so sure right now. I remember my phone was in a bootloop situation, and I tried to see if I can connect it to my computer so I can use RSA and reflash stock ROM. But it wouldn't work.
It's possible that I missed something though. So yeah, you might be right.
In fastboot use "fastboot -w "then flash stock (from lolinet)then one more tine "fastboot -w" it should boot up without usb debbuging enabled