Hi All,
My A210 recently deciced to brick itself, I was watching a movie when it rebooted into fastboot screen saying fastboot failed so i powered off and it's only powered up in APX mode
Code:
0955:7330 NVidia Corp.
I've tried to use nvflash but failed, Is the Secure Boot Key Calc the same for the A210 as it is on acerhacks or the perl/c code thats been posted about.
I also have no idea of the other nvfaslh values like --odmdata and which bootloader do i use.
Can anyone point me in the right direction, i've tried the same nvflash commands in windows and also failed.
nvflash posted for a500 say's unknown device found, other nvflash error's at
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
the above happens when you run the program once and hangs when you re-run the program , --resume also returns a error
Code:
Nvflash started
[resume mode]
failed executing command 25 NvError 0x8
command failure: sync failed
Any help anyone please ?
darkspr1ite
Hi All,
well i've continued my reasearch, according to androidlife.de
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
this message means it's secure boot, even though i've tried a key generated by the acerhacks sbk generator it's not working ,
i've used several sbk generators and they all seem to give the same key, or not work at all.
Can anyone answer if the SBK generator does work for A210 or is it only tegra2 for a500?
i am assuming my device is sbkv2 and not one,
this is the bootloader in use prior to the brick
Code:
androidboot.bootloader=JB-3fb8d46
and my UUID
Code:
androidboot.serialno=015d256487300205
and the generated SBK
Code:
SBK: 0x90EA5D00 0x1DDB0700 0x1520E402 0x8CF65E03
is there no hope ? i cannot send back to acer, i live in africa and no easy way to ship to place of purchase, UK.
darkspr1te
EDIT: I think i figured out whats happened, I pulled the sd-card out to add some files to transfer to my phone and I noticed it had the original firmware file there named update.zip, so somehow it's upated from that and you cannot reflash booloader.blob from the update while it unlocked ? , i dont recall installing the update, my update's were all done via fastboot or sideload , anyway this is only a assumption and in no way really helps me get a correct sbk code for my device,
APX repair not possible without Tegra 3 Based SBK
Hi All,
Well it seems the SBK generator ive beel following is only for a500 tegra2 based device and not for Tegra3, so until a leak from acer or someone cracks the sbk for acer i have no chance of recovering this device, a shame , my cm11 files are push back to my git so anyone can continue the development of the rom.
regards
darkspr1te
Related
I have a B70 transformer (just 20 days old). Rooted with universal rootkit.
Wanted to install Ubuntu[emmc install].
Checked sbk version using sbkcheck uitlity. It first gave sbk version 1.
So went ahead Ubuntu install. Could'nt complete beacuse of "connection failed nverror 0x8".
So again ran sbkcheck utility. Got some error cant remember.
and now i cant do anything.
Just displays Entering NvFlash recovery mode when plugged in to usb.
Tried nvflash unbbricking gives "USB device not found"
Please Help!!!
You can try to use NVFLah unbricking method.
http://forum.xda-developers.com/showthread.php?t=1123429&highlight=nvflash
Tried nvflash unbbricking tool it gives "USB device not found"
I just ran into something along these lines too, accept i was installing the ICS alpha build.
I used the NvFlash from the revolver 3.11 thread to get back to a working state at least
Download link to NvFlash:
http://www.multiupload.com/PFMWB39SK4
Just run flash.bat
1pratham said:
I have a B70 transformer (just 20 days old). Rooted with universal rootkit.
Wanted to install Ubuntu[emmc install].
Checked sbk version using sbkcheck uitlity. It first gave sbk version 1.
So went ahead Ubuntu install. Could'nt complete beacuse of "connection failed nverror 0x8".
So again ran sbkcheck utility. Got some error cant remember.
and now i cant do anything.
Just displays Entering NvFlash recovery mode when plugged in to usb.
Tried nvflash unbbricking gives "USB device not found"
Please Help!!!
Click to expand...
Click to collapse
do you get the transformer into apx mode at all?
Thanks for your replies
Got nvflash unbricking tool working from windows. Don't know why it wasnt working on linux.
All fine now.
Just to make sure, since the unbricking tool worked, does it mean I have a sbkv1 device?
Yes you have sbk v1
I have a similiar problem. But i have an 3G model (TF101G), and its not mine its from a friend.
When i power on it only gets to the Eee pad Logo, than it stays there.
Can get into the wipe menu, where you can choose between wipe and "cold booting Linux", but cant get into asus recovery menu (Android Guy with gears).
Tried also nvflash with Windows and Linux, but everytime error "0X4".
my SN begins with "BA0K", so probably a SBKv3 device or?
But i cant be brick! there must be a way, because i can get into the Asus wipe menu and into APX-Mode. Everytime here in the forum its said that this is not really a brick, but perhaps though?
I hope not.
Or have i to be wait until the SBKv3 key will released?
pls help me
When i power on it only gets to the Eee pad Logo, than it stays there.
Can get into the wipe menu, where you can choose between wipe and "cold booting Linux", but cant get into asus recovery menu (Android Guy with gears).
Tried also nvflash with Windows and Linux, but everytime error "0X4".
Click to expand...
Click to collapse
@knopper84
That's exactly my problem , except I have the non-3G model (TF101). I'm currently downloading munsterrr's solution:
Download NvFlash revolver:
Just run flash.bat
Click to expand...
Click to collapse
Hope it will work . You should try it too.
[EDIT: Just tried munsterrr's solution. It didn't work at all. I guess I'll just wait for you guys to find a solution ]
Regards,
HorClok.
hmm i think i have tried it yesterday. Its this file ( http://www.multiupload.com/PFMWB39SK4 ) or? it gave me the same error (0X4)
For me it looks like exactly the same nvflash + bat like usual.
Or maybe is there something different there?
Which SBK you have? I think SBKv1 or?
IDK what SBK is...
I thought there was something different there.
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
knopper84 said:
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
Click to expand...
Click to collapse
Couldn't tell you, I don't use Linux.
So the Mac Version of the sbkcheck util works better?
Horclok said:
Couldn't tell you, I don't use Linux.
Click to expand...
Click to collapse
You have a B80 according to your other thread. This mean nvflash won't work.
knopper84 said:
i still tried the SBKcheck util on Linux-Live CD. It worked with "sudo", but i get SBKv1.
I think that is only because of the tool, because i have an 3G Model or?
Click to expand...
Click to collapse
If I remember correctly, 3G models have the SBKv3 but it reads as SBKv1.
Sent from my Transformer TF101 using XDA App
Hello everybody, I am very new to this and I am trying to install the Eagles blood 4.0.4 ROM. When I get to the step where you use the "one click recovery flasher" I get the "boot loader failed" error below. I get the S/W upgrade on the screen but when I hold the vol down + power i get the box with the lid open and the arrow like its updating instead of the blue LG logo. I have tried it a few times and i get the same thing. What am I doing wrong? Thanks for the help.
================================================== =============
================================================== =============
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
================================================== =============
================================================== =============
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208241415197
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
================================================== =============
================================================== =============
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Maybe you have an LG-P990 and not a LG-P999. Remove the back cover and look bellow the battery and it will tell your model. If it says LG-P999 you're in the right forums, If it says LG-P990 you're in the wrong forums, you have to go to the OX2 forums right here on xda.
it says LG-P999DW
If you're running windows 7 or vista, did you right click the program and run it as admin?
Follow this guide instead, but basically you need to re-flash recovery.
http://forum.xda-developers.com/showthread.php?t=1056847
That was is! I needed to open it as administrator. Thanks for the help! Im sure ill have more questions.
rootme4g said:
That was is! I needed to open it as administrator. Thanks for the help! Im sure ill have more questions.
Click to expand...
Click to collapse
Anytime
Dimension2035 said:
If you're running windows 7 or vista, did you right click the program and run it as admin?
Click to expand...
Click to collapse
Good deal. I forgot about that one in Windows.
rootme4g said:
Hello everybody, I am very new to this and I am trying to install the Eagles blood 4.0.4 ROM. When I get to the step where you use the "one click recovery flasher" I get the "boot loader failed" error below. I get the S/W upgrade on the screen but when I hold the vol down + power i get the box with the lid open and the arrow like its updating instead of the blue LG logo. I have tried it a few times and i get the same thing. What am I doing wrong? Thanks for the help.
================================================== =============
================================================== =============
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
================================================== =============
================================================== =============
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208241415197
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
================================================== =============
================================================== =============
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Click to expand...
Click to collapse
And, just a tip. Only post your issue once and don't hijack threads.
cool thanks
dude i am Waiting about a day since there appeared to letter "sending file: fastboot.bin".
if you know something about it can you help me?
I have the same problem. Help pls.
I have P990. I installed official ICS yesterday and then rooted it by an img file. I have to go back to GB. I can't use smartflash, it gives me error something like partitions 7 error.. I can't use nvflash it gives me same error in this topic, even if I try as administrator. Did I brick the bootloader?
If you have a p990 then you're in the wrong forum and anything you try from here will not work
Having intermittent power issues with LG P999DW - Hardware Issues ? Help
Hi,
I am having intermittent issues with LG P999DW. When I leave the phone for a couple of day off, battery removed, I am able to perform full recovery with NVFlash.
After a while, (last time less than an hour) the phone is dead. APX is working but NVFlash stops at "waiting for bootloader to initialize"
yesterday, I was able to Root it and afterward install One-Click-G2x-recovery-flasher-04-28-12
nothing much to do now ...
Any one have seen the same issue ?
I am trying to obtain a replacement mainboard (SAFY0400802) but it look like it is impossible to buy.
it is not anymore under warranty.
Thanks in advance
Did you download the driver correctly. Theres a step by step how to use nvflash and driver installation or on youtube.
Sent from my Nexus 4 using xda app-developers app
LG P999DW dead, Jelly bean not working
Hi,
I have two p999dw phones, the procedure from multiple threads/post works (e.g. super one click, CWM boot) have been tried.
My phone is working fine, my wife's stay 'dead'
So this help me in 'clearing out' driver issues.
One phone works perfectly, almost got it on Jelly beans (Android 4.1.1) before rebooting in loops. Got it back to stock recovery.
The other one need 3 days before coming up from deads. I am thinking about putting it in oven since in the cold does not resurrect it.
After trying different threads and removing an assert from scripts in cm-9.9.9-JB-p999-2, I think I am at the point of saying that I will be stuck to froyo for a while with Videotron from the multiple threads/posts .... the JB 4.1 seems to work on P990 & P999, not yet the P999DW ...
tried the forum with cm-9.9.9-JB-p999-2.zip, gapps-jb-20120726-signed.zip, cwm-5.0.2.8
Someone knows about a working rom with P999DW ?
Thanks
I will keep hope, LG seems to have released V30 (Android 4 ICS) in Europe ... for the P990 at least...
LG Optimus 2X P999DW, stuck at froyo for now ... Videotron, Canada
Hi, I know there are many threads with this particular problem, I did my research and I find this kinda strange (Iam also desperate...)
Long story:
Ive been swapping between official ROM and customs like a madman and Ive always rooted using this method (downgrade, then vipermod), but this time I accidentaly tried to enter recovery at first boot and since then Iam stucked at "EEE Pad" logo with half full progress bar.
tl;dr summary:
no adb
C10 transformer, sbkv2
no recovery
on boot w/ volume down it says 8.6.6 - the one Ive downgraded to; It also says "checking for ota recovery"
sucessful APX mode connect, universal drivers
When using standard nvflash ROM the process is terminated with "write error" message and disconnects the transformer - sbk2 problem, so Ive tried EasyFlasher which utilizes Wheelie for B70+ devices and the exact same thing happens (well, console and GUI says that everything is OK, but when the nvflash is getting ready the device gets disconnected too). There are many people saying in the thread that Wheelie helped them with basically the same problem...
Now Iam downloading linux to try Wheelie manually.
Any ideas how to fix this or I can pretty much toss my transformer out of the window?
Thanks for replies.
nevermind, Iam an idiot - did not realised that I actually have TF101G so sbkv3 and no nvflash for me
so, do you know if there is any "nvlash-for-sbkv3" project in progress?
Hi,
Have a TF300 that was still on ICS. Unlocked bootloader, Shut down to enter fastboot mode and nothing is happening.
Screen is blank, Power Light comes on if connected to charger,but can't connect to computer.
Have reset through pinhole in side of case.
Have turned it off with the internal switch doesn't respond at all.
Has anyone else had this happen?
Any suggestions accepted, greatfull.
Okay have manged to get it to boot using the keyboard/dock.
Have copied the 1st five files for NVFlash access just having drama getting it into APX mode.
Bill
Maniac_au said:
Hi,
Have a TF300 that was still on ICS. Unlocked bootloader, Shut down to enter fastboot mode and nothing is happening.
Screen is blank, Power Light comes on if connected to charger,but can't connect to computer.
Have reset through pinhole in side of case.
Have turned it off with the internal switch doesn't respond at all.
Has anyone else had this happen?
Any suggestions accepted, greatfull.
Okay have manged to get it to boot using the keyboard/dock.
Have copied the 1st five files for NVFlash access just having drama getting it into APX mode.
Bill
Click to expand...
Click to collapse
Check my signature for a link that includes much information about accessing apx.
I hope this helps.
Thanks tobdaryl
Ok have managed to get into APX Mode, However insted of showing up as NVidia APX mode device it shows up as Asus Transformer Prime APX Interface.
When I type "wheelie --blob blob.bin" it responds with error "Failed to open blob file blob.bin"
Is it the device driver that is the problem? After doing even more reading I don't believe it's that cause checking
the naked drivers inf file it matches with the PID & VID.
However had to pinch my wifes Sammy to remove their drivers as mine got wet a few weeks ago.but the device tree shows up as SAMSUNG Android Phone with the Asus Transformer Prime APX Interface under the tree.
Is blob.bin on the tablet? It boots with the correct message AndroidRoot 9.4.3.30r01 in top left corner.
Bill
Maniac_au said:
Thanks tobdaryl
Ok have managed to get into APX Mode, However insted of showing up as NVidia APX mode device it shows up as Asus Transformer Prime APX Interface.
When I type "wheelie --blob blob.bin" it responds with error "Failed to open blob file blob.bin"
Is it the device driver that is the problem? After doing even more reading I don't believe it's that cause checking
the naked drivers inf file it matches with the PID & VID.
However had to pinch my wifes Sammy to remove their drivers as mine got wet a few weeks ago.but the device tree shows up as SAMSUNG Android Phone with the Asus Transformer Prime APX Interface under the tree.
Is blob.bin on the tablet? It boots with the correct message AndroidRoot 9.4.3.30r01 in top left corner.
Bill
Click to expand...
Click to collapse
The way the driver shows is not an issue. Many have reported that and used it with success. That is the price we pay for universal drivers.
wheelie --blob blob.bin
is in the list of files you should have created. Find them and place in your directory with wheelie.
NVFlash Files you should have created ( 8 total )
blob.bin
blob.txt
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
I guess I can assume they are in the folder with fastboot?
Looks like I spoke to fast.
Once your blobs have been generated you will need to retrieve them from the “internal” SD card from the AndroidRoot directory (e.g. /sdcard/AndroidRoot). You can do this either through MTP mode or by pulling them using adb.
tobdaryl said:
The way the driver shows is not an issue. Many have reported that and used it with success. That is the price we pay for universal drivers.
wheelie --blob blob.bin
is in the list of files you should have created. Find them and place in your directory with wheelie.
NVFlash Files you should have created ( 8 total )
blob.bin
blob.txt
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
I guess I can assume they are in the folder with fastboot?
Looks like I spoke to fast.
Once your blobs have been generated you will need to retrieve them from the “internal” SD card from the AndroidRoot directory (e.g. /sdcard/AndroidRoot). You can do this either through MTP mode or by pulling them using adb.
Click to expand...
Click to collapse
Okay thanks for your help got it to work after a few goes.
This is a FrankenTablet that I fitted a Screen & Digitizer from my other JB locked unit.
Its been sitting in a box turned completely off waiting for this.
Bill
Maniac_au said:
Okay thanks for your help got it to work after a few goes.
This is a FrankenTablet that I fitted a Screen & Digitizer from my other JB locked unit.
Its been sitting in a box turned completely off waiting for this.
Bill
Click to expand...
Click to collapse
Great! Welcome back. Sounds like you've had your share of problems.
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
only thing I can guess if you still have the stock Recovery is trying the reset button on the left side under the external sd slot. But this can make it worth.
What exactly to do with reset button ?
Sent from my Nexus 4 using xda app-developers app
petition
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
rhc94 said:
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
Click to expand...
Click to collapse
How did you take a blob.bin????
atoma1972 said:
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
Click to expand...
Click to collapse
yeah m8 same as me from 2 days now your soft briked and nothing else to do but w8t or send it to asus and be charged for the repair.
Sign the petition and maybe wer in luck some day not to far.....