Can anyone help me out?
My asus selfie z00ud only opens fastboot mode. No bootloader, no recovery, no os. I tried flashing with flashall_aft.cmd but no success. At fastboot flash asdf asdf.img it says remote write failed and process intrrupts. I tried to flash twrp recovery. On screen it says successfully written over pc but no functioning on phone. When plug into adaptor it directly opens fastboot mode screen without pressing any button. On recovery mode shortcut it opens fastboot mode. Is their hardware problem? I tried with QFIL, but no success. Bootloder is locked and usb debugging was not on, when this fault came to my phone. Adb command only detects fastboot device.
Related
Greetings everyone! I have currently two issues where I can't get away from.
I'm currently unable to access download mode and recovery Mode due to Secure Booting Error 1003.
I can't format the phone either.
Only thing that I can do is access fastboot mode via doing recovery mode buttons method.
[470] fastboot_init()
[470] Loading keystore failed status 5 [570] USB init ept @0x8f20b000
[590] udc_start()
[690] -- reset --
[690] -- portchange --
[810] fastboot: processing commands
This is what appears on phone. At first I tried to root phone, didn't work, then I downgraded the phone and was able to root. Then I tried to root TWRP so I could flash the ROM and everything but somehow something didn't work that made me get secure boot error 1003. I tried to use flashify to flash images that probably weren't correct thus led me to be stuck on fastboot now. I downloaded SDK and ADB and I tried to erase laf.img and then try oem unlock with no success because it gave wrong command error.
I also tried LGUP method, the phone while on fastboot mode couldn't be found, even then when phone was on Android 5.0 rooted, It was unknown. So that method apparently didn't work out.
I'm still stuck here. Any help? Any ideas would be highly appreciated.
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognise it and flashtool worked
Jason_L said:
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognize it and flashtool worked
Click to expand...
Click to collapse
I gave a shot and it was unsuccessful. It says this:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
i got that spontaneously when i try to reboot and factory reset.It wasnt rooted so after i remove battery it works fine i'm not sure about that.
I unlocked my bootloader. Unlike any other moto g5 plus device it shows bad key on startup. I entered into fastboot mode and tried to flash twrp recovery. I get FAILED (data transfer failure (Unknown error)) msg every time. I tried to enter recovery mode both by pressing button and enter command. What should I do now. I really need to install twrp recovery.
Screen Shots :
https://photos.app.goo.gl/ZixyDYUwG8egLT8U8
https://photos.app.goo.gl/PFPHQ2S21b7hwBhj6
https://photos.app.goo.gl/ek7yNoF7HBQJtAme9
1) Are you using the original USB cable, or a high quality data cable?
2)Have you tried using other USB ports on your computer and do you have the latest minimal ADB/fastboot (https://forum.xda-developers.com/showthread.php?t=2317790 ) or the Google ADB tools? https://developer.android.com/studio/releases/platform-tools If you're on Windows 10 or 8.1, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
3)Bad key or N/A on boot is normal when your bootloader is unlocked. If you want to hide that, you could try to flash a custom logo.bin via fastboot (or TWRP if you get it working).
3 months back i hv flashed fastboot rom successfully. but now i stuck with different problems with no solution
1) mobile is dead, when i hold power button mobile screen blink for a second and off again
2)when mob is dead i cant go in developer option and do all that stuff
3)in fastboot mode when i type command "fastboot oem unlock" it shows error
4)when bootloader is locked i cant flash fastboot rom through mi flashtool
this all happen because of choosing wrong patched_boot file at the time of installing magisk manager.
cmd cammand only recognize my device but cant unlock. i find only one solution that is test point method. before i proceed to that need suggestion from u gye's should i go for testpoint or to service center coz mobile is still under warranty.
You can flash stock ROM in edl mode with locked bootloader.
Put phone in fastboot mode and type "fastboot oem edl".
You should be able to flash stock ROM with Miflash. If your device is not recognised update your drivers. Google for qualcomm qloader drivers.
Next time before flashing a modified boot.img try to only boot it and see if it works.
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
Hello,
I had the Syberia ROM and decided to switch to MIUI ROM.
I did the process with fastboot and mi flash tool but failed and as a result the phone no longer opens. I didn't lock the bootloader but it was giving me an error. Then I saw that probably because I used old version of Mi Flash. I downloaded the Fastboot ROM from https://xiaomifirmwareupdater.com
Right now if I try with the keys to enter fastboot or recovery, the Redmi logo flashes for several minutes and then some time it stabilizes. So through the buttons I can't do anything.
If I connect it to PC it does not recognize the device. Neither through Minimal ADB and Fastboot nor with adb devices.
I understand that I have to somehow get into fastboot mode and flash the rom but I can't find any other way.
What do you suggest I do?