[dev][apx][nvflash][tegra-note-7][update]

smalldog123

New member
Mar 23, 2011
1
0
0
Similar experience

Nvflash 3.08.1700 started
Using blob 3.09.1700
secure tool version 3.09.1700
warning: Minor version of nvflash and secure tool are not same
Use "./nvflash --cmdhelp --versioninfo" for more information

chip uid from BR is: 0x600000015c3e1040240000000d038640
rcm version 0X350001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x35 major: 1 minor: 2
chip sku: 0x5
chip uid: 0x000000015c3e1040240000000d038640
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
board id: 0
warranty fuse: 0
dk burned: true
boot device: emmc
operating mode: 6
device config strap: 0
device config fuse: 0
sdram config strap: 0

RCM communication completed
sending file: flash_signed.bct
- 8192/8192 bytes sent
flash_signed.bct sent successfully
BCT sent successfully
odm data: 0x4069e000
Limited Power Mode Set
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader_signed.bin
- 1079152/1079152 bytes sent
bootloader_signed.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Nv3pServer version 3.09.1700
warning: Minor version of Nvflash and 3pserver are not same
Use "./nvflash --cmdhelp --versioninfo" for more information

Limited Power On - nothing to do
ML execution and Cpu Handover took 2 Secs
Taking backup of FCT
failed executing command 20 NvError 0x120002
Unable to retrieve Partition table from device NvError 0x0
bootloader status: partition table is required for this command (code: 8) message: nverror:0x3 (0x3) flags: 0
Partition table does not exist on device
Skipping backup of partitions
Continuing create using flash_signed.cfg
Partition backup took 3 Secs
setting device: 2 3
deleting device partitions
deleteall failed
command failure/warning: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x5 (0x5) flags: 0

:crying:
 

Cesar97

New member
Feb 15, 2016
2
0
0
Hello friends. Please help me. I made from this device brick. I do all the instructions, but when I open flash_signed.bat, nothing happens. Opens an empty window and all.
PS I have windows xp.
Please, help me.
 

arhogroovy

New member
Mar 1, 2016
1
0
0
gazer tegra note 7 II APX
have any ideas ? stuck on :

D:\4.4.2-ota2.5 Nvidia Branded>flash_signed._forced.bat
Nvflash 3.09.1700 started
Using blob 3.09.1700
chip uid from BR is: 0x600000015c41e0c42000000004010080
 

saurabhsaini

New member
Mar 22, 2016
1
0
0
tegra note bricked

My tegra note bricked after installing OTA3.0 from Nvidia

I read that advent 4.3 image has the solution as mentioned on this thread. I installed the pcusbdriver as mentioned in instructions.

clicked on flash_signed as mentioned

But nothing is happening.

Also the instructions said to do all the things before installing driver on windows 8. I have win7 64 bit i didnt do that could it be a problem.
If yes can anyone tell me how to do those settings on win 7
 

arunbiju969

Senior Member
Apr 27, 2014
195
112
0
Adimali
My tegra note bricked after installing OTA3.0 from Nvidia

I read that advent 4.3 image has the solution as mentioned on this thread. I installed the pcusbdriver as mentioned in instructions.

clicked on flash_signed as mentioned

But nothing is happening.

Also the instructions said to do all the things before installing driver on windows 8. I have win7 64 bit i didnt do that could it be a problem.
If yes can anyone tell me how to do those settings on win 7
Hey does it boot into boot loader (power+vol up)
 

hacktrix2006

Senior Member
Jan 15, 2011
1,681
566
0
My tegra note bricked after installing OTA3.0 from Nvidia

I read that advent 4.3 image has the solution as mentioned on this thread. I installed the pcusbdriver as mentioned in instructions.

clicked on flash_signed as mentioned

But nothing is happening.

Also the instructions said to do all the things before installing driver on windows 8. I have win7 64 bit i didnt do that could it be a problem.
If yes can anyone tell me how to do those settings on win 7
Ok guys if you have a P1640 and you have flashed the nVidia OTA 3.0.0 you have bricked your device where it can't be repaired via APX.

The latest for the P1640 is OTA 2.5.

What you have done is flashed a P1988 firmware image and bootloader which wasn't clever to do. Infact it clearly stats that OTA 3.0 is a P1988 image.


If however you have a P1988 Tegra Note 7 why are you trying to use a P1640 APX image it will not work at all. Look at my thread http://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839 .

The only option now fo you guys that can't use APX to recover the device is now contacting nvidia directly and RMA'ing the unit.