Database Info

[Q] Lost sdcard after restart during cache wipping

I restart my phone because it did a lot of time to reset cache. I regered the time I did it but was late.
Now my phone opens but does not have mobile network and cannot access my /sdcard/
From recovery I can see my sdcard. What can I Do?

Are you fully stock? If so, then format /cache partition and then perform a factory reset via stock recovery.
If you aren't fully stock, and use a custom recovery then I would suggest you to perform a factory reset from the custom recovery (it won't wipe internal sd)..
If it still doesn't work then you need to go back to fully stock by flashing the factory images from Google.
- Sent from an IceCold Hammerhead!

Yep, just keep wiping / formatting cache until it fixes or fastboot flash the stock cache.img
Sent from my Nexus 5 using Tapatalk

vin4yak said:
Are you fully stock? If so, then format /cache partition and then perform a factory reset via stock recovery.
If you aren't fully stock, and use a custom recovery then I would suggest you to perform a factory reset from the custom recovery (it won't wipe internal sd)..
If it still doesn't work then you need to go back to fully stock by flashing the factory images from Google.
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
I am not stock at all. I thought if I could copy sdcard to otg before all these.

pagratios said:
I am not stock at all. I thought if I could copy sdcard to otg before all these.
Click to expand...
Click to collapse
Just flash the stock recovery via fastboot and then format cache multiple times until it successfully formats! Your data won't be lost.
Since you rebooted before the cache was formatted, it has ended in a messed up /cache partition.
If you want to backup data, you can use adb pull from recovery...

See above
Edit.. By that I meant my previous post
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yep, just keep wiping / formatting cache until it fixes or fastboot flash the stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It says cannot mount cache.
vin4yak said:
Just flash the stock recovery via fastboot and then format cache multiple times until it successfully formats! Your data won't be lost.
Since you rebooted before the cache was formatted, it has ended in a messed up /cache partition.
If you want to backup data, you can use adb pull from recovery...
Click to expand...
Click to collapse
Now. I am pulling my data and then I'll flash stock.
I have a backup before the mistake. If I restore it?

pagratios said:
It says cannot mount cache.
Click to expand...
Click to collapse
In fastboot? That is an unknown error in fastboot to me.
Sent from my Nexus 5 using Tapatalk

pagratios said:
It says cannot mount cache.
Now. I am pulling my data and then I'll flash stock.
I have a backup before the mistake. If I restore it?
Click to expand...
Click to collapse
You can try to restore the backup but I doubt if it will solve the issue. However, there's no harm in trying..
The cache partition is messed up.. It needs to be formatted first. That's why I suggested you to go back to stock recovery and format cache...
I have tried wiping cache on Philz Touch and twrp and it didn't solve my problem. I had to format the cache partition using the stock recovery and voila! Everything was fixed.

vin4yak said:
You can try to restore the backup but I doubt if it will solve the issue. However, there's no harm in trying..
The cache partition is messed up.. It needs to be formatted first. That's why I suggested you to go back to stock recovery and format cache...
I have tried wiping cache on Philz Touch and twrp and it didn't solve my problem. I had to format the cache partition using the stock recovery and voila! Everything was fixed.
Click to expand...
Click to collapse
Yes but if you're flashing stock recovery fastboot you may aswell flash cache.img instead which is a well documented fix in this forum
Sent from my Nexus 5 using Tapatalk

rootSU said:
In fastboot? That is an unknown error in fastboot to me.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My bad. I understand to have done this from TWRP. I haven't tried yet to do something from fastboot due to the backup.

rootSU said:
Yes but if you're flashing stock recovery fastboot you may aswell flash cache.img instead which is a well documented fix in this forum
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah. I guess it will save some time and will be relatively easy for the OP!
pagratios said:
My bad. I understand to have done this from TWRP. I haven't tried yet to do something from fastboot due to the backup.
Click to expand...
Click to collapse
Flashing the stock cache.img won't wipe your saved data or backups.. There's no harm in trying.. However, if you're skeptical, adb pull all your important stuff and then do the flashes!

Finally I flashed cache.img and seems that everything is good again. Thank you for your help.

Lollipop doesn't boot. Kitkat can't access internal storage

Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?

Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app

I've already tried that, didn't work :crying:

Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?

Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.

_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/

Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.

Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.

_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...

Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.

Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.

Replace internal storage, nothing else you can do

Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good:

Bootloop after making nanodroid with twrp in lollipop

Just flashed "openrecovery-twrp-2.8.5.0-falcon_STOCK_KK" in my lollipop.
Then made a nanodroid backup to my otg pendrive.
Then when i reboot i stuck in a bootloop
How to fix it.
Do i have to erase cache after flashing recovery????

I don't know if it is still the case, but I have had to use the following fastboot command before I could access TWRP again in this situation. The command will wipe internal storage entirely.
fastboot erase userdata​
Follow the TWRP thread for developments: http://forum.xda-developers.com/mot...y-twrp-2-8-2-0-touch-recovery-t2980621/page10

.:Addicted:. said:
Just flashed "openrecovery-twrp-2.8.5.0-falcon_STOCK_KK" in my lollipop.
Then made a nanodroid backup to my otg pendrive.
Then when i reboot i stuck in a bootloop
How to fix it.
Do i have to erase cache after flashing recovery????
Click to expand...
Click to collapse
I had the same problem but I can't remember how I solved. I do remember that I deleted all the user data. I then tried to do another nandroid and again it ended up with a boot loop so I think it's a recovery bug. I wouldn't do nandroid backups via recovery until the bug is fixed. I think there is an app in the play store that can make backups without the recovery but I haven't tried it.

.:Addicted:. said:
Just flashed "openrecovery-twrp-2.8.5.0-falcon_STOCK_KK" in my lollipop.
Then made a nanodroid backup to my otg pendrive.
Then when i reboot i stuck in a bootloop
How to fix it.
Do i have to erase cache after flashing recovery????
Click to expand...
Click to collapse
i did exactly the same thing that you did flashed twrp 2.8.5 made backup booted and boom - STUCK ON LOGO
i have erased my entire phone and no success yet

This issue is now fixed with the latest version of TWRP just released: http://forum.xda-developers.com/mot...ry-twrp-2-8-2-0-touch-recovery-t2980621/page1

lost101 said:
This issue is now fixed with the latest version of TWRP just released: http://forum.xda-developers.com/mot...ry-twrp-2-8-2-0-touch-recovery-t2980621/page1
Click to expand...
Click to collapse
Hey this is not solved yet
Because i flashed the latest 2.8.5 and currently my phone is in coma and its not booting any os
Ps:my data partition is corrupted does anyone know how to repair that
Sent from my E6 using XDA Free mobile app

sjandroiddeveloper said:
Hey this is not solved yet
Because i flashed the latest 2.8.5 and currently my phone is in coma and its not booting any os
Ps:my data partition is corrupted does anyone know how to repair that
Click to expand...
Click to collapse
You need to format 'data' as I describe in post #2.

lost101 said:
You need to format 'data' as I describe in post #2.
Click to expand...
Click to collapse
You are not getting it bro i have erased everything but whenever in custom recovery i reset my device it says cant mount data
Sent from my E6 using XDA Free mobile app

sjandroiddeveloper said:
Hey this is not solved yet
Because i flashed the latest 2.8.5 and currently my phone is in coma and its not booting any os
Ps:my data partition is corrupted does anyone know how to repair that
Sent from my E6 using XDA Free mobile app
Click to expand...
Click to collapse
You need to format data partition not erase.
Don't remember how to do that.
I just flashed stock lollipop then flashed twrp.[didn't made backup this time,it's not working i think.waiting for update from dev]. Now twrp just works fine[with that screen flickering]

.:Addicted:. said:
You need to format data partition not erase.
Don't remember how to do that.
I just flashed stock lollipop then flashed twrp.[didn't made backup this time,it's not working i think.waiting for update from dev]. Now twrp just works fine[with that screen flickering]
Click to expand...
Click to collapse
I meant format only
But the thing is recovery is not mounting data partition
Do you have a solution for that
Sent from my E6 using XDA Free mobile app

lost101 said:
I don't know if it is still the case, but I have had to use the following fastboot command before I could access TWRP again in this situation. The command will wipe internal storage entirely.
fastboot erase userdata​
Follow the TWRP thread for developments: http://forum.xda-developers.com/mot...y-twrp-2-8-2-0-touch-recovery-t2980621/page10
Click to expand...
Click to collapse
Thanks hit to you!
Your suggestion saved my day!

I flashed the entire firmware and it didn't worked for me. How can I fix that? I had to flash CM and then reinstall the backup I made.
Whats the fix for having everything working as before? Cause i'll need to flash stock again to be able to receive OTA updates.
Will "fastboot erase userdata" fix all these problems?

22/3 version is working fine with nandroids, today I did a backup and restored it succesfully :good: also flickering is gone

jneto3000 said:
I flashed the entire firmware and it didn't worked for me. How can I fix that? I had to flash CM and then reinstall the backup I made.
Whats the fix for having everything working as before? Cause i'll need to flash stock again to be able to receive OTA updates.
Will "fastboot erase userdata" fix all these problems?
Click to expand...
Click to collapse
Yeah! It should, since it worked for me!

aumshethia said:
Yeah! It should, since it worked for me!
Click to expand...
Click to collapse
hey im a bit confused. so i am in the twrp 2.8.5.0 bootloop (alternating between black screen and warning boot loader screen). Once i do the fastboot erase cache method, whats my next step?

butthurtlocker said:
hey im a bit confused. so i am in the twrp 2.8.5.0 bootloop (alternating between black screen and warning boot loader screen). Once i do the fastboot erase cache method, whats my next step?
Click to expand...
Click to collapse
According to these people(not me) when you enter command fastboot erase userdata your phone should boot normally
I suggest you to flash Philz touch because backup restore are working fine there
Sent from falcon
PRESS THANKS IF HELPED?

butthurtlocker said:
hey im a bit confused. so i am in the twrp 2.8.5.0 bootloop (alternating between black screen and warning boot loader screen). Once i do the fastboot erase cache method, whats my next step?
Click to expand...
Click to collapse
No, Not erease cache, but "erase userdata".
Use the command "fastboot erase userdata" from command prompt, that's all.
After you do this, press power button to switch your Moto G off and press power button again to start it. Your phone should normally boot and will be fresh as arrived from factory
Hope this helps you.

.:Addicted:. said:
Just flashed "openrecovery-twrp-2.8.5.0-falcon_STOCK_KK" in my lollipop.
Then made a nanodroid backup to my otg pendrive.
Then when i reboot i stuck in a bootloop
How to fix it.
Do i have to erase cache after flashing recovery????
Click to expand...
Click to collapse
i have same problem last month
just installed philz recovery
reset cache davlik cache phone boot up now.

butthurtlocker said:
hey im a bit confused. so i am in the twrp 2.8.5.0 bootloop (alternating between black screen and warning boot loader screen). Once i do the fastboot erase cache method, whats my next step?
Click to expand...
Click to collapse
sanads said:
i have same problem last month
just installed philz recovery
reset cache davlik cache phone boot up now.
Click to expand...
Click to collapse
YEAH!
That will work too :good:

aumshethia said:
YEAH!
That will work too :good:
Click to expand...
Click to collapse
i tried to erase delvic cache.
But that didn't help.
why i should erase user data when i can flash full rom???
i don't want to lose userdata & those backed up file doesn't contain user data[opened in ubuntu,only system datas are backed up.no user data].
is there any way to pull user data using adb or something[i just want to know for future reference as i already flashed rom n phone is fine ]

Deep clean?

What is the expert method to deep clean, wipe every thing my OPO and than flash a ROM?
Hoping to hear from you experts.
Thanks.

Mike2040 said:
What is the expert method to deep clean, wipe every thing my OPO and than flash a ROM?
Hoping to hear from you experts.
Thanks.
Click to expand...
Click to collapse
You can flash the stock images via fastboot, that will erase everthing and get you back to stock. You can then install a custom recovery and flash roms again.

gsmyth said:
You can flash the stock images via fastboot, that will erase everthing and get you back to stock. You can then install a custom recovery and flash roms again.
Click to expand...
Click to collapse
No need to prior Wipe data, Factory reset, Wipe all storage etc?
Thanks.

Mike2040 said:
No need to prior Wipe data, Factory reset, Wipe all storage etc?
Thanks.
Click to expand...
Click to collapse
There is a command to wipe user data, see the below guide.
http://forum.xda-developers.com/showthread.php?t=2839471

Reason!
Thanks for your expert replies.
The reason for asking was and is for you to know in depth what happened.
My OPOs BL is unlocked and rooted.......at times try other ROMs like Hydrogen, RR, etc.
I was surprised to see and empty Baidu folder size 80 bytes shown by ES File manger, after I flashed back COS 12.
The way I flash is firstly reboot to TWRP, Format > type yes, than Factory reset, than Advanced Wipe ALL except OTG, power off the OPO.
Power on in fastboot mode, connect to pc and flash COS ROM using those commands.
All is good, except the empty Baidu Folder, fail to understand how did it persist.
Other thing is when I later flash TWRP over stock, and than when I perform a factory reset before flashing another ROM, see red SD card errors? ........have to keep rebooting to TWRP.
The way I flash is TWRP > Format type yes > Factory reset > Wipe all except OTG > Mount OTG-USB containing the zip, install zip swipe flash > once done > Reboot. (before reboot don't clear dalvik and cache).
If I take screen capture of TWRP they wont be saved in Gallery.
TWRP 2.7.8.0 when flashed on start up showed this.........
"TWRP has detected an unmodified partition. TWRP can leave your partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing from replacing TWRP and will not offer to root your device. installing zips or performing adb operations may still modify the system partition.
Never show this screen during boot again."
To sum up my queries are:
1. How can I perform a deep clean of OPO, and than flash COS 12 using fastboot, so I don't see any Baidu etc empty folders.
2. Than flash TWRP and and if needed can take it's screen captures.
3. Later if required can flash new custom ROM with out issues.
Bottom line to clean my OPOs Storage that includes SD card.
Btw my OPO isn't giving any issues or bugs and working great, no EFS issues etc.........
After reading all care to edit/correct what am I doing incorrect?
Thanks again.

Add
Is this the command to format user data?
Code:
fastboot format cache

Mike2040 said:
Thanks for your expert replies.
The reason for asking was and is for you to know in depth what happened.
My OPOs BL is unlocked and rooted........
Click to expand...
Click to collapse
I have seen people querying the Baidu folder before (i have it myself), it seems to be a folder left by ES file explorer, have you ever installed that? It doesnt seem to be anything malicious, although a lot people were spooked, thinking it was spyware of some sort.
https://forums.oneplus.net/threads/baidu-in-es-file-explorer-manager.303595/page-2
---------- Post added at 03:08 PM ---------- Previous post was at 02:58 PM ----------
Mike2040 said:
Is this the command to format user data?
Code:
fastboot format cache
Click to expand...
Click to collapse
Below is the command for flashing the userdata file via fastboot. If you have downloaded the fastboot image files, I think it basically pushes a blank file to overwrite/format the user data space/parition.
Code:
fastboot flash userdata userdata_64G.img

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