I think I hard bricked my phone and it only show something about fastboot and it detects it when i connect it with usb but I cant flash anything because I always get some unknown error. I can't access download mode and anything else cause no matter which button combination I press it always boot into fastboot. On screen I get only this text:
fastboot int()
loading keystore failed status 5
Usb init ept @ 0x....
udc_start()
--reset---
--portchange---
fastboot: processing commands
Bootloader was locked and phone wasn't rooted. This happend when I tried to flash kdz with flash tool but it was interrupted while process was being done, so what can I do now?
Related
Hi, hope this is the right place to post this.
So my Nexus 7 (2012) was stuck in a boot loop, Google logo followed the little splash thing and repeat wihtout actually loading up. All I could open was the fast boot menu and the four options: wipe data/clear cache etc. I downloaded the relevant drivers, Android SDK, the factory image etc.
I was following these instructions to unlock the bootloader so I could flash the tablet:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This all worked fine.
fastboot oem unlock was typed next and the bootloader unlocked fine.
I then went to typed **fastboot flash bootloader bootloader-grouper-4.23.img**. Apparently what's meant to happen is:
sending 'bootloader' <2100KB>...
OKAY [ 0.123s]
writing 'bootloader' ...
OKAY [ 9.876s]
finished. total time: 9.999s
However mine just got stuck at the "writing 'bootloader' ..." stage. It was like this for quite a few minutes when it's supposedly meant to take a few seconds. "Signature match" showed up in the top left corner of the tablet however it is unresponsive, you can't move the buttons to show the Recovery mode/Power Off options.
I foolishly closed the command window and opened a new one. I tried to do the next stage "fastboot reboot-bootloader" however it just says "FAILED (command write failed (unknown error))" You get basically the same for all the other commands either unknown error. If you try to flash the bootloader again it fails and says invalid argument. My tablet was still recognised by the PC, showing the fastboot screen with Start in the top right and signature match in the top left. However any other prompts would fail. Eventually I unplugged the tablet and was able to turn it off with the power button.
Previously I had had trouble opening the fastboot menu or even getting to load to the boot loop (not responding to the button presses very well) however so far the display hasn't powered on at all. The only response you get is when it's plugged in you hear to device connected and disconnected sounds, and it is recognised as APX in the Windows device manager.
So what should I do? Is it fully bricked? My tablet is out of the 1 year warranty (This probably voided it anyway). Greatly appreciate any help anyone can give me
Normally flashing of a bootloader with a signature mismatch should not work, there are some protections build in, so I see two possible situations for you:
Either you are stucked in APX-mode, but the old bootloader is still working: in that case hold down the power button for at least 20 seconds to turn it off completely and then try to restart the tablet again
or flashing of the bootloader started, but failed during writing the new image. In that case the probability that you have a brick is very high ...
Hi I've seen threads around that have the same issue is there any help I can get.
I only have access to fastboot
my device will hang on LG logo
I've tried flashing recovery and it won't boot into it
I also tried https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3 and cannot flash misc, fota, but I can flash cache
- the error i get here is " remote: cannot erase this partition in unlocked state "
-- so i locked it with fastboot oem lock and fastboot flash lock and i get the same error with it declaring a " locked state " forcing me to unlock the bootloader again
I've attempted to flash .kdz files with no luck as im in download mode and the guides even say to put in download mode and LGMobile support tool isn't able to detect phone saying it's not even plugged in.
- is there a .dll file or something i need I've read twice in two different post maybe it's typos
I ran LGMobile support tool and it fails after downloading the .kdz file (my guess) not being able to put the phone in download mode is causing it to do so
I'm running out of ideas can anyone help?
HKnight said:
Hi I've seen threads around that have the same issue is there any help I can get.
I only have access to fastboot
my device will hang on LG logo
I've tried flashing recovery and it won't boot into it
I also tried https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3 and cannot flash misc, fota, but I can flash cache
- the error i get here is " remote: cannot erase this partition in unlocked state "
-- so i locked it with fastboot oem lock and fastboot flash lock and i get the same error with it declaring a " locked state " forcing me to unlock the bootloader again
I've attempted to flash .kdz files with no luck as im in download mode and the guides even say to put in download mode and LGMobile support tool isn't able to detect phone saying it's not even plugged in.
- is there a .dll file or something i need I've read twice in two different post maybe it's typos
I ran LGMobile support tool and it fails after downloading the .kdz file (my guess) not being able to put the phone in download mode is causing it to do so
I'm running out of ideas can anyone help?
Click to expand...
Click to collapse
update: I managed to get back into twrp by issuing the command -- fastboot flash boot boot.img -- I renamed it boot.img and it worked
update: I'm back now in android after flashing my rom.
credit goes to : http://android.stackexchange.com/questions/2210/installing-rom-from-fastboot-can-someone-help
Can someone marked this solved
HKnight said:
update: I managed to get back into twrp by issuing the command -- fastboot flash boot boot.img -- I renamed it boot.img and it worked
update: I'm back now in android after flashing my rom.
credit goes to : http://android.stackexchange.com/questions/2210/installing-rom-from-fastboot-can-someone-help
Click to expand...
Click to collapse
this does not work for me! after it says writing boot.... it fails.
alright so your still in fastboot right?
Doesnt work for me. Say
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
Im stuck in LG LOGO and i can´t access to recovery.
Hi, yesterday I decided to flash my Moto g4 xt1621 I put a rom of 7.1.2 and I did not work some things and I decided to put a stock rom of 6.0, I appeared a poster of software update to 7.0 and I gave it yes, I left it updating and never started again.
Try fastboot mode, with usb, charging, with the button on 10 minutes, but nothing turns on the screen, the only thing the phone does when connecting to the charger is the charging LED that turns on and off. The phone has 2 months , no computer recognizes the device.
I know that when I put a non-original rom I lost the warranty.
Upgrade.
After researching a lot, now my computer recognizes the device as two devices.
"Unknown USB device (link in compliance mode) and Fastboot athene_13mp S"
I managed to make it even though the phone boot, but it does not let me do anything in fastboot. (I do not see the rare android logo), and I get these messages:
Start Up Failed: Your device did not startup successfully.
Use the software repair assistant on computer
to repair your device.
Connect your device to you computer to get
the Software Repair Assitant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No boot imge found. Skip to fastboot
Boot up failed
ERROR: No boot imge found. Skip to fastboot
Boot up failed
ERROR: No boot imge found. Skip to fastboot
Boot up failed
USB Connected
Try putting the boot.img of the stock rom rom that I put and it will not let me either:
"downloading 'boot.img' ...
OKAY [0.533s]
booting
FAILED (remote failure)
finished. total time: 0
new edit: no have imei/meid and "sku"
"
So my phone booted into the stock recovery (no TWRP installed) when I accidentally selected the wrong update method in magisk. It kept on rebooting to the recovery even after selecting reboot device and tried clearing cache. Even after that it booted back to the recovery. Then I turned off the phone. And now when the phone turns on it goes to bootloader even after selecting recovery mode. And in the bootloader "Bootloader Version" and "Baseband Version" are blank. This is what it shows;
Fastboot Mode
PRODUNT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - "Serial number available"
SECURE BOOT - yes
DEVICE STATE - unlocked
PC doesn't recognize it either.
Under device manager it says "Unknown USB Device (Device Descriptor Request Failed)
I'm having 6T 6GB RAM (International)
Bootloader unlocked
Any idea as to why this happens and how to solve it?
Thanks
PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader
dushan90 said:
PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader
Click to expand...
Click to collapse
Use MSM Tool to recover the device. That's the easiest option.
Does it wipes the device?
Also I was on 9.0.13. And I could find only MSM Tool 9.0.12.
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
Beast mode nice job and thanks for sharing your fix
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issue..
Is it possible to restore the baseband version by entering this commands?
In my situation, I already wiped and boot into the system.
dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
I get this error by trying your solution:
```$ sudo fastboot --set-active=b
error: Device does not support slots.```
```$ sudo fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Also tried the other option without better results:
```$ sudo fastboot --set-active=a
error: Device does not support slots.```
```$ sudo fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Maybe it's because I'm using OnePlus 6 instead 6T?
how was this fixed?
hi guys, zenfone3 soft bricked. enters fastboot mode. There is no recovery mode, the phone stays on the asus screen while booting. I tried to install stock recovery
I tried to install twrp, this did not happen because the bootloader is unlocked. The bootloader lock cannot be unlocked via fastboot.
I tried to install with the asus flash tool, I tried 5 different stock roms, the same error I got on 2 different PCs;
run flash image script failure (failed (remote:failed to write partition))
After getting this error, I tried to do fastboot oem reset-repartition while trying to fix it, but I also got the following error;
failed (remote permission denied)
ı not fixed.