Both times I have wiped data/factory reset with the latest version of Clockworkmod, the recovery has not been able to mount my system partition. The first time this happened, I put the phone into fastboot and flashed TWRP. It couldn't mount the system either.
After the first time, I thought it was a fluke. However, I just wiped data/factory reset again yesterday and the same thing happened. I had to flash the restore all binaries from Google to get the phone back up.
So, my question is, why is this happening? I'm far from new when it comes to root/custom ROMs, and I've never had this issue before on any of my previous phones (EVO, Nexus S, GS3). Does anyone have any idea why this would be corrupting the system partition? I've flashed TWRP to see if that performs any better.
It could be the emmc going bad. Leo an eye on it. In the future, instead of flashing the flash-all.bat just flash the cache.img in fastboot
Sent from my Nexus 5
That would be odd that it'd be going bad so soon. I've only had the phone about 2 months, and I've not flashed much besides a few ROMs and kernels.
Basically, my wife's phone was constantly rebooting. I had heard of power button issues so I tried to open the phone to fix that. After fiddling around with the button the problem persisted. I read somewhere that wiping the cache would help so I prepared to do that.
As I was waiting for the cache to wipe... the phone reboot again. It now does not boot (sits on the boot screen after the Google logo goes away) and says invalid argument when I try to wipe the cache.
According to this post, flashing the cache.img will fix the corrupt cache and allow me to wipe it.
Unfortunately my wife's phone has not been backed up, nor has the bootloader been unlocked. Is there ANY way to backup/retrieve files before unlocking the bootloader so I can fix the cache corruption issue? She has stock recovery, running lollipop.
Would really appreciate help in this matter, the pictures on her phone are from a year of travelling (not my best idea to leave them on her phone...but I digress).
If your phone keeps rebooting, and bootloader is LOCKED, its going to be hard to do anything to recover user data.
Having said that,
If you had ADB debug enabled before this disaster, you could try to ADB Sidleoad the Nexus 5 Lollipop OTA zip from stock recovery.
Then you data would remain intact.
Best of luck
Artorias90 said:
Basically, my wife's phone was constantly rebooting. I had heard of power button issues so I tried to open the phone to fix that. After fiddling around with the button the problem persisted. I read somewhere that wiping the cache would help so I prepared to do that.
As I was waiting for the cache to wipe... the phone reboot again. It now does not boot (sits on the boot screen after the Google logo goes away) and says invalid argument when I try to wipe the cache.
According to this post, flashing the cache.img will fix the corrupt cache and allow me to wipe it.
Unfortunately my wife's phone has not been backed up, nor has the bootloader been unlocked. Is there ANY way to backup/retrieve files before unlocking the bootloader so I can fix the cache corruption issue? She has stock recovery, running lollipop.
Would really appreciate help in this matter, the pictures on her phone are from a year of travelling (not my best idea to leave them on her phone...but I digress).
Click to expand...
Click to collapse
Contact me on hangouts/email: [email protected]
I can flash custom recovery without unlocking bootloader or wipe. If the /data partition didnt get corrupted we could recover the files.
Sent from my Nexus 5 using XDA Free mobile app
Has my brain gone broken? I thought you could fastboot stock img files without unlocking the bootloader?
Ben36 said:
Has my brain gone broken? I thought you could fastboot stock img files without unlocking the bootloader?
Click to expand...
Click to collapse
You can try that too.
What version of Android did you have on the phone?
In order to flash factory images, you’ll need to have the Android SDK HERE
Then you need to download the same version of Hammerhead Factory Image
you have been running on her phone HERE
Extract the correct Hammerhead Factory Image using 7zip or other extractor tool.
Then copy the cache.img from the extraction to the SDK/platform-tools folder.
From within your platform-tools folder, open a command prompt.
I'd recommend wiping the partition before flash.
-First type the following command
fastboot erase cache
-Then type the following command
fastboot flash cache cache.img
Plenty of tutorials in the sticky's if you need to learn more .
Best of luck
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
I got a nexus 5 off of eBay, the seller said he had tried to root it and failed so I thought I would have a crack at it.
I thought it would be an easy restore but I ran into a few problems:
Phone originally came with 6.0.1 installed.
On android 5+ I could not access the standard recovery screen, and when I pressed power+volUp it just said formatting /data and would not move from that.
Rolled back to 4.4 and I got into the ususal recovery screen.
Tried to do a factory reset, but it again stuck at formatting /data.
I left it the entire night while I slept and it was still saying formatting /data. in the morning, nothing had changed.
Trying to boot the phone normally just left it on the 4 startup screen.
I've tried doing a full flash of stock android with each seperate part manually.
Also /data is unable to be mounted in any custom recovery, like it is corrupted or locked somehow.
With the stock recovery, it cannot be detected by adb, but in cwm it can.
EDIT: checking the /data folder in adb shell shows it's completely empty, and the same with system even after flashing and flashing again.
Can anyone advise me as to what might be the problem here?
Reflash all partitions manually, including userdata.img file. After flashing the last partition, boot directly into stock recovery and perform a factory wipe, then reboot.
Done that multiple times, I get the same result on stock android.
I don't want to root or anything like that right now, just get it back to a working state.
So you flashed the userdata.img file?
audit13 said:
So you flashed the userdata.img file?
Click to expand...
Click to collapse
yes multiple times
If you flashed userdata.img multiple times and the phone still can't perform a factory reset, the emmc chip may be damaged.
Recovery of J700T from "Device storage corrupt you must factory reset" error
Time to talk to the XDA brain trust before I make matters worse. I had rooted my J700T and all was well, also using link2sd. Unfortunately, I made a fatal error by attempting to use FolderMount (rather than creating the links myself), ending up in the Samsung "/data corrupt you must factory reset" error. Also unfortunately, when I earlier flashed TWRP (and then flashed SuperSU via TWRP) I did not choose to wipe the phone at that point to give /data & /system access, so I can't access them through TWRP's adb access. The "reset phone" option on the "you must factory reset" page fails of course, since it tries to boot into recovery which is TWRP not stock. I tried to do a typical TWRP wipe (I can still boot into TWRP of course, and into the download screen), but the result is that when the phone is started normally it continuously loops with the Galaxy J7 splash screen on and off at about seven second intervals (only stopped by pulling the battery).
So the question is, what's the best way to proceed? I saw another page here with the four ODIN files to flash back to stock, but the dropbox account is suspended due to overuse. Ideally, something I could do through TWRP would be even better, and this time I'd like to do the full reset and turn off the crypto so that in the future TWRP has full access to the internal phone data, not just the SD card.
Any guidance would be much appreciated. Thanks!
Can I Restore the Samsung 700t1 withowithout pc
Jersto said:
Can I Restore the Samsung 700t1 withowithout pc
Click to expand...
Click to collapse
If you mean completely back to stock (day one out of box), no.
sent from this device on this app....
So you had twrp as your recovery, you decided to mess with your system partition, you don't have free access to a PC yet it seems you neglected to do the one thing that would have got you out of this mess in a pinch?
That is spending literally 2 minutes to make a nandroid backup?
The main reason really for having a custom recovery. ?
Your only option now is to flash the stock firmware and FORMAT DATA.
Okay guys. Now we got that out of our systems, let's work on some solutions.
All good?
sent from this device using this app....
Thread cleaned up. Please stay on topic.
Regards
Vatsal,
Forum Moderator.