I had a tablet (Alcatel U3A_7_WIFI running Android Go) working alright. In order to root it, first I made (what I thought was) a full backup with mtkclient : python mtk.py rl ./backup After the rooting went wrong, I tried to flash a stock ROM (with SP Flash tool). Found many variants for that model and they all work perfectly while doing black and white output. But as soon as colors are involved I get this stripe pattern (and bluish colors): The battery indicator shown when charging, has the same color problem, so I think it has to be something happening at a very early stage. Does anybody know how to solve it? Or what could be wrong? I tried flashing individual partitions with mtkclient from the backup I had (no way to flash the whole thing back, as far as I know). But half of the time this bricks the tablet (just BROM mode) and the other half nothing changes. Colors are still the same, bluish and striped.

I am following the below post to root my Xperia E Dual. > [How To Root Xperia E! Latest Update! (Locked Bootloader)\*LINKS > UPDATED* NOOB > GUIDE!](http://forum.xda-developers.com/xperia-j-e/general/how-to-root-xperia-e-update-locked-t2409525) In step 4 to install Framaroot APK we need to Check the option "Unknown sources" and "Usb dubugging" (in Developer options) But when I am turning on the Developer option Flashtool is showing an message like below: 08/048/2014 01:48:38 - INFO - Device connected with USB debugging off 08/048/2014 01:48:38 - INFO - For 2011 devices line, be sure you are not in MTP mode I have tried changing the Usb connection mode but problem is not resolved. Could you please help? **Some info:** Operating System Used to flash: Windows 8.1

I have a Sony Xperia X8. When I tried to flash it using Flashtool v0.6.8.0, it returned ERR_DYNAMIC="SIN header verification failed". This is the log: 17/016/2013 20:16:47 - INFO - <- This level is successfully initialized 17/016/2013 20:16:47 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25 17/016/2013 20:16:47 - INFO - You can drag and drop ftf files here to start flashing them 17/016/2013 20:16:52 - INFO - Device disconnected 17/016/2013 20:16:55 - INFO - Selected E15_nAa-13_2.6.29.6-nAa-13.ftf 17/016/2013 20:16:55 - INFO - Preparing files for flashing 17/016/2013 20:16:55 - INFO - Please connect your device into flashmode. 17/017/2013 20:17:06 - INFO - Device connected in flash mode 17/017/2013 20:17:06 - INFO - Opening device for R/W 17/017/2013 20:17:07 - INFO - Reading device information 17/017/2013 20:17:07 - INFO - Phone ready for flashmode operations. 17/017/2013 20:17:07 - INFO - Start Flashing 17/017/2013 20:17:07 - INFO - Flashing loader 17/017/2013 20:17:07 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed" 17/017/2013 20:17:07 - ERROR - Error flashing. Aborted 17/017/2013 20:17:07 - INFO - Device connected in flash mode 17/017/2013 20:17:08 - INFO - Device disconnected 17/017/2013 20:17:11 - INFO - Device connected in flash mode 17/017/2013 20:17:12 - INFO - Device disconnected I get this from S1TOOL: Welcome to S1 tool. TO CONNECT NEXT PHONES X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY PRESS AND HOLD "BACK" BUTTON... PLEASE ATTACH TURNED OFF PHONE NOW RUNNING S1_EROM VER "R8A029" SOFTWARE AID: 0001 LOADER AID: 0001 FLASH ID: "0020/00BC" LOADER VERSION: "R4A045" MODEL (from GDFS): E15i SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6 CUSTOM VERSION: 1242-6780_R5B FILESYSTEM VERSION: WORLD-1-2-5_2.0.1.A.0.47 SERIAL NO: BX902AVHMC SEMC SIMLOCK CERTIFICATE Elapsed:10 secs. Why can't I flash my Xperia X8? How can I fix it?

I was already using CWM on kitkat until I officially updated my Micronax Unite 2 A106 (MT6582) to lollipop. But when I tried to use the same recovery made for kitkat in lollipop, it did not work. Why does that happen? Does that mean I can't use recovery made for kitkat in lollipop?

According to xda wiki "The recovery is completely independent of the Android system". Does it mean that, No matter which version of Android I have, the recovery of any version should work. If recovery is independent of android then why does that recovery not working. I am confused.

I've got tablet Asus MeMo Pad 7 (ME173X). I don't know what happened with him (is it broken physically or by software). Tablet don't respond on buttons, or charger. I connected it to computer dmesg shows (device also disconnect after one second and connect again): usb 2-1.3: new full-speed USB device number 3 using ehci-pci usb 2-1.3: New USB device found, idVendor=0e8d, idProduct=0003 usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 cdc_acm 2-1.3:1.0: ttyACM0: USB ACM device Sometimes but very rarely dmesg shows also (including above): usbcore: registered new interface driver cdc_acm cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new interface driver usbserial usbcore: registered new interface driver usbserial_generic usbserial: USB Serial support registered for generic usbcore: registered new interface driver option usbserial: USB Serial support registered for GSM modem (1-port) I found stoc firmware, to flash preloader but every time I got error Storage type mismatch! scatter storage type is hw_storage_emmc target storage type is hw_storage_none I was looking some more info. I read some info about meta mode. I tried connect device holding vol up or vol down (both) but device is always recognize as above and flashing also return the same error. Is there any chance to unbrick this tablet?

I am trying to flash a rom via mediatek flash tool, my problem is that when I connect the tablet to my PC it connects the mediatek preloader but after 2 seconds it disconnects. What can I do with this ?

I have problems flashing the firmware of a tablet with **Mt6580**, I am using SP flash tools and Betools. The problem is that the flashing runs normally and ends without problems, but the tablet does not turn on. When reading the Region EMMC_USER with The SP flash tool, it is empty. However, the EMMC_BOOT region is the only one that is written and is where the preloader.bin is loaded, but the rest of the files are not written. What could it be that the EMMC_USER region is not written?

I wanted to install twrp on Moto G5s but faced the following error:

Inspiron-7501:~/Downloads$ fastboot flash recovery twrp-3.5.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15714 KB)                      OKAY [  0.711s]
Writing 'recovery'                                 (bootloader) Image not signed or corrupt
OKAY [  0.132s]
Finished. Total time: 0.848s

I tried multiple recovery images, including lineage recovery, and, as i mentioned, twrp. I checked for the right files for my device (montana) and unlocked the bootloader previously. If someone has an idea, i would appreciate some help. Thanks in advance, Bennett.

I was just curious as I don't understand the MTK preloader that much. Considering if a wrong one is flashed, then you are left with unrecoverable brick (correct me if I'm wrong). So, it seemed odd to me that it would be kept in the same flash as other partitions like system, data, cache, etc. I have tried checking some partitions directly from the phone which seem to indicate that it might be sharing the same flash memory as other partitions, but the scatter files that I have seem to indicate otherwise. I also did some search on XDA Developers, but it left me even more confused. Any help will be appreciated.

I am looking for a cloning tool similar to Macrium for Win10, that is capable of cloning Android devices to a runnable virtual machine image.

For all Android Products there are 2 ways to flash the SW image: 1. EDL Mode(Emergency Download Mode) - Normally used when bootloader can't be booted up or for first flash 2. fastboot mode Both of above method requires flashing via USB connected to Host PC. Query: Do we have any alternative way to re-flash full SW image to Android Device which does not bootup without using HOST PC?

So basically I have a Stock Sony Xperia Z3 Docomo variant (if I recall correctly it was D6653) that I used all the way from 2017, until I had to store it on my desk cabinet for two years because the screen was broken (although before the screen went completely messed up, I managed to enable USB debugging in order to mirror the screen on my laptop with scrcpy so I can use it). Until finally I got a chance to replace the screen earlier this weekend Problem is, I already forgot the pattern to unlock it. Not even my brother (who used it sometimes to game back then) remember the pattern. Worse part is some of the SIM card, even when it does have data plan (I just simply put the SIM from my other phone), the phone is just going to show as full bar Roaming (R) and no internet at all so this phone completely have no network (although I do also have suspicion that data connection is probably disabled), and obviously that means I can't use google account to unlock it Wanted to use TWRP or Aroma File Manager to delete the pattern lock file, but then I realized I have to flash recovery first, and even if I do now understand how to do it on Z3 model because I already read various guide from various forum since Saturday, the problem is that OEM unlock isn't even enabled simply because at the time it was still a bit functional, I don't see it as something I need, as I don't root or flash a custom ROM on any phone that I use. And as additional note, as time goes on obviously all of the laptop at home had gone many clean reinstall, which means no ADB key backup, and I can't authorize because pattern lock Is there hope left, or this phone is completely locked? (TLDR: Phone locked because I forgot lock pattern, no Internet, data stuck at R, no connection so I can't recover with google account, USB Debugging on but not OEM unlock)

My phone Lenovo A850 (MT6582) bricked just now. I accidentally pulled out the USB cable when it was flashing stock ROM by using Smart Phone Flash Tool. Now it's not charging and won't turn on, like a dead phone. I can get into MTK Meta Mode by pressing Volume Up & Volume Down then connect the USB, with and without battery. But when I try to flash anything, it gives error 4032. Please help me this is not my phone and I broke it! It does nothing when I press power button.

I'm trying to flash my Micromax Canvas A1 (AQ4501). I'm following this guide . As per the instruction, when I click on download I should connect my phone. Now, my device gets detected by Windows (see the image below). But the download is not starting. What am I missing here?

I was trying to root bluboo s8a with TWRP following this tutorial When I reached step 2 of installing the ROM with sp flash tools, the ROM installed up to the end but the phone stopped powering (doesn't show anything). I tried downloading other customs ROMs for bluboo s8 but they were customized to be flashed with TWRP because they had no scatter files. I landed on one custom ROM which I flashed into the phone with sp flash tools and the phone powered on and I could hear the sound when I press the buttons and when the phone is powering on but the screen shows a dark screen. I would like to go back to the stock ROM or a working custom ROM. I took some screenshots of the settings of the About Phone before trying the rooting process. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> About Phone (click images for larger variants) **Update:** Now I have gotten some ROM from the seller's website. It's in a zip file with one .cpb file and a folder named dbs. The folder has two files. When I try flashing the .cpb file with QGDP, I get an error of CPB Package is not complete. How can I overcome this please?

So far, all the download addresses I can find are from third parties, does MediaTek officially offer downloads?

Hi does anyone have experience installing **TWRP** on a **Huawei P9 Eva-l09**, ive **FRP locked** my phone on factory reset and don't know the old account, i've **unlocked** the **bootloader** but when I run the command from the **Fastboot** to flash the **Official Eva TWRP img** I get an error E:\Downloads\huawei>fastboot flash recovery twrp-3.1.1-1-eva.img target reported max download size of 471859200 bytes sending 'recovery' (25282 KB)... OKAY [ 0.552s] writing 'recovery'... FAILED (remote: image verification error) finished. total time: 0.571s From research on other places I've found that it has something to do with how it writes to the partition as I've also tried > recovery_ramdisk and had another error saying that the partition file size is wrong. E:\Downloads\huawei>fastboot flash recovery_ramdisk twrp-3.1.1-1-eva.img target reported max download size of 471859200 bytes sending 'recovery_ramdisk' (25282 KB)... OKAY [ 0.552s] writing 'recovery_ramdisk'... FAILED (remote: partition length get error) finished. total time: 0.564s If anyone could assist me in the install or show me a guide on how they did it I would appreciate it as I cant find the answer anywhere

I'm trying to flash stock Android 8 onto my Xperia X F5121. Please see screenshots below: What did I miss ?

I'm trying to install .575 firmware on my Xperia Z3 dual D6633 device with flashtool but as i connected to the pc (with vol down pressed) flashtool says ERROR - Device connected in flash mode but driver is too old. How I can fix this? I'm on latest Marshmallow update and unlocked bootloader.

I download SP Flash Tool And recovery file zip,extracted recovery zip which contain three files: 1)scatter .txt file 2)recovery image file 3)recovery read me file After that i opened tool.exe and select the scatter file but don't able to tick the recovery name object