Related
My Samsung galaxy tab verizone wireless failed a flash from odin, now it is a rebbot loop. I can access in Download mode but the sistem stop on wait usb cable, and naturally windows can't detect it. In recovery mode (droid + box) windows can detect tab but kies can't do this, the tablet screen otherwise remain black. In the apx recovery with nvflash my pc can detect apx device i install driver and form the prompt says on all command
rcm version 0x4
command send failed (usb write failed)
please could you give me a hand
Do you think i need customer service? I read about locked bootloader and sbk. Does anyone know the key for unlock bootloader?
thank you
up
I can help you rigth now i already know how to do.
Friend to my happend the same thing i already know exactly what to do.
if you need help i can help you.
contac me at [email protected] or [email protected]
help please
when ive tried to use nvflash i get the locked bootloader error msg.
if you can help with any suggstion that wiould be so awesome its been a month like this. ,
Did you ever get past this?
[email protected] said:
My Samsung galaxy tab verizone wireless failed a flash from odin, now it is a rebbot loop. I can access in Download mode but the sistem stop on wait usb cable, and naturally windows can't detect it. In recovery mode (droid + box) windows can detect tab but kies can't do this, the tablet screen otherwise remain black. In the apx recovery with nvflash my pc can detect apx device i install driver and form the prompt says on all command
rcm version 0x4
command send failed (usb write failed)
please could you give me a hand
Click to expand...
Click to collapse
I'm dying 6 months not workigm
kuryaky said:
Friend to my happend the same thing i already know exactly what to do.
if you need help i can help you.
contac me at [email protected] or [email protected]
Click to expand...
Click to collapse
This is an open and public forum. Post the solution to this problem here so others can fix their tabs aswell..
ruipalmeira said:
This is an open and public forum. Post the solution to this problem here so others can fix their tabs aswell..
Click to expand...
Click to collapse
The post you responded to was made nearly a year ago.
ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz
Dhont said:
ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz
Click to expand...
Click to collapse
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img
kk
dibb_nz said:
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img
Click to expand...
Click to collapse
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid? or they have something to do with the kal-E1001?
Also i live in Belgium ... so i cant figure out wich or what packages to download but i got several yes .. prolly all ...
JUst info i wanted to give ..
But thx for the File gonna try that 1 now
Dhont said:
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
Click to expand...
Click to collapse
bootloader version v0.03.12-ics this is the stock bootloader which is locked
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid?
Click to expand...
Click to collapse
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC
dibb_nz said:
bootloader version v0.03.12-ics this is the stock bootloader which is locked
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC
Click to expand...
Click to collapse
There is also the option of building against the Windows Driver Kit using MSVC.
This have the slight disadvantage of having to download about 1300MB (MSVC+WDK) and no instructions if you don't have any idea how to compile.
Besides having to have Windows...
Hi everyone!
I am workiing on my problem since soo many days, now I am asking for help.
Here is all infos I can provide to you:
1) In january, I played with ROMs and CW, but I don't remember the names or versions I played with. For all those months since january, my A500 worked perfectly. August 20th, in the morning, I pressed POWER to play with it, and nothing happened: only the Acer logo.
- I can't open in recovery, when I press Power + VolumeDown, I have this:
Erasing cache before sd update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
- USB from my PC can't communicate with the tablet at this point, so I can't use any ADB commands.
- I can open the tablet in fastboot ! I tried to flash with the command: fastboot flash recovery recovery.img, but the tablet respond:
Fastboot: Not support the command in Lock Mode
Failed to process command download: 004d7000 error(0x2)
Click to expand...
Click to collapse
Even if I launch, in this right order:
fastboot oem unlock
fastboot flash recovery recovery.img
[got the same error msg from the tablet]
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!
MillerXL said:
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!
Click to expand...
Click to collapse
If you were playing with roms and CWM earlier, then there is a good chance your UID number is in one of the Clockworkmod back-up files. Check your external SD card (hope you didn't do something foolish like format it).
You get the "erasing cache etc, because the recovery is borked, and it's trying to run some update file that isn't/is there because it can't boot the OS. Also, bootloader/recovery versions may be mismatched.
With ICS+ you have to have the unlocked bootloader to use fastboot commands. Can't do it on a stock bootloader.
If you do not have a UID, you have to use Linux or an Ubuntu install on your PC. There's a couple threads on how to do this, and what scripts to run. @dibb_nz knows a little more about using linux to get the UID.
MillerXL said:
Hi everyone!
I am workiing on my problem since soo many days, now I am asking for help.
Here is all infos I can provide to you:
1) In january, I played with ROMs and CW, but I don't remember the names or versions I played with. For all those months since january, my A500 worked perfectly. August 20th, in the morning, I pressed POWER to play with it, and nothing happened: only the Acer logo.
- I can't open in recovery, when I press Power + VolumeDown, I have this:
- USB from my PC can't communicate with the tablet at this point, so I can't use any ADB commands.
- I can open the tablet in fastboot ! I tried to flash with the command: fastboot flash recovery recovery.img, but the tablet respond:
Even if I launch, in this right order:
fastboot oem unlock
fastboot flash recovery recovery.img
[got the same error msg from the tablet]
- I can open the tablet in APX mode ! But I don't have the CUID of the device........... I tried to find it from USBdview, and I even tried with Linux.
I tried all I could find on Internet. Maybe someone here can help me ? i'm sad that there is nothing to "plug and reset"
Thank you!
Click to expand...
Click to collapse
Your bootloader is not unlocked which is why u have the fastboot error.
As @Moscow Desire said, if u do not have a nandroid backup stashed somewhere,u need linux to get yr cpuid use this guide here http://forum.xda-developers.com/showthread.php?p=28294316
Sent from my GT-I9300 using Tapatalk 4
I followed all the stepts provided to get the uid with ubuntu. But I got this message from the terminal:
[email protected]:~$ cd Desktop
[email protected]:~/Desktop$ sudo su
[email protected]:/home/ubuntu/Desktop# gcc apx.c -o apx -lusb-1.0
apx.c: In function ‘main’:
apx.c:22:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘uint64_t’ [-Wformat]
[email protected]:/home/ubuntu/Desktop# ./apx
Error: Failed to open device!
Click to expand...
Click to collapse
I left a message in the topic, now I wish for a path to solve the error.
Thanks for your help !
There's quite a bit of info all thru that thread, you may find an answer in there somewhere. I can't help with linux side of things sorry. .if u are u runnin 32bit rather than 64bit there is a slight alteration to the commands, thats about all I can offer at this point
Sent from my GT-I9300 using Tapatalk 4
---------- Post added at 08:02 PM ---------- Previous post was at 07:55 PM ----------
MillerXL said:
I followed all the stepts provided to get the uid with ubuntu. But I got this message from the terminal:
I left a message in the topic, now I wish for a path to solve the error.
Thanks for your help !
Click to expand...
Click to collapse
dibb_nz said:
There's quite a bit of info all thru that thread, you may find an answer in there somewhere. I can't help with linux side of things sorry. .if u are u runnin 32bit rather than 64bit there is a slight alteration to the commands, thats about all I can offer at this point
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Oh, one other thing...power off yr tab and enter apx mode via the buttons...use paper clip to push in the reset button, you should feel a click as u push it...hold it in and then press the power button, wait for the power light to come on and then release the power button. After another second release the reset button. .it can be finicky to get right..if I remember correctly yr tab should vibrate too
Sent from my GT-I9300 using Tapatalk 4
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???
Yet another Newb
I have googled / search / read many posts & threads over the past days & weeks.
I had a Acer Iconia A500 freeze @ the Acer logo screen like so many other have had, BUT I managed to fix it last time.
My mate has an Acer Iconia A501 ( so its got a sim card as well ) & its done the same thing.
I have tried the same process as the last 1, but to no avail as yet.
I'm needing some help please guys as I bet its something really simple , but I cant see why its not working for me.
OK AFAIK its all been stock Acer roms & OTA updates.
Processes so far..
Power on & hold down volume + & slide screen lock get this & then reboots
erasing user data .. erasing cache...
Power on & hold down volume - & slide screen lock get this
Bootloader v0.03.12-ICS: starting fastboot USB download protocol
Power on & hold Volume - release power button when it vibrates / starts to boot , still hold down vol button
I have tried the same update.zip file as my last A500 experience , but it got me to the android icon with the spinning globe for hours, left from any where from 40 mins to over night & same basically a lockup. then tried again & somehow got it to almost 90 ish % & stayed like that for ages.
Now I can only get it to see the green android guy for 10-12 seconds before he falls over & dies with the red triangle & black exclamation mark inside it.
I'm not fussed on what rom etc or even stock acer again as I can OTA it back up to last again.
I would just like it to work again & see where I am going wrong...
Anyone able to assist in my error please.
OH micro SD card is formatted to Fat under Win7,
OR should it be Fat32 ?? ( I am going to format with another A500 Tablet & hope it works better )
Also when I go to start it
Power on & hold Volume -, release power button when it vibrates / starts to boot , still hold down vol button
it shows on screen that its erasing data before booting & seeking the update.zip file from sd card etc..
SO it looks like its all doing what it should be , but then doesn't.
Still looking for the reason why this flash recovery wont work.
Using various versions & ensuring all are renamed to update (update.zip file) & messages on booting are the same.
looking for / accessing update.zip file etc etc
Android guy sits there & now I cant even get the status bar below him , its just the guy 10 seconds & dead with his guts hanging out
Any thoughts or a correct file to go with the bootloader appreciated.
Am I doing something wrong OR is it that corrupt its stuffed ???
Thanks to you guru's for assistance
Next instalment
My next instalment on the "unhappy" A501
I have moved my trying to an XP Pro SP3 machine.
I have installed the USB driver package & also the Windows update for the MTP.
I plug in & turn on , windows detects the Acer Iconia A500 & loads into Dev Manager as Acer MTP
It doesn't load enough to appear as a separate drive in the "My Computer" though.
I spose its a small step , but still getting no where.
Please Help :crying:
as I would like to hand this back as I need to move house & it will take some time for me to get setup again to be able to look at fixing it.
Ask for more info & I will reply ASAP
Uninstalled the MTP update , same for the USB driver package & rebooted.
made sure the Acer dir had gone as well.
Installed USB driver pack again & looked at that it contains.. MTP folder & drivers are in there already ..
Still shows up as Acer MTP & nothing in My Computer.
I did see that it shows up with the yellow exclamation mark after a while & then re connects again. ??
IF I start Blackthunders A500 Filemanager using the power button / vol + & flicking the screen lock on/off, I start with Bootloader ver & "starting fastboot USB download protocol.
IS this any help to fix the tablet ??
edit : How do I confirm it has USB Debugging turned on IF I cant turn it on ???
Hi Noel, sorry you got troubs
Your ext sd card should really be formatted via android, although there is a tool for windows you can use called sd_formatter, HP also have a formatting tool, google either one - I have previously posted the sd_format tool "here somewhere" will provide the link if I can track it down.
The drivers are the most important part of getting your tab up and running again.
If you have the Acer ones and the USB ones installed correctly, you should be good to go. In saying that, it can be a real biarch when you're in the position you're in.
Uninstall the acer drivers, reboot. Do not have your tab connected, wait for windows to fully start and its done updating itself or woteva it needs to do lol.
Run the driver exe. If your tab is not booting its hard to tell if usb debug is enabled or not. ANd windows will have trouble detecting it....sooooo......
Go to the root guide in my sig, post #2 download the "babsector file". You will also need to download an ics or jb rom, there is a stock rooted ics or you can use one of 'civato's' Flex roms - I'm still running one of his old ICS ones and it does me fine, I've not kept up with the latest roms, so I cannot help you much with that sorry!
Download your rom and put it on your sd card (if theres a formatting issue we will find out very soon!!!)
Babsector is run via your PC, now, win7 32bit systems work best for this, so if you aint got one, find a mate thats got one! You will save yourself alot of grief by not using win8. Even XP or vista will work!!
You'll need to enter your cpuid so keep that at the ready.
Babsector will flash cwm recovery and install the unlocked bootloader for you.
After running the first bat file, enter recovery and do a complete wipe, (enable data/media option) It has to be a FULL wipe theres no getting around it. And yes, do the wipe procedure at least TWICE!!!!
Once the wipes are done, flash the rom and then run the b.bat file for good measure. As long as you see the big white "PASS" after running each bat file, you're good to go.
IF there is a problem, babsector will output an error....post that and we'll go from there!
Good Luck
dibb
dibb_nz said:
Hi Noel, sorry you got troubs
Your ext sd card should really be formatted via android, although there is a tool for windows you can use called sd_formatter, HP also have a formatting tool, google either one - I have previously posted the sd_format tool "here somewhere" will provide the link if I can track it down.
The drivers are the most important part of getting your tab up and running again.
If you have the Acer ones and the USB ones installed correctly, you should be good to go. In saying that, it can be a real biarch when you're in the position you're in.
Uninstall the acer drivers, reboot. Do not have your tab connected, wait for windows to fully start and its done updating itself or woteva it needs to do lol.
Run the driver exe. If your tab is not booting its hard to tell if usb debug is enabled or not. ANd windows will have trouble detecting it....sooooo......
Go to the root guide in my sig, post #2 download the "babsector file". You will also need to download an ics or jb rom, there is a stock rooted ics or you can use one of 'civato's' Flex roms - I'm still running one of his old ICS ones and it does me fine, I've not kept up with the latest roms, so I cannot help you much with that sorry!
Download your rom and put it on your sd card (if theres a formatting issue we will find out very soon!!!)
Babsector is run via your PC, now, win7 32bit systems work best for this, so if you aint got one, find a mate thats got one! You will save yourself alot of grief by not using win8. Even XP or vista will work!!
You'll need to enter your cpuid so keep that at the ready.
Babsector will flash cwm recovery and install the unlocked bootloader for you.
After running the first bat file, enter recovery and do a complete wipe, (enable data/media option) It has to be a FULL wipe theres no getting around it. And yes, do the wipe procedure at least TWICE!!!!
Once the wipes are done, flash the rom and then run the b.bat file for good measure. As long as you see the big white "PASS" after running each bat file, you're good to go.
IF there is a problem, babsector will output an error....post that and we'll go from there!
Good Luck
dibb
Click to expand...
Click to collapse
Morning dibb
I have the Acer USB driver pack that has MTP files as well, is this all I need or maybe that's the start of my problems ??
( Acer ones and the USB ones installed correctly ?? )
1 of my many issues is that as its not my tablet , I don't have the cupid at all.
It wont start so I cant get it that way , & tried to connect with blackthunders A500 file manager as well but doesn't output any data that I can see / find.
Im thinking I have to flash with an unlocked bootloader before I can do anything - Yeah ??
I am quite happy to eventually go back to stock ICS @ the ends so anything is good.
R u familiar with Linux at all, its the only way of retrieving yr cpuid.
If not, it will be a matter of finding an update.zip that will work 4 u. There is one in the root guide u can try?
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
R u familiar with Linux at all, its the only way of retrieving yr cpuid.
If not, it will be a matter of finding an update.zip that will work 4 u. There is one in the root guide u can try?
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Hi
Not played with any Linux before so this might be funny at best to say the least.
the update.zip you suggest , is that the HC 3.1 full ??? (then rename to update.zip) on sd card & try ??
Yep, there's a guide stickied in general for using Linux to get it.
And yep the hc 3.1 FULL. If u get it booting you can OTA all the way to ics, but that's quite time consuming. So root it and install cwm, that will get u yr cpuid. After that unlock the boot loader!!!
I see there's a kit Kat Omnirom, based on civatos flex Rom, gonna give it a spin myself
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Yep, there's a guide stickied in general for using Linux to get it.
And yep the hc 3.1 FULL. If u get it booting you can OTA all the way to ics, but that's quite time consuming. So root it and install cwm, that will get u yr cpuid. After that unlock the boot loader!!!
I see there's a kit Kat Omnirom, based on civatos flex Rom, gonna give it a spin myself
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Tried using USBdeview to get the cupid, found a sting with 15 character's so tried that with a "0" at the start.
used the SB calculator & then blackthunders APX flasher , but it didn't work.
got all the way through with out any issues , but didn't actually flash it
Had assistance from JdgM3NT4L but still trying
the issue is the CPUID though to ensure I have it
more help the better
.
*fergs* said:
Tried using USBdeview to get the cupid, found a sting with 15 character's so tried that with a "0" at the start.
used the SB calculator & then blackthunders APX flasher , but it didn't work.
got all the way through with out any issues , but didn't actually flash it
Had assistance from JdgM3NT4L but still trying
the issue is the CPUID though to ensure I have it
more help the better
.
Click to expand...
Click to collapse
Hi dibb_nz
with lots of help from JdgM3NT4L I now have the cupid & can get through all of Blackthumders apx flasher up to the 2nd stage of the flashing where its uploading the image file.
it goes into this about 50 % then just hangs...
How long should it normally run for the flashing ??
.
Oh dear, this is not an error u want to see...Would explain the freezing issues. I've never seen a suuccesful solution for the ebt error. Just keep trying sooner or later it will flash....also the tdv4 file has been known to work , you'll be back on hc 3.2 with that but you'll have root and cwm if that's any consolation, lol...
The manual nvflash methods work best babsector or civs nvflash. If it is a faulty chip then even if u do get it booting it won't be a permanent fix.....
See how u go with the other methods k?
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Oh dear, this is not an error u want to see...Would explain the freezing issues. I've never seen a suuccesful solution for the ebt error. Just keep trying sooner or later it will flash....also the tdv4 file has been known to work , you'll be back on hc 3.2 with that but you'll have root and cwm if that's any consolation, lol...
The manual nvflash methods work best babsector or civs nvflash. If it is a faulty chip then even if u do get it booting it won't be a permanent fix.....
See how u go with the other methods k?
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Looking for a link to civs nvflash...
is that on your pages as well , I haven't seen it as yet
.
Yep it is, it's on the unlocked bootloader post as well
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Yep it is, it's on the unlocked bootloader post as well
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Thanks
Is there any advantage to using XP rather than win7 ??
.
Not thats ever been report ed, but hey, woteva works
Sent from my HTC_PN071 using Tapatalk
*fergs* said:
Thanks
Is there any advantage to using XP rather than win7 ??
.
Click to expand...
Click to collapse
Ok
looks like its almost a lost cause..
using civs flasher in APX mode under win7
gets through the start of the flashing to failed executing command 25 NvError 0x120002
command failure: sync failed <bad data>
bootloader staus : Bct Write Failed <code22> message : nverror:0x42008 <0x6042008> flags :0
then it has *press anykey when your A500/501 is in botloader mode
press any key to continue .. so I did anyway
flashing bootloader : bootloader_v8.bin
nvflash started
[resume mode]
formatting partition 4 please wait.. command execution failed cmd 13, error0x120002
failed!
command failure: format partition failed <bad command>
bootloader status: unknown operation <code: 1> message: flags:0
.
When u tried the apxflash tool earlier, there's an option to "dump" yr bct - If u didn't do that try dumping it, and then choose " use saved bct' , sorry dude its been a loooong time since I've had to do it so I may not have the wording exactly right
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
When u tried the apxflash tool earlier, there's an option to "dump" yr bct - If u didn't do that try dumping it, and then choose " use saved bct' , sorry dude its been a loooong time since I've had to do it so I may not have the wording exactly right
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Ok thanks.
Will try that as well when I try #17 again shortly.
will make sure tablet is connected in APX before I click "dump"
I assume because I get all this way with multiple programs , the CPUID & SBK have to be correct ??
.