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.
Related
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
S-OFF HBOOT 1.93.0002
Mobilicity Stock ICS Rooted
4EXT Recovery
dpsi said:
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
Click to expand...
Click to collapse
Did you try boot into recovery & delete unwanted data?
dpsi said:
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
Click to expand...
Click to collapse
I'm going to list the following commands you should do. I assume that you know how to use Fastboot and the like and already have the drivers set up. If not, there are threads out there that explain in detail on how to do that.
Ensure the battery is fully charged before doing anything
Take out the battery and reinsert it. Hold the Vol Down button and press power button. This will take you into bootloader mode. Use the Volume Up/Down buttons in the bootloader mode to boot into FASTBOOT mode. You will know if you're in the fastboot mode when you see the text "FASTBOOT" highlighted in RED. If you see the text "BOOTLOADER" highlighted in BLUE, you are NOT in fastboot mode.
After you have entered fastboot mode, plug in the usb cable. The highlighted "Fastboot" text should change into "Fastboot USB". After that, open the command prompt. You should have had the fastboot drivers set up before starting this.
Input the following commands EXACTLY (including their respective case):
fastboot erase cache
fastboot erase system -w
After that's done, reboot into recovery and re-install your ROM of choice. NOTE: Upon doing those fastboot commands, you will lose all of your data and your ROM on the phone.
crazykas said:
Did you try boot into recovery & delete unwanted data?
Click to expand...
Click to collapse
If formatting won't work, how do you think I can delete files?
Keylogger_0 said:
fastboot erase cache
fastboot erase system -w
Click to expand...
Click to collapse
Code:
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.000s
Any other ideas?
dpsi said:
If formatting won't work, how do you think I can delete files?
Code:
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.000s
Any other ideas?
Click to expand...
Click to collapse
Run this tool http://forum.xda-developers.com/showthread.php?t=1762936
Take note that this installs a tmobile ruu so you need supercid. Be sure to follow instructions.
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
Run this tool http://forum.xda-developers.com/showthread.php?t=1762936
Take note that this installs a tmobile ruu so you need supercid. Be sure to follow instructions.
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
That did it, thanks.
Had a problem where I was stuck on the htc logo loading screen. I assumed this was because I had been tinkering with mods and screwed up the whole rom, but after downloading a new version of android revolution hd and using the adb push command to put it on my internal storage, even after flashing it, i am still stuck on the htc loading screen.
if i can run the clockwork recovery mod or bootloader, but cannot get past the htc loading screen, does that mean the phone is broke?
also ive noticed the bootloader says unlocked "tampered" i dont know if thats significant, but i didn't notice it before.
i have googled this problem and the only reference i could find, was a few articles about the rom being corrupt and instructions how to flash a new one (which ive already done anyway)
i presume the phone is broke?
pontypool said:
Had a problem where I was stuck on the htc logo loading screen. I assumed this was because I had been tinkering with mods and screwed up the whole rom, but after downloading a new version of android revolution hd and using the adb push command to put it on my internal storage, even after flashing it, i am still stuck on the htc loading screen.
if i can run the clockwork recovery mod or bootloader, but cannot get past the htc loading screen, does that mean the phone is broke?
also ive noticed the bootloader says unlocked "tampered" i dont know if thats significant, but i didn't notice it before.
i have googled this problem and the only reference i could find, was a few articles about the rom being corrupt and instructions how to flash a new one (which ive already done anyway)
i presume the phone is broke?
Click to expand...
Click to collapse
you just need to clear the cache
fastboot erase cache
C:\fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\fastboot>
Click to expand...
Click to collapse
clsA said:
you just need to clear the cache
fastboot erase cache
Click to expand...
Click to collapse
already did that and the other cache dvlaik or something. i think this is probably worse than a software problem.
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now
Hello all, I recently started the process of rooting my HTC One X+ and it all went smoothly until it came time to flash a recovery.
I used Windroid Universal toolkit to get started, thinking it would make things easier (not that I haven't rooted a phone before).
I unlocked the bootloader just fine, in the bootloader it gives "*unlocked*".
Next, I tried flashing TWRP with the toolkit, it brings me to bootloader, but when going to HBOOT and hitting recovery, it just brings me back to bootloader. Hmm, weird. So I decide to do it manually, download latest TWRP for evitareul (2.8.5.0), reboot into fastboot.
Execute: fastboot flash recovery twrp-2.8.5.0-evitareul.img
and it gives me this:
"sending 'recovery' (8224 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.153s"
I don't know whether it matters, but when going into HBOOT it pops up with some errors saying something along the lines of unable to access SD or something. It goes too fast to really write it down.
So I think maybe deleting cache would help, and to no avail. I look up online for the error code and nobody seems to have an answer for it. I apologize if this has been answered elsewhere on the forums, I looked for quite some time before posting a new thread. I'm not sure what is going wrong.
My end goal was to flash recovery, make a back up, then flash superSU but if I can't flash recovery then I'm not going to do anything else and risk a brick.
Does anyone know what's up with this error and how to fix it?
You're flashing a wrong recovery.
Coolgoly said:
You're flashing a wrong recovery.
Click to expand...
Click to collapse
What recovery should I be flashing then? My device is Evitare_UL, and I am getting img files from
HTML:
https://dl.twrp.me/evitareul/
.
I have tried other versions to no avail.
Evitareul should only have 2.5 TWRP out....