For updating to android 4.3 , I flashed my N7.
I download the package the factory image from Google .
I entered the fastboot and do things following:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15r.zip
when it come to
Code:
fastboot -w update image-razor-jss15r.zip
there is a warning about the bootloader
At this time ,bootloader seems didn't chaged , it's still grouper not flo.
I modified the android-info.txt to cheat the program and the tragedy start.
The windows remind me there is 6 unknown device. And then it fully bricked.
Now, When I turn on the N7, the screen stay blank.
APX device appear while connect to PC.
Can't enter fastboot mode ,can't enter recovery. even the screen can't be lighten.
Anyone else meet the same trouble or someone can help?
Before this, I have had try the follow tools.
The Nexus7 toolkit--won't work
tegra-android-developer-pack from nvidia website tegra developer tools --won't work
nvflash and wheelie from androidroot.mobi --can't work --(It's a rediculous project I think, If the fastboot work,why we need to flash rom via nvflash)
Sorry, but if you really flashed the files above, you have bricked your N7 completely. Probably you should have looked around and informed yourself before starting to flash files which are not compatible with the N7.
Btw. if you had used wheelie before, you would have some recovery files and you would be able to recover yourself from the brick. So it's not a ridiculous project at all.
I thought it's common sense to read, read, read and read a bit more faqs/how-tos/guides before doing anything to a device.
First of all, 'grouper' is the codename of the 1st gen N7 Wi-Fi (the 2012 model) while 'flo' is the 2nd gen N7 (2013 model), so you can't flash ones image to the other device.
Secondly, your device might be saved, but only if you still can access it with fastboot. If so, then flash the proper images for your device using a toolkit or a guide, if not, then you have a nice paperweight.
37nook said:
For updating to android 4.3 , I flashed my N7.
I download the package the factory image from Google .
I entered the fastboot and do things following:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15r.zip
when it come to
Code:
fastboot -w update image-razor-jss15r.zip
there is a warning about the bootloader
At this time ,bootloader seems didn't chaged , it's still grouper not flo.
I modified the android-info.txt to cheat the program and the tragedy start.
The windows remind me there is 6 unknown device. And then it fully bricked.
Now, When I turn on the N7, the screen stay blank.
APX device appear while connect to PC.
Can't enter fastboot mode ,can't enter recovery. even the screen can't be lighten.
Anyone else meet the same trouble or someone can help?
Before this, I have had try the follow tools.
The Nexus7 toolkit--won't work
tegra-android-developer-pack from nvidia website tegra developer tools --won't work
nvflash and wheelie from androidroot.mobi --can't work --(It's a rediculous project I think, If the fastboot work,why we need to flash rom via nvflash)
Click to expand...
Click to collapse
This is a text book example of what happens when people don't read enough, and don't fully understand what they're doing. And it's not as if there aren't enough guides and how-to's here on XDA... and even on other forums!
Hi, 37nook...
You have almost certainly over-written your bootloader with a completely incompatible version designed for a different tablet (2nd gen Nexus 7)... and thus you are hardbricked. This is why you can't access fastboot mode and why your tablet defaults to APX mode when you hook it up to your PC.
And unless you had at some point run the flatline procedure BEFORE being bricked, your tablet is unrecoverable.
Regarding flatline (nvFlash) itself, it's designed, primarily as an emergency recovery measure... and not as a replacement for fastboot, as you seem to suggest in your post. It's preemptive and needs to have been executed before being 'bricked' in order to generate your own unique 'wheelie blobs', which are created on a per-device basis. Without these, nvFlash alone is useless.
It's not much comfort, I know... but I can only suggest you chalk this down to experience, and next time, with whatever tablet/phone you next end up with.... PAY ATTENTION TO WHAT YOUR DOING, AND READ EVERYTHING, and if you're still a little unsure... POST A QUESTION. Better to feel like you're asking a dumb question (which might not be so dumb), than end up with an expensive paperweight.
Rgrds,
Ged.
AndDiSa said:
Sorry, but if you really flashed the files above, you have bricked your N7 completely. Probably you should have looked around and informed yourself before starting to flash files which are not compatible with the N7.
Btw. if you had used wheelie before, you would have some recovery files and you would be able to recover yourself from the brick. So it's not a ridiculous project at all.
Click to expand...
Click to collapse
nvflash is not a good choice for one to flash his device because of higher risk.
there is too many tools available with a lower risk.
That's the reason I didn't use wheelie before.
You are right, I am a very impatient person, and now I get a lesson.
Erovia said:
I thought it's common sense to read, read, read and read a bit more faqs/how-tos/guides before doing anything to a device.
First of all, 'grouper' is the codename of the 1st gen N7 Wi-Fi (the 2012 model) while 'flo' is the 2nd gen N7 (2013 model), so you can't flash ones image to the other device.
Secondly, your device might be saved, but only if you still can access it with fastboot. If so, then flash the proper images for your device using a toolkit or a guide, if not, then you have a nice paperweight.
Click to expand...
Click to collapse
It's actually a nice paperweight now.
Thank you for your reply which tells me where I went wrong.
It's a really serious mistake, and it's also a painful story.
I can't access it with fastboot ,so said.
GedBlake said:
This is a text book example of what happens when people don't read enough, and don't fully understand what they're doing. And it's not as if there aren't enough guides and how-to's here on XDA... and even on other forums!
Hi, 37nook...
You have almost certainly over-written your bootloader with a completely incompatible version designed for a different tablet (2nd gen Nexus 7)... and thus you are hardbricked. This is why you can't access fastboot mode and why your tablet defaults to APX mode when you hook it up to your PC.
And unless you had at some point run thev flatline procedure BEFORE being bricked, your tablet is unrecoverable.
Regarding flatline (nvFlash) itself, it's designed, primarily as an emergency recovery measure... and not as a replacement for fastboot, as you seem to suggest in your post. It's preemptive and needs to have been executed before being 'bricked' in order to generate your own unique 'wheelie blobs', which are created on a per-device basis. Without these, nvFlash alone is useless.
It's not much comfort, I know... but I can only suggest you chalk this down to experience, and next time, with whatever tablet/phone you next end up with.... PAY ATTENTION TO WHAT YOUR DOING, AND READ EVERYTHING, and if you're still a little unsure... POST A QUESTION. Better to feel like you're asking a dumb question (which might not be so dumb), than end up with an expensive paperweight.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for your suggestion
There is still a question
I actually run these code twice.
First time a got a warning. because of the file content of android-info.txt in image-razor-jss15r.zip
the code
Code:
fastboot reboot-bootloader
must have been executed, and the bootloader is still grouper.
means the code
Code:
fastboot flash bootloader bootloader-flo-flo-03.14_img
didn't work
And the second time
Code:
fastboot -w update image-razor-jss15r.zip
led to the tragedy because I modified the android-info_txt in image-razor-jss15r_zip
What happened in updating image-razor-jss15r_zip ?
37nook said:
Thank you for your suggestion
There is still a question
I actually run these code twice.
First time a got a warning. because of the file content of android-info.txt in image-razor-jss15r.zip
the code
Code:
fastboot reboot-bootloader
must have been executed, and the bootloader is still grouper.
means the code
Code:
fastboot flash bootloader bootloader-flo-flo-03.14_img
didn't work
And the second time
Code:
fastboot -w update image-razor-jss15r.zip
led to the tragedy because I modified the android-info_txt in image-razor-jss15r_zip
What happened in updating image-razor-jss15r_zip ?
Click to expand...
Click to collapse
That is indeed puzzling... if after flashing the incorrect bootloader, and the bootloader is still showing as 'grouper' AFTER fastboot reboot-bootloader, then I'm puzzled.
I'm also further puzzled, that the rest of the flash went ahead... seemingly successfully. I know on my 'grouper', when fastboot flashing back to factory stock... if the bootloader isn't the correct version (for that version of factory stock), the flash aborts with the message 'Incorrect bootloader version'. I'm not sufficiently knowledgable though, concerning the specific details of the second gen Nexus 7 and it's associated stock factory images, to make further comment.
It's just possible (though unlikely), you might just be stuck in APX mode, instead of having a corrupted bootloader.
I assume you've tried all the usual button press combos... detailed here.
If you can boot into the bootloader, your Nexus 7 is recoverable... though I'm not optimistic.
Rgrds,
Ged.
OP, did you ever have any luck?
zamboniman87 said:
OP, did you ever have any luck?
Click to expand...
Click to collapse
+1
Hard Bricked Nexus 7 2012 Wifi NVFlash tool reports "uknown device found"
I just need to know and maybe need help modifying the adb/fb/apx android_apxusb.inf file more specifically targeted toward the nexus 7 for windows xp, my tablet does not boot into fastboot mode so fastboot.exe and adb.exe commands for reviving my tablet is out of the question.The nvflash tool in apx mode would be my only hope as the tablet stays with black screen and does not even show battery icon of it charging.I have been searching day and night for a solution and nothing.I have tried all the button combinations for the weird amount of seconds blah blah and nothing, i have tried everything, believe me...nvflash would be my only hope.I do not have any backed up blob.bin files so I can not use wheelie.exe I even tried someone elses blob.bin but no It is because the uid is unique I understand, I even opened the blob.bin file with notepad and supplied my CSSN code and the first part worked but the next part stumped me.... the rcm version part.I have the Secure Boot Key generated by supplying the CSSN of device in blackthunders tool so I want to run NVFlash.exe --bl bootloader-grouper-4.18.img --sbk 0x10117000 0x761CD506 0x7EE73604 0xBE055203 --sync.I have tried the universal naked drivers 0.73 but "ASUS Transformer Prime APX Interface" shows up in device manager after modifying the android_apxusb.inf file and supplying it the "Hardware device id" from device mamager by right clicking selecting properties etc;.Could there be an entry I could put in the android_apxusb.inf file for nexus 7 that nvflash.exe would not report "Uknown Device Found" and would recognize my nexus 7?.I did get the "ASUS Transformer Prime APX Interface" succesfully installed but nvflash is whining about the device being unknown.Furthermore I would like to make clear that the were no exclamation yellow triangles or anything and the device reported as working properly in device manager.I dearly would appreciate some insight into this.This all happpened on a personal quest to flash another kernel.Sequentially I use "TWRP" to wipe everything that they suggest you wipe" Davlik cache", "data", and two others, but after I wiped them I noticed that those were recommended to be wiped for flashing another ROM.I read just a little more down in the webpage that for flashing a kernel I only needed to wipe Davlik Cache and Data.I restarted the tablet and bam! bootloop.The android colorful spheres and no further.To recover from this I used Skip's Nexus v1.8.0 used the Soft-Bricked Bootloop option on the middle right of the tool's GUI hit the Flash Stock+Unroot buttton and let it run.I would let it run then it would take to long and appear to not progress so I stopped it and re ran it.This happened a few times but I finallly got it to complete, and after the toolkit rebooted my device i saw the "GOOGLE" Text when device booted.I waited for about 2 minutes and I saw it was not getting anywhere so I powered the Nexus 7 device off.
Next thing I did was press power button and nothing.I have tried everyhing, I assume that the solution would be nvflash and a cutomized .INF file pin point targted specifically for the nexus 7 2012 WiFi only tablet.Please help me, if there is no special APXInterface entrie i can edit the android_apxusb.inf file to help nvflash detect my device then it is game over for me.LOL I have seen many people post with a similar and identical poblem that have given up but I'm determned.LOL
Begining to think that it has to do with the nvflash.exe version is why.
After downloading another nvflash.exe with it's acompanying .dll's I found a nvflash program that executed and did not display the familiar "unknown device found" error message.I did it with the "NVidia USB Recovery mode for mobile" driver, nothing fancy.I was surprised that that nvflash version at least ran.The nvflash version i used is the nvflashtf201which is the Tegra3 ICS nvflash.I run that version of nvflash and I at least get this message in the command prompt on Windows XP sp3 after issuing a "harmless" nvflash --sync command.
Nvflash v1.13.87205 started
chip uid from BR is: 0x0000000000000000015d483bd137ec12
rcm version 0X4
Command send failed (usb write failed)
I googled around and some people say that it is because the bootloader is locked, and other say it is because the SBK version is 2 or higher or somthing if im not mistaken.As far as I know is that before I got the gadget hard bricked the boot loader was unlocked.I have even gone as far as to reformating my other computer and installing Unity Linux just to get my device accepting the nvflash commands I have configured the "rules.d" files to what "lsusb" shows I have tried different versions of nvflash like from upload sites and even from nvidias site even tried a newer cable (the newer cable works better but the old one still works)., I downloaded the "Cardhu" "Jelly Bean" stuff from the Tegra Android Development Pack 2.0r6 ( not 2.0r7 because the Tegra Android Development Pack 2.0r7 gives me an md5 hash blah blah error and would not install). The Tegra Android Development Pack 2.0r6 comes with nvflash.The reason I downloaded it was just to get nvflash.I do not have any blob files backed up, I only have the SBK from the chip uid of my device thus would like to try and get a hold of an nvflash in which the "--sbk" command parameter has not been deprecated.I understand that maybe i might not get lucky as the the newer nvflash programs might all have the "--sbk" parameter neutered as well as a few more command parameters.So does anyone know if there is a nvflash version that has the -"--sbk" command paramete support so that I can test and verify if the failed error message above if because I did not supply the program a Secure Boot Key or am I wrong about thinking I need to supply nvflash with a Secure Boot Key in this newer version given the program has a recent algorithm given the program found my devices chip uid as shown in the comman line output above? If thers nothing I can do then can some one comfirm.If there is another nvflash binary that is Tegra3 ICS and has the "--sbk" parameter then point me to where I can find it, or pm me. Thanks
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?
funkyo0o said:
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?
Click to expand...
Click to collapse
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.
Blob.bin files are encrypted I think.
mzanette said:
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.
Click to expand...
Click to collapse
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.
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 don't say I didn't warn you it would not work.
current solution
mzanette said:
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.
Click to expand...
Click to collapse
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
i am waiting to know what is the mess that take it to APX mode; only after that i will order a motherboard.
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.
faizleaves said:
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
i am waiting to know what is the mess that take it to APX mode; only after that i will order a motherboard.
Click to expand...
Click to collapse
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.
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???
Related
For a few months now my a500 has been having problems, but I've only recently been able to spend some time looking at it. I've gone through many unbrick threads, and recovery threads, and bootloader patch threads, and am still stuck.
Here's the problem(i think): at some point I must have flashed a rom without wiping /data. Now when I use CWM to wipe the device it says it can't remove the packages.xml file.
After learning about the packages.xml file, i now understand why my tablet would force close, reboot, and generally behave badly, since the new rom can't write to the packages.xml file.
Edit: The solution was very simple, and I'm surprised it wasn't suggested in all the other "i can't delete packages.xml" threads i'd seen. The attribute flags on that file were set to immutable and append-only. I had busybox installed and was able to issue "chattr -r -i" on the file and then it removed fine and after flashing a new rom everything is glorious.
Here's what i've tried so far:
I've tried removing the file through adb, the adb shell, the terminal emulator on the tab itself.... no good.
I've tried using fastboot to reformat the data partition.... No good. apparently the HC bootloader doesn't allow this.
I've tried patching the HC bootloader, upgrading to the ICS bootloader.... this is where I'm stuck and need help
I can't get any of the utilities that are supposed to work over APX mode to work. I can get the tab into APX mode and it shows up both in windows as some Acer Iconia Something Recovery Something... but it seems as soon as the utility tries to send it commands the device disconnects. I tried this in linux as well with the same result. As soon as I send any commands to it via nvflash (even just "wait for device") it disappears from udev.
Can someone please help me either
1) figure out another way to just fix the permissions on the packages.xml file
2) figure out what is going wrong with apx mode
3) tell me another way to format the data partition.
4) tell me that i'm just missing something really obvious that is a 1 click fix?!
The bootloader you currently have in tha tablet doesn't have anything to do with APX mode. It is not used at all.
This is how APX works (simplified):
- Tegra2 CPU enters download mode, for which the software is written on one time programmable memory inside the processor itself
- APX waits in download mode for commands from nvflash utility
- nvflash downloads to tablet's RAM bootloader binary (the one you use in command line) together with other data like BCT and ODMDATA (those are actually not required by all APX commands)
- APX runs the bootloader downloaded to RAM (not the one in eMMC) and runs commands you give it with nvflash.
So APX support needs to be implemented in bootloader you download to the tablet (for example Skrillax_CZ's bootloader_apx.bin).
As for your main problem I'm afraid this probably means that your tablet's eMMC flash memory has failed. I'm not 100% sure but there shouldn't be any problem removing the file or formatting the partition using nvflash.
Post messages you get when using nvflash (whole output would be great). We will see where to get from there.
Thanks for getting back to me, I'm at work now so will mess around a little more when I get home.
for a little clarification when I was talking about the bootloader issue i think the utility i was thinking of was fastboot. I had seen some suggestions of using fastboot to format the partition and then found out that the HC bootloader doesn't work with fastboot. That's when I followed the trail to try to install the ICS bootloader and got into the APX stuff with nvflash, though it seems that if I can get nvflash working, I can format the partition with that and not need to flash a new bootloader.
As I said, I'll mess around a little more when I get home and post some logs, but I'm still worried about why the apx device disappears from my system as soon as i try sending it commands.
Hmmm you probably don't have your tablet's CPU ID. You need that in order to do anything in APX mode. It is somehow possible to get CPU ID from the APX itself but you would need to search the forum how to do it (AFAIK it is required to connect tab to a Linux machine to do that).
I've tried to flash custom ROMs on my nexus 7, 3 times now, each time has the same result. I flash the ROM, then the Gapps and wipe data/cache. What happens afterwards is an endless boot cycle and a frozen bootloader (after rebooting into bootloader pressing up and down do nothing, neither does power button.) So i pull the battery and reboot into bootloader, now it works. This time it is a little different. Usually I can go into CMD and re flash stock, fallowing the instructions on this forum. This time when I try the command "adb reboot bootloader" I get "Failed to find device",even tho my computer recognizes it as an "Android ADB Interface." So I decided to try and re install my ADB drivers and I get "Failed to handshake device' or something along those lines.
My bootloader also reads a little differently than usual so I'll list the information below, it might be helpful.
"Product name - grouper
Variant - not defined yet
HW version - ER3
Baseband version - N/A
Signed - not defined yet
Lock state - unlocked'"
So I'm stuck with a nexus 7 in bootloader and my computer is not able to connect to it. Any help would be nice. I've already tried fallowing the returning to stock guide 3 times so please don't give me a bunch of **** about that.
Help would be nice, information/instructions would be amazing. Please help.
CptHoovsen said:
Help would be nice, information/instructions would be amazing. Please help.
Click to expand...
Click to collapse
After you boot into the boot loader, Windows sees the device name as Grouper - and there is no Windows driver for Grouper.
Try to find a Linux system to connect with. Linux is much less picky about device names.
*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.
An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?
sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....
Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:
So a couple of weeks ago I accidentally let my battery die, which I try not to do because I have trouble getting it to turn back on again and this time it did just that: my tablet wouldn't power on at all. I searched up my symptoms: Power light comes on, Doesn't vibrate, Black screen, and everything pointed to either my motherboard went kaput or APX Mode. A new motherboard for my model is upwards of 50$, so I tried looking into what APX Mode meant. I'm decent with computers but this was beyond me, or more so that I have no idea where to find the files/programs to flash(?) it. Anyway digging through the threads here I looked at a recent one here and on a whim I tried the suggestion, even though it was to another problem they were having with APX Mode. And it worked!
My tablet turned on fine, but I am skeptical of how long that will last. So, some questions that I hope someone can help me with are, what is a "fastboot", and does it hurt the system in any way if used repeatedly? Is there another way (an app or something) that will be able to tell me my UID and SBK other than through a Linux computer? Also, bootloading, does that root the device in any way? When I was looking around it didn't sound like it did, but then sometimes it did and now I'm just confused.
Any help would be greatly appreciated, and thanks for looking!
All files needed for unlocking the bootloader, rooting and unbricking can be found in the root guide in my sig. Along with methods of retrieving the cpuid and also a guide to flash the bootloader using the apxflash tool - I try and keep download links up2date, let me know if you have any probs.
If your tab does have a faulty emmc and I'm not saying it does...it will eventually fail, being stuck at the Acer screen seems to be the most common symptom, followed by the inability to flash.
Fastboot gives the ability to perform wipes and flash via the windows command prompt...
Root is gained (on ics) with icsRoot tool...once done you can then nvflash the unlocked bootloader.
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
All files needed for unlocking the bootloader, rooting and unbricking can be found in the root guide in my sig. Along with methods of retrieving the cpuid and also a guide to flash the bootloader using the apxflash tool - I try and keep download links up2date, let me know if you have any probs.
If your tab does have a faulty emmc and I'm not saying it does...it will eventually fail, being stuck at the Acer screen seems to be the most common symptom, followed by the inability to flash.
Fastboot gives the ability to perform wipes and flash via the windows command prompt...
Root is gained (on ics) with icsRoot tool...once done you can then nvflash the unlocked bootloader.
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Ah, thank you! I will definitely go through those. I checked the cpuid one last night in case it decided to die while I was sleeping, so that's good. Although my sister's tablet doesn't have that file on hers at all? And its the same model ... anyway.
emmc? Forgive me, I am not well versed in these abbreviations. It hasn't gotten stuck at the Acer screen yet since I've had it, but ... its always a possibility.
Hmm, I didn't have it connected to the computer when I tried fasbooting it — is it considered something else when you power the tablet on holding the Power Button + the Volume Up button? Maybe it wasn't in APX Mode at all then, but I don't know if that makes it better or worse. No other way would make it turn on, it was just a dead black screen no matter what I did, and then I tried that and the Acer logo popped up.
And, sorry just to be clear, there's no way to unbrick a tablet without rooting it?
Thanks so much
emmc = memory chip!
Per+vol down = custom recovery
Pwr+vol UP = fastboot
Drivers - From Acer and adb_fastboot drivers from android sdk (or the mini.zip in the guide)
Cpuid/sbk imperative to run most of the unbricking files which are based on nvflash.
Root - unavailable on hc 3.2, not needed to unbrick but usb debugging needs to be enabled in settings. For ics use icsRoot,
skrilax_cz unblocked bootloader - needed to install custom roms. Needs cpuid. Will also flash cwm recovery. Gives fastboot ability. So you can flash a new recovery thru Windows command prompt i.e. enter fastboot
Open command prompt
Type in: fastboot flash recovery "name_of_your_recovery'.img
EUU - Acer upgrade tool which gets you back to stock. PC based, needs cpuid and also used to unbrick.
update.zip - Acer stock updates, some are full os dates some are just incremental updates. Used also to help with softbrick like getting stuck on the Acer screen. Cpuid not required, flashed via ext sd card.
Think that's it in a nutshell...as stated get your cpuid NOW
Which build of Android is the tab running??
Sent from my HTC_PN071 using Tapatalk
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Hi, bluescreened803...
APX mode is usually indicative of a corrupted bootloader partition. This could occur as a result of a bad bootloader flash (for example, with a loose/dodgy USB cable connection, during a bootloader flash), or as a result of overwriting/flashing the bootloader partition with something that is not a valid bootloader.
Whatever the cause, the Nexus 7 cannot boot without a bootloader, nor can it be placed in fastboot mode to receive fastboot flash commands. Similarly, it cannot boot into recovery mode, whether that be stock recovery or a custom recovery such as TWRP.
It's hard-bricked, and will display in Windows device manager as an APX device.
But... check out these button press combos...
https://forum.xda-developers.com/showthread.php?t=2133986
If these button press combos fail to revive your Nexus 7, then it's almost certain that it's hard-bricked, and will require a motherboard replacement to get it up and running again.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.
bluescreened803 said:
Thanks for your help!
I tried your button combinations but non of them worked. Is there anything I can do with the device in APX mode???? Can I not reflash a new bootloader???????
I also did find that in APX mode you can use nvflash to restore your device, but that requires device specific blob files that I cant get.
Click to expand...
Click to collapse
Hi again, bluescreened803...
Apologies with my delay in responding - been busy with family.
------
Regarding reflashing the bootloader...
You're in a catch-22 situation. You need a bootloader in order to flash a bootloader. Without a working bootloader, you cannot 'send' fastboot flash commands to the Nexus 7, and thus cannot flash a bootloader
------
Regarding nvFlash...
I suspect you're alluding to the 'flatline' procedure from 2013...
https://forum.xda-developers.com/showthread.php?t=2455927
This is a procedure which generates device specific 'wheelie blobs' - these 'blobs' are then stored away (eg., on your PC) in preparation for a rainy day, in the event that the Nexus 7's bootloader ever becomes corrupted or overwritten.
Theoretically, these 'blobs' can then be latterly used to rebuild/reconstitute the bootloader, and make the Nexus 7 bootable again, via nvFlash in APX mode.
Unfortunately however, these 'blobs' need to be created BEFORE the bootloader is damaged. And for the sake of emphasis...
Wheelie blobs are device specific.
Wheelie blobs are NOT cross-transferable.
In other words, 'blobs' generated on a specific Nexus 7 will ONLY work for that specific Nexus 7, and not for any other Nexus 7.
-------------------------------------------------
Some thoughts...
I always thought that 'flatline' was somewhat experimental, with a fairly low chance of success, but nonetheless, back in 2013, I generated my own Nexus 7 wheelie blobs - it was a nerve wracking experience, 'cos it involved (if I remember correctly) fastboot flashing a special custom modified version of Clockwork Mod Recovery, which in turn, flashed a special modified version of the bootloader, with special API 'hooks' in it, which allowed the creation of the 'blobs'. It seemed to have gone quite well, with the 'blobs' and associated files successfully created.
However, I never had the opportunity to actually test my 'blobs' out, because it would have entailed deliberately 'bricking' my Nexus 7 in order to actually test them and see if I could resurrect it from hardbrick...
...which wasn't something I was wildly enthusiastic about doing, for tolerably obvious reasons
Anyhow, my Nexus 7 is no longer in use, and last year, to free up space on my laptop, I deleted a lot of stuff, including all my Nexus 7 related files, including my wheelie 'blobs'.
-------------------------------------------------
If your Nexus 7 is bootloader hard bricked, and it certainly sounds like it probably is, then your only realistic recourse is to replace the motherboard.
Rgrds,
Ged.
bluescreened803 said:
I attempted to flash the factory image for Android 4.4.4 on my Google Nexus 7 (2012), but it wasn't successful.
This now resulted in my device no longer booting up, I am also unable to get into fast boot mode, or recovery mode.
When I plug my device into my computer, it shows as an unrecognised device.
I have, however, managed to get my device into APX mode and my computer partially recognizes it in this mode (in device manager, but not showing in adb devices or file explorer). If that helps at all?
What can I do to restore my Nexus to a fully working state?
Click to expand...
Click to collapse
There is a guide on how to unbrick your Nexus. I have post it on XDA, go check it out.