Database Info

[Q] How long should the Wipe data/ factory reset take?

from CWM? I started it 20 min ago and every time I look at the screen it says:
-- Wiping Data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E;format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure

Terra27 said:
from CWM? I started it 20 min ago and every time I look at the screen it says:
-- Wiping Data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E;format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
Click to expand...
Click to collapse
It happens in seconds. last time it happened to me i had to odin. i suggest using ayoteddys cmw3xx

How do I acquire that? Sorry I'm very new to phone dev

Terra27 said:
How do I acquire that? Sorry I'm very new to phone dev
Click to expand...
Click to collapse
nahh no problem dude, i know what its like to soft brick your phone so ill help to the best of my knowledge. http://forum.xda-developers.com/showthread.php?t=1126631 it's here. on teddy's first post. so pretty much, you would download it, put it onto your phone which is the /sdcard part, then 'flash it' (fancy word for install) by going into cwm mode, and going to install .zip from sd card, find the cwm3xx file at the bottom, then flash it. THEN it'll pop up a 'new' cwm mode and from there factory reset, reset the cache, go to advance and erace dalvil cahe and check your mounts, then flash the new rom..if your trying to flash a rom that is lol. if you have questions post away!

oh and i think this should go in the general section.

Im stuck on the Sidekick/Tmobile/Samsung screen now and it will vibrate once, then 3 times then wait 3 seconds then vibrate once then 3 times etc.. WHy?? is it bricked now?

Terra27 said:
Im stuck on the Sidekick/Tmobile/Samsung screen now and it will vibrate once, then 3 times then wait 3 seconds then vibrate once then 3 times etc.. WHy?? is it bricked now?
Click to expand...
Click to collapse
its soft bricked you have to odin!

tylermaciaszek said:
its soft bricked you have to odin!
Click to expand...
Click to collapse
Yeahh that happened to me too, and i had to odin, but it wouldnt read the phone so i had to uninstall and reinstall the drivers on my comp. then go into download mode and odin.

Yup, that kept happening to me.. Im gonna try and install this cmw now.. By the way, do i still have to check the mounts and storage because i've successfully installed the maximus rom gingerclone. Do i have to check mounts and storage everytime i need to flash a rom, if so what should they be, as far as Data, sd card, cache, and system etc..?

Blaggah said:
Yup, that kept happening to me.. Im gonna try and install this cmw now.. By the way, do i still have to check the mounts and storage because i've successfully installed the maximus rom gingerclone. Do i have to check mounts and storage everytime i need to flash a rom, if so what should they be, as far as Data, sd card, cache, and system etc..?
Click to expand...
Click to collapse
no you do not have to check!

Yes you do need to check! Not checking is what makes you soft-brick.
it should read:
System: Unmount
Data: Unmount
Cache: Unmount
Anything else isn't an issue.
Don't worry about the errors reading that cache file, they happen to everyone, it's part of the kernel.

sduvick said:
Yes you do need to check! Not checking is what makes you soft-brick.
it should read:
System: Unmount
Data: Unmount
Cache: Unmount
Anything else isn't an issue.
Don't worry about the errors reading that cache file, they happen to everyone, it's part of the kernel.
Click to expand...
Click to collapse
i thought once your on the red recovery you don't need to check! i never check....

terra i'm having the same problem you are. keep this thread in mind http://forum.xda-developers.com/showthread.php?t=1214432 hopefully i'll be getting a response soon. orange cwm is my nightmare

Please help!
I am getting this error on my sidekick 4G
E:format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
i was trying to upgrade to Lite'ning ROM but it gave me this error, i did already ODIN to stock and it did not work and what i mean by it did not worked i did get to stock and started from scratch but still getting the same errror..... any other suggestions?

Don't worry about that error, that just means that you don't have an android secure partition on your sdcard. nothing to worry about.
I don't see why red CWM would be any different from Orange CWM in having to check mounts... I always check my mounts, and have always had to.

well u say not to worry but i can't update the rom to the lightning rom b/c i cannot factory reset, if i don't factory reset, phone bricks

You don't have to factory reset, just make sure you check your mounts. that's why it's bricking.

ok... so what are the mounts?

Please see thread: [RECOVERY] CWM for the SK4G. Enjoy!
therion0 said:
I am getting this error on my sidekick 4G
E:format_volume: make extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure
i was trying to upgrade to Lite'ning ROM but it gave me this error, i did already ODIN to stock and it did not work and what i mean by it did not worked i did get to stock and started from scratch but still getting the same errror..... any other suggestions?
Click to expand...
Click to collapse
Please see thread: [RECOVERY] CWM for the SK4G. Enjoy!
You will find in the OP (original post #1) there is a step:
CWM Final
http://www.krylon360.com/file_host/sk4g/update.zip
Place in the root of your SD.
After your in clockwork mod recovery (orange) (and have downloaded the update.zip to sd card) make the selection: -apply sdcard:update.zip (this will load cwm again (red cwm)
Now: reattempt!

sgs4g BRICKED help!

Getting a E: failed to mount /data (invalid argument)
e:\format_volume: rfs format failed on /dev/block/stl10
on samsungs recovery screen. it boots up only in to here not OS
had OC'd my phone using method in bible and my phone froze and wouldnt boot. tried to just odin a new kj3 and this is where i started to notice the brick.
I also tried a method by krylon which he provided me PIT file and to odin with partition checked and didnt help.
I think my partitions are all wacked. Anybody have a fix for this?
In the vibrant forums there are fixes with the exact same issue but i cant find any on sgs4g forum. And I obviously dont want to flash vibrant files. Their fix requires a odin pit file with partition checked.
Thanks!!

I have had this happen to me. I all I did was reformatted and partioned the drive using pc. The program is called magic something. Do that then ordinary and you should be good as new.

It's not bricked if it still turns on.
Sent from my SGH-T959V using XDA App

droodski said:
Getting a E: failed to mount /data (invalid argument)
e:\format_volume: rfs format failed on /dev/block/stl10
on samsungs recovery screen. it boots up only in to here not OS
had OC'd my phone using method in bible and my phone froze and wouldnt boot. tried to just odin a new kj3 and this is where i started to notice the brick.
I also tried a method by krylon which he provided me PIT file and to odin with partition checked and didnt help.
I think my partitions are all wacked. Anybody have a fix for this?
In the vibrant forums there are fixes with the exact same issue but i cant find any on sgs4g forum. And I obviously dont want to flash vibrant files. Their fix requires a odin pit file with partition checked.
Thanks!!
Click to expand...
Click to collapse
The method I gave you does work. I know because I made it happen last night. had voodoo enabled, ODINED KH2 (with sbl) and stock KH2 kernel, and the Pit that I pulled off my phone, it rebooted me into stock recovery, with the same error. I did a factory reset through recovery, as well as wiped cache. I still had the same error, but when I rebooted the phone (through recovery) everything came up just as it should.

i appreciate the help you've given me krylon, and i do believe you. how ever im not sure why its not working for me i also tried what you just posted. what does (with sbl) mean? when i try rebooting from the stock recovery after factory reset and cache wipe, it says cant mount data rebooting and just reboots back in to recovery, im also getting errors on factory resetting
@HB66 what do you mean ordinary? is that a program
and it will actually wipe the internal drive?

I got the rainbow screen when i boot into download mode and my phone wont rebboot fully

Sorry I ment odin but the phone got it wrong.

You need gb bootloader, odin the kernel, and kg4 should fix it. The flash your rom

Try unchecking repartition if you get that error again...
Sent from my SGH-T959V using XDA App

@HB66 now is the program called nortons partition magic? it formats and detects the internal HD? are their any steps i need to know

champ1919 said:
Try unchecking repartition if you get that error again...
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
tried that

Will pay
will pay to who ever gets this working for me!
we can gmail chat or whatever if some one wants to help

What ROM did you have on there before?

Well? Still broke or not? Suspense is killing me....
Sent from my SGH-T959V using XDA App

We PMed a bit and it's fixed. The gist was that he formatted the SD card (he was following an earlier suggestion) and he ODINed the KG4 leak that has the right bootloaders, PIT, CSC, Phone, & PDA file.

Oh Oh
stephen_w said:
We PMed a bit and it's fixed. The gist was that he formatted the SD card (he was following an earlier suggestion) and he ODINed the KG4 leak that has the right bootloaders, PIT, CSC, Phone, & PDA file.
Click to expand...
Click to collapse
Can you help me too? Yes, this is an old post but i'm having the same problem. Tried to return to Stock rom & i soft brick.
I get an E: failed to mount /data (invalid argument)
E: delete_data_files:Can´t mount/ data your storage not prepared yet. Please Ui men u for format an reboot actions
e:\discard_filesystem_for_rfs: Can´t mount/ data
I tried installing stock but it never boots, actually it boot loops on Samsung logo.
Any idea how to fix it?

Jordaliz09 said:
Can you help me too? Yes, this is an old post but i'm having the same problem. Tried to return to Stock rom & i soft brick.
I get an E: failed to mount /data (invalid argument)
E: delete_data_files:Can´t mount/ data your storage not prepared yet. Please Ui men u for format an reboot actions
e:\discard_filesystem_for_rfs: Can´t mount/ data
I tried installing stock but it never boots, actually it boot loops on Samsung logo.
Any idea how to fix it?
Click to expand...
Click to collapse
Do a factory reset in your recovery.

Emmm...
jd1639 said:
Do a factory reset in your recovery.
Click to expand...
Click to collapse
I've tried that but i get this error:
e:\format_volume: rfs format failed on /dev/block/stl10
Seems useless to reset through recovery.

Reflash. Sounds like lagfix was on when you did whatever you did.

ok so i was switching from audiophile to "rcs unnamed rom??" and then back to audiophile again because something wasnt rtight when i got the second rom running...i had it going before its not the roms fault i did something wrong....then i made ANOTHER mistake going back to audiophile. So its stays stuck on the logo screen forever i waited an hour or two and pulled the battery. every time after that i would get stuck at the samsung logo screen...so i boot into recovery and flash a nandroid backup of audiophile....now its really f'd i cant get past the "asterisk" symbol that shows up right before the "charging battery bar" when i try to get into recovery or download mode if boot normally it stays stuck at the logo screen. need some help here....and odin doesnt see the phone...my pc sees it and calls it an unrecognized device.

[Q] Am i bricked?

I bought galaxy fit just a week ago and rooted it 4 days ago. It worked fine after rooting.
Today, i was trying to install an update.zip with DSP manager and i got this message
"finding the package ....bla bla bla
installation started
installation aborted"
I thought i failed and selected to reboot the device. Now my phone is stuck at a screen with "SAMSUNG" written on it and vibrates every now and then.
** i see the boot animation
** I can enter the debug (or whatever) mode. Where we can update from an update.zip and reset
So my question is "AM i bricked??? How do i recover?

tvirus7 said:
I bought galaxy fit just a week ago and rooted it 4 days ago. It worked fine after rooting.
Today, i was trying to install an update.zip with DSP manager and i got this message
"finding the package ....bla bla bla
installation started
installation aborted"
I thought i failed and selected to reboot the device. Now my phone is stuck at a screen with "SAMSUNG" written on it and vibrates every now and then.
** i see the boot animation
** I can enter the debug (or whatever) mode. Where we can update from an update.zip and reset
So my question is "AM i bricked??? How do i recover?
Click to expand...
Click to collapse
Boot in Recovery " Home + Power Key "
Select "Wipe Data" or something like that in recovery and then reboot.

Is it possible to recover without wiping the data? I don't want to loose my customizations and apps on phone

tvirus7 said:
Is it possible to recover without wiping the data? I don't want to loose my customizations and apps on phone
Click to expand...
Click to collapse
I don't think so....
There is no way around this....

OMG!!!! i doesn't work!!
wipe data/factory reset -
Formatting DATA:...
Formatting CACHE:...
unmount (/cache) attempt 1
(unknown error: 0) rc=0
Data wipe complete
wipe cache partition -
Formatting CACHE:...
unmount (/cache) attempt 1
(unknown error: 0) rc=0
Cache wipe complete
When rebooted, it again stuck on the screen with "SAMSUNG" written on it. Does that mean i killed my phone?

naa
Flash cwm through odin , do backup through it, then flash a new firmware..
Flash cwm again and restore everything other than system through advanced restore.
That's what I would have done.
(At your own risk)
Sent from my GT-S5670 using Tapatalk

Can you give CWM zip?? the only method i found is through ROM manager.

http://forum.xda-developers.com/showthread.php?t=1277759
I havent tried out the zip method(if there is any)..Download cwm from above link and use odin to flash it in download mode(power+center+down volume button)
---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------
tvirus7 said:
Can you give CWM zip?? the only method i found is through ROM manager.
Click to expand...
Click to collapse
Do not use ROM MANAGER. You will brick your phone for real

Its not totally bricked. anyway flash clockworkmod and then flash another rom but first make sure you made a backup of your ROM through the Clockwork Mod so you can revert back to that rom from before and then flash a new rom and it should boot up.
like what the above poster said ^

Not bricked
Same thing happened to me last week
i installed creed's rom v1.0 via odin.
Cleared user data and wiped cache .
And it rebooted perfectly.

No you haven't bricked your phone dude....the same thing happened to me and all what I did was I reflashed CWM and then installed CM 7.1...and my phone was back to normal....
Sent from my GT-S5670 using XDA App

Problem installing Android KitKat (either Omnirom or Cyanogenmod)

Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!

toiel said:
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
Click to expand...
Click to collapse
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.

Same problem here
gooniegoogoo2 said:
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Click to expand...
Click to collapse
Same problem here... I can't properly do some of the advanced wipes in the process of trying to install omni.
I did as you suggested and tried wiping them individually but to no success.
I am definitely not as fluent in this stuff as a lot of you on here are, but I am competent/confident enough to follow good instructions.
Somebody help please!

Cant install KitKat Roms
I am having the same issue and have done the same thing. Tried installing both CM and OMNI with no success. the recovery is telling me the came thing that it cannot mount E:\ 'cache' and other files i need to wipe.
Some one please help.

i was wondering...
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?

But it worked before
ohDevious said:
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
Click to expand...
Click to collapse
I'm getting the same "can't mount cache" error when converting to Big Part - I had previously been running several Big Part roms, and had no problem with the conversion at that time - I then reverted back to stock (using VZW OTA's) for awhile, but want to give the Big Part roms another shot - I've tried several methods of reverting to stock, then coming back to install a 10.1 ROM, which is successful, but when I flash the Big Part TWRP and try the conversion, I get the cache mount error every time - I can revert to the "normal" TWRP, reformat, and re-install non-big part roms without a problem - help us Obi Wan! WTF?

I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
Click to expand...
Click to collapse
I forgot to mention click the format data tab under wipe and type yes.

I just had this same experience. I think the directions are somehow missing a step or we're misreading it.
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
I forgot to mention click the format data tab under wipe and type yes.
Click to expand...
Click to collapse

A day not spent well
I am having the same issue all of you guys are having. I had 10.1 stingray (4.2.2) running well and thought it was time to try Kit Kat. Both the ROMs wind up the same way, a loooong running splash screen (over an hour before I manually rebooted). Over and over no mater how many ways I tried to wipe the XOOM I kept getting the Can't mount the cache message. I was able to revert back to 10.1 but I can't figure why others can make the install and we cannot. I have asked others on the forum but no one can answer the question?
Anyone? Thanks! Paddy

I was finally able to figure this out last night. I was looking at my cache and data formats and both were formatted as f2fs. I believe it's under wipe in the latest TWRP (2.7.1.0), there's an option on the left that shows you the format type of your drives. On non BigPart TWRP I changed the cache and data to ext4. Rebooted back into recovery, and followed the guide posted here to apply BigPart to my Xoom: http://forum.xda-developers.com/showthread.php?t=2506997 :: Then I was able to load Omni BigPart edition with no issues at all. I'd be happy to give more details if anyone wants. I'm in the office now, otherwise I'd post some snap shots. I'll update this when I get home.

has anyone recovered from the "unable to mount cache" error? I have followed all the information in this thread, checked out the relevant links all to no avail.
The only additional data I can provide is that when I go into the wipe menu (TWRP 2.7.1) / advanced / select cache / and "repair or change" I have all 0's for the cache size MBs. Repairing the cache or changing file system claims to be successful, but it's always 0 MBs. For grins I tried all of the above with TWRP 2.6.3 and had no better results.
Thanks in advance.

Nexus 5 stuck in boot loop animation (MMB29V Marshmallow)

no power button problem
without any reason the phone rebbot itself and stuck in boot loop animation....stock MMB29V Marshmallow , no root, only unlocked
tried:
-wipe cache and data
-reinstalling all singles images files
-reinstalling with flash all bat and finally it works...
what's the problem???
and now? there is something to check? have to change the phone???
tnx

Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.

Ok but i need ti know if is possible to check the health device status

What do you mean by health? You mean each component?

I mean if is possible that something hardware is defective or going to be defective.
can I run some tests?

I know of no tests that are available to the public.

Ok

audit13 said:
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace

WallaceLau said:
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
Click to expand...
Click to collapse
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?

audit13 said:
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
Click to expand...
Click to collapse
First time I did a wipe it took over an hour, then the phone rebooted to the dead android screen. So I tried to wipe again, and it seems like all subsequent wipe took anywhere between 3-5 minutes. No error on each wipe (can't say on the first one, since by the time I got back to the phone it has already rebooted). And yes, I did flashed everything - boot, cache, recovery, system, userdata, bootloader, radio - not exactly in that sequence, but all of those partitions are flashed with the image that comes with the Google download package. Then factory reset and reboot.
Thanks,
Wallace

Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.

audit13 said:
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
Click to expand...
Click to collapse
Did a "fastboot format cache" and "fastboot format userdata", no error. Still won't boot... are those the commands you are referring to?

Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.

audit13 said:
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
Click to expand...
Click to collapse
Tried all those, and yes same result... also, I flashed a different recovery (TWRP) and thereafter I can't even flash new ROMs anymore. ADB Sideload error our (forgot to write down the error message), and if I copy the file to internal storage and flash from there, TWRP will get stuck for hours.
How common are eMMC corruptions?
W.

The emmc problem is not that common, but it does happen. I'm not sure if it is partition or software corruption or a physical defect.
Other xda members have encountered emmc problems too that could only be fixed through a motherboard swap.

I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk

Sarvesh.huddedar said:
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk

The constant boot looping could be a power button problem?

kenbrownstone said:
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk

Sarvesh.huddedar said:
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Maybe im mistaken but evertime i had to put in a password in ttwrp i had gotten encrypted...you get it fixed? My friends started bootlooping for no reason and wouldnt stop til the battery was dead.. Never seen a stock phone do that..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
Reasearch it.... It totally sounds like what happened to me...
Sent from my Nexus 6P using Tapatalk