yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
jwr66v to jwr66y

First of all, I am using a wifi-only nexus 10. I am running 4.3 build # jwr66v. A few weeks after updating to this back in June, I got another ota update. It doesn't say anything about jwr66y but says 4.3 jellybean and is 1.8 mb in size. Strange, since i am already running 4.3. When i try to install, i get a dead android and 'error'. So for several months, i have just been ignoring the ota update. Now, it seems as though i cannot get an ota for or manually install kitkat until i am running jwr66y. I went ahead and unrooted (i only rooted in the first place so i can use usb functions with stickmount - really stupid and annoying that i have to deal with rooting and now this problem because the product doesn't otherwise let you do what it is built to do), but i am still unlocked. When i enter bootloader mode it says i am unlocked and this is confirmed when i fastboot devices. I installed the sdk/adb platform toolkit for my mac osx, downloaded and extracted the factory image for jwr66y, placed its contents in the same folder as the platform tools, downloaded the jwr66v factory image comminus supplied (which downloaded as an .img, so did not need to be extracted), and replaced the "bootloader-manta-mantamd03.img" file with "bootloader-grouper-4.23.img". When i try to flash this by entering "Users/myusername/foldername/./fastboot-mac flash bootloader bootloader-grouper-4.23.img", or when i try to flash boot.img, etc., I get "error: cannot load 'bootloader-grouper-4.23.img': No such file or directory" in terminal and "fastboot status - FAILInvalid partition" on the tablet.

Please help!!!

also: i have tried flashing jwr66y's bootloader with the same results and i have enabled usb debugging
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
I suggest to you to go to the N10 forum, here and use the latest factory image, here.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Well, bootloader-grouper is for a 2012 WiFi Nexus 7, so be glad it didn't work. You should get the correct factory image - https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
thanks for the quick replies. comminus, the link you provided brings me to a blank, untitled page

[MENTION=4105641]evio[/MENTION], thanks and i know i should be in a n10 forum but this is the forum i found that seemed to have instructions with my specific problem (other than the fact that it is a different tablet i know) i am confused though. The link you provided me is the same one i have been seeing and it does not have anything for jwr66v so...

Am i still supposed to swap the jwr66v bootloader file? Even though comminus' link didn't work for me, i see from its title that it is referring me to kot49h, which according to evio's link is the most recent version of 4.4 for nexus 10. Does this mean i can skip jwr66y? The manual install directions i have read online for kitkat all say that i should be running jwr66y first.

edit: sorry nevermind about the dead link. my downloader window was open and hidden. but still, you think i can bypass jwr66y and go directly to 4.4?
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
The link I provided downloads the KOT49H factory image for Nexus 10, just checked it again. Here's a link to the webpage that has the link, although you should have been able to get there with some very light googling. Nexus 10 factory images.

The message about the JWR66V bootloader has nothing to do with Nexus 10 - disregard it. You don't need to be on JWR66Y to apply a factory image to your tablet, that would be a silly requirement. After you have the correct factory image, the commands you need to run are in the flash-all.bat or sh file. Depending on your setup, just run the batch file or shell file.
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
Thank you so much for what you do. Is it possible to provide or direct me to more specific instructions for what you are saying. I am obviously not too savvy
[Nexus 7 Q&A, Help & Troubleshooting] aeldergoth:
Works fine up until "> fastboot flash bootloader bootloader-tilapia-4.23.img"

which returns...

error: cannot load 'bootloader-tilapia-4.23.img': No error
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
is the "bootloader-tilapia-4.23.img" file in the same directory as fastboot?
[Nexus 7 Q&A, Help & Troubleshooting] aeldergoth:
Crap. somehow I got 4.18 :-X
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Make sure you've got the factory image you want - nakasig-kot49h (I'm assuming you've got a 2012 3G Nexus 7) and run the commands in flash-all.bat or flash-all.sh
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
when i run /Users/myname/nameoffolder/./fastboot-mac flash flash-all.bat (or .sh) i get:

unknown partition 'flash-all.bat'

error: cannot determine image filename for 'flash-all.bat'

and

unknown partition 'flash-all.sh'

error: cannot determine image filename for 'flash-all.sh'
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
I don't know what your trying to do, but that command you're running is totally fubar'd! You're trying to flash a file called flash-all? Why on earth would you try and do that; that's a batch or script file & not an image!

You seriously need to do some more reading before you totally screw your device!
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
LOL :D
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
because after 5 hours straight trying to resolve this, i tried while waiting for a response after reading this:

(

Originally Posted by comminus

After you have the correct factory image, the commands you need to run are in the flash-all.bat or sh file. Depending on your setup, just run the batch file or shell file.

)

and asking for clearer instructions, like how to "run" them.
[Nexus 7 Q&A, Help & Troubleshooting] aeldergoth:
Up and running, once I sorted out the right filename. Thank you very, very much. Up and running with a fresh factory image and setting it up as you read this.
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Seriously man, you're so out of your depth that I'm worried you're going to end up with a dead device.

There's pro's & con's for using toolkits, but I think you might want to take a look at something like http://www.skipsoft.net.
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
[MENTION=5720148]robe5pierre[/MENTION]: The flash-all.bat is for Windows and the flash-all.sh is for Linux/OSX. You can run the one is for your system by double click (or execute it from a terminal).
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
...stop.

The commands you need are *inside* the .sh file. A .sh file is a shell script; a batch of commands.

I don't want this to come across as condescending... you need to do some more research / learning with regard to fastboot, adb, and general terminal use. Everybody starts somewhere, so don't take it personally.

[MENTION=5720148]robe5pierre[/MENTION] Send me a PM if you get stuck, I'll see what I can do.
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
Thanks! i am fully aware of my being unaware. while i cannot post links because i am a new member, everything i have read online says that i cannot jump from 4.3 jwr66v to 4.4x, especially the most updated kot49h. If i CAN do this, all that would have sufficed here would have been a clearer explanation of how to "run" or "execute" the flash-all.sh file you had mentioned. I realize it is not your duty to explain these things to me but i thought i would ask someone who knows about my specific device and issue rather than look up 'how to execute a command or file in terminal' and educate myself on the differences between a regular execution and a fastboot
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
The only situation you would need a specific version of Android before updating to a newer version would be in applying an incremental over-the-air (OTA) update. This patches files from one version of Android to another.

With factory images, we're formatting partitions and loading new files. This is akin to formatting your computer and loading the OS on from a disk or USB drive. In short, when installing a factory image with the commands that are provided in the archive, there are no Android version requirements. All that matters is that the correct factory image is selected for the hardware.
[Nexus 7 Q&A, Help & Troubleshooting] stompysan:
I found an interesting problem with restoring stock on my brother's Nexus 7. It would constantly error out with "Invalidstate" on the bootloader. After looking a bit further, the error "Signature mismatch" came up on the Nexus 7. I re-downloaded the package and still got the same error. I found that the bootloader in the 4.4.2 update is different than the 4.4 update, but the filename and version number are the same (bootloader-grouper-4.23). The MD5 was completely different, despite the version number being the same. Using the 4.4 update bootloader with the 4.4.2 update zip worked fine. Just thought I would post this for anyone with issues.
[Nexus 7 Q&A, Help & Troubleshooting] robe5pierre:
thanks comminus. i sent you a pm, but have not heard back. since i cannot find a good nexus 10 post regarding this particular issue, i will continue to post here. can somebody please tell me how i am supposed to run the flash-all.sh file from terminal? i think i am doing it correctly: /Users/myname/myfolder/./flashboot-mac flash-all.sh, and i have tried variations, by adding 'flash' before 'flash-all.sh' or removing 'fastboot' but i cannot find clear instructions anywhere and terminal responds: command not found
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
hi can you help it keeps saying image not found when i get to it ?

it says failed to load image no such file or directory
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
here is what i get ive attached a picture i hope

all the files are in platform tools

p.s. not sure if it matters but in fastboot mode it shows bootloader 4.23 as already on the tablet
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Image must be placed (as well as all other files) in the same folder where ADB.exe is. Usually ..../sdk/platform-tools
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
it is though
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
You're going to need to provide a lot more detail than that, for anyone to be able to help you.

We need to see exact descriptions of what you're doing, how you're doing it, exact error messages, screenshots etc etc.

You're not really giving anything that we can go on.
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
i did screen shots post 699
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Sorry, missed them. You've shown a screenshot of all the files in the right place (in the android sdk platform-tools folder) and yet in the screenshot of when you run 'flash-all.bat' you were in your home directory. You need to run that from the sdk platform-tools directory.

(Look at the contents of flash-all.bat - you'll see there's no paths to the files that are being flashed, so it'll assume they're in the directory that you're currently in...which they're not.)
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
i edited the path in settings but will undo that and type it in command instead then and give that a try
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
It's nothing to do with the path to the sdk - it's the flashing script that expects the images to be in the same directory that the script is run from. Just run a command prompt from the platform-tools directory and away you go.
[Nexus 7 Q&A, Help & Troubleshooting] petera1024:
ok thanks how do i run a command prompt from the directory i always pull it up from the start menu

---------- Post added at 02:50 PM ---------- Previous post was at 02:43 PM ----------

found out its installing right now thanks very much your a star :D:victory:
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Glad you got it working.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I wrote you "as well as all other files", all files must be in the same folder.

Great it works now, mate :)
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
All the files _were_ in the same folder; that wasn't the problem. What he wasn't doing was executing the flash-all.bat from within that directory. He was executing it from his home directory by editing the path variable to include the platform-tools directory. This allowed the batch file to run but not find the image files.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I know, mate. Now is fine, that it works for him.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Maybe save them on the PC... like usual...
[Nexus 7 Q&A, Help & Troubleshooting] hannibal585:
asking for help in multiple threads

hello

i am sorry to do it

i have the tab in the bootloader for 2 days now and i am afraid to reboot it (for fear of bricking)

i am not sure if i have intentionally/unintentionally erased the bootloader

i was nervous, ..

i have left the device powered in bootloader

Q: how can i know i can safely reboot to bootloader?

Q: Is there bootloader image that i could flash into it? I have tried 4.18, most of 4.23..

the rest the story is here. sorry for ..

hello

please help

n7 (2012) on one of the lastest cm11 nightly, started random freezes a couple of days ago.

this morning, stuck at 'google' logo, blank screen on trying to boot recovery

tried to read similar cases, decided to try factory image KOT49H.

I did

> fastboot erase boot

> fastboot erase cache

> fastboot erase recovery

> fastboot erase system

> fastboot erase userdata

> fastboot flash bootloader bootloader-grouper-4.23.img

at that point I got an error.

not knowing what to do and thinking the os was already gone with my erase commands, I desperately tried a few fastboot commands.

stress, no power backup, scheduled loadshedding (in my city, country)

i am not sure if ever did 'fastboot erase bootloader'

but I am sure I tried oem lock and unlock

then i read that that particular bootloader had an error, but.. i downloaded 3 different images

and i still failed to flash any of them. I have not rebooted for fear that i may have mistakenly

erased the bootloader, even though that could maybe help (maybe not).

now i have bootloader from nakasi-krt16s (md5 df53028033c9eccf4fe5ba7bc198ce24 that is version that should flash).

but everytime i try

> sudo ./fastboot flash bootloader bootloader-grouper-4.23.img

I get

sending 'bootloader' (2100 KB)...

OKAY [ 2.257s]

writing 'bootloader'...

FAILED (remote: (Unknown error code))

finished. total time: 2.399s

i tried to flash nakasi-jdq39 bootloader with

./fastboot flash bootloader bootloader-grouper-4.18.img

sending 'bootloader' (2096 KB)...

OKAY [ 2.248s]

writing 'bootloader'...

FAILED (remote: (Unknown error code))

finished. total time: 2.384s

what shall I do? is there a way to figure out if the bootloader is still there? Is there another bootloader that I should try to flash. Will it reboot to bootloader?

The display reads v 4.18

thank you so much for helping.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=4011315]hannibal585[/MENTION] the guys who own N7 will know if 4.23 bootloader (JB ) fits to a KK rom (KOT49H). Otherwise, did you try to erase cache again or to use different USB port or to reboot bootloader? BTW now I can' t find do you have a WiFi or 3G model, but if the second, you need bootloader for tilapia, nakasig image.
[Nexus 7 Q&A, Help & Troubleshooting] hannibal585:
thank you

yes, i have done

> fastboot erase cache

I have tried different USB port

- I am afraid to reboot bootloader for fear that it is gone -

I have a grouper (WiFi only)

please help, it has been standing there on last bootloader boot for 3 days now.

regards
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
At some point, your battery will get empty. IDK how is with N7 but Samsung needs ceirtain amount of juice in download mode to be flashed successfully. I think you will have to try to reboot-bootloader or turn off and charge....

BTW, did you use the adviced bootloader from the OP? It is not the same one that comes together with the grouper ROM build as it will fail in general!

You need the JWR66V bootloader for JWR66Y firmware!
[Nexus 7 Q&A, Help & Troubleshooting] ArXiLaMaS:
Thank you very much! I had the same problem and spent so many hours trying to found out what is wrong.
[Nexus 7 Q&A, Help & Troubleshooting] hannibal585:
@tetakpatak

thank you

I have tried the above motioned image and others. Nothing would flash.

anyone got better idea?

please

either i have to find a way to write a bootloader or know that previous loader is still therea and i could reboot safely.

thank you.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=4011315]hannibal585[/MENTION] that is frustrating, as I hoped it would finally help.... :(

I really hope now [MENTION=4194102]comminus[/MENTION] will write you soon and bring some good idea what to do now...
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Unless you explicitly erased the bootloader, it will still be there. A failed attempt to flash the bootloader will not cause the previous bootloader to be erased.

Are you using the latest version of fastboot? Have you tried using a different computer?

Also, try flashing the latest bootloader from the KOT49H factory image.
[Nexus 7 Q&A, Help & Troubleshooting] hannibal585:
thank you.

i dont remember doing a

>sudo ../fastboot erase bootloader

but, it is possible. If I am writing a file, comes with an error, instinctively I would tend to erase the existing one and try again.

I have learnt too late the bootloader was not just an ordinary file, it probably has encrypted information calculated at the time of flashing which would allow google to track each device uniquely, with a serial number. Even if I was going to write a bootloader, it was not necessary to erase it first.. bla, bla

you have reconfirmed to me the precise circumstances when an existing bootloader will be gone/damaged. that is comforting. I still have hope that it will eventually reboot to bootloader. But the fact that it currently refuses stubbornly to write the bootloader gives me a bad feeling. you know, my wishful thinking was not making the world go 'round.

my guess would be, in a normal world

-you intentionally erase a bootloader, but it is still running in the volatile ram (until a reboot)

-you flash a new bootloader, the process would get the necessary info from the ram, done

but not for me, these days, alas!

I do not remember where I downloaded my fastboot/adb for linux from. It is a precompiled binary. fastboot does not show the version number, ADB is 1.0.31, got it about 6 months ago.

I have not tried using a different computer -since I have never had a hint of problem until now. I will borrow a laptop and see -i am not hopeful though. because the problem was not sending the file to the tablet, it is the tablet reporting an error

sending 'bootloader' (2100 KB)...

OKAY [ 2.257s]

writing 'bootloader'...

FAILED (remote: (Unknown error code))

finished. total time: 2.399s

the first bootloader i tried, without a thought, never imaged that it would cause me all this, was KOT49H.

what do you think?
[Nexus 7 Q&A, Help & Troubleshooting] dexviajiboy:
check/update your google usb driver

if you already install android-sdk, you grab it from here and extract to folder ie.extra addon (see instruction on that page base which your running OS) before update the driver in device manager (your PC)

example to update on windows 7

http://developer.android.com/sdk/win-usb.html#
[Nexus 7 Q&A, Help & Troubleshooting] haygij:
After going back to stock, I have no service on my tablet.

I've tried everything, it detects my sim card and my provider but shows no service.

It just went off, for no reason.

It's Nexus 7 3G 2012.

Any ideas?
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
What exactly did you do to return to stock?
[Nexus 7 Q&A, Help & Troubleshooting] haygij:
Locked and unlocked bootloader.

Unrooted and rooted the device.

Flashed both 4.2.2 and 4.4.2 and their radios separately.

Tried also flashing Cyanogenmod Rom.

Nothing, no service, but the device recognize the operator and receives APNs from him.
[Nexus 7 Q&A, Help & Troubleshooting] fozzie:
Sure there's not a cellular service outage where you are?
[Nexus 7 Q&A, Help & Troubleshooting] haygij:
Yes!

For sure
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Is your IMEI still OK?
[Nexus 7 Q&A, Help & Troubleshooting] haygij:
Yes, I think so...

It starts with 3544000...
[Nexus 7 Q&A, Help & Troubleshooting] cabbieBot:
edit:

Save yourself a lot of time and trouble and make sure you download the correct factory image. I lost about 6 hours trying to work around flashing the NakasiG instead of Nakasi to the wifi only 2012 nexus 7. Good times, good times...
[Nexus 7 Q&A, Help & Troubleshooting] jtpryan:
I have 2 problems at this point. 1. I cannot unlock the bootloader. 2. I don't know if USB debugging is on or off and the device will not boot past the Google label.

So, is there a way to check USB debugging via ADB or can I flash without unlocking the bootloader?
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
Boot into bootloader mode (hold power + vol-) and use the "fastboot oem unlock" command.
[Nexus 7 Q&A, Help & Troubleshooting] basuraunak:
I am struck at the

works!!

chaged port and rebooted bootloader
[Nexus 7 Q&A, Help & Troubleshooting] kostikneon:
thanks for the instructions
[Nexus 7 Q&A, Help & Troubleshooting] Dommla:
Damaged bootloader

Hi, I've got a strange problem. My bootloader (4.23) is damaged I guess or at least, my Nexus won't boot. I'm stuck at the google screen with the message that 'booting failed'.

I can enter fastboot mode but don't have recovery access. The device is also not recognized as an adb device but as 'Google Nexus 7 Bootloader Interface'.

Now I wanted to unlock my bootloader (fastboot oem unlock) to be able to flash a new one but I always get the message, that the procedure failed because of an 'unknown error'.

If I try to flash a new bootloader directly I certainly get the massege, that this failed because of my locked bootloader.

Is there any chance to escape out of this dilemma?

Thank's for your Help...
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
[MENTION=5779563]Dommla[/MENTION] First part of the OP explains very exactly what is necessary to do. As you seem not to have much experience with flashing, it would be strongly recommended that you carefully read the OP again. In bootloader mode you can't run ADB, but only fastboot commands. Without unlocked bootloader you can't do basically anything with the vital functions of the device. Otherwise it could be just driver related ptoblem and you have to fix that first.
[Nexus 7 Q&A, Help & Troubleshooting] Dommla:
Okay, thank's for the quick response. So I have to get it unlocked someway. The drivers are not the problem, I fixed that already while reading a lot about my problem. The device's fastboot connection is good. Also the screen with the question whether I want to unlock or not apears on the device.Thereafter the process fails.

Is it possible, that the bootloader is damaged with the result that I can't unlock it? That would meen the device is hard bricked I guess?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
fastboot oem unlock

causes error? If access possible, try to wipe cache and reboot bootloader then try to unlock it again.

When you are in bootloader mode, does your device No appear after entering

fastboot devices