tf201 Black Screen - APX Only Mode Stuck sending bootloader
Device is unlocked
Only way to communicate to the tf201 is to use Volume + Up button.
Screen is black but has full power and vibrates. Device manager does recognize the device as Asus Transformer Prime APX Interface.
Using backup of blob.bin for this specific tablet. I have been able to nvflash this device in the past. Please advise if there is anything else I can try or other dos commands I can try. Thank you XDA Members.
Command reads as follows and locks up at sending file: 100%
C:\>cd tf201
C:\TF201>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a44601005
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Related
Can only run APX mode.. no Odin.
Was running Touchwiz 3.1 when all of a sudden, my tab locked up.
I powered down and it never came back up.
I can get it into APX mode, but get the following when I try to reload the bootloader.
C:\nvflash>nvflash --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x038891c54140XXXX
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Did some searches here and wasn't able to find something that would work.
Is there any way to use nvflash to repair?
Thanks!
I got my Tab 10.1 (32 GB, white, unlocked) yesterday, and loved it. But it is no more. I was trying to get it into bootloader mode, and the two icons that should appear did for a second, then disappeared. It was the last thing I saw on the screen.
I tried plugging it in to my computer and into the wall. I tried holding the power button down for a looooooonnnnnggg time. I tried holding power and volume up, then power and volume down. I tried holding power and touching the screen. The only info I could get out of it was being able to get it into APX mode and trying nvflash. When I got to step 17 of section 2, this is what my computer told me:
c:\nvflash>nvflash --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c7107417f60d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Click to expand...
Click to collapse
Unfortunately, that makes no sense to me. Is it done for good? Anything I can do to revive it?
hi,
I have asus tf101 , and not work. Non-stop is black screen. I Connected to PC and pc visible my tablet. Okey, i go to nvflash but:
C:\Documents and Settings\klaviu.s\Pulpit\ASUS NFLASH\Win>cd C:\Documents and Se
ttings\klaviu.s\Pulpit\ASUS NFLASH\Win\
C:\Documents and Settings\klaviu.s\Pulpit\ASUS NFLASH\Win>"nvflash.exe" --bct tr
ansformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odm
data 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0380624041ff93d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
- 1361053/1361053 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
and then do not go. How do I fix this?
If the battery is broken it may be wines that?
This is the TF201 forum. You aren't likely to get help for your device here.
Hi,
I'm new here so I'll make it the most clear I can.
Device: LG P760
Date of production: on battery it is 02.2013 but it was in repair back in the middle of 2014 and god knows what it has been done there. Probably change of whole mainboard
Soft: Stock 10(someting) on Android 4.0.4 -Branded > Update to 20h JellyBean - Branded >>service>> not branded 20h > Flashed manually 20b Europe Open
EDIT: AP Bootloader Version: LK May-2012 (From hidden menu)
Target: Unlock bootloader
What have I done so far:
Windows 7
1. Standard console
Code:
adb reboot oem-unlock
2. RomToolkit 2
3. LGL9Toolkit
4. Bunch of scripts found here
5. Omap4boot
Result: Pretty much reboot of system without any effects
Linux Ubuntu 14.10
1. Standard console
Code:
adb reboot oem-unlock
Result: reboot of phone without any effects
2. Connecting via fastboot and
Code:
fastboot oem unlock
using modified by myself script found somewhere
Code:
#!/bin/sh
which fastboot || echo install fastbooot first, e.g. on ubuntu sudo apt-get install android-tools-fastboot
which fastboot || exit
echo 'Connect LG L9 *without battery* to PC using data cable'
sudo ./usbboot p940-aboot.2nd p940-u-boot_fastboot.bin && echo usbboot ok || exit
echo 'DO NOT disconnect usb cable. Insert battery, then press enter'
read x
sleep 10
echo fastboot devices:
sudo fastboot devices
echo 'UNLOCK'
sudo fastboot oem unlock
which resulted in:
Code:
/usr/bin/fastboot
/usr/bin/fastboot
Connect LG L9 *without battery* to PC using data cable
waiting for OMAP44xx device...
reading ASIC ID
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: de1584c8b14d699fb234d5c31e2cdd6a9932669d
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
[*] msg size = 4
[*] data size = 21552
waiting for 2ndstage response...
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
** Done **
usbboot ok
DO NOT disconnect usb cable. Insert battery, then press enter
fastboot devices:
0A3F08331801D013 fastboot
UNLOCK
...
FAILED (remote failure)
finished. total time: 0.000s
That is pretty much everything. I've read about some magic cable and something about encrypted bootloader but I'm more than confused now. Am I doing someting wrong, especially on Linux (more acquainted in this type of system)? On Windows I have to exclude drivers problems, tried on 3 different machines, waited long before unlocking
Well, I'm in your same situation, but mine has been produced the 31/5/2013, so it have an encrypted bootloader.
I try to recover my tablet which stay in APX mode.
I already used wheelie and nvflash in order to restore my tablet, I think i have all required files ( blob.bin, bricksafe.img, bootloader.ebt ...) but that don't work.
wheelie is buggy and blocked in an infinite loop
Example : wheelie --blob blob.bin
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a440ff123
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Example : wheelie --blob blob.bin -U bricksafe.img
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a440ff123
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
any help will be appreciated.
Thanks
Thanks to @Clamor for his help ...
Required files :
blob.bin - from Generate wheelie blobs
bootloader.ebt - from Generate wheelie blobs
recovery.bct - from Generate wheelie blobs
bricksafe.img - from nvflash --resume --rawdeviceread 0 2944 bricksafe.img
flash.cfg - gived by Clamor and attached to this post https://forum.xda-developers.com/attachment.php?attachmentid=4488839&stc=1&d=1525009259
First command, this initialize BootConfigTable & Bootloader
Code:
./nvflash --bct recovery.bct --setbct --configfile flash.cfg --create --bl bootloader.ebt --blob blob.bin
Second command, this flashes partitions 2 (BCT), 3(PT), and 4(EBT) :
Code:
./nvflash --resume --rawdevicewrite 0 2944 bricksafe.img