Related
I Have noticed quite a few - as in 3+ Moto G 2nd gens's are having problems with corrupted partitions, i.e OTA fails to install half way through or cant install via Mfastboot and / or Custom recoveries.
Due to the corrupted partition (or rather partition table) IT wont allow flashing / erasing or clearing / factory resets
There's no proven cure but MAYBE locking and then unlocking boot loader again may fix this as it WIPES data.
AS a Precaution I suggest anybody that who is thinking of upgrading / downgrading or restoring does a FULL FACTORY reset AFTER they have backed up phone.
Yes its extra work but with memory cards being cheap and playstore / google accounts backing up your apps, contacts etc, it's simply lazy and Dangerous Not to backup....
so...
my moto gave up during OTA update to 5.0.2 -> flash and rebbot OK, but "optimizing applications", took an eternity, then (in the middle of the job) the screen went black.
after a cold reboot it finished and everythings allright now..
My Moto G has this problem too!
The userdata and cache partitions seem to be corrputed as they give the error: blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata ( /cache )failed
This happens in stock recovery.
Help
I have this Problem too.I was in lexodus Rom then my phone shutdown,then i Turned it on and all apps fc's .I tryed to flash it With twrp but it cames an error execute update binary .I cant restore or wipe anything .And when i try to restore it with you stock Rom installer in succes but it still the same rom with the same Problem .I need help Please PS sorry for my Bad english
When the partition table is completely hosed, you can't lock the bootloader, only unlock. And unlocking in this state does not wipe it.
There is no recovering from this state, and honestly you get what you pay for with these phones.
When the battery drops below 5%, there is a high probability of the eMMC being ****ed in this way (I have had it happen on 4 phones now!). Undoubtedly a major design flaw.
I messed up partitions on my oneplus one. Most specifically the data one trying out f2fs. I was able to recover the partition by formatting it with a combination of philz cwm, twrp, and parted. I don't remember what I did as I was desperate to fix my oneplus. You can look into learning how "parted" works and you may be able to reformart the partition through adb shell.
I know this is a bit of hogwash help, but I was able to recover my /data partition.
Edit: also if I understand correctly, just because your partition table gets effed up, doesn't mean your recovery doesn't contain the proper information to put it back properly. I was able to boot my phone into temporary philz and twrp by command line using fastboot. I'll see of I can find some info.
Sent from my Moto G 2014 using XDA Free mobile app
Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.
In twrp i can Format all expect infernal storage .when i Format data it says OK but the data is still there and When i try to boot philz cames a bootloop
rukusx7 said:
Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.
Click to expand...
Click to collapse
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Also no Chance to recover our moto g ?:crying:
Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
I'm on the same boat, but actually when I try to boot, it goes in an endless bootloop of a Motorola logo (not the animation particularly). I've tried only with TWRP. I'll try later with CWM.
Flashing goes well but.... crap, I hate this
Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
So if i unlock bootloader and root phone will i be at risk?? Or i am only at risk if i mess with partitions or try to lock bootloader again?
How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.
Darksl1der said:
How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.
Click to expand...
Click to collapse
Sorry to ask but, do you even know what a emmc flash programmer is?
jhonnyx said:
Sorry to ask but, do you even know what a emmc flash programmer is?
Click to expand...
Click to collapse
Am enthusiast of device-modding, IT-engineer and a big fan of Motorola phones since 2005.
Of course I understand.
I mean this tool could help somehow by taking part of restoring, but supposed to fix issues over WRITABLE memory.
In case of RAW partitions - should delete partition table and recreate then, since plain format refused.
Anyway, my point was about this tool - it's not classic HardBrick state, Bootloader is working thou. We will use flasher if we'll replace eMMC-chip, for example
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
Can you boot into fastboot mode?
If yes...then boot into fastboot mode and reflash stock firmware using fadtboot commands
droider007 said:
Can you boot into fastboot mode?
If yes...then boot into fastboot mode and reflash stock firmware using fadtboot commands
Click to expand...
Click to collapse
For this i need unlock bootloader.
Example:
Device in fastboot mode
Conected in pc
Command in console cmd:
fastboot flash recovery recovery.img
Then
(Bootloader) preloader
FAILED (remote failure)
Errors..
I need help to unlock bootloader of device whitout check allow oem unlock in device because it no power on!!!
Check how to boot (not flash) to TWRP from fastboot. When you get into TWRP do a Factory Reset and reboot.
mausv said:
Check how to boot (not flash) to TWRP from fastboot. When you get into TWRP do a Factory Reset and reboot.
Click to expand...
Click to collapse
fastboot boot recovery.img
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
same issue with me any solution for this.?
m not able to flash stock firmware it says
E:footer
E:signature failure
and when m unlocking boot loder it says oem unlock error
anujanuj said:
same issue with me any solution for this.?
m not able to flash stock firmware it says
E:footer
E:signature failure
and when m unlocking boot loder it says oem unlock error
Click to expand...
Click to collapse
someone found the solution:?
What error in bootloader log?
Enviado desde mi XT1563 mediante Tapatalk
Can you, at least, boot in stock recovery mode? If you can already boot in fastboot mode, you can use volume up and down keys to toggle between all the options, toggle it until you see "Recovery mode" and then push power button. Your phone will reboot in recovery mode and an option to do factory reset should be there. Stock recovery is less powerful than TWRP recovery but, it if you have a hard time installing TWRP, it could be another solution.
OTA possibly flashing, pushing the sd fastboot
Enviado desde mi XT1563 mediante Tapatalk
check this for enable
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
flopezm said:
check this for enable
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Click to expand...
Click to collapse
what if phone shows internal and external memory not mounted
fix of hardbikd ....
here u go ...1st go fastboot mode n flash the stock file on fastboot mode the ...press power bottom 20 time fastly then u see warning bootloder logo the wait 5min after completing go 2 developsr allow oem ........
anujanuj said:
what if phone shows internal and external memory not mounted
Click to expand...
Click to collapse
Can you explain?
Sent from my XT1562 using Tapatalk
K.khiladi said:
Can you explain?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
nothing this is too old post now my issue is solved
anujanuj said:
nothing this is too old post now my issue is solved
Click to expand...
Click to collapse
Mate your posts are everywhere on the forum.. ??
Sent from my XT1562 using Tapatalk
K.khiladi said:
Mate your posts are everywhere on the forum..
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
yes because my phone was dead and i had fade up
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
Just get flash stock android 5.1.1 rom from fastboot if that doesn't work try getting into recovery mode and flashing the stock rom via adb sideload.
motorola x play ...stuck in boot
I am using a Motorola X Play 32 Gb Dual Sim phone with a Marshmallow 6.0.1
I'm now stuck at bootup with Start Up Failed.
Startup failed Error
your device didn't start up successfully
use the software repair assistant on computer
to repair ur device.
connect ur device to your computer to get
the software repair assistant
AP fastboot flash mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
Error: failed to pass validation. backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
pls Help by step by step methods I am Stuck.....Please
scorpionking3010 said:
I am using a Motorola X Play 32 Gb Dual Sim phone with a Marshmallow 6.0.1
I'm now stuck at bootup with Start Up Failed.
Startup failed Error
your device didn't start up successfully
use the software repair assistant on computer
to repair ur device.
connect ur device to your computer to get
the software repair assistant
AP fastboot flash mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
Error: failed to pass validation. backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
pls Help by step by step methods I am Stuck.....Please
Click to expand...
Click to collapse
same thing for me, been weeks cant find any solution
Hello guys,
Sorry for my bad English
My phone just turned off even if the battery is almost full. When I turned it on its stuck in a boot loop. Sometimes it's goes to a screen where it would say process not responding. It's still on the stock ROM and recovery. I didn't try to root it or flash anything on it.
I tried some troubleshooting like flashing the firmware from the Asus website but it didn't work. Please help
Have you try flashing from Micro SD card in stock recovery?
M Huzaifah said:
Have you try flashing from Micro SD card in stock recovery?
Click to expand...
Click to collapse
Thank you for the reply bro. I already did and it's still not working.
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
you can install custom recovery?
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
After these commands, had to do a wipe data/factory reset prior to update from sd card (adb sideload not work at alll).
but no luck, keep boot looping...
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
sofamensch said:
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
Click to expand...
Click to collapse
this command result error:
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.802s
used this instead: fastboot flash boot boot.img (with boot.img extracted from firmware)
target reported max download size of 268435456 bytes
sending 'boot' (24547 KB)...
OKAY [ 0.813s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.550s
but my case is serious, giving up
maybe you should unlock the bootloader before trying those commands
why don't u try, adb sideload option once, give it a try
i dont know what firmware my dads ze550kl is...
and it is bootlooping continously....
what is best files to flash via recovery update from sd card method?
i want to save my dads internal memory
Try this:
fastboot boot recovery.img
Click to expand...
Click to collapse
This may result an error if you don't flash the right file,it depends on your firmware version. I have a file that works on lolipop (twrp.).
I had the same issue, as my device was on warranty period i took it to the service centre and they said the mother board is damaged
Im facing the same problem I installed a new ROM from SD card and it was successfully done but the phone is still stuck in boot loop and unfortunately my USB debugging is disabled my bootloader is locked and my phone is not rooted and it's in stock recovery can anyone please help me
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
I face the same bootloop problem with my mother's cellphone. The bootloader is locked and USB debug is disabled.
I tried to flash stock img via adb sideload, and although it succeed, after factory reset in Recovery (and pull battery several time) I could finally get into the "setup wizard" of Android system.
However, the system will go into bootloop again when the wizard goes to "wifi" setup. The phone will not go into setup wizard again unless I do a factory reset (and battery pull) again...
It seems there are some hardware failure at Wifi component (Since I already erase all \data, \cache), and this failure caused reboot of the system...
Any idea?
mayankarya837 said:
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
Click to expand...
Click to collapse
hey did u finnd any solution for this>???
hello all,
my yureka(a05510) CAN boot into bootloader and recovery,
Ive tried flashing roms, different recoveries(twrp v3.00 and 2.8), formatting data, mount, resizing partitions, annabathinas method, flashing fastboot images(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) through fastboot commands and batch files like flash-all.bat (lots of times) and even YGDP method for flashing stock firmware(gives unknown error:5 last error:997 msg: CP8675_I02_P1 , download failed please try again.) i even tried writing emmc img to micro sd(i believe used when phone does not boot into fastboot mode, though NOT my case) and hoped it would change something but that failed too.
please help. thanks in advance.
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Pranay_619 said:
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Click to expand...
Click to collapse
Fastboot erase system
Fastboot erase cache
Fastboot erase userdata
Sent from my AO5510 using Tapatalk
When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.