i think i've ****ed up my zenfone 2.
i can only go to fastboot and i can flash boot.img , droidboot.img and recovery.img
but i can't flash system.img (it says error: cannot load 'system.img') and everytime i try to go to recovery , it just freeze on asus logo and that's it.
i can't flash asus zip file (from asus site) because the size of the file is too large and i receive error.
i was using a custom rom and decided to return to stock.
how can i fix my phone?
Your system.img is corrupted somehow, if you are using shakalaca's img just delete the current one in your folder and unzip like you did before, that worked for me after the same thing happened to me while flashing.
okay.i have some good news (for myself )
i can now get into Recovery mode.it's stock recovery with and android robot in it and saying "installing System Update"
but after a few seconds it says error and that's it.
i use "adb devices" but there's no device connected.same for "fastboot devices"
now what should i do?
p.s : i get error everytime i want to "fastboot flash system system.img" and everytime i use "fastboot -w".for flashing system it gives the "error: cannot load 'system.img'" and for -w it says "FAILED (remote: flash_cmds error! )"
edit: now i have TWRP recovery.it's the UN-Tethered one.so i don't think i can install stock rom.right?
what should i do if i want to install stock rom?
edit 2:finally.i installed a custom rom for now.everything is ok.the phone is up and running.
but now i want to return to stock rom.how?
Related
Hi, i'm trying to flash by using fastboot with command prompt. I can't flash anything by useing the recovery option in hboot because it keeps taking me back to the hboot menu.
Right. I extracted the rom.zip from the RUU Rom "testruu" which went okay, it has all the images, includeing the recovery image to get it working again. but when i type in "fastboot -p (serial number) update rom.zip" which the rom.zip is located in the sdk tools folder. it comes up with the error
"Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in "MS-DOS symbols.........."
Any ideas? i tried flashing other rom's but they don't contain the "android-info.txt" within the image zip package.....
Please help because my phone is 100% dead with no recovery working and stuck at the htc logo screen.
so no one knows how to flash in fastboot? well great.
Enter fastboot then plug Desire to your computer and run official RRU (*.exe file)
That should help
Cheers
TWRP recovery request fastboot command
I tried to flash twrp.img on my Zenfone 2 ver 2.17.40.12 (rooted). I guess there was a version mismatch, because I ended up with the screen saying "Fastboot cmd waiting". I am allowed to power down and normal boot, which work, but options "recovery mode" and "restart bootloader" return me back to the same screen saying Fastboot cmd waiting.
I tried to do a factory reset, but I got the same screen and nothing else. I downloaded ZIP file with the correctoriginal recovery for my version and tried to use fastboot command update, but it failed with message saying that archive does not contain android-info.txt and neither android-product.txt.
I will appreciate your advice to resolve my problem.
Well, fastboot is showing error because you're trying to flash ZIP file for the recovery mode(like TWRP) that doesn't have compatibility with fastboot mode.
You have to flash the .img file for your zenfone2(Z00A or Z008) with the command below.
Code:
fastboot flash recovery twrp.img
And also, model number(Z00A or Z008) is shown on the screen when booting in fastboot mode.
I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!
Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?
BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
please , i want to know , how can i give fastboot on my redmi7 device
H R Habib said:
please , i want to know , how can i give fastboot on my redmi7 device
Click to expand...
Click to collapse
This is a forum dedicated to the Poco F3 so I think you should ask it on the Redmi 7's forum
Use MiFlash to flash the fastboot Version of stock.
ClementNerma said:
HI there!
After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it failed to check the sparse CRC.
So I looked for a solution and finally commented out the line that sent the CRC files to the device at the beginning. The flashing worked fined, but after rebooting I'm now stuck in a bootloop.
I entered fastboot by holding Volume Down + Power and got into it without problem, but when I tried to flash TWRP to install something else, I got the "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" and after checking, it seems that my bootloader has been re-locked!
So I'm now stuck in fastboot, both the Global and EEA roms won't work, and I can't flash an alternative recovery.
What can I do?
Thanks in advance for your help!
EDIT: I ran the official MiFlash Unlock tool, which tells me my device is unlocked, which is really weird. The "fastboot oem device-info" command indicates: "(bootloader) Device unlocked: true".
Click to expand...
Click to collapse
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Phoost said:
Use MiFlash to flash the fastboot Version of stock.
Click to expand...
Click to collapse
I didn't find an official MiFlash tool and I don't trust closed-source tools for this kind of things.
avidduo said:
Don't flash recovery. Use this command instead:
Code:
fastboot boot recovery.img
and it will boot into recovery. Then you can install recovery ramdisk.
Click to expand...
Click to collapse
I tried that but it didn't work.
EDIT: After re-trying several times, I was finally able to make it work by booting with ArrowOS' recovery. TWRP was not accepted, but ArrowOS' one was
So I've been able to flash the Xiaomi.EU rom, I'll stick with it for now.
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.