First off, the original thread is here: http://forum.xda-developers.com/showthread.php?t=1950232
It looks like some users are having an issue with the following results:
1. Unable to boot into Fastboot - HAS SINCE BEEN FIXED
2. Unable to wipe/flash from CWM
3. Unable to wipe /cache or /data
We aren't sure if this is a hardware issue or a software issue, but we are trying to figure it out.
I am running Epinter CM10 (from early september), and I hadn't flashed a new version of the rom since then. A couple days ago my phone started giving me a bunch of errors (application crashes) so I decided to update to the latest version and wipe. After wiping, and flashing, I rebooted and everything looked the same. All my applications were still on lancher and all my texts were there. So it clearly didnt work, when I went back into CWM I tried wiping specific partitions manually and found there were errors when trying to format /data and /cache. Trying to reboot into Fastboot it gets stuck at "starting fastboot protocol support", and never is detectable from command prompt.
My first question - Are there any ways to wipe the Atrix outside of CWM and Fastboot? Would flashing a SBF from RSD do anything? (I am already rooted which you probably knew from the fact im running epinter CM10)
Has anyone found themselves in this situation and found a fix?
Thanks for your help.
Firstly, questions go to the Q&A section.
Secondly, I've faced this issue a few weeks ago where nothing happens when I wipe everything and flash a new ROM. But miraculously my restore worked and then everything went smooth after that. I came from Epinter's CM10 as well, I restored to Maxblur I think. Now on MROM, flashing still works.
If you have the time and are desperate to flash something, you can try to SBF back to your previous firmware. Only problem is, you might need to wipe you phone using... fastboot.
I'm not sure though, it might be a hardware issue.. Besides, my digitizer is failing and my wifi disables and locks itself every now and then...
Edit: Reading you post in that other thread, you mentioned that your phone went into "starting USB protocol". Do you have the correct drivers loaded on your computer? Have you tried reinstalling CWM or another recovery?
Sent from that Atrix.
Thank you for your reply. The reason I moved it here was that some others had this issue with epinter and it straddled the lines of Dev and Q&A, and there wasn't much exposure on the Q&A forum and it seemed that others using epinter were having this issue.
1. I will try a restore and report back on if that worked (I tried restoring before which resulted in a failure when it gets to /data)
2. I will double check fastboot is properly installed.
3. I will also try flashing the CWM non-touch version
**Edit**
Update to item 1:
I tried restoring a backup on CWM and got the following log:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while formatting /data!
boot in fastboot your atrix. power on + vol down, then when show fastboot press vol up. then in windows cmd write this commands.
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (reboot to recovery)
Flash ROM.
if doesnt work try with moto-fastboot program and moto-fastboot commands, mine atrix worked fine
try installing another recovery i get this same error its work for me
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
sjbayer3 said:
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
Click to expand...
Click to collapse
I always thought we needed to use moto-fastboot, not just fastboot.
I also used romracers recovery and then Th3Bill's Full_Wipe flashable wipe tool to recover from a similar situation.
Good luck.
Okay.
I found moto-fastboot, and using that STILL nothing gets wiped.
I tried flashing the non-touch recovery, and well it shows everything success... but when I open recovery its still the touch recovery.
It just seems like something is locking me out from doing any wipe or flash to my phone, I am just baffelled that nothing has worked so far.
Trying to format from fastboot and I got this output, type ".FAILED ()" certainly doesn't sound good.
C:\Users\ofsstbay>fastboot format userdata
formatting 'userdata' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.014s
C:\Users\ofsstbay>fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.012s
C:\Users\ofsstbay>fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.010s
In addition, when I flash recovery:
C:\Users\ofsstbay\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-oly
mpus.img
sending 'recovery' (4824 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.125s]
finished. total time: 0.415s
On the phone screen it says:
Flashing partition recovery
Flashing StorMgr partition: SOS
Belongs in Q&A. I closed other one since this has more replies. There aren't any exceptions for organization on the forums. Please do not post questions in Development even if they "straddle the lines." Thanks!
Same issue here! I was on uriels awezome rom when it happened. I've tried fastboot, and even rsd lite wiping everything at once, individually to no avail.
Well I even tried going through the originaly root unlock and recovery flash and still didn't do anything. None of my backups work either still
any one figure this out yet??? I can't think of anything else to try myself.
is it possible that the internal sd is corrupted and possible the data partition as well?
I was thinking the internal card was corrupt as well.
Is this something that can be removed and replaced or is it built into the board?
i looked that up. I saw a different phone where it is removable but not necessarily replaceable. I know there is a way to use the sd card as the internal but the directions are above me. I wish some devs were reading this thread. Doesn't seem like it's got enough interest from the people who could really help.
Be nice if we knew what caused this. I don't know what the three of us could have done to cause these problems. I have scoured google for answers and ways to repartition and tried so many things and I am giving up.
Hi guys,
So, I'll start by saying I haven't seen this problem before. And, if I had to venture a guess, I'd say your hardware is borked (not being able to format is a big clue).
But, there are some things to discuss and try before you use your devices as paperweights.
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
Third, I recommend avoiding touch recoveries. The best ones are still sketchy and it is very easy to do things accidentally. There is a reason that button CWM makes you scroll through 10 "no" before you get to "yes".
__________________
Please do the following:
1) Ensure that you are in fact running the correct version of fastboot with the correct drivers for your PC. Be 100% certain.
2) Enter fastboot mode and do "fastboot devices" (no quotes) and make sure your device is recognized.
3) If your device is properly recognized, try this:
a) "fastboot erase cache"
b) "fastboot erase userdata"
c) "fastboot erase boot"
d) "fastboot erase system"
e) "fastboot reboot"
After fastboot reboot does your device boot to OS, or stay on the boot logo? If your device stays on the boot logo, you wiped your OS (which is good).
Next install the most recent CWM button recovery.
If that works, flash a stable ROM. Nothing experimental - try a stock GB ROM (fruit cake, NottachTrix, etc.) or CM7 and see how things go.
There is some useful fastboot information available here.
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
upndwn4par said:
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
There is some useful fastboot information available here.
Click to expand...
Click to collapse
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
boonemeat said:
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
Click to expand...
Click to collapse
sjbayer3 said:
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
Click to expand...
Click to collapse
No. A newer version is fine, as long as you are using the correct drivers.
______________
What Recovery were you both using? I think one of you mentioned touch CWM.
______________
Have either of you tried Th3Bill's wiping tools? (I use them all the time)
Another way to install recovery would be via ROM Manager.
hi folks,
I wanted to update on lollipop but no success.
I don't know why but my Z2 (locked bootloader, rooted, 4.4.4. custom rom, philzdualrecovery) don't work as it should.
In flashtool I stuck in "reading device information" by flashing a stock rom.
In recovery (TWRP or PhilzTouch) I cannot format all my partitions. System, cache and boot did work but data not!
(I formatted system, cache and boot for preparing for a new rom.)
I see "/data" as an empty partition with 0 MB size. What happened? Entering recovery only works with an insered SD Card. Fastboot mode works also.
I tried to erase partitions but fastboot-cmd said "failed: remote command not allowed" (or something like that).
Have you any idea? Do you need more information?
Thanks alot!
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Gleichzwei said:
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Click to expand...
Click to collapse
Boot to bootloader, and enter the following commands:
fastboot format cache
fastboot format userdata (NOTE THAT THIS WILL WIPE THE CONTENTS OF YOUR SDCARD)
fastboot reboot
In trying to encrypt my phone under one of the latest nightlies of CM13 the encryption process failed but left TWRP trying to unlock a corrupted system partition.
So I can't get into TWRP and my system tries to infinitely load.
Is there a way to fix this soft brick?
Can I just fastboot erase (system, cache, data?) some partitions so they're clean and TWRP tries to start so
I can flash a good rom from my memory card?
And does TWRP actually store anything essential to TWRP on any of those partitions? (system, cache, data?)
And are there any other partitions I need to wipe to ensure a unencrypted system so TWRP finds nothing
exisisting to unlock and just tries to start up looking at a empty system?
Actually format[:[<fs type>][:[<size>]] <partition> is what I'd need to use isn't it?
fastboot format system
fastboot format cache
fastboot format data ?
So yeah i'm a right that this is all i need to do to fix my device is fastboot format the partitions,
or will it make the situation worse?
But at this point without the security of a recovery I really don't want to blind shoot and try and fix without out atleast running it by someone asking if it's a good idea, I'm still a little 'green' with Android.
For all I know TWRP keeps some essential files on atleast one of the major partitions, and
may go into a worse state of I format them to remove the encryption, but right now it seems
like the fix, and i know that doing a full clean format on my device will remove encryption
as I've had my device successfully fullly encrypted many times and this is the first nasty issue
I've run into on doing a total clean upgrade and then encrypt.
Shouldn't have screwed around without it forgetting I need to receive a call on it in the morning. >_>
>_< never mind I can click the cancel button and access TWRP without mounting the partion (hello), well
if anyone would have replied thanks anyway, I figured out the problem myself.