yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] funkyo0o:
I am almost giving up.

I have been trying to run the tools to check the SBK version.I have read and understand that the reason that I get that usb write error is because of 1.) a locked bootloader. 2.) the SBK version. and the other reasons I am not familiar with.I do not know how to unock the bootloader from APX mode(If that's possible at all.)I did have the bootloader unlocked before running the Nexus 7 toolkit v1.8.0.The option that I ran before my tablet got hosed was the option in the toolkit "Back to Stock" "Current status:" which I had the Soft-Bricked/Bootloop" option selected under the "Flash Stock + Unroot" button which I pressed. After the latter process was finished it rebooted my tablet did it's magic(as I could not see a better way to recover my tablet from the anterior soft brick event which happened before I was led to this process by trying to flash Faux123 kernel) my tablet got stuck at the "Google" with white text and all black screen.The tablet took to long to boot (more then a minute )so I shut it down with the power button.I went to power it on by pressing power button and WALA! hard bricked i'm hosed.The tablet does not boot into fastboot or anything. I cannot use ADB or fastboot either, just the complicated APX mode.I wish tablets were reformatable like computers.But back to the reason for the post;I ran the sbkchek tool and I get a "Segmentation Fault" error.I see many indiviuals in this forum had success running the tool.I am on a 32bit pc with Unity Linux OS.I tried a live cd with Puppy Linux and same error.I tried running the SBKDetect tool that downloaded these forums and the Live CD gives me the "cannot execute binary file" even though it is flagged executable or whatever(I'm not familiar with linux pardon the pun)".I am gonna try to run the tool on Unity Linux and see if I have success but I doubt it will work.Does anyone know if the 2012's Nexus 7 SBK version is SBKv1 or SBKv2?If there are different versions im not sure.I am guessing that the newer than 2012 versions of Nexus 7 have a different SBK version then the earlier ones.I have a question.Could the process of finishing the Nexus 7 Toolkit's "Flash Stock + Unroot" process have changed my bootloader to a locked bootloader and that's why i am getting the RCM Version 0x4 Cannot (Write to USB) error? If it is then what good is it to me if Icannot unlock the bootloader from APX mode? It's a dawg gone shame becuase I have the SBK.Can some one give me some insight or confused dog the right way.lol?
[Nexus 7 Q&A, Help & Troubleshooting] mzanette:
I'm in the exact same situation. Nexus 7 2012 hard bricked, shows up in windows with APX driver. Nothing on the screen (stays dark). I have another blob.bin file from my Nexus 7 (bricked one is a friends), but I don't know how to go about modifying blob.bin, if it's even possible, or even finding out this device's SBK. Wish there was a way.
[Nexus 7 Q&A, Help & Troubleshooting] funkyo0o:
Blob.bin files are encrypted I think.

Right.I have tried modifying the blob file but I think it would not work.I have not studied nor am I ever gonna reverse engineer a closed source program, nor am I a cryptographer, but nvflash uses some bit strength of encryption to genrate that blob.Since it is encrypted and it would be defeating the purpose of an encryption algorithm existing at all(unless it is a "Proof Of Concept" cracked cypher like WEP) to always generate the same "blob" of "pseudo random data"; and aside from defeating the purpose dumb if it did;Then my guess would be that the probabilty is low to none.But you sure can use the "CSSN" number or "UID" on the box your device came in or a sticker inside your device, then get the "SBCalcv1.1.zip" tool (you should be able to easily find if you google it.There is a link in these forums) and follow the intuitive graphical user interface and it will calculate and display your SBK in a 0x00000000 0x00000000 0x00000000 0x00000000 "format".But getting the SBK was easy what is not goin for me is getting the tools "sbkcheck" and "sbkDetect" (These 2 tools are for Linux only I think) to run without the errors and show me what version.I am not sure if I am wasting my time with the probability my device is SBKv2.If i am not mistaken SBKv2 is the brain child of the manufacturers genius idea of locking the devices down more.So what I understand if I am not mistaken (someone correct me if i am wrong) is that SBKv1 can be used with nvflash but not SBKv1.And having a locked boot loader would make the nvflash tool cough up the dreaded "RCM Version 0x4 Command send failed (USB write failed)" error or whatever the error was lol. Locking the devices down more would increase there sales with the surefire fact someone is bound to brick their device.Instead of investing efforts to facilitate the device's recovery (which probably would be trivial) in case of a human mistake they just seem to want to DRM hardware.If you paid for the darn thing you should have the right to fix or repair the dawg gone thing,it would not hurt anyone but all the patents and intellectual property, registered trademark crap would not allow it.
[Nexus 7 Q&A, Help & Troubleshooting] funkyo0o:
Someone else blob.bin file might not work but..

I am pretty sure for the reasons i have explained above a blob.bin file will not work which is not unique to the indiviual device it was generated or created on but if you feel that lucky and with all due respect did not understand why then here it is.Good Luck:P don't say I didn't warn you it would not work.
[Nexus 7 Q&A, Help & Troubleshooting] faizleaves:
current solution

Guys i think there isn't any solution right now, need to wait for Google or some developer to make a proper toolkit to solve that.

till that the only solution i think is to change the Motherboard; that's available on ebay, ;)

but for me i did nothing with my tab, it was updated it self through OTA to 4.4.2.

just working fine but then after a day it got stuck i restarted it,(it took more time then normal to restart) and dead

but what i am confuse of is, if i buy a motherboard and this problem appear again :confused:

i am waiting to know what is the mess that take it to APX mode; only after that i will order a motherboard. ;)
[Nexus 7 Q&A, Help & Troubleshooting] iBolski:
Is it still under warranty? You could send it in and have them possibly fix it under warranty. I tried to update to KitKat via the normal method and something went amiss and I went into APX mode as well.

I informed Asus about it and they had me RMA it and it was fixed, free of charge since it was still under warranty (less than year old).

Never hurts to try.
[Nexus 7 Q&A, Help & Troubleshooting] Scuba Jeremy:
I think I'm the newest member of the hard-bricked Nexus 7 club. Not a happy place to be.

Same thing happened to me last night. Watching YouTube, screen froze, audio kept playing. Went to hard restart, and the Nexus 7 was stuck in a boot loop. Went to boot into fastboot (vol - and power) and it would come up in fastboot, but would not boot to recovery. Restarted a couple times, and now, it's stone dead - won't boot to fastboot, or white Google screen. Nothing. It will connect as an APX device, and I've installed generic drivers. I'm trying to communicate through adb or fastboot, but nothing.

I can't imagine what happened. It was accidentally dropped from about 4 feet earlier in the week - maybe something came loose?

This sucks.
[Nexus 7 Q&A, Help & Troubleshooting] Tomtom5893:
My Nexus 7 (V1) is on APX Mode i have installed the Universal Naked Driver 0.73. Gives it every Chance to bring it back to Android???
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
Did you try to hold down the power button for at least 20 seconds?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
...or alternatively, press VOL-DOWN (and hold) followed by the POWER BUTTON (hold both for 20 or 30 seconds). This should boot your device into the bootloader itself and from which you should be able to fastboot flash a Google factory stock image.

Hi, Tomtom5893...

If your Nexus 7 is 'stuck' in APX mode, then the prognosis is not good I'm afraid.

APX mode is normally the mode the device naturally defaults to in the absence of a working bootloader. The bootloader is critical to the Nexus 7.... if, for whatever reason, yours has become corrupted or erased, then you have a hardbricked Nexus 7, and without previously generated, unique device specific

'wheelie blobs'

using the

'flatline procedure'

, then your Nexus 7 is likely unrecoverable.

But having said all that, APX doesn't necessarily signify a 'broken' bootloader... you can electively enter APX mode ON PURPOSE... so there is a slim possibility that your Nexus 7 may have entered APX accidentally, possibly as result of some key press combo by yourself, as detailed

here

.

If this is indeed the case, the solution, as alluded to by [MENTION=2188693]AndDiSa[/MENTION], is to long press the POWER BUTTON for a good 20 seconds or more.

One final point... if your bootloader is dead... then you won't see the white-on-black battery charging animation when you hook up your Nexus 7 to the mains wall charger.

Anyway... try the button key press combinations referenced in my last link, above.

Good luck... and I hope you get your Nexus 7 working soon.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Tomtom5893:
[MENTION=2188693]AndDiSa[/MENTION]

"Did you try to hold down the power button for at least 20 seconds?"

yeah but it start only in apx mode and the Display is off but thx :)

THX for you reply. Im not so good in English can you tell me easyer so i can understand you??? (sorry but i can only speak german) What i now is that i nothing see on my Display it is off at any button press... Sorry for my bad english but thx for your Support :)
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Tomtom5893...

I've just run my previous post through

Google Translate

>Deutsch...

Don't know how good a translation this is. You probably have better English then I have of German:).

Hope this means something to you...:).

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
[MENTION=2145424]Tomtom5893[/MENTION]: send me a pm if you still have problems, so we can talk in German
[Nexus 7 Q&A, Help & Troubleshooting] Tomtom5893:
Yes thank you I have also tried :) but the translation is not so good ... but I think my Nexus7 is forever broken ...: (anyway thanks for your support.)
[Nexus 7 Q&A, Help & Troubleshooting] sknnypete:
Hello Guys,

I've read all the post on this thread, for some odd reason, I went to factory reset my N7(2012) then it went dead never came back up, found that it went to APX mode, I've installed Universal_Naked_Driver_0.72 driver, my windows 7 box is able to see in the device manager, but abd doesn't work or fastboot, I've tried all the button combination nothing works, if anyone can please help. I've been doing research on this for a few days, I've used the search to look for a solution myself. Please any help would be great.

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] dysan911:
APX Mode after update

Just wanted to chime in and report I'm in the same situation. OTA update the other day. Sluggish performance the first day I used it after the update so I did a force reboot and its been in APX Mode ever since. Black screen. :rolleyes: It really doesn't inspire any confidence for me in purchasing another Nexus. I was always very careful with handling the tablet. I never dropped it or got it wet. An OTA Update and BOOM its bricked is ridiculous in my opinion. I called Google Tech support and they worked with me to try a few things and then transferred me to ASUS who basically determined I was no longer under warranty and invited me to purchase a new Nexus 7.

Wow, why don't you identify all devices out of warranty and brick those too!. :mad:

Anyhow, just venting, I realize now from this thread that getting it to work is likely a lost cause.
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
Put it on the *original* charger for some hours and then press the power button for at least 10 (better 20) seconds. The device should exit APX mode unless you flashed a wrong bootloader or the hardware of the device is damaged.
[Nexus 7 Q&A, Help & Troubleshooting] cybalive:
Any Luck?

Hey

I know this an old thread but:

Now have a hard bricked N7 2012.

(interrupted flash of KitKat)

Can achieve APX mode occasionally

Can get to Recovery screen but...

No ADB update because USB debug turned off.

Factory reset not possible...Partition corrupted

Wipe Cache No Good...Partitions corrupted

Cannot reboot to bootloader.

Has anyone managed to flash reinstall the bootloader yet (or workaround)?

Listening hopefully
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
Same here

Hi,

this just happened to me as well.

I wanted to flash the Android 5.1.1 factory image, but the process got interrupted. Maybe because the connection got interrupted.

After trying to reboot the device I just got a blank screen. I tried different key combinations for several times but none of them helped. The device wont show the charging battery when the wall charger is plugged in. The only sign of live I get is the APX mode when I plug it into my Windows PC.

Anybody who can help?
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
It happened to me also!!!!!

Upgraded to stock 5.1 a few weeks back, had not used my N7 since then. Went to start it, have over 30 apps that needed updating from the app store. I let that happen, automatically. After failing to install inbox, facebook, and maps. tried again to update the apps. Started to get some type of "launcher" and "gapps" error loop. Restarted the n7 and it was "stuck" at the spinning "dots" screen for a very long time. I let it stay there for at least an hour. So I went to reboot it in "fastboot" mode Volume- "Down" and Power Button. got into it "Andriod" laying down with box open. I was able to scroll through my options in fast boot, power off, recovery, reboot, etc... and I was going to backup my "SD storage" via fastboot and just reflash it to stock 5.1.1 since it was out.

I was not able to back up anything. Went to restart the N7 was was stuck at the "google" screen. Went to reboot into "fastboot" again and was not able to. Plugged the N7 in it and it is now only showing that it is in "APX" mode. Use all possible combos of buttons presses and time limits 5sec 10sec 15sec 20sec 30sec 60sec, etc... opened it up and unplugged the battery for 6 hours. NADA.....

The N7 now is unresponsive. No battery charging indicators, No Fastboot, No backlight, blip.... The only thing is when plugged into a PC the PC wants to install "APX" drivers....

searched XDA, add many other sties... looks like my "bootloader" somehow got "F-uped" and its "Hard Bricked" and the only solution is to swap out a Mother Board for a working one... unless someone has come around to flash a new "fastboot" without "fastboot" to start I see no other option other than some type of hardware swap......

please correct me if I am wrong....
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
I think my device is hardbricked, too.

I did just read this topic about flatline, a tool which can access your nvram and flash a new bootloader, but to do this it needs a blob file. This blob file is unique for each device and you need to create it while the device is working, because you need a working fastboot to flash their custom recovery.

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

Since I heared about this for the first time today, I didn't create these files. So, yes, I think the only way to get it working again is a new Mother Board.
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
Thats what I figured, I also looked into the NVflash and "blob" files and I didnt make one before my N7 decided to bomb out. I also read that google/asus does not care since all n7 2012 units are now out of warranty. Just to send it back to them at your cost, blah, blah, blah X.XX amount of dollars to fix it or buy a refurb 2013 N7 etc....... I think it's cheaper just to snag a motherboard on ebay, I just picked up a 32gb one for 30 bucks (USD)... 16 and 8 gb ones are even cheaper. lets see how good I am in swapping that thing out.... freakin updates!!!! I hope the motherboard I get will be running 4.4.4 or something under 5.0 and I will keep it at that version. I am not sure if the N7 2012 can handle it... It was running very slow and laggy when I had 5.1 on my N7...
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
I am looking for a new Mother Board as well now. I didn't found one yet, just damaged Nexus 7 with broken displays or something like that. But their board should work fine.

I did use some 5.1 custom roms which had a very bad performance, I wanted to check out Googles Factory Image, but now I have a bricked Tablet. Maybe I will stay at 4.4 with the new board, had a much better performance with it.

I will definetly back up these blob files, to prevent this from happening again.
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
ebay has many of them, about 35-40 dollars for a 32gb, 20's for a 16gb, and teens for a 8gb motherboard... I am sure these are all returns from cracked screens, bad charging port, etc... you just want the motherboard....
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
Thanks, I did already search for these, but at the german ebay I didn't found one yet. I think I will just buy a old Nexus damaged on the outside and take its motherboard to put it into mine.
[Nexus 7 Q&A, Help & Troubleshooting] NeoPreacher:
maybe this one: http://www.ebay.de/itm/Platine-Mainboard-mit-Rahmen-und-Kamera-ASUS-Nexus-7-16GB-2012-/151672149332?pt=LH_DefaultDomain_77&hash=item23505d5554
[Nexus 7 Q&A, Help & Troubleshooting] fwayfarer:
Wow, so for about $75 bucks you could just assemble a 'like new' N7 from a motherboard and frame, battery and screen new from Amazon, and replacement case back? I knew parts were getting cheap but that seems like a hell of a deal if you can do the assembly yourself.
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
Thank you, I found another board from the same seller on auction, where I got it for 3,90€. Hopefully it won't be too hard to replace it with my old one.
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
I just replaced my motherboard, I have to say it was fairly easy for me. I had my N7 opened and the bricked MB out in about 15 minutes. The replacement one fit in perfectly. The hardest part I think was to gently peel back all that tape and copper heat sink material. Also be careful with all of those little cable connector flips parts. They are very very very delicate!!! There is a very good two part video on youtube and if you are familiar with some of the cable connectors that are used. Its like a walk in the park.

Anyways for about 30 bucks I have a working N7 32gb version running 4.2.2 and bootloader locked. I am sort of on the fence about unlocking the bootloader and rooting it again. I might just let it update itself OTA to 5.1.1 and then see what happens. I dont really want to flash roms and really didnt use any of the rooted features/app much. Call me lazy....
[Nexus 7 Q&A, Help & Troubleshooting] NeoPreacher:
good for you, man. maybe you give a short feedback about your replacement experience. i need to do this too in a couple of days. wish you success :fingers-crossed:
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
I have seen a guide on ifixit now, it shouldn't too hard. I also have some experience with these connectors from my notebook. I had to disassemble nearly every part of it to access the RAM slots.

Thank you:), I will report back when I got my replacement board.
[Nexus 7 Q&A, Help & Troubleshooting] Homurato:
Hello everyone here, i'm just another hard bricked nexus 7 owner after the 5.1.1 upgrade blah blah with the APX mode

the good news (?) is the fact that i can still access the fastboot mode with the lying droid and get identified with fastboot devices,

so i try to format partitions and everything goes alright, i send the bootloader and get an OK message,

but too bad next i get a failed [FileWriteFailed] message when trying to write the bootloader (or anything else)

any help would be appreciated if i can bring it back to life :)

PS: bootloader unlocked and i can access fastboot mode, tried the NRT without success
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
If I were in your shoes, I would try to do a "full" flash of 5.1.1, not just the bootloader... I think I was at your point before and then I "lost" fastboot and was stuck with a "hard bricked" mother board... Thus needing replacement...

Good luck...
[Nexus 7 Q&A, Help & Troubleshooting] Homurato:
Thanks for the tip, but i already tried flashing using NRT toolkit's softbricked/bootloop forced flash mode

everything got sent to the tablet OK, but when writing i get the writing errors, i'm guessing it's a writing error maybe corrupted memory i don't know

i tried formatting every partition and it was successful , but then again when i try to flash i get the writing error
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
Probably you should try without a toolkit, just plain fastboot commands. If then you get errors it's probably a hardware problem, but as long as you are using a toolkit for flashing ... Just my 2cents
[Nexus 7 Q&A, Help & Troubleshooting] Homurato:
yes i just tried the NRT first next i tried the fastboot commands and flashall.bat with the same writing errors, everything got sent Ok but the writing fails
[Nexus 7 Q&A, Help & Troubleshooting] mk69:
try another pc with a new install of all the drivers, etc..., and also another usb cable. eliminate all simple stuff before you pull your hair out....
[Nexus 7 Q&A, Help & Troubleshooting] sorg:
Tell you my story (not actually mine, but i've been involved):

N7 of my friend was stuck in boot loop. Most likely, there was some automatic update over night when battery dried out. Anyway, device refused to boot into Android, but could boot into fastboot and recovery.

Because friend already tried factory reset (and it didn't help), i've decided to flash factory firmware since no any valuable data already left on device. I've download the latest Android 5.1.1 firmware from Google site for Nexus 7 2012(tilapia), and run flash_all.bat. And when it came to command fastboot flash bootloader <blah-blah-blah> it stuck. So, i've waited for several minutes (enough to flash the whole firmware) and since there was no any progress i've interrupted it. And since that time device is stuck in APX mode. As far as i understand it's hard brick now.

I'm not a dumb and have enough experience to simply flash factory image.

But as you see now, even this standard procedure can simply lead to a hard brick.

Now, of course, I think I could simply delete the line with bootloader flash. I always tell everwhere "Do NOT flash fastboot/bootloader unless you really need to." And i usually follow this rule. Since i'm tinker with my devices, i never flash bootloader in order to have emergency way to recover. But this N7 wasn't tweaked or hacked any way, my be that's why i had no reason to avoid it. I've simply had been caught by the thought "C'mon, it's an official Google firmware on unmodified device!" And then boom - hard brick.

What was surprised me is how easy to hard brick this device using even official firmware update.. This is really very bad design. There should be a way to recover from a bad *official* flashing procedure, but there was none. Why bootloader doesn't check signature before actual writing to flash? It's very simple procedure to implement and very useful.

Well.. Now i know i cannot trust even to Google...

P.S.: Actually, i still have no idea why flashing procedure of boot loader was stuck. Could it be because of incompatible fastboot.exe which lead to send incompatible binary data to device? Without checking of check-summ on device side it's possible, IMHO...
[Nexus 7 Q&A, Help & Troubleshooting] hensur:
I had the same problem some month ago. I wanted to flash the Factory Image because all 5.1.1 ROMs i tried had some performance issues on my N7. The flashing process stuck at the bootloader and my device was bricked.

I bought a N7 with a broken display from ebay and could replace the mainboard. Now its working again.