I've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
jynlude said:
I've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
Click to expand...
Click to collapse
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
jynlude said:
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
Click to expand...
Click to collapse
I have exactly the same error and cannot find any answer.
Can someone please help ?
yankeefr78 said:
I have exactly the same error and cannot find any answer.
Can someone please help ?
Click to expand...
Click to collapse
happen to have found a solution? i might just restart and try again from scratch
Same issue here. Recreated blobs, uninstalled and reinstalled drivers, rebooted everything, tried a different computer, no change.
Making an addition to this thread. Also having ongoing "Error 3 receiving response from command" when entering "./wheelie --blob blob.bin"
When run as root, I get:
"RCM_Receive communication failure"
The device is showing up when I run lsusb
Anyone been able to find a work around?
wanted to see if anyone can help with an update to see if anyone was successful with this yet? still scared to flash to hairybean without successfully going through this process
This worked for me
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
I'm glad this worked for you too! Gives promise that it will help others.
After bricking my TF201 once, I learnt my lesson and was not going to proceed without taking all the right precautions.
jynlude said:
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
Click to expand...
Click to collapse
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
unfortunately I dont have luck whit that, i can run 2 times wheelie.
1. time it says error 3
2. time it says nverror 0x2
and then device disconnects, i press and hold power and it boots directly into APX and i can start over with the same result
any solutions? :crying:
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Is it even possible to brick APX mode?
dj_chapz said:
Is it even possible to brick APX mode?
Click to expand...
Click to collapse
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
jim.g87 said:
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
Click to expand...
Click to collapse
Im trying to recover. I got the backup files. Long story short, flashed wrong recovery, wiped eMMC (all partitions gone i think) so i need to repartition. I am in constant APX mode, cant get out, if i hold power it reboots directly into APX...
I had the same problem, try use this version.
redvirus said:
I had the same problem, try use this version.
Click to expand...
Click to collapse
It's a long time ago but thanks, this version helped me overcome error 3.
:good:
Related
Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
arjona00 said:
Hello all.
I have an Asus TF201 bricked.
I readed a lot of forums, and nothing to do for now.
My Asus was fall in brick after install cwm, and now, only can reboot in APX.
When I reboot normal or fastboot, it only show logo and stop.
I can't enter in fastboot, adb dont detect my device.
Wheelie detect but I havn't got blob.bin, so I can´t use nvflash.
Arggg!
Is there any solutions?
Click to expand...
Click to collapse
I seem to have the same problem
Hi!
I have the same problem.
Somebody can hepl us please!! Thank you
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
alemap said:
why? why is so hard to find files to unbrick tf201?, ****ing secure boot, links deads
sometimes what is legal is not fair,
sorry but my skills are a dried **** as my translator
i try to find a .bct no encripted to build the blob.bin with my doubtful sbk from sbkCalc, but nothing,
I know it's possible, but I also realize that I will not be able to do.
Click to expand...
Click to collapse
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Did you have nvflash enabled before you bricked? If not then you have a paper weight.
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yes i enabled nvflash before brick, but i dont copied the blob.bin o any other file from the root backup folder to my pc.
i dont find it, maybe i delete carelessly when try install kitkat in the tablet.
tremendous fail !!.
If you bricked without having your NVflash blob files backed up, you're out of luck at the time of this writing. For a HARD BRICK, which you are experiencing, the ONLY way to recover if with those blob files. I have mine on google drive, dropbox, and on my PC for safekeeping.
I sold the prime I managed to brick for parts on ebay. I got $100 for it, but that was well over a year ago. There are better tablets out there, and most of them definitely put this old guy to shame. I would suggest upgrading your hardware, as the device you have is no longer usable.
I hate to be the bearer of bad news, but this is the chance you take when you unlock bootloaders, hack and flash ROMS, root, etc. Sometimes $h!7 happens. That's life.
Hello,
I have the same problem.
TF201 bricked !
Unable to go into the bootloader, so unable to go on fastboot !
I never activate nvflash so i dont have my blob file.
I'm sofwtare programmer, i think we could fin any way to hack nvflash or a wayt patch any blob file in order to be compatible for our device....
Please, union made strong ! We need to create or get a hack in order to use correctly APX!
---------- Post added at 08:35 PM ---------- Previous post was at 08:07 PM ----------
alemap said:
I downloaded Tegra Android Developer Pack and image "dalmore" where are some utilities to generate encrypted necessary to enable executing commands in the boot. These are: nvsecuretool.exe or nvsbktool.exe.
but anyway the correct key is needed.
I used the calculator sbk but do not know if this works only for Acer tablet with tegra2.
A desperate chance. would take the sbkcalculator, and the apk asus application to unlock the boot, and test if there is any clue as to how you can make the sbk from cpuid on this model.
but I have no hopes for it.
I hope someone knows how to get the sbk from the cpuid for asus tf201.
Click to expand...
Click to collapse
Interresting post...you could have the sbk on the tabs sticker...
But the question is...how patch a blob file in order to use the NVFlash....
I'm software programmer, maybe i can help you dude !!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Restorer said:
I'm sorry, but it is only possible to un-brick a hard-bricked TF201 by using files that have been created on your own device with NVFlash.
Click to expand...
Click to collapse
There is probably a way to hack this file....to patch this....
I would like to compare two file in order to see differences....maybe it's simple to merge and patch.....
Wellcome to the Wall.
Hello all,
I am trying to "re-energize" an Asus TF201 I inherited from a friend. The overall objective is to get a newer custom ROM on the thing so it will be worth something more than a Very Slow paperweight! I have read until my eyes are popping out, rolled up my sleeves, and gave it a try.
I started with stock 10.4.2.18 (2012) bootloader and 4.1.1.
Unlocked w/Asus tool and rooted with motochopper.
Started the NVFlash process (via matthill.edu) and got this far:
"With the Command Prompt window still open in C:\fastboot type adb pull /data/media/AndroidRoot You should have the following 7 files download from your Transformer Prime:
recovery.bct
create.bct
bootloader.ebt
blob.log
blob.bin
pt_restore.log
pt_patch.log"
I only have the first five -- no .log files.
I have limited experience with this stuff, so what does this mean?
Can I try the NV Flash process again to see if it will "pick up" the missing .log files?
I so appreciate the greater expertise out there!
ElizS said:
Hello all,
I am trying to "re-energize" an Asus TF201 I inherited from a friend. The overall objective is to get a newer custom ROM on the thing so it will be worth something more than a Very Slow paperweight! I have read until my eyes are popping out, rolled up my sleeves, and gave it a try.
I started with stock 10.4.2.18 (2012) bootloader and 4.1.1.
Unlocked w/Asus tool and rooted with motochopper.
Started the NVFlash process (via matthill.edu) and got this far:
"With the Command Prompt window still open in C:\fastboot type adb pull /data/media/AndroidRoot You should have the following 7 files download from your Transformer Prime:
recovery.bct
create.bct
bootloader.ebt
blob.log
blob.bin
pt_restore.log
pt_patch.log"
I only have the first five -- no .log files.
I have limited experience with this stuff, so what does this mean?
Can I try the NV Flash process again to see if it will "pick up" the missing .log files?
I so appreciate the greater expertise out there!
Click to expand...
Click to collapse
Maybe you missed this ?
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Thx Josh
Hello,
I download from the ASUS website the firmware with version "V10.4.2.18 Only for WW SKU (Android 4.1)" and the pop-up for update de firmware appear normally to me.
Then, the TF201 restarted and since then does not passes through the ASUS Logo.
I Was on 4.0.0.3, firmware 9.4.2.28 and tried to upgrade to a superior version (my mistake as I can see now).
Even when restarting with Power + VOL DOWN the only thing that appears is :
----......................
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.2.28-20120525" A03
Checking for android ota recovery
Booting recovery kernel image
-----------
And stays here forever... No option with the 3 icons, so I can choose USB... And neither the VOL UP during this process does nothing...
Anyone can help?
Thanks in advance
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
sl0mar said:
Looks like you updated to an incompatible version. The first thing you needed to do was to unlock the bootloader. Volume up will not work unless you specifically enable nvflash, which is the second thing you needed to do. Considering that you still have usb, you may be able to use fastboot to replace your recovery. From there you may still be able install an older rom. If you can get at least some kind of rom running, you'll want to enable nvflash first thing so that you can make your tablet bricksafe. Let us know if you get that far...
Click to expand...
Click to collapse
I installed the drives and the PC recognizes the TF-201.
But it seems that fastboot can't recognize the tablet.
Well, I didn't get so far...
But I still want to try, but I'm a little lost...
Any help?
what you see when u run fastboot devices ?
inbg said:
what you see when u run fastboot devices ?
Click to expand...
Click to collapse
From my PC device manager I can see the asus transformer Prime APX Interface and is saying that "This device is working properly.".
However, every command that I sent from fastboot the result is always the same:
< waiting for device >
I'm completely out of ideas to get this back to work...
THATS BAD do u have working adb ?
No i don't...
HOW to Reserruct from APX mode^
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
logicmate said:
HI all,
I have been searching for months how to unbrick the tf201 after trying to load the official update from Asus.
I see so many users stuck like myself in APX mode with the "unlocked" message and Asus Logo.
I have tried in all described ways on the forums to get it to fastboot mode but nothing is helping.
Asus as many have written, are charging a lot for repair, I even bought another used one hoping I could upload the saved blob file from it but it is device related as I read. Is there any solution that will help?
I see a lot of advanced users creating roms and upgrades but never proposing how to unbrick this device in APX mode.
Thank you for all developers here who take the time to push things forward. :angel:
Click to expand...
Click to collapse
Logicmate, seems there is no help how to unbrick the tf201 in APX mode...
Did you get lucky meanwhile?
This relates to the recommendation in this post.
I followed this guide and got as far as step 25. I have used the "by-name" in the 'dd' 'of' path (instead of "byname").
The device appeared to go into a reboot and froze with the Oppo logo as described in step 26.
Unfortunately fastboot and adb cannot communicate with the device anymore. All I see is a battery charge symbol on the phone when pluged into the PC. Attempting to start the phone normally or in recovery briefly displays the logo and then nothing.
Please help.
you must have made a mistake while following the guide.
it worked for countless others.
check your pm.
celoxocis said:
you must have made a mistake while following the guide.
it worked for countless others.
check your pm.
Click to expand...
Click to collapse
Thanks for your help via PM. I'm not sure if my reply PM got through.
The instructions therein seemed to reference files not available in the zipped package, so I was unable to continue.
Trying a few other things I did manage to get some sort of communication via the fastboot command however attempting to unlock or flash twrp returns a permission error.
If I was able to reestablish adb comms I could try the steps again, but I still can't get that working.
Any thoughts?
shlape said:
Thanks for your help via PM. I'm not sure if my reply PM got through.
The instructions therein seemed to reference files not available in the zipped package, so I was unable to continue.
Trying a few other things I did manage to get some sort of communication via the fastboot command however attempting to unlock or flash twrp returns a permission error.
If I was able to reestablish adb comms I could try the steps again, but I still can't get that working.
Any thoughts?
Click to expand...
Click to collapse
The word document is outdated but that's what I got from the OEM.
But basically what you have to do to unbrick your device is to plug in your phone to your PC.
Install the Driver in the package. Start the exe file. Read the instructions.txt file. Start flashing.
Why you are not successful with the guide and others are. I can not tell you. I would carefully read the steps and look out for copy/paste errors.
I need help too
Sorry to jump on this but I am in the same situation could you PM me the fix please.
Thanks and respect in advance
My TF201 is working. Recovery ok. Android is working and booting.
But every time when i want to reflash by fastboot i endup with
`< waiting for device >` Fastboot is responding on `devices` command with device id but on flash still waiting.
Now when i was trying again to flash i noticed something.
`lsusb` is returning my TF201 as
```
Bus 003 Device 049: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
```
I think thats my problem. Does anybody know how to repair it ?
Next step
Ok i figured out It's not a problem. This state is ok but still problem in flash -
After i reconfigured udev and serval things finaly able to call flash command but it only says "sending"
I'm sending there a recovery - flatline so 7MB waiting 5 minutes. No success.
Any ideas?
What bootloader version does it say your 201 is running?
NP
I was on some stock bootloader. Then i downgraded to 10.4.2.15. Finally i figured out fastboot on my PC was not communicating with tablet.
So i flashed recovery from my Macbook without any problem... Backuped tablet with wheelie and nvflash.
So my problem is gone. Now i flashed again kernel_chooser every thing is fine.
Just now im trying to find some old images of some linux and kernel to boot up some linux.
If you know about tell me. Otherwise we can close this thread.