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
Related
everything is working but for some reason i cannot gt it it recovery mode any longer.. was working fine when i got. it.. just hangs with the message "recovery key detected"
so i followed some steps here and tried to flash the recovery img. from the latest stock firmware.. results look fine.. but it still hangs and never gets into recover mode..
double checked the recovery directory is there (i am trying to reflash cwm which obbviously is not working) and the command file is correct pointing to sdcard and the update.zip is int he root of sdcard (from internal cwm)
still just hangs and "recovery key detected"
here is the output when it tried to reflash the recovery partition which i assumed somehow got munged.. but no idea.. any help would be appreciated.
D:\gtab>nvflash.exe --bl bootloader.bin --download 9 recovery.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144043439f4617
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
\ 3522560/3522560 bytes sent
recovery.img sent successfully
D:\gtab>
D:\gtab>
well bit the bullet and reflshing everything to stock and starting over.. will let you know..
ie
D:\gtab>nvflash_gtablet.bat
D:\gtab>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfil
e gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144043439f4617
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
D:\gtab>
igkahn,
Probably was quicker and less trouble than trying to work through the other.
When you get to the stock, you might want to run Settings/Security/Wipe
Factory Data just to make absolutely sure you're good to go.
Once you get back to stock, you can OTA back up to 3588 and from there you
can go where you want to.
Rev
I am having the same issue
I am having the same issue with not being able to enter the recovery mode. everything is working but for some reason i cannot get it in recovery mode any longer.. was working fine when i got. it.. just hangs with the message "recovery key detected"
I am a newbie to the Android OS would appreciate any help on how to fix this problem.
Were you using stock recovery? ClockworkMod? What ROM did you have installed? Have you recently made any changes? Updates?
How do you expect help if you don't give us any information?
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.
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 %