New answers tagged

0

The phone has less chances of turning on. Especially if the software that resides on the phone has a different and or modified boot or recovery image as compared to the stock images. Easy and wise option is to reload its Operating System because luckily you have a computer. No matter how MTP or other transfer protocols may fail to work, VCOM which is ...


0

Same problem with my BQ M8... Here is how I solved it: -With the phone conected via USB, Launch CMD to run ADB and test as many times as needed that the PC and terminal can talk to each other with the command "adb devices". Eventually after several attempts, it will return the device and number. Posibly stating the work "recovery". -Go into bootloader ...


0

Heads up to anyone that finds this happening on a Nexus 7. Same problem except there's a secondary problem after explicitly specifying platform tools. Force flashing userdata doesn't allocate all the remaining space for userdata. Solution is to resize it afterward before first boot. If you try to resize after first boot you will get stuck in a boot loop and ...


3

There are different versions of fastboot.exe available. One old version I have has the command line option -c as -c <cmdline> override kernel commandline The recent versions for Android SDK (v29.0.5-5949299) does not has the -c option. Instead it has the option --cmdline which seem to the the exactly same thing: --cmdline CMDLINE ...


-1

Try Using a USB hub. This is a problem with new laptops and PCs


0

Fastboot is implemented in bootloader (like aboot or LK) i.e. in boot chain it loads even before the first process (kernel) of main OS. It has its own very minimal kernel which doesn't recognize any hardware components (even on device) except those necessarily required at this stage (processor, memory, display, flash storage etc.). Communication with PC over ...


0

boot in recovery from fastboot, once in twrp enter adb shell, or use -> Advanced -> Terminal fastboot boot recovery.img adb shell be careful with dd especially double check partition name and partition size. in your /etc/recovery.fstab there might be just a symlink but no worry you can use it dd will targeting the real partition. cat /etc/recovery....


Top 50 recent answers are included