MTK 65xx does not respond to flash - General Questions and Answers

I have a problem with my HTC 626g (MTK 65xx), I had a custom rom installed on it for several months, everything worked without a problem, but yesterday after the reset the phone fell into the bootloop, when trying to enter the TWRP phone turned on the system and not recovery, bumping into the bootloop.
I tried to flash the stock system through SP Flash Tool, there were no errors on the computer, everything went well and finally the message "Download Ok", but after turning on the phone it turned out that nothing was flashed, the phone tried to turn on the previous system and still had bootloo.
I decided to format the phone and then flash the stock system, it turned out that I still can not flash anything, that is - on the computer everything looks good, but the phone itself behaves as if I did not flash anything.
Currently the phone has no system, recovery, fastboot mode, etc., the phone has only Meta Mode when connected to the computer, SP Flash Tool still detects it, but I can not do anything, I tried to format the whole phone and then flash the preloader, I tried to flash the preloader itself, preloader with the system, preloader and then the rest of the system, etc., but I have nothing, after Meta Mode, the phone does not react to anything, and in SP Flash Tool I do not have any errors, each time it looks like a correct system flashing.
Can I still do anything with this phone?

Related

Nexus S won't boot to OS

I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!

Help - Can't boot phone, stuck in recovery

I flashed a CWM, and did a backup. I then wiped the data partition in preparation to flash Cyanogen. At some point my computer lost the connection to the device so I could not push the file. So I ran restore from CWM, the restore completed, but when I go to reboot device, it just reboots back into recovery. Am I missing something? Please help, my phone is completely unusable.
I tried rebooting into fastbook from CWM, and it did, and my PC see's the phone, but when I boot into recovery, my PC stops seeing it so I cannot push CWM.
I reflashed a different recovery clockworkmodrecovery.6051.falcon, and it still drops the USB connection when you go into recovery, so adb push does not work. I tired restoring again, the phone just reboots into CWM. Is my phone completely dead? It seems no matter what I do I cannot get my PC to see the phone when CWM is running. In fastboot, it sees it fine, as soon as you go into recovery, it drops the USB connection and you cannot push files.

[Solved] Fully wiped phone(D6633), no recovery, fastboot command not allowed

Update: So thanks for all the help guys, i just downloaded a firmware from Flashtool's XperiFirm and flashed it to 23.4.A.1.232, I'm just going to apply root and recovery and i'm set.
Hello, I was using a stock based 5.1 ROM when i tried to change the theme and the screen just went black i was receiving messages and stuff so i knew the ROM was working but it had no interface i tried waiting to no avail so i restarted the phone and saw the screen still black. Since i had just recently installed the ROM and did a SD and internal storage wipe for a fresh start, i just said screw it i'll just use my old twrp backup and booted into recovery HOWEVER before flashing the backup when i went to do "Advanced Wipe" i must have accidentally ticked the wrong thing because being a moron i restarted the phone and i suddenly had no recovery or rom. So now when i turn on the phone the only thing it's showing the Sony logo in the middle and "XPERIA" in the bottom.
I can still access fastboot and flash mode.
I started up fastboot and tried to flash the dual recovery kernel but i kept getting the "Command not allowed" error.
I used flashtool to Relock/Unlock my phone and still got the same error.
I re-installed all the drivers still the same error.
I tried different USB ports and cables.
I know i can flash a firmware using XperiFirm from flashtool, but my internet connection is slow, has frequent disconnects that restart the download and the ISP charges like 5$ for every Gb i download, also i dont like to wait a day to download a firmware that i'll change in a few hours.
If you can help me get twrp in my phone i'll be a happy camper , if not i'll just have to flash the firmware :|
Thanks in Advance, Dan
UPDATE: i made and ftf from a ROM i had laying around and flashed it with flashtool but i've still got the same issue with no improvement. I just cant get why fastboot flash commands arent working.

Nexus 5 bootloop bricked - CAN'T FASTBOOT/SIDELOAD FLASH - Need QCom TESTPOINT

I had a Nexus5 that was stock, and working.
I unlocked the bootloader and flashed to 31E, using the factory image.
It was OK afterwards. I used
After a week it one day randomly rebooted, and hasn't booted since.
After power on, there is Google screen for ~50sec, and then colour animation for 30+min.
THE PROBLEM - FASTBOOT FAST WRITE FAILURE
I can boot into fastboot. It says its unlocked. I can erase and flash laf, boot .. but Most of them, like recovery, cache, it says
FAILED (remote: flash write failure)
Obviously, if you run the flash-all or anything similar you will get the same thing.
RECOVERY IMAGES - FAIL
It says it can't mount /cache. Mounting system, and then wiping cache spits out 20 mount errors. Factory reset/wiping - same.
fastboot boot with 4 different TWRP boots after 5min to TWRP logo screen, and shows up in adb. I found a CWM recovery that booted,
but had lots of mount errors.
I played around with parted, and make4fs, trying to recreate partitions - no dice.
they are there under block./mmcblk0 - 29 of them. I get errors that journal is outstanding when trying to e2fsck. And trying different superblock didn't work either.
SIDELOADING - FAIL
I tried sideloading from ADB. Doesn't work. Complains about mount points. 0%.
LG DOWNLOAD MODE - NOT EXIST??
I cannot boot into "LG" Download mode. 2 other LG phones boot immediately into download , so I'm 99% sure the cable or PC, or "static" is not the issue.
QDLOADER - NO EFFECT
Finally, Qualcomm USB QDLoader - I got it working in Win10 x64.
To boot device into QDLoader, it has to be booting up normally to Google screen, and you are holding all buttons for 8+ sec, until you see it in Device Manager.
I tried both the 16GB and extracted TOT flash, and they completed, but phone is the same. Still cannot flash factory image.
I tried running RAM test. Success. EMCC read and erase test are OK, but "rwrite" test fails immediately (write protected???)
So, I tried flashing the system, cache, misc, persist, modem and recovery from BoardDiag. They completed, taking 30min for system and 20min for cache.
Still fails.
QFIL - WHERE FILES?
Where do I get the files for QFIL? Is it worth even trying?
FYI, for reference, I basically gave up and bought a new phone.
This error message basically means your eMMC is "fried":
FAILED (remote: flash write failure)
The failing eMMC BoardDiag test confirms it.
I dont believe so many people would have Sandisk eMMC (the one in Nexus5) which would suddenly become completely broken.
I'm quite sure some internal project engineer out there knows of some "fuse" or "write-block" that's causing this...
But, in meantime, I've decided its better to be enjoying the phones I express ordered from Hong Kong...

I just want to asked if my phone is hard or soft bricked

I tried to root my phone and in the process i used the wrong mtk boot img file, so i use the format except for boot loader of sp flash tool. my phone does not turn on but i can still flash files to it using sp flash tool. I just want to ask if i can still do something?
I am using an mtk 6765 but i was trying to flash mtk6763, ive already downloaded a firmware stock for my device but im am encountering a lot of problems in flashing the stock. update* when i try to flash the stack rom, there is an always an error on md1img because it seems that i need to disable boot verification but i cant since my phone's screen wont even turn on, the only way i think i know its functioning is by flashing things in it

Categories

Resources