messed up pretty bad.
cant have regular boot or recovery
but got fastboot i guess
screen is stuck on hero logo and a 'fastboot usb' on top right corner
#fastboot devices works! show me serial number but cant flash anything
get a FAILED (remote : not allow) ....
any one any help.....plzzzzzzzzzzzzz
Moved to general as not development.
Try fastboot boot recovery.img
Also if you explain what happened or what you did, we can likely help.
Related
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
ANtiHazarD said:
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
Click to expand...
Click to collapse
ANtiHazarD said:
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
Click to expand...
Click to collapse
ANtiHazarD said:
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
Click to expand...
Click to collapse
I had the same thing yesterday happen but before freaking out I left my phone connected to my pc in recovery with the error on the screen and used ADB to flash a new recovery right over the old one and it worked try that. Boot phone into recovery (if you still can after everything you have done) with your phone connected to your PC, open up ADB and flash the recovery file that way.
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
coz now i don't have any recovery... only HBOOT...
ANtiHazarD said:
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
Click to expand...
Click to collapse
Anti I am not trying to be mean but thats cause you freaked out when you saw something you never have before instead of taking a breath and asking first.
If you can hold down the back button and power on your phone and get into the fastboot menu you should still be good. you can flash the recovery image from fastboot. Follow the instructions on amons page to do it.
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
ANtiHazarD said:
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
I dont really use fastboot much, so I cant help you there but you should be able to flash the recovery. try a different recovery, try Cyanogens recovery file. All I do know is it has to be in the tools folder.
okey! thx, now will try!
ANtiHazarD said:
okey! thx, now will try!
Click to expand...
Click to collapse
No Problem, let me know how it turns out.
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
ANtiHazarD said:
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
Click to expand...
Click to collapse
Not that I know of. I could be mistaken but that all has to be done through recovery. But maybe somebody else will chime in on the conversation. If fastboot isnt fixing recovery then, I am sorry to say it but you might just be SOL and you might want to see if your phone is under warranty still. haha
So in CMD on windows you are typing this in:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
and its not working? And you placed the recovery img in the tools folder where your sdk is right.
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
and all other steps is right!
fastboot devices :
HT94XNG01269
than :
fastboot flash recovery recovery-RA-dream-v1.7.0.img
got:
sending recovery 'recovery' <4602kb>... OKAY [1.750s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 3.141s
Click to expand...
Click to collapse
MD5 sum FINE!...
It's scary... what i should to do... i don't know...
ANtiHazarD said:
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
Click to expand...
Click to collapse
I am just going to ask a simple question is your G1 Rooted? with your phone off hold the back button which is the button at the bottom with the arrow then hit the power button you should get a white screen with a little android at the top.
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
maybe i can use this:
fastboot flash system rom.zip
Click to expand...
Click to collapse
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
ANtiHazarD said:
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
Click to expand...
Click to collapse
See I am running Danger just like most people, thats the difference in the fastboot access. the 3 android skaters is the proper screen. So you are in the right spot. You should have also menu options like hit menu to reboot etc...I cant remember the others. But still its right. So if you are doing the fastboot commands as posted and it still gives you an error then it was something to do with when you did all those remove commands.
I think you pretty much have a nice heavy paperweight sorry bro. Only thing I think of is keep trying the fastboot command or maybe see if there is a way to flash stuff through fastboot. I dont think there is but you can look and see. Good luck, let me know how it turns out. If I was you I would just go get a slide or the new Galaxy S
ANtiHazarD said:
maybe i can use this:
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
Click to expand...
Click to collapse
That looks promising you can try that. good luck
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 All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
How are you trying to boot into download mode, are you trying to do it via fastboot or the hardware buttons?
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
im having the same problem, i dont have download more or twrp now, all i have is fastboot
i am going to assume going into download mode through fastboot is the only option for the two people posting for help here. from what i see from the posts, both hardware buttons sequence , or the plug in & down volume are the ONLY way to get to fast boot.
and fast boot is the only thing available on the phone.
i have labeled that a soft brick .
i asume one of the two help seekers have used the magisk 20.2 trap?
the release proved to be a problem , there is a tutorial on how to fix it.
i will go look for that and try to edit it into my responce later.
for now, are the two seekers already acomplished in this procedure?
TWRP Installation Tutorial for Linux Mint and Ubuntu users ยป AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
20.2 problem notes and fix
Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode. https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705...
forum.xda-developers.com
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
ok i found a way to get into twrp (if ever installed)
1- turn off your phone
2- hold Volume Down + Power button until you see the LG logo
3- When you see the Logo release the power button while still holding the volume down and immediately after release press power button 3 times.
4- you will see a factory reset screen, press yes twice and it will go to twrp.
NOW WE NEED TO FIND A WAY TO FLASH A WORKING ROM THRU TWRP
Hello, I am trying to flash TWRP to my zenfone, I managed to do it once by some miracle with the exact same setup as I have now.
by typing fastboot devices I get K6AXB7616289*** fastboot
but if I try to flash anything with the phone connected I get no output at all.
If I try to flash with the phone disconnected I get <waiting for any device> and no change when I connect it.
In both of these cases when I disconnect the phone I get:
Sending 'recovery' (31332 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
It is overall wonky and seems to change depending on nothing. Sometimes while writing sudo fastboot reboot bootloader I get to the bootloader as expected, but sometimes I get an error but still manage to get to the bootloader and other times it boots up normally.
I am running ParrotOS from a USB
I also posted in here as my problem is very similar but I hope this post resurrects this particular topic: https://forum.xda-developers.com/t/...but-fastboot-devices-is-working-fine.4295449/
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Yeah im writing fastboot flash recovery and then the path to my twrp.img. I managed to flash it once after a lot of struggle but now I can't do it again.
After posting I saw that I'm using a USB 3 port and my laptop doesn't have a usb 2 one so I think that might be the issue.
Considering I can get three different outputs from the same command in the span of a couple seconds I think that the problem might be hardware related. I can update once I get my hands on a USB 2 port.
Kaynejulian said:
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I have now tried with a USB 2 port and there is no change.
I have had issue when the phones in fastboot and I'm able to flash via his method. Using platform tools I copy all my IMg's into the folder then open a command prompt window in that folder and fastboot reboot bootloader or fastboot reboot fastboot. Which I learned the hardway is fastbootd mode and then and only then did it actually flash. I also learned the hardway that you boot directly from in fastboot mode or it all just cycles back.
Fastboot reboot.
What version zenfone model and what is system is it running?
If your device is running android 10 or newer then is a different process as you'll need to flash the super.img rather than individual imgs like system vendor product ect
Tue shore image also means it matters where you flash the img
Get a fastboot getvar all printout to me and I'll do what I can to help u get it running again