yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Root definitelly wouldn't improve tablet's OTA update capability :D

But flashing the update manually like in the OP would always work.

I've never used OTA, they occasionally cause bricks and bootloops, check just in this thread how many such reports. Update 4.4.3 will be probably just a minor bug fixes improvement rather than noticable update.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] cptsashimi:
When mine was stock rooted I believe I would still receive a prompt to download the update as normal, and everything worked fine other than the fact that I would lose root. Which isn't a problem with a nexus, root is easy to reattain.
[Nexus 7 Q&A, Help & Troubleshooting] Recl@imer:
Got it. Thought the same. Thanks man.

---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------

Thanks man.
[Nexus 7 Q&A, Help & Troubleshooting] dkkussner:
failed to load "...." no such file or directory

Hi guys,

I got the same problem as many people here before, but for some reason I cannot find my mistake. I put the image in the right directory and "fastboot devices" shows me my tablet even though Windows does not recongnize it.

I got a 2012 WIFI Nexus 7 (32GB) with no operating system currently and recovery mode is not working.

When I type in the command "fastboot flash bootloader bootloader-grouper-4.23.img" it says: "cannot open 'image....img'

and when I type in "fastboot -w update image-nakasi-kot49h.zip" it says: failed to load 'image....zip': No such file or directory (When I typed it in for the pictures attached to this reply I made a spelling mistake and typed .img and not .zip but I already tried the right one and the computer gives me the same reply).

I attached some pictures so you can have some more details about the problems. I hope you can help me solve this problem.

P.S.: I'm sorry for my bad english, but i'm coming from germany.
[Nexus 7 Q&A, Help & Troubleshooting] juliomulio:
Help!! boot looping nexus 7 2012, tried everything?

Help!!! Hi, I'm a bit of a newbie and am looking for some support on a Nexus 7 2012. I did the OTA for 4.4 and then started having the boot loop issues. I followed the online guide etc to re-flashing, and upgraded to 4.4.2 (using the dodgy 4.23 bootloader image from google, now used the better version). Everything was fine for a few weeks, I then started to have reboot problems again (it usually happened with the Independent Newspaper app).

I then tried to reflash using Rootkit, Android Toolkit, manually using SDK etc to no avail.

Currently the problems are (device boots and is unlocked):

- Keeps boot looping, or if it does start, freezing then boot looping

- Cannot delete apps

- Cannot factory reset using any method

- Reflash, go through all the steps - makes no difference

- Cannot relock

- Cannot activate USB debug

- If it starts after bootloop, it goes back to old restore point (any new apps added don't appear etc)

It is as if a previous reflash was written to a partition, and the new flashes I'm doing are going to another partition that is not booted (at this point I don't know what I'm talking about).

I've tried using different USB etc.

Any ideas out there??

Thanks, Julian
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=4018124]juliomulio[/MENTION] it sounds to me like a corrupted /data partition.

IDK what you meant with "can't factory reset using any method"

I would try to format /data with PhilZ or TWRP

Maybe it is a hardware related problem, then only service can fix it

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] juliomulio:
Thanks

Thanks!

Going to try TWRP, I'll let you know how I get on.
[Nexus 7 Q&A, Help & Troubleshooting] morjul:
Please, help me!

By mistake flash geeb_KK_4-4_bootloader_only.zip (Optimus G E975) in my device F180l. And now only run fastboot.

Follow the commands with files bootloader of F180l :

> fastboot erase boot

> fastboot flash bootloader bootloader.aboot.img

> fastboot flash bootloader bootloader.sbl2.img

> fastboot flash bootloader bootloader.sbl3.img

> fastboot reboot-bootloader

Is correct? The folders in device? Is Ok?!

Thank you very much!!

Sorry my bad english
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
You are in wrong thread here. We don't know your device and no one who feels any responsibility will dare to give you such answer.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] juliomulio:
No luck with TWRP

Hi, no luck with TWRP in terms of doing wipe or format. Actually does both but after reboot, no changes. Will look into Philz. thx
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Yes, try also PhilZ. But ad TWRP is also reliable for formatting if also PhilZ doesn't help consider that it might be a hardware issue.

See what happens if you flash a custom ROM with your custom recovery...

tetakpatalked from the legendary i9000
[Nexus 7 Q&A, Help & Troubleshooting] youknow_88:
I have all-f2fs on my partitions and use the slimkat kernel and rom, I made a mistake when trying to update the rom and long story short i'm in a bootloop. I can't find the device in adb but i find it in fastboot. So my question, can i flash the factory image in fastboot on all-f2fs or will make it worse?
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
You've got a N7 2012 WiFi (and not GSM) yeah?

Have you tried flashing a 4.4 ROM version?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=5929210]zxcv654[/MENTION] it sounds good to me. Just reboot into the recovery mode and format /data.

IDK if N7's stock recovery has that option, I own N7 2013. If no, try boot it via ADB in any custom recovery (or flash custom recovery with fastboot commands) and wipe data and cache

tetakpatalked from N7100

---------- Post added at 01:00 AM ---------- Previous post was at 12:58 AM ----------

It should be all fine again if you format all partitions back to ext4 first. Use any custom recovery to do so and after that flash whatever OS you like.

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] zxcv654:
Yes - N7 2012 WiFi (and not GSM)

I used WUGFresh with KRT16S

Log:

-----------------------------------------

erasing 'boot'...

OKAY [ 0.021s]

finished. total time: 0.022s

******** Did you mean to fastboot format this partition?

erasing 'cache'...

OKAY [ 0.022s]

finished. total time: 0.022s

erasing 'recovery'...

OKAY [ 0.022s]

finished. total time: 0.022s

******** Did you mean to fastboot format this partition?

erasing 'system'...

OKAY [ 0.022s]

finished. total time: 0.022s

******** Did you mean to fastboot format this partition?

erasing 'userdata'...

OKAY [ 0.033s]

finished. total time: 0.033s

sending 'bootloader' (2100 KB)...

OKAY [ 0.295s]

writing 'bootloader'...

OKAY [ 0.593s]

finished. total time: 0.889s

rebooting into bootloader...

OKAY [ 0.020s]

finished. total time: 0.020s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

Creating filesystem with parameters:

Size: 14442037248

Block size: 4096

Blocks per group: 32768

Inodes per group: 8176

Inode size: 256

Journal blocks: 32768

Label:

Blocks: 3525888

Block groups: 108

Reserved block group size: 863

Created filesystem with 11/883008 inodes and 96825/3525888 blocks

Creating filesystem with parameters:

Size: 464519168

Block size: 4096

Blocks per group: 32768

Inodes per group: 7088

Inode size: 256

Journal blocks: 1772

Label:

Blocks: 113408

Block groups: 4

Reserved block group size: 31

Created filesystem with 11/28352 inodes and 3654/113408 blocks

--------------------------------------------

Bootloader Version...: 4.23

Baseband Version.....: N/A

Serial Number........: 015d24a427441c19

--------------------------------------------

checking product...

OKAY [ 0.040s]

checking version-bootloader...

OKAY [ 0.022s]

sending 'boot' (4990 KB)...

OKAY [ 0.662s]

writing 'boot'...

OKAY [ 0.176s]

sending 'recovery' (5530 KB)...

OKAY [ 0.733s]

writing 'recovery'...

OKAY [ 0.193s]

erasing 'system'...

OKAY [ 0.017s]

sending 'system' (611886 KB)...

OKAY [ 78.354s]

writing 'system'...

OKAY [ 27.509s]

erasing 'userdata'...

OKAY [ 0.028s]

sending 'userdata' (137526 KB)...

OKAY [ 17.115s]

writing 'userdata'...

OKAY [ 6.254s]

erasing 'cache'...

OKAY [ 0.016s]

sending 'cache' (9052 KB)...

OKAY [ 1.107s]

writing 'cache'...

OKAY [ 0.432s]

rebooting...

finished. total time: 132.813s

-----------------------------------------

Same outcome - bootloop.

I used the bootloader that came with the image files.

Should I put a different bootloader on instead?

Should I use a different image altogether?

I'd love to get on 4.4.4, but I'd also love to just get this to work.

Thanks for taking the time to respond!
[Nexus 7 Q&A, Help & Troubleshooting] zxcv654:
I got into TWRP and did a factory reset .. still bootlooping.

Thanks for taking the time to write.
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Your device is wiped anyway, so you may as well try the latest 4,4.4 - https://dl.google.com/dl/android/aosp/nakasi-ktu84p-factory-76acdbe9.tgz

You've nothing to lose.

(I vaguely recall something from a while back about one of the 4.4.3 downloads being incorrect; perhaps the one you're using was it!)
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Which recovery did you use? Try again with manually formatting /data (under mount and storage) if you have used CWM, try the same procedure with PhilZ or TWRP. CWM doesn't wipe properly on some devices.

It seems to be all fine with installing the system, formatting /data should help you to boot successfully.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] zxcv654:
I have TWRP installed and wiped the data partition - still looping.

An idea occurred to me this morning.

I've done half a dozen flashing sessions on this.

I have flashed stock recovery every time.

Yet, I still have TWRP installed. It seems to me that if the flashing was as successful as the logs are showing then I should be back to a stock recovery.

Any idea on how recovery can be manually erased and written (with OKAY output) - but not actually change?

Thanks again for your help with this issue.

---------- Post added at 10:55 AM ---------- Previous post was at 10:34 AM ----------

I'm working through flashing 4.4.4.

Flashing the bootloader included in the build from Google gets: "FAILED (remote: (InvalidState))"

I've seen this on previous flashing attempts with some of the builds.

Is there a bootloader-grouper-4.23.img from a different build that you would recommend?

Flashing KRT16S didn't have a problem with the bootloader - would that file work with 4.4.4?

Thanks for your time helping me.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Mate, this could be a sign that there is a hardware issue. Regarding your bootloader question, I strongly recommend never to try to use a different bootloader than belonging to the firmware.

So if you have used the bootloader from the OP for JB 4.3 and flashed KitKat firmware, I strongly doubt it will ever boot.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] Travisdroidx2:
Sorry out of the loop. Downloaded factory images for 4.4.4 and 4.23 boot loader was no good. Errored like mentioned in op. Is 4.18 boot loader the most current?
[Nexus 7 Q&A, Help & Troubleshooting] Rotoq:
Thanks guys! Phenomenal effort and guide! Great work!
[Nexus 7 Q&A, Help & Troubleshooting] Flash23:
I had that same problem with the new boot loader... I took the one from the OP and it worked flawlessly

Thanks!!! My N7 is alive again
[Nexus 7 Q&A, Help & Troubleshooting] theBlissfulReveler:
Help!

I followed everything above, but when i do -w update image, i get the message

"failed to allocate 659520372 bytes

error:update package missing system.img"

What do i do?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
-w update (nameofthefile).ZIP (not image)... right?

Otherwise I didn't understand your question.

EDIT: is there system.img in your firmware zip package?

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] theBlissfulReveler:
thanks for the reply!

That's what i meant, sorry.

Yes, there is a system.img in it.

I tried flashing the files individually; everything goes fine till i flash system. When i do, it just stays there for couple of minutes without doing anything, then says sending system for a long time, and then finally gets stuck at writing system.

I've tried changing cables and ports on my pc.

Also I tried using TWRP to flash the factory image but it cannot even do a wipe, and says E:cannot mount \data

I'm really worried, please help!
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
OK, mate- don't worry now yet :)

Well, this was an important hint- it could actually be, that the /data partition is corrupted. If so, you might be lucky and get it working by simply formatting it with TWRP. Did you try that? If it displays again "can't mount..." try to mount /data manually in TWRP.

That is exactly what I had to do on my brand new Nexus 7 flo right after unlocking the bootloader.

tetakpatalked from the legendary i9000
[Nexus 7 Q&A, Help & Troubleshooting] :
This ^^

?
[Nexus 7 Q&A, Help & Troubleshooting] theBlissfulReveler:
Thank you guys so much! :)

I had tried to format data but it didn't work; got the same error.

However, I somehow got all back to stock with fastboot, and it's all up and working- except for the bootscreen, which is actually from one of my previous custom roms. But I remember that everything flashed successfully. So now the only problem is changing the bootscreen without rooting it again- how do i do that?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Cool, mate! :) congratulations!

Normally (with other devices) it is the file called "logo.bin"

Once you are sure the file matches perfectly well the device (or possibly you can find it and extract it from the factory image) it can get flashed with fastboot command:

fastboot flash logo logo.bin

There is a Moto G thread where many people flash various custom splash screens, it is quite active ATM and I'm quite sure you can use it as how-to reference also for the Nexus 7:

http://xdaforums.com/showthread.php?t=2548530

tetakpatalked from P5110
[Nexus 7 Q&A, Help & Troubleshooting] theBlissfulReveler:
Couldn't get the logo.bin; i can't seem to extract the .img further. I tried 7zip and winrar. :/
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Please specify: do you mean the splash screen, or boot animation?

Please write me which factory image did you flash and I will try to find the file in my Linux ASAP

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] theBlissfulReveler:
I mean the boot animation, the stock one being the glowing nexus 'X' logo.

I flashed nakasi-ktu84p (https://dl.google.com/dl/android/aosp/nakasi-ktu84p-factory-76acdbe9.tgz)

Thank you :)
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
OK, I see... That onenshould be easier to replace. In all AOSP roms (I never use stock firmware) it is a zip file called "bootanimation.zip" that is placed in system/media folder.

You can simply replace that file with root access, just mind to change the permissions to 644

It is actually very strange that the bootanimation of the previously used ROM has remained, I've never yet heard of something similar....

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] n1kolaa:
if you got this isues with kk installing bootloader you shoud use bootloader from jwr66y( http://xdaforums.com/showthread.php?t=2417097)

https://code.google.com/p/android/issues/detail?id=62198
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Jeez, mate- can you please edit post and erase the huge quote? (and you quoted wrong person- OP)

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] Salmonella_6:
Nexus 7

I new to this and I have read a number of post. My problem is that my Nexus 7 will only load to the Google screen. It is unlocked as indicated by the open lock at the bottom. I can enter fastboot and also recovery. Thats all. I have tried countless time using wugfresh to restore my nexus 7. I have been unable to do so. Can anyone walk me through the process using wugfresh and the correct files I need to download?
[Nexus 7 Q&A, Help & Troubleshooting] k.bergmann2:
im currently on kitkat with f2fs. do i have to go back to ext4 when i want to flash 4.1.2?

_______

never mind. solved.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=6022997]Salmonella_6[/MENTION] regarding the fact that both recovery and bootloader modes work, there is nothing to fear. I don't ever use toolkits and prefer exclusively manual way.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] :
You've posted in the very thread that has the guide to flash manually and likely be successful. ?
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
fastboot -w update does not work

When triying to flash the stock rom, all the procedure works except for the last step. When running

fastboot -w update image-nakasi-ktu84p.zip

I get te message: writing 'recovery' FAILED (remote: (FileWriteFailed)).

Does anybody know what is wrong?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Are you 100% sure you're trying to flash a firmware for your device? Sorry for asking, just trying to exclude this possibility

:)

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
I think so. I've got a Nexus 7 WiFi 8gb (2012), and I've flashed factor image Nakasi. Moreover, I've tried with 4.4.4 (KTU84P) and 4.4.3 (KTU84L) and I've obtained the same result. I think I will try with an older one.
[Nexus 7 Q&A, Help & Troubleshooting] :
Your device is Grouper.
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
What do you mean? Am I using the wrong image? What image should I use? Sorry, I'm a newie.
[Nexus 7 Q&A, Help & Troubleshooting] :
If you have a 2012 N7 WiFi only, then yes, your devices name is Grouper. That's what you should be flashing. ?
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
Thanks. But there is no grouper firmware in google webpage (developers.google.com/). Where can I find it?
[Nexus 7 Q&A, Help & Troubleshooting] cptsashimi:
You're right. Nakasi is the right image. I believe grouper refers to the hardware (2012 WiFi) and nakasi refers to the factory provided software for that hardware. I think this all goes back to the early nexus phones that had different hardware (GSM V CDMA) but would use same image but with different radios etc.
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
Any ideas of how can I fix my problem?
[Nexus 7 Q&A, Help & Troubleshooting] :
Ah, sorry... Yes you are right. Nakasi =Grouper. My bad.

When selecting Roms Grouper is usually the device name. But for firmware it's Nakasi.

Thank you for the correction. ?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Nexus 7 2012: both are "Grouper"

nakasi = wifi only

nakasiG = 3G and wifi

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] :
Sure... Kick me when I'm down. ?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Try with another USB port, or cable. Void USB 3.0 ports... I hope something will work.

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] :
Can you guess what's on my Grouper. Lol

Been stock over a year... 4.2.2. I don't mess with it. It's a family device. ?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I understand :)

I have flashed on my friend's device (which is identic like yours) a factory 4.3 which was smoother, faster and had better battery life. This guide was my reference how-to, comminus has written an awsome OP here.

I however really love custom ROMs with dark mode in GApps and kernels that can wake the device on double tap. It saves hardware buttons a lot [emoji56]

It is up to you, just mind that unlocking the bootloader wipes totally whole data, it will be blank like when it was brand new.

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] :
Oh, mines rooted, no ads, debloated , tweaked..... But on stock 4.2.2...cause I'm happy with it. Lol

I mess with my phone's only... So when I break them temporarily... No one yells at me. ?
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
Not working!!!!

I've changed the usb port and cable. I've tried both images ktu84p and ktu84l and I've got the same result when running the last command. Then, I've tried with the oldest image: jzo54k. And, after flashing bootloader 3.41, I get that Device version-bootloader (see attached image) is 4.23. It seems that I can't write anything in my device. What can I do?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I am really sorry, mate, IDK what should you do. It could indeed be a corrupted memory. Can you flash a custom recovery like TWRP or PhilZ and try to format /data, /cache and /system partitions and then try to flash again?

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
I will make a try. I've just changed the tablet USB connector. Do you think this has something to do with the flash error?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
One never knows, mate. It is worth trying. There is often an easy solution for something that might look like a big problem. Give a try.

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] galois10:
I can't flash a new recovery. I've tried with cwm following this guide and it does not work. I think it is a hadrdware problem.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I also fear it seems to be a hardware related problem. If after your enter in CMD "fastboot devices" proper serial no and "device" returns, you might need another internal memory, which isn't a big deal for the service.

Just one last try: IDK if Nexus 7's bootloader is capable of booting custom recovery directly via fastboot without flashing it....

Recovery image should be kept in the same folder where fastboot.exe is and renamed to "recovery"(img)

Now the command would be:

fastboot boot recovery recovery.img

If it works, try to format system, data, cache and dalvik cache. Maybe it would fix the data system of internal memory. Please use TWRP or PhilZ as they wipe in general more reliably than the CWM recovery does (due to an old bug that still hasn't been fixed until v6.0.5.0, also re-root on exit fails regardless of your choice)

Data partition seems to be an "achilles' heal" of Nexus tabs, on my N7 flo the /data partition was corrupted after the device was in use for just 10 minutes, right after unlocking the bootloader. I have fixed it with formatting with PhilZ within one minute. However, I was able to flash it.

Good luck, mate!

tetakpatalked from N7100