Persistent bricking of a Moto G XT1040 LTE
I'm happy to PayPal $20 to anyone who figures this one out...
One day it was working, and then - it froze and went to the loading screen and stayed there. I've unlocked and rooted and used for months with no issue. I've tried everything I can find to fix my Moto G LTE gen-1 XT1040, and I'm at my wits end.
It works, in the sense that I can load fastboot, and I can load CWM (I cannot load any version of TWRP), but I can't get into an operating system. I've tried flashing the stock OEM, I've tried flashing lolipop, slimkat, cyanogenmod - no luck with anything. It does not load into recovery (stock, CWM or TWRP) but can load CWM with "fastboot boot cwm.img" (fastboot flash boot cwm.img then booting into recovery fails).
It looks like some parts of the cyanogenmod flashing stuck, but since then nothing else seems to do anything. Also, the system partition seems to be "raw" when I try to use it - I can't delete my user data (things have persisted despite wiping commands from fastboot and in adb and in CWM). It looks as though anything I'm trying isn't "sticking". I've tried to be as detailed as possible with screenshots.
Maybe: corrupted system partition? somehow things are "locked"? should be hardbricked and then reinstalled as device driver? hardware issue?
All images / screenshots / logs with details are here: imgur.com/a/dQQGD
Any suggestions, tips, advice on this one? Your help would be very appreciated.
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
lost101 said:
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
Click to expand...
Click to collapse
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
canwond said:
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
Click to expand...
Click to collapse
I was under the impression the appearance of partitions being 'raw' was just another symptom of corruption. I gave some ideas to try regarding formatting in the later posts of this thread.
Look for an XT1040 with broken screen, but still functional; as a cheap way to get a motherboard.
Related
Does anyone have tips on extracting RFS images on a Linux box?
So far everything I've found on extracting RFS images indicated to either:
1) Use MagicISO/PowerISO - these are proprietary Windows tools, I'd prefer not to have to reboot or move to another machine
2) Mount it as a VFAT filesystem - this didn't work for me last time I tried it
Any other suggestions? It's not something I usually bother with as I'm almost always doing kernel work or working with already-extracted userland filesystems, but with all of the AT&T Gingerbread leaks coming out I'd like to be able to analyze these without waiting for someone to CWM it up.
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
LinuxBozo said:
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
Click to expand...
Click to collapse
That's what I tried before (see 2) above) - didn't work. Tried both autodetect and forcing vfat.
Maybe just that particular RFS image (was one of the ones from gtg's Ultimate Unbrick packages) was wonky... Will try again tonight with I3/I4.
Works Here (TM) ;-)
LinuxBozo said:
Works Here (TM) ;-)
Click to expand...
Click to collapse
Weird. Whatever RFS image I was trying to mess with last time around must've been mangled... UCKI3 mounts fine.
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Dani897 said:
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Click to expand...
Click to collapse
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
LinuxBozo said:
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
Click to expand...
Click to collapse
Ok so if I wanted to release an Odin package it would mean dumping it from my phone then. Gotcha!
Thanks.
Hello,
I recently rooted and installed a custom ROM CM10 nightly onto my transformer, and proceeded to wipe data as normal. I went to do it, and it was taking a long time, 5-6-7-8 mins passed and I thought something is wrong. So I force turned it off. Not that all it said for that time was "formatting /data..." or something.
Well, it failed to boot as expected, so I tried wiping again with no luck. Went and flashed TWRP recovery and it's showing errors:
E:Unable to mount '/data' (tw_mount)
E:failed to mount /data (Invalid argument)
I'm not sure how to proceed due to lack of knowledge. I noticed there's a file manager and terminal on this recovery so perhaps it can be fixed using those, or ADB or something.
Either way, I would like to request help from the TF300T community.
Thanks in advance,
Kris
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
linkandzelda said:
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
Click to expand...
Click to collapse
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
ogredeschnique said:
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
Click to expand...
Click to collapse
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
How can you Wipe Data, if the /data isn't/can't be mounted?
I'm having this same issue with my RazrMaxx...
I posted my issue here: http://forum.xda-developers.com/showthread.php?p=35222826#post35222826
Z1013 said:
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
Click to expand...
Click to collapse
Well, in my opinion, I think the rom wasn't readable or working. If you have taken a backup before flashing the nightly rom, you can restore it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
Just did this with my tf300t last night. Do you still have the blob files?
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!
devcor said:
Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!
Click to expand...
Click to collapse
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.
nbrian2012 said:
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.
Click to expand...
Click to collapse
I did. With, without it. I reflashed different roms hundreds of times.
you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus
chongns said:
you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yeah, I tried, but it only reloads recovery for some reason.
Any ideas?
I have a serious problem with my Elephone P6000 (MTK6732). Following a freeze, it seems my internal storage got corrupted. After a few attempts at fixing the issue by wiping and formatting in recovery, I resorted to a clean flash through SPFT. SPFT looks like it's working, but I suspect it's not actually writing anything, because:
- the format part of the operation is way too quick
- I am not injecting a custom recovery in the scatter file, but my custom recovery remains functional on the phone
- nothing changes in terms of normally booting the phone (i.e. it doesn't)
I have some I/O errors in dmesg, and I very well understand this could simply be a case of hardware failure that no amount of hacking can fix, but I read this is not always the case so I am still giving it a shot.
I also tried using parted via adb, but the changes I make don't seem to persist. I can still mount and unmount /cache and /system and their contents don't appear to be damaged. I wanted to give SP Multiport Flash a shot, but it complains about the COM port and I can't figure out how to set it properly.
Is there anything left to try or should I assume it's indeed a hardware problem? SPFT not working really concerns me. Would a nandroid backup help? I think I made one a few months ago and I am looking for it on my PC but I haven't found it yet. For clarity, I can still boot into Fastboot and CWM, I can still use a shell via ADB and SP Flash Tool still talks to the phone.
Forgive me fot bumping this but it would be great to get some help.
Hi,
You've asked in the correct section: http://forum.xda-developers.com/android/general/p6000-thread-bug-fixes-faq-info-t3028845
so I'll close this thread.