[Q] N7 [F2FS] stuck at Google Logo BL Avail. - Nexus 7 Q&A, Help & Troubleshooting

Hello guys, i have a problem with my N7 2012 WIFI Grouper, i flashed a F2FS Rom with F2FS TWRP 2.7.0.0 Rec. and every worked fine for 2 days, till this morning, i powered it this moring up and it stuck at the Google Logo. Access to Recovery is not possible, but i can boot it via Fastboot ... all Data is Lost even on the Internal SDCARD but i dont find any Mount SDCARD option, that i can copy the Data on it.
I hope that you'll can help me.
Here is some LOG of TWRP:
Erimary block device '/dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point /data' is not present!
E: Unable to mount '/data
E: Unable to recreate '/data/media folder.
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/boot'
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/staging'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
E: Unable to mount '/data/media/TWRP/.twrps when trype to read settings file.
Click to expand...
Click to collapse

It looks like you have a NAND failure. There seems to be an epidemic of these NAND and corrupted bootloader failures in the first generation Nexus 7s as they approach two years of use. I found a used $50 32GB motherboard (or $35 16GB motherboard) was far more cost effective than Asus' $213 repair estimate.

Related

[Q] failed to mount /data

Hi,
My Acer Iconia A500 is in serious trouble.
I use TWRP v2.1.3 and Bootloader Skrilax_CZ's V8.
My problem started with a loop at startup of Android, not passing the cyanogenmod load screen.
I had no backup to restore.
Used an external memory card to install android rom again.
But I can not mount / data.
In the TWRP screen:
- Install / sdcard/cm-100201211140-UNOFFICIAL-a500.zip ...
Fiding update package ...
Opening update package ...
Installing update ...
* Verifying filesystem ....
* Verifying partition sizes ...
E: Ubable to mount / data
E: Failed to mount / data (Invalid argument)
E: Failed to mount / data (Invalid argument)
The option to mount also can not check the option: mount data.
Could anyone help me?

[Q] Nexus 7 (2012) Stuck in Startup Loop?

I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
So, update here: I tried to mess with it some more this morning and it seems that it got through the factory reset it was stuck on, but I'm still having issues with constant freezing.
I can get to the "Google" bootup screen and where the colored circles spin around before bringing me to the menus to set up my Wi-Fi and account and all that (like it did when it was first out of the box), but now it continues to freeze while trying to set up these settings.
I managed to input my Wi-Fi password and skip over the rest of the settings in hopes of getting into the system before another freeze and now it gets stuck on a black screen that only shows the "back" arrow at the bottom and the battery and internet indicators at the top right.
Any ideas, guys? I can effectively get into the bootloader now, but attempting to wipe through the recovery menu gives the same errors as before while clearing cache seems to work without issues.
I attempted to use a Nexus Root Toolkit to "Flash Stock + Unroot" with the "Soft-Bricked/Booloop" option selected and everything seemed to work until it got towards the end when the program stops responding.
Now I can't boot into the system at all and I only get a very primitive "bootloader" that says Google (instead of showing the Android) and that's it. I can use the volume keys to browse between "Start", "Restart bootloader", "Recovery mode", and "Power off". Both Start and Recovery mode bring me to the same exact screen while "Restart bootloader" seems to bring me to a complete bootloader, but choosing any of those options brings me right back to the screen without all the info.
I feel like I'm just messing this up more the more I mess with it and I'm not sure what else to try. This Nexus 7 is completely stock, by the way.
MrTripStack said:
I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
Click to expand...
Click to collapse
Hi, MrTripStack...
Unfortunately, this doesn't sound good at all, I'm afraid...
Your error outputs suggest some kind of partition corruption... and given that your device is running unrooted factory stock (ie, no modifications), I'm inclined to suspect hardware failure with the devices internal eMMC chip. The "failed to mount..." errors are suggestive of this.
The only thing I can suggest, is you attempt to fastboot flash back to factory stock (see download link in my sig. below for the factory image for your specific device).
Full instructions available here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
(But be aware of a known issue fastboot flashing the v4.23 bootloader that ships with some versions of factory stock; fastboot flashing it causes error messages. Pay particular attention to the comment in red, right at the top, in the very first post in the above link/thread.)
-----------------------------------------------------------------------
I'm not optimistic this will work though... if there is a problem with the eMMC chip, you will likely see a whole raft of similar error messages during the fastboot flash process.
For what it's worth... good luck.
Rgrds,
Ged.
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip).
GedBlake said:
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip) .
Click to expand...
Click to collapse
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
MrTripStack said:
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
Click to expand...
Click to collapse
I'm no hardware expert, but I really don't think it's possible to replace the eMMC chip. It's pretty much 'embedded' into the motherboard, and soldered into place by a computer controlled machine, with very fine and very precise spot soldering... way beyond the capability of any human equipped with a soldering iron to attempt.
You could though, consider replacing the motherboard itself, which has been attempted by another XDA member, and apparently, successfully...
http://forum.xda-developers.com/showpost.php?p=54798993&postcount=824
Rgrds,
Ged.

help me, please...

Forgive my poor English, please.
I want to root my moto G5 plus. So I unlock bootloader and flash TWRP 3.1.0 directly.(Maybe it's a problem)
When i wipe the data, it show me that information:
Could not mount /data and unable to find crypto footer.
failed to mount '/data'(Invalid argument)
unable to recreate .data.media folder.
Updating partition details...
failed to mount '/data' (Invalid argument)
...done
unable to mount storage
Failed to mount '/data'(Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
unable to mount to storage
I cant't enter the system, it just into TWRP again and again.
And now, my computer concider my device is Moto Z2 Play, it doesn't show the internal storage.
Can I get some help in there, please?
I suggest to reboot from TWRP to bootloader, then fastboot flash the 3.1.1-0 version from the TWRP thread which shouldn't have this problem. Try not to use older outdated guides/videos/etc and read/search the current forum threads first to help avoid problems.
You can also flash the image from within TWRP as well.
Just ran into this problem earlier. Go into fastboot/bootloader and enter "fastboot continue". It'll reboot into system afterwards
thanks to everyone, i fixed this problem. I just flash NPN25.137-35 Stock Full Firmware in bootloader.

[HELP] Cant mount /data /system /cache, Unknown partition 'osip' .

Model: T00F
Intel z250 1.6 Ghz
Suddenly my apps started closing in custom rom (montana rom) like contacts,camera etc.
So i tried to restarted my phone but it stuck on boot animation.
Then i tried to wipe and flash this rom again from TWRP 3.1 but it showed me error:-
E:Unkown File System: 'osip'
E:Unable to find partition size for '/misc'
E:Unable to set bootloader message.
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Now i cant wipe, change file system, install and mount.
Here's other things i've tried:
1.) Re-partition my Android
error: /parted: line 1: syntax error: unexpected word (expecting ")")
2.) Debrick Asus Zenfoen 5 with no fastboot, no recovery, and ruined partitions.....
(https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/page1)
error: debrick.bat didnt worked properly.
cannot adb sideload my firmware.. same error (unable to mount /cache)
3.)Hard Bricked Zenfone Unbrick (Last method to try)
https://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
error: failure FW + OS cannot be downloaded
PLEASE HELP ME...
I cant afford new phone this time.
yes I gived like error like too
FW + OS cannot be downloaded

i have a problem with TWRP, pls help

Well, I installed TWRP on my Moto G5+, model XT1680, because I wanted to root it, but after I installed the wlan_custom it appeared TWRP with this message
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Unable to mount '/data' (Invalid argument)
Full SELinux support is present
Unable to mount '/data/media/TWRP/.twrps
MTP Enabled
Installing zip file '/sdcard/wlan_custom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Pushing modules...
How can I get out? Altrough my phone responds only to screenshots.
All help will be appreciated.
I have same problem will update when I find a solution
I finally fixed this problem by going into TWRP and reformatting the data to ext4 then a reboot and reformat the data back to f2fs.

Categories

Resources