Tag Info

New answers tagged

0

I've solved my problem for myself by re-locking the bootloader and then repair the device using Sony PC Companion. Device is again in mint condition ;) I'll add a supporting link later.


0

Folks consider adb sideload <ZIP> when they have a ready to flash .zip file. The command is mostly used when booted into Recovery mode. Fastboot on the other hand deals with per partition flashing at a time. E.g. fastboot flash recovery <IMG> -- only flashes Recovery partition and not all the relevant partitions for ROM installation. ADB ...


0

You should wipe the data once, when you start. This may not be necessary if you are (for example) only flashing a recovery, flashing a very similar ROM, etc. You shouldn't need to erase images/partitions before flashing over them.


0

Try flashing the stock recovery img using twrp or flashify. I'm sure you are rooted.


1

ok i got it .. also problem fixed and phone working now .. all i had to do is to put phone in SD Update Mode where it says "Battery Level is Low" then i connected charger and left it for 2 hours then Update process started.


1

There is no Fastboot Command that does this. However you could try holding the power button down until the screen goes blank and then letting go off the power button before the device starts to boot (before the vibrate). This is the only viable way... The list of available Fastboot commands are: usage: fastboot [ <option> ] <command>   ...


0

Try using SP Flash tools. It's for mtk devices like yours. You will need the correct drivers. Look this up on XDA, there is a fair amount of risk involved. You MAY BRICK THE PHONE. I have a Canvas Knight,and the same problem occurred with me too. I finally gave up and chose an unrooted phone.


0

Use adb reboot bootloader, and then Mac OSX,assuming the drivers work, will detect it in fastboot mode, as attested to by fastboot devices. If your android version is lower than 4.3, use Framaroot to root it, use Flashify to flash a custom recovery, and flash the CyanogenMod rom.zip from the custom recovery. No PC involved.


0

I encountered the same error so after a lot of research I referenced this site: http://androidforums.com/threads/recovery-unofficial-cwm-6-0-5-0-peregrine.859010/ Before you flash recovery you need to transfer the file to the SD card. After I did that I ran the below: C:\adb>fastboot flash recovery CWM-6.0.5.0-peregrine.img I then booted into recovery ...


0

Based on OP's clarification done in the comments below Izzy's answer, I propose the following solution if one's device is locked out and ADB is not enabled under Settings. Note that this method is tested on Stock Android 4.2.1 and Stock CM 12.0 (Android 5.0) , both devices having custom Recovery (ADB always enabled as default) . If your Stock Recovery ...


2

Details for that can be found in our usb-debugging tag-wiki (where I've just added them): By default, USB debugging is disabled with stock ROMs (some custom ROMs however have it enabled by default). To toggle it on or off, you can find the corresponding switch in Settings › Development – a section originally hidden with Android 4.2 and up. You can make ...


3

This may vary with the device, but on Nexus devices, as soon as you accept the bootloader unlock on your device after issusing fastboot oem unlock, the device is wiped so you would not be able to see the data in TWRP. This is evident because after issuing the fastboot oem unlock command to a Nexus device and confirming the operation on the device, the ...


0

Sorry for a second answer but I think Izzys answer is not getting the point perfectly. First of all your Question: How do i get the device to show up in 'fastboot devices' once I enter recovery mode? This won't happen at all. Recovery and fastboot are different things. Fastboot is mostly part of the bootloader of your device which is probably a ...


0

I'm afraid the stock recovery (as pointed out in the comments) doesn't come with ADB enabled, which is why your device is neither shown with adb devices nor with lsusb when you've booted it into <3e>. The only way around this (if you really need to access the tablet via ADB while booted into recovery-mode) is flashing it with a custom recovery, such as ...



Top 50 recent answers are included