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.
Related
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:
Good Morning,
I've recently purchased a Lenovo IdeaTab A2109 Tegra 3 running 4.1.1 (build A2109_A411_03_13_121126_UK) running stock but with the bootloader unlocked via fastboot.
Last weekend I read about APX/NVFlash which (subject to the backup) gives my device a true bootrom recovery to allow me to restore my device in the case of a brick (handy for if I mess around with custom roms).
So far I've tried using both Windows 8 (with Nvidia generic drivers) and Linux Mint 15 (in a VM) but both have ended in failure producing the following errors:
Windows 8) "Unknown Device Found"
Linux) "Nvflash v1.5.66719 started
rcm version 0X4
Command send failed (usb write failed)"
Two theories I have right now are 1) I'm missing something e.g. firmware.bin, key, etc. or 2) NVFlash is incompatible with my tablet but the problem is I can only find information/specific software for other tablets e.g. Asus TF.
Are there any suggestions for what I can try to get this working? I am able to get temporary root access via CWM and ADB if I need to get anything off the device.
Thank you.
Boot Rom is DRM protected
tech3475 said:
rcm version 0X4
Command send failed (usb write failed)"
Thank you.
Click to expand...
Click to collapse
0x4 incidates the Boot Rom is DRM protected.
As far as I got you need to change the motherboard to an unprotected Boot Rom.
m.hataj said:
0x4 incidates the Boot Rom is DRM protected.
As far as I got you need to change the motherboard to an unprotected Boot Rom.
Click to expand...
Click to collapse
Thanks
Looks like it will be impossible (for me) then since I can't find anything about it for this tablet (e.g. SBK, bootloader, etc.) for this model and I can't do something this low level.
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
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?