Need help with APX mode - Asus Eee Pad Transformer Prime

Hello,
I tried to flash Android 4.4 with an updated version of TWRP.
Once the installation was done, my tab hangs at the bootscreen.
I'm seeing the asus logo, but without the text "This device is unlocked"
Lucky me, i have the NVflash, and the blobs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and the imgs
Also i'm able to get in the APX mode
Code:
D:\Tablet Brick safe\tf201_nvflashpack>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07875164040c
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
So what should i do next?
Thanks dor the help.

---

brantje said:
So what should i do next?
Thanks dor the help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1927818
And boom goes the dynamite..

---

wickid_d said:
http://forum.xda-developers.com/showthread.php?t=1927818
And boom goes the dynamite..
Click to expand...
Click to collapse
If I don't have blob.bin, can I unbrick my tf201 ?
How can I get this file ?

---

darkjeff said:
If I don't have blob.bin, can I unbrick my tf201 ?
How can I get this file ?
Click to expand...
Click to collapse
With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little.

---

wickid_d said:
With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little.
Click to expand...
Click to collapse
I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot.

---

darkjeff said:
I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot.
Click to expand...
Click to collapse
Have you tried using adb to reboot to it? 'adb reboot-bootloader'? Even if CM (or any rom, for that matter) is just barely starting to boot, you should be able to do this. Once you get to fastboot, follow this guide:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
And then follow the guide in my previous post in this thread and that will at the very least get you back to stock.
And remember, whenever you flash something in fastboot, no matter what it is, use the option '-i 0x0b05'.. Like for recovery 'fastboot -i 0x0b05 flash recovery (name of recovery here)' This will save you more headaches.

---

Trouble with generating blob.bin with Flatline_tf201.img / CWM
Moved to proper thread

---

brantje said:
Hello,
I tried to flash Android 4.4 with an updated version of TWRP.
Once the installation was done, my tab hangs at the bootscreen.
I'm seeing the asus logo, but without the text "This device is unlocked"
Lucky me, i have the NVflash, and the blobs.
So what should i do next?
Thanks dor the help.
Click to expand...
Click to collapse
Did you solve it? I think i am in same trouble.

---

vanquishe said:
Did you solve it? I think i am in same trouble.
Click to expand...
Click to collapse
Mot yet l. Will look into it this weekend. Quite busy with work.
Sent from my SM-N9005 using Tapatalk

---

I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
1. Stock JB, newest from OTA, untouched
(im from japan, so i think its a JP SKU)
2. Followed guide to unlock + backup blobs + enable nvflash for JB
http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
3. Rooted with motochopper
4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14]
http://forum.xda-developers.com/showthread.php?t=2589554
4.1 Downloaded and transfer following files to sdcard folder
cm-11-20140220-UNOFFICIAL-tf201
pa_gapps-modular-mini-4.4.2-20140227-signed
4.2 Downloaded recovery.img.SOS 2013-12-29 08:42
http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS
4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS
(I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly)
4.4 restart TF, "power+down", select RCK
4.5 Did the following in recovery menu:
a. Backup, but did it to sdcard instead of ext storage
b. wipe data/factory
c. wipe cache partition
d. wip dalvik cache
e. install zip: cm-11-20140220-UNOFFICIAL-tf201
f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed
At step f, the screeen said somthing about insufficient space.
So i thought i would try without GAPPS and selected reboot system now.
5. Got stuck at Asus word in middle of screen
a. Bottom right shows "Powered by nvidia terga"
b. Oddly, top left no longer displays "device is unlocked"
6. Tried to reboot (holding power long time)
a. Screen black out, vibrate
b. Tried to get to fastboot (power + down) but the icons never show
c. Constantly stuck with Asus screen
7. Attempted to follow guide:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
a. "Power + up", apx device shows in windows 7 device manager
b. wheelie.exe --blob blob.bin
c. nvflash.exe -r --download 4 bootloader.EBT
(bootloader.ebt is the output i got previously from flatline)
(my bootloader.ebt is 1,558,608 bytes)
(blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes)
d. This is the log
log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader.ebt
bootloader.ebt sent successfully
e. Device went black screen, device manager does not show APX
f. I power the device up but shows black screen. "power + down" still does not work.
g. However, "power + up" still get APX device in windows.
---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ----------
Im thinking I could try either of the following:
Option 1:
1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed
and try to go as far as I can and pray for the best
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Option 2:
1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T]
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
seems to talk about unlock-token.img,bricksafe.img,factory-config.img
but it is for tf300T
also, i have no idea how to get the following file
"this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run
"Code: nvflash -r --download 5 twrp.blob"
Option 3:
1. Sit and wait for help... no one on MIRC seems to be responding T T
Any ideas?

---

vanquishe said:
I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
Any ideas?
Click to expand...
Click to collapse
Ok, first off, it IS 0x0b05.. 0b05 is the vendor/hardware hexadecimal ID number, which is why -i (short for ID) when using fastboot. You can verify this by hooking the tablet up to a linux environment and running 'lsusb' in terminal and looking for the Asus line. In Windows, I'm not exactly sure why the 0x gets added at the front. I guess it's just how Windows handles hardware IDs. (source: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ part: (Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05".))
Second, you won't be able to install the full PA Gapps along with CM11 - you're right, there isn't enough room. Use either the micro or mini package. This is talked about in the CM11 thread you mentioned, where I have been frequenting, as of late.
Third, and finally, what exactly are you waiting on? You've done everything correctly as far as I can tell. Just start the process over with reinstalling stock via this guide:
http://forum.xda-developers.com/showthread.php?t=1927818 and you can either flash TWRP through nvflash mode like you did (good job on that ), or via fastboot, and go from there. Whether it shows 'this device is unlocked' or not, at this point, shouldn't matter.. You've run through the nvflash process and created your blob.bin along with the other files.
I hope this helps.

---

Hi Mates,
Will start looking into it now.
As long i can get TWRP i'm happy, because then i i'm not far from installing a custom rom.
14:55 - Tablet was empty its charging now
16:27 - I'm screwd i think...
D:\Downloads\Tablet Brick safe\Tablet Brick safe\tf201_nvflashpack>wheelie.exe -
-blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07875164040c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
Will keep this post updated about my progress.

---

vanquishe said:
I am in the same fix. Here is what I did so far. I hope someone can provide some advice.
1. Stock JB, newest from OTA, untouched
(im from japan, so i think its a JP SKU)
2. Followed guide to unlock + backup blobs + enable nvflash for JB
http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/
3. Rooted with motochopper
4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14]
http://forum.xda-developers.com/showthread.php?t=2589554
4.1 Downloaded and transfer following files to sdcard folder
cm-11-20140220-UNOFFICIAL-tf201
pa_gapps-modular-mini-4.4.2-20140227-signed
4.2 Downloaded recovery.img.SOS 2013-12-29 08:42
http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS
4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS
(I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly)
4.4 restart TF, "power+down", select RCK
4.5 Did the following in recovery menu:
a. Backup, but did it to sdcard instead of ext storage
b. wipe data/factory
c. wipe cache partition
d. wip dalvik cache
e. install zip: cm-11-20140220-UNOFFICIAL-tf201
f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed
At step f, the screeen said somthing about insufficient space.
So i thought i would try without GAPPS and selected reboot system now.
5. Got stuck at Asus word in middle of screen
a. Bottom right shows "Powered by nvidia terga"
b. Oddly, top left no longer displays "device is unlocked"
6. Tried to reboot (holding power long time)
a. Screen black out, vibrate
b. Tried to get to fastboot (power + down) but the icons never show
c. Constantly stuck with Asus screen
7. Attempted to follow guide:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
a. "Power + up", apx device shows in windows 7 device manager
b. wheelie.exe --blob blob.bin
c. nvflash.exe -r --download 4 bootloader.EBT
(bootloader.ebt is the output i got previously from flatline)
(my bootloader.ebt is 1,558,608 bytes)
(blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes)
d. This is the log
log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader.ebt
bootloader.ebt sent successfully
e. Device went black screen, device manager does not show APX
f. I power the device up but shows black screen. "power + down" still does not work.
g. However, "power + up" still get APX device in windows.
---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ----------
Im thinking I could try either of the following:
Option 1:
1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed
and try to go as far as I can and pray for the best
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Option 2:
1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T]
http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717
seems to talk about unlock-token.img,bricksafe.img,factory-config.img
but it is for tf300T
also, i have no idea how to get the following file
"this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run
"Code: nvflash -r --download 5 twrp.blob"
Option 3:
1. Sit and wait for help... no one on MIRC seems to be responding T T
Any ideas?
Click to expand...
Click to collapse
Exact same boat, so will try and look for answers now.
Where on mirc, maybe we can help each other.

---

I will just sit quietly here and wait for anyone with an answer.
(Yes, me too)
vanquishe said:
(what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img)
Click to expand...
Click to collapse
Yes, that.
I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore.

---

Xerxes-3.0 said:
I will just sit quietly here and wait for anyone with an answer.
(Yes, me too)
Yes, that.
I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore.
Click to expand...
Click to collapse
I had help from a nice person from IRC. Now my TF201 is up and running again.
I will up the process he guided me once I get home later.

---

Please thank lj50036 from the CMB team.
It was him that guided me thru the process to unbrick my TP.
-----------------------------------------------
Bricked situation:
1. Last activity before brick: Stock with latest OTA -> Flatline (OK) -> Motochopper (OK) -> Flash CWM recovery (OK) -> Unofficial CM11 (Reboot = bricked)
2. Stuck at ASUS logo on power up/reboot. (Device is unlocked no longer shows on top left corner)
3. Cannot get to fastboot (power + dwn = stuck at ASUS logo)
4. However, can invoke APX mode (power + up = APX device detects in windows)
-----------------------------------------------
Preparation:
1. All the output files from the flatline (blob.bin, unlock-token, bricksafe, factory-config etc)
2. Fastboot,adb,nvflash exe (you should have all these when you did flatline)
3. Enough battery (I left it overnight to charge, since I had no way of checking batt)
4. The stock firmware from ASUS (you should get the same version as the one you had prior to brick)
-----------------------------------------------
Actual process:
1. I was told to put all the files from fastboot,nvflash etc in C root (ie .exe,.img,.dlls, bin etc). I think it is not a must, as long as you have all the files together and dir has no spaces.
2. Unzip the firmware file from ASUS.
My case: the file name is JP_epaduser_10_4_2_18UpdateLauncher, extracted to find JP_epad-user-10.4.2.18. Extract again to find a file called Blob, which is about 500mb.
3. Copy the blob file to C root
4. Open CMD as admin. Make sure you do so as admin.
5. Goto C root, type: cd\
6. Just make sure you can execute the following exe: fastboot, adb, nvflash, type: fastboot
The commands should output the help related info....ie parameters etc
7. Now boot you tablet into apx conneted to your pc from tablet to pc no hubs docks> Device manager shows Asus tranformer prime APX interface.
8. Type: wheelie --blob blob.bin
My output:
C:\>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a49042111
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
My tablet screen shows:
top left: entering nvflash recovering mode / nv3p server
chip uid: 015c7d7a49042111
center: Asus
bottom right owr by...
9. Now it may reboot at the end of this just get back to apx mode on your tablet.
Type: nvflash -r --download 7 unlock-token.img
Output:
C:\>nvflash -r --download 7 unlock-token.img
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
unlock-token.img sent successfully
*My device black out. So i rebooted to APX again as instructed.
10. Type: wheelie --blob blob.bin
11. Type: nvflash -r --download 14 factory-config.img
Output:
C:\>nvflash -r --download 14 factory-config.img
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
factory-config.img sent successfully
*My device black out. So i rebooted to APX again as instructed. An did wheelie again
12. Type: nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Output:
C:\>nvflash -r --rawdevicewrite 0 2944 bricksafe.img
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
bricksafe.img sent successfully
*device did not blackout this time. So no need to reboot.
13. Type: nvflash -r --go
Output:
C:\>nvflash -r --go
Nvflash v1.13.87205 started
[resume mode]
14. Power + DWN to try to get to fastboot. Select the USB icon.
*windows device manager should detect fast boot interface
*confirm this by typing: fastboot devices
*my output was: 015c7d7a49042111 fastboot
15. Type: fastboot erase system
Output:
C:\>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.671s]
finished. total time: 2.671s
16. Type: fastboot erase recovery
Output:
C:\>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.929s]
finished. total time: 1.929s
17. Type: fastboot -w
Output:
C:\>fastboot -w
erasing 'userdata'...
OKAY [ 50.110s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 61980278784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 15131904
Block groups: 462
Reserved block group size: 1024
Created filesystem with 11/3784704 inodes and 283616/15131904 blocks
sending 'userdata' (141195 KB)...
Created filesystem with 11/3784704 inodes and 283616/15131904 blocks
sending 'userdata' (141195 KB)...
writing 'userdata'...
OKAY [ 26.179s]
FAILED (command write failed (Unknown error))
finished. total time: 76.878s
*dont be bothered by the error
18. Type: fastboot devices
Output:
C:\>fastboot devices
???????????? fastboot
19. Reboot and get back to fastboot again, check that your device is detected by Type: fastboot devices
Output:
C:\>fastboot devices
015c7d7a49042111 fastboot
20.fastboot erase boot
Output:
C:\>fastboot erase boot
erasing 'boot'...
OKAY [ 1.874s]
finished. total time: 1.874s
21.Type: fastboot erase misc
Output:
C:\>fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
22. Type: fastboot erase cache
Output:
C:\>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.713s]
finished. total time: 1.713s
23. Next cmd takes long time. Type: fastboot -i 0x0B05 flash system blob
* During the writing process of this step you will get the blue bar on your screen.....
Output:
C:\>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.225s]
sending 'system' (537604 KB)...
OKAY [ 90.363s]
writing 'system'...
OKAY [130.010s]
finished. total time: 222.600s
24. Type: fastboot -i 0x0B05 reboot
*this reboot should bring you to stock rom
*will take some time, just be patient
*does not matter if you have usb connected or not
-----------------------------------------------
If you reach here, you should have a fresh TP with stock, except its unlocked.
Hope this helps.

---

This is great, thank you.
I actually wanted to do this yesterday evening when i found out that the prime has run out of battery (because I'm a genius), but I will do this today.

---

Ok, it did not work from scratch, but then, I had already another ROM so I made things difficult.
With your checklist, I got to step 13, but still only APX mode. So i did some guessing work.
What I did (in short, assuming I have everything till your step 7 and doing the wheelie everytime):
a) nvflash -r --download 4 bootloader.ebt
b) nvflash -r --download 7 unlock-token.img
c) nvflash -r --download 5 recovery.img.SOS (the modified CWM from namidairo for his unofficial CM11)
d) nvflash -r --rawdevicewrite 0 2944 bricksafe.img (no wheelie afterwards)
e) nvflash -r --go
Now I DO have the option for fastboot but no recovery (unrecoverable boot loader error).
Will continue frfom here.
===
Next: Another bootloader. I tried the blob.EBT from the stock ROM and with this, it actually tries to boot by itself (showing "device is unlocked").
===
Fine. I repeated wheelie and step c), got the blue bar, now I have thew modified CWM v6.0.4.5. Running. Yay me.
Okay, after one try with CM11 ended me where I was starting, I came back to CWM with step a) and b), and now I'm going to bed.

---

I am stupid and skipped flashing the stock ROM.
Stupid me. Now it works. Weee!
Did I say thank you? I think just one time. Thank you for posting thes extrensive get-youself-out-of-the-dirt-manual.

---

This thread has the most important info for the TFP I've seen. This info should be shared out to the Brick recovery thread (and linked to the custom ROM threads)! I've been thinking of moving from Androwook to CM11, and the only way I would try it is with a really good grasp on recovering the blob files. So again thanks, this is now bookmarked to my favorites. And especially a huge thanks to Xerxes-3.0 and vanquishe. You both just saved me from my future brick!