[Bricked Nexus 5] can't mount /persisit ,/data; Currupt Partition; Flashing Failed - Nexus 5 Q&A, Help & Troubleshooting

My rooted Nexus 5 has got bootloop issue because of faulty power button. It keeps restarting on its own. After replacing the power button with new One from LG Service center, now it stuck
at marshmellow boot screen, that boot keep running entire day untill battery died. LG Service center guys told me to replace the mother board. Since i was not convinced, i decided to make sure
if it is really required. My Nexus 5 has CWM recovery ver 6.0.4 with usb debugging on. Fastboot, adb everything is working. But if i tried to flash / wipe or mount i simply get error
can't mount /persist
cant mount /data
I tried following links to fix it-
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
https://forum.xda-developers.com/go...orial-how-to-flash-factory-images-lg-t2713833
and some other first hand advice like run "Flash-all.bat" from stock rom, use WUG Toolkit to fix soft brick and flash stock rom or try flashing another custom recovery. But no matter what i try
CWM never get replaced and again same error. i was able to flash TWRP ( only untill reboot)and able to see folders under File Manager. But can't select Data, persist if try to wipe or mount from there.
One thing though, While using LG Flash tool my device never got detected in the tool even though i could see LG USB Serial Port under device manager in PC.
Please suggest if there is anything can be done to get it into working mode ,or motherborad replacement is the only way to go ahead.

You could try repartitioning device. try doing this:
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
Actually resizing system partition also deletes userdata partition and it should work after recreating it. You have nothing to loose if it is already broken.

Try flashing the oldest stock ROM from the Google site. Make sure to flash userdata.img and perform a factoru wipe before booting the phone for the first time.

aciupapa said:
You could try repartitioning device. try doing this:
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
Actually resizing system partition also deletes userdata partition and it should work after recreating it. You have nothing to loose if it is already broken.
Click to expand...
Click to collapse
Okay. Let me just try what you said. Will post the result
Edit1 -
I was not able to unmount /cache, /data .
On umount /cache it restart on its own and for other unmount /data and unmount /system invalid argument.
This is what happend (See image)--
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

audit13 said:
Try flashing the oldest stock ROM from the Google site. Make sure to flash userdata.img and perform a factoru wipe before booting the phone for the first time.
Click to expand...
Click to collapse
I am really sceptical if this will work. Since I have already tried flashing oldest rom of marshmallow (6.0.0).
Anyways, it won't take much time so will try to flash KitKat and let you know.
Edit -
Result was as expected
remote : failed to erase partition
remote : flash write failure

Any other Help ?? How to make sure if its really hard brick and not soft brick?

Sounds like the internal memory chip is damaged. I had one phone where I could not flash anything so I changed the motherboard and everything worked perfectly after the change.

I think I have a similar issue. Someone please help!

Related

Lost phone storage???

So this morning I made a Nandroid backup (everything was acting normal) and I flashed the LeeDroid ROM then his insecure boot image since my phone wouldn't boot without that. Since then, my phone just will not recognize the internal SD card from Android (although, it is fine in Recovery). I posted about this in the LeeDroid thread because I thought it was ROM specific, but I just restored my Nandroid and the issue persisted. I have no clue what happened here. Any ideas?
Not sure if it is related but since I flashed the new ROM (even after restoring) I get that Android is Upgrading (runs through all apps optimizing) screen on each boot. Is this related to the boot img? Would the boot img have restored when I ran the Nandroid?
hah2110 said:
Not sure if it is related but since I flashed the new ROM (even after restoring) I get that Android is Upgrading (runs through all apps optimizing) screen on each boot. Is this related to the boot img? Would the boot img have restored when I ran the Nandroid?
Click to expand...
Click to collapse
Hi I saw your issue in the LeoDroid thread also. I think if I were you I would flash the stock HTC recovery and do a factory reset with that. Or flash a RUU file.
To answer your question though, if you restore a nandroid it does include your old boot.img
dc211 said:
Hi I saw your issue in the LeoDroid thread also. I think if I were you I would flash the stock HTC recovery and do a factory reset with that. Or flash a RUU file.
To answer your question though, if you restore a nandroid it does include your old boot.img
Click to expand...
Click to collapse
Why would the recovery be involved though? I don't get what caused this. The Recovery console sees my memory card just fine.
Ok so in ROM Toolbox - Root Browser, the sdcard shows up as a file, not a folder. When I click on it, it has empty contents. Does this help? I have full permissions on the file. The sdcard is pointed to /mnt/sdcard but when I specifically go there, it is empty. When I check permissions on sdcard under mnt, they are all unchecked and when I check them off, it is unsuccessful... ARGH
Could someone post their fstab file for me so I can mimic it and push to the phone, I think it is related.
Thanks
Ok so I do have an fstab file and here are the contents
dev_mount sdcard /mnt/sdcard emmc /devices/platform/msm_sdcc.1/mmc_host
Is that correct? Why does the mount command in the shell day fstab not found or corrupt?
Sent from my HTC One S using Tapatalk 2
May be a stupid question, but in settings it doesn't show anything under Phone Storage? What do you see there? Can you try to format it? Can you put a screen shot of your Storage settings? Here is what mine looks like.
You say you can access SDCard from Recovery, did you try to go to Mount and Storage and format SDCard?
FYI I'm on leedroid.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says phone storage and total space and available space are "unavailable".
hah2110 said:
It says phone storage and total space and available space are "unavailable".
Click to expand...
Click to collapse
Do you have important files on the sdcard your trying to recover? If not have you gone back to a stock recovery and tried to clear storage yet?

Bricked Or Not Bricked?

I have a friends G2x here I wiped his sdcard cause he said he had a back up but he did not but we had it running on hellfire. He wanted me to install CM7 for him so I went ahead did a factory data reset, wiped cache, delvik, and formated his /sdcard cause it was full and he said he had everything on his computer. Well After doing the wipes an formatting I mounted the sdcard via cwm and put on the cm7.zip and gapp.zip flashed both went to reboot and now it only gets to the second LG boot logo with I guess cm7 design behind it and then reboots so I am bootlooping but I am able to boot into recovery still so I am like WTF happend? lol Ive tried a few things already but I was wondering if anyone had this happen to them? By the way my friend only backed up photos no his whole sdcard so I have no Nandriodbackup :crying: FAIL
also just found out via CWM trying to mount internal SDCARD I get this error:
E: Cant Mount /emmc/
seems like there is no /sys file when I do error report i get
failed to open /sys/class/android_usb/android0/stat: No Such File or directory
Was CWM flashed using nvflash or ROM Manager?
Sent from my LG-P999 using xda premium
I'd use nvflasher and start from scratch. also did you goto mounts and format system?
i always do before flashing new rom.
Sent via G2x on CM7 b135.2 w/faux 52 kernel
Well original install I am not sure he bought the phone an it was rooted but I did do nvflash to cwm and to stock to see if either would boot and it didnt work either way it but I did the NVFLASH CWM so I could have CWM recovery but right now all i can do is boot into recovery if I try to boot system it just bootloops
I have formatted /sys , /sdcard, attempted to format /emmc but it gets an error and says cant mount skip format is it possible his internal sdcard or memory is dead?
Try using the Batch Cleanup tool. You can find it in the Dev section. Then flash a GB ROM and see what happens
Sent from my LG-P999 using xda premium
The G2X is nearly impossible to brick. There is almost no way to brick it. There will always be an answer from the community ready to help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok I am going to try to use that batch clean up tool in the dev section will post results
Ok so did the batch had done it early as well here is a pic of the cmd I ran looks good to me and I am able to boot into recovery but once more I end up boot looping I attempted to install cm7 should I try a different gb rom?
Thanks for the help and suggestions everyone I finally got it did the batch clean up then went ahead and located stock rooted nandroid backup files setup the directory in the sdcard and then restored back up and Booted right up into stock rooted device! I then re-attempted to flash the cm7 latest stable an sends me into boot loop so I am going to say that the rom .zip on that latest cm7 stable is corrupt or something went ahead to the previous stable before that one and flashed it booted right up ! so Thanks a lot again guys and hopefully this will be helpful to anyone else that may encounter this same issue I knew it could be fixed since I could boot into recovery

Stuck in a bootloop

[Deleted]
johnfocker said:
Hello everybody!
I'm posting today cause I got stuck in a bootloop when trying to factory reset from a freshly flashed Asus stock rom.
I was previously tinkering with cynaogenmod installs when I found myself facing those kind of errors:
Code:
E: Can't mount / cache/recovery/command
E: Can't mount / cache/recovery/log
E: Can't open / cache/recovery/log
E: Can't mount / cache/recovery/last_log
E: Can't open / cache/recovery/last_log
Since I was unable to flash anything from that point via recovery, I flashed the latest asus stock rom via fastboot and the tablet booted again.
Then I flashed CWM recovery to be able to flash CM11 again but I got the "Can't mount" errors again so I booted the tablet on the stock rom and tried a "Factory reset" from the Settings menu...
Now I'm stuck on this nice screen and everytime I try to coldboot the tablet I'm unable to access fastboot anymore... It boots directly to that screen and never gets past it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I feel like I'm screwed this time... please help me ^^'
Click to expand...
Click to collapse
You should NEVER use the "Wipe Data" option from the bootloader or factory reset from Settings with a custom recovery installed! Any kind of wipe or format can and should be done from recovery.
But don't worry - you'll be fine.
The factory reset command starts the recovery and asks it to wipe the data partition. And you keep interrupting it. I've seen your scenario a number of times. Connect your tablet to a power source and let it do it's thing. Go to bed. Sleep over it. The next morning it'll most likely be finished.
And before you flash anything else, check your bootloader and recovery versions. Most likely one or both are incompatible with CM 11 or each other.
I've done the exact same thing, was in a hurry and wasn't thinking... I never usually do a factory reset from settings, I don't know what I was at. I hope your right and it will come on eventually. I can't boot to Recovery I can't boot to fastboot, nothing works... Its a nice brick at the moment. Did you ever get this sorted?
Sent from my HTC One using Tapatalk

twrp - can't install this package on top of incompatible data

i have followed all the steps using NRT to unlock boot-loader and root the phone.
Installed TWRT manager and flashed the recovery.
Now i am trying to flash CM12 for the first time and stuck with error message "can't install this package on top of incompatible data" during flashing .
downloaded the following flash zip from CM website: cm-12.1-20150901-SNAPSHOT-YOG4PAO237-hammerhead.zip (281.77 MB)
Can any one help me what needs to be done to proceed further.
i didnt wipe the data before. Now its working and closing the thread
I wiped everything on my phone via TWRP. Still getting this error!
This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM
mesaj said:
This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM
Click to expand...
Click to collapse
How did you do that?
dsarcinelli said:
How did you do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
This guide might help, you do it in TWRP by going to Format > Advanced > select partition > Change filesystem > Ext4
Wiping data worked for me
2sumanth said:
i didnt wipe the data before. Now its working and closing the thread
Click to expand...
Click to collapse
In twrp, I had to fumble around to find advance wipe to clear data but worked like charm after that.
Thank you!
xiaomi note 4g dior
Let me tell my story,
My friend gave me an old xiaomi note 4g which was stuck at the MI icon on boot,
Luckily the phone did not lock boot-loader
So I use xiaomi flash rom to flash global room , it worked after i tried sometimes.
Then I booted to the phone, and other problem came, the phone was linked with an Mi Account , and my friend forgot everything about it
not email, no phone number
I did a search and they said the only way to bypass the MiAccount is using a Resurrection ROM or balallala
so I ended up with using
1. fastboot to install twrp
2. open twrp --> open adb sideload mode.
3. Open window command line and install Resurrection ROM though adb sideload
While installing rom though adb slideload , i got the same issue with topic
SO i cleared data and tried again,
IT WORKED , NO MORE ****ING MiAccount
THANK a lot
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi
Playing with my wife's Nexus 5, bootloader unlocked, rooted, and latest TWRP installed but when trying to flash from android 6.0.1 to Lineage, I'm getting an error 7 image shown I hope.....
Is this just because I haven't wiped the data first ? (I'm fairly sure but...)
I dont dare try 'cause if it's not that she'll kill me, so would like to be sure before I wipe all her data..
Thanks
Update, it was that I just wiped all except the SD and flashed, all is just great

Flashing wrong recovery killed all of my partitions — Help!

Hi all,
I'm going to make a long story short and say that my brother's phone has a cracked screen, so I tried to use TWRP to backup everything through ADB. But googling SM-J530F TWRP brings 'j5lte' as one of the first results, I went and flashed it under the wrong assumption that j5lte was SM-J530F's code name (it was not) and that caused severe bootloops.
I flashed correct TWRP, but USERDATA would not mount. I panicked and the crystal bleeding was progressing fast, so I pulled the entire mmcblk0 to dump a raw image of the phone's NAND.
This was the right move, as the phone is completely dead now. Crystal bleeding has made the screen completely dead, but the phone still works.
All I'm left with is the raw NAND backup.
The first thing I did was inspect the image with fdisk. It can recognize the GPT partition table and structure. The USERDATA partition is at the very end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GDISK is also recognizing it no problem. It seems like the partition table is in good condition:
GPARTED is also recognizing partitions, but it does not look good:
Looking at more information:
For the record, e2fsprogs is installed. It's always installed by default. GPARTED here is complaining about the superblock, but I can see that its looking to open the partition through /dev/loop0p24 which is no good. The kpartx tool is giving me access to all the partitions of the image through /dev/mapper/loop0p24, so that explains the errors.
Superblocks seem to be present in USERDATA:
I tried mounting the partition with a backup superblock, but...
I was at a loss at this point, so I tried mounting the SYSTEM partition just to see what happens and... it worked?
This proves what I said: This partition is fine, GPARTED was complaining simply because its trying to target them through the wrong device path.
But this raised the question: What the heck is wrong with the USERDATA partition? Why is it ext2 (Isn't that SUPER old?) and could it be that its not corrupted at all, and I'm just trying to mount it the wrong way or something? TWRP couldn't mount it though (Why?).
Being at a loss, I tried repairing the ext2 USERDATA partition using `fsck.ext2 /dev/mapper/loop0p24` and it found so many errors (including a corrupted journal) the file I redirected stdout to (console output) ended up being 78MB. Here it is if you want it (obviously can't post here).
So anybody knows what I can do? Is there any hope? I'm positive that the recovery image couldn't have corrupted the USERDATA partition (How could it? I still can't find a possible explanation). And even if it did, it couldn't overwrite the files. The file data should STILL be in that partition completely in-tact (There's NO WAY the recovery image overwrote them) though the journal is gone, so I can't use a tool like extundelete to recover them.
I tried to flash the phone with a stock rom through download mode to reconstruct everything with a healthy structure. This was so I could flash TWRP again and pull another NAND raw dump to have as a healthy reference I could use, but this doesn't work. Odin fails and I don't know why because the screen on the phone is dead.
Is there some place where I could get this maybe?
Is there something you can suggest I do?
Thanks!

Categories

Resources