Hi. When i turn the phone on, it goes automatically to fastboot mode. Since I flashed something wrong in TWRP, i can not get out from fastboot. Also i can not flash any fastboot roms with miFlash, it ends always with a failure, no such file or directory.... I downloaded the fastboot rom, i extracted it, selected it, refresh+flash but nothing helps. What now?
Adb fastboot current slot is ‘b’, but after restart comes fastboot mode again.
what happens when you boot the other?
fastboot --set-active=a
Related
I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache
Recently installed cm11, woke up today to phone being unresponsive, try to reboot it and it enters fastboot mode. I searched hours to find a solution but cant seem to find any. Can someone help me out here?
I'm not sure why it went into fastboot mode how did you flash CM11?,
But try to get the phone in to recovery mode by holding the volume up button while powering up, If it works, sideload the update.bin file you want. If it doesn't ask here for the recovery image with your fire os version. Download that, boot the phone into fastboot mode, connect the phone to PC and install the drivers and type the normal way `fastboot -i 0x1949 flash recovery recovery.img` or better yet `fastboot -i 0x1949 boot recovery.img` then sideload the update.bin file.
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Hi all,
I'm a bit stuck. Went to sleep last night with a working phone. Woke up this morning with the device turned off, and trying to turn it on always bumps me into Fastboot. I'm guessing my custom ROM tried and failed to update overnight...?
I can run fastboot commands, but trying to boot using a boot.img from a downloaded ROM (fastboot boot boot.img) still kicks me into Fastboot. Tried installing a Stock ROM, and the full install goes through, but still reboots to Fastboot.
I've downloaded the MSM tool and EDL package to see if I can get that to work, but you guessed it, I can't get into EDF mode (holding both vol buttons and connectting the phone sends me to Fastboot).
Anyone any ideas
Arran
In my case I fixed it by swapping to the other slot...
getvar current-slot to see the active partition
fastboot --set-active=a to set partition a instead.
Rebooted - all OK
I have a XT1710-10,
I had some problems with my network, so I flashed the latest Oreo stock image via fastboot.
My network problems got fixed but everytime I reboot now, phone enters the No Command screen.
To boot into phone I have to go into fastboot and Click "Start" there.
Everything else seems to be fine. How do I solve this?
The file I flashed was
XT1710-10_ALBUS_RETIN_8.0.0_OPS27.76-12-25-15-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
you forgot to reset, run fastboot oem fb_mode_clear while in fastboot mode