Nexus 7 major issues, may be bricked, guides don't seem to account for my problem

Hi, this forum seems pretty active, which is exciting! Hopefully someone can help me out here. I have searched a bunch and see a lot of similar things to my problem, but I'm running into issues that aren't really described by anything else I am looking at.

Quick background
The device is a 2013 Nexus 7, Wi-Fi version. I never unlocked/rooted the device, so it was basically factory settings. On Thursday everything was working fine. Later that day, it started showing the message "unfortunately the process google.process.gapps has stopped" as soon as I unlocked, even after rebooting. I was not launching any apps. I could navigate for about 1 second every time I hit "OK" on the error before it popped back up, so I tried all the fixes I had found online for the problem (clearing app cache/preferences, disabling/enabling download manager, etc). I decided just to wipe the device and reset from factory defaults. I wasn't confident in the Factory Reset working correctly while the error kept popping up, so I booted into Recovery Mode and just decided to do the Factory Reset from there.

The reset seemed to freeze, but eventually the device rebooted and I got the text "erasing" with the animated robot. This will stay that way for forever, though sometimes it eventually turns into the android icon with the red exclamation mark.

The current problem
Right now, if I boot the device normally, it will show the google logo, then go into "Erasing", which animates. If I hit Power+volume up, it seems to be "erasing /data" but it never gets further than that. If I turn it off, it will turn itself back on and go back to erasing. I have left it on for 14+ hours and it never progresses, other than the times it sometimes stops showing "Erasing" and instead just goes to the red exclamation mark.

I can get to the bootloader menu by holding volume down+power. If I select recovery mode, it shows the Android animating logo (no text) and if I hit Power+Volume Up it shows "Formatting /data..." in the bottom. Eventually this fails and recovery mode will pop up with the following text at the bottom:

Code:

---

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
etc for last_install, last_kmsg, log, and then repeated all again 1 more time
E:Failed closing /dev/block/platform/msm_sdcc.l/by-name/misc (I/O error)
E:Failed to mount /cache (Invalid argument)

---

If I select "Factory reset/wipe" now, it shows the following:

Code:

---

--Wiping data...
Formatting /data...
then all of the above errors again

---

I tried downloading and installing the Nexus Root Toolkit and running the "Flash Stock + Unroot" iwth the "Soft-bricked/bootloop" option, but all it seems to do is restart the device a bunch of times and then get stuck on "erasing 'userdata'...

Code:

---

Flash Stock + Unroot...
 --------------------------------------------------


sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.007s

sending 'boot' (7256 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.008s

erasing 'cache'...
OKAY [  0.145s]
sending 'cache' (4664 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.153s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.008s

sending 'recovery' (7860 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.007s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.008s

erasing 'system'...
OKAY [  0.732s]
sending 'system' (822754 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.740s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.008s

erasing 'userdata'...

---

Any suggestions on how I might be able to repair my device? It seems completely screwed up, I have no experience with the flashing/bootloading stuff.

Thanks!

Stuck on bootloop, and odin doesn't seem to work...

Hey,

As the title says the phone is stuck in bootloop after I was playing around with knox and enabled "Knox active protection" (the phone is rooted with pingpong...)
Sooooo the phone restarted and is now stuck in the loop :crying:

I know I had the latest update installed 5.1.1 I think and I live in Sweden so i should have the international thingy, but I don't really know more than that unfortunately... Searched around and found this thread but i was a bit too late for that warning, so i tried to flash the phone with odin but i only receive this message/error...
G920FXXU2BOFJ_G920FTEF2BOF1_G920FXXU2BOFJ_HOME.tar .mp5 <-- The name of the file I tried.

So I don't really know how to fix this problem and i've searched for info about it but i can't find any... And it's my only phone so I really need to fix it :(

Cant seem to get viper4android to work

I learned about viper4android and that is what made me start this crusade. I literally spend all of yesterday researching and learning how to root and troubleshooting viper4android and I still can't seem to get it to work.

I rooted my phone and flashed the latest version of TWRP, and installed superSU as well. I initially had a lot of trouble getting the busybox drivers to install but I finally managed to get the latest version installed. The app busybox on rails verifies that the current version of the busybox drivers are installed.

I tried different methods of installing viper4android and I don't have any luck with any. I get the app installed but once I launch the app it asks me which drives I to install, I try to install the super quality drivers but the drivers will not install. I've done a lot of googling of what the problems could be but the "fixes" people suggest dont work. The latest thing I tried was installing SELinux and changing the mode to permissive before trying to install the the drivers but the drivers will still not install.

Any ideas on what to try next? I've granted all these apps permanent permission through superSU. The other thing I've been wanting to do is to remove all the ATT bloatware, but even the app I got for that called "uninstall" will not uninstall all the bloatware which makes me wonder if something is incorrect. However in the bootloader it says my phone is "modified" and "unlocked".

Any help would be appriciated, and I should also mention I have lolipop 5.0.2.

Can't seem to mod S2

Hi guys,

I wouldn't post here unless I was completely out of answers and I really would like some help.

I have a Galaxy S2 gt-i9100 (international) tha tI am trying to mod with Cyanogenmod. But no matter what I try, I get Status 7 errors.

Both the boot and the phone info screen say this is a GTi9100.

The phone runs CWM 5.8.1.8. It is rooted (I ran Rashr and updated).

I have tried the following ROMS:

cm-10.1.3.1-i9100-signed
cm-10.1.3-i9100
cm-12.1-20150827-NIGHTLY-i9100
cm-12-20150102-UNOFFICIAL-i9100

No luck - I always get an aborted installation with a Status 7 error.

I'm out of ideas. Tutorials say you can fix Status 7 by updating CWM, but it is at the highest I can get.

thank you,