Hi there, i have spent hours trying to recover my Moto G XT1032 using this forum and I have mad progress but my phone is still dead.
Phone:
Motorola XT1032 - it was the latest stock ROM, always updated to the newest version. (Very probably a non-branded EU retail, 5.1 ROM)
Problem:
Battery got drained. When put on charger, it was 'optimising cache app x of y' for a long time, sometimes it does this anyway.
Then it went into bootloop, stuck at the Motorola logo. It doesn't restart and the logo doesn't starts animating like it normally does.
Fastboot (Power + vol down) worked, but going into recovery failed, leaving me stuck with the same M logo.
Solutions tried:
1. Connection to computer: didn't work. Seen as 'fastboot device' when in fastboot but that's it.
2. Using Android recovery software. Useless because of the above and useless pieces of software anyway. :D
3. Re-flashing stock ROM. After installing Motorola drivers and mfastboot, I tried to flash FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC, and according to the phone it was successful, but it still left me stuck at the bootloop. Even after manually flashing everything from partition tables to system images.
4. I unlocked the phone to install a custom TWRP recovery. The unlock was successful.
5. Tried to install TWRP recovery - to recover my files at least -, the command line says success, the phone says 'partition size mismatch'. Many have said in this forum to ignore this message - well, I can't since it can't write the recovery partition.
6. At this point the factory recovery started working ('no command' screen, then pressing 'vol up + power') :confused:
7. I have been able to boot into TWRP with
What a workaround! Well, I have at least been able to access my files over MTP. Yay! :fingers-crossed:
8. Here comes the problem: I can't wipe the device. I can't copy anything over MTP. I can't delete files over mtp: it looks like the files are deleted but they reappear after restarting the device.
Note: I can access a simple
in recovery.
So once again, I'm unable to install a custom recovery via mfastboot, and it looks like the whole device was write-protected for whatever reason. At least I've been able to save my data thanks to the useful resources here! Any ideas about what else I could possibly try?
Any help is much appreciated!
Phone:
Motorola XT1032 - it was the latest stock ROM, always updated to the newest version. (Very probably a non-branded EU retail, 5.1 ROM)
Problem:
Battery got drained. When put on charger, it was 'optimising cache app x of y' for a long time, sometimes it does this anyway.
Then it went into bootloop, stuck at the Motorola logo. It doesn't restart and the logo doesn't starts animating like it normally does.
Fastboot (Power + vol down) worked, but going into recovery failed, leaving me stuck with the same M logo.
Solutions tried:
1. Connection to computer: didn't work. Seen as 'fastboot device' when in fastboot but that's it.
2. Using Android recovery software. Useless because of the above and useless pieces of software anyway. :D
3. Re-flashing stock ROM. After installing Motorola drivers and mfastboot, I tried to flash FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC, and according to the phone it was successful, but it still left me stuck at the bootloop. Even after manually flashing everything from partition tables to system images.
4. I unlocked the phone to install a custom TWRP recovery. The unlock was successful.
5. Tried to install TWRP recovery - to recover my files at least -, the command line says success, the phone says 'partition size mismatch'. Many have said in this forum to ignore this message - well, I can't since it can't write the recovery partition.
6. At this point the factory recovery started working ('no command' screen, then pressing 'vol up + power') :confused:
7. I have been able to boot into TWRP with
Code:
mfastboot boot twrp-3.0.0.0_2-falcon.img 8. Here comes the problem: I can't wipe the device. I can't copy anything over MTP. I can't delete files over mtp: it looks like the files are deleted but they reappear after restarting the device.
Note: I can access a simple
Code:
adb shell So once again, I'm unable to install a custom recovery via mfastboot, and it looks like the whole device was write-protected for whatever reason. At least I've been able to save my data thanks to the useful resources here! Any ideas about what else I could possibly try?
Any help is much appreciated!
from xda-developers http://ift.tt/28RoMiS
via IFTTT
No comments:
Post a Comment