yashsingh1/xdaforums huggingface dataset:
[Nvidia Tegra Note 7] StainlessS:
Today, panic stations as I thought I had bricked my Advent Vega Tegra Note 7.

I had updated yesterday to KitKat along with additional OTA updates, but decided

to go back to 4.3 to capture the update after main KitKat update (2nd of 6 updates [EDIT: forgot to cap that one]).

I unlocked bootloader via fastboot, then flashed system.img (4.3 from Advent) and then the TWRP

recovery.img EDIT: Also locked bootloader..

On boot, it got itself stuck Powered ON at the TEGRA NOTE (white on black) screen, all was doom and gloom.

I finally figured out that holding down Volume+ then pressing the power button quickly and then

pressing again (whilst still holding the volume+ button down), I could get into the recovery menu

to access TWRP. In TWRP I did a factory reset and hoped for the best.

On reboot, all was still doom and gloom. So I thought maybe it might be necessary to have the

appropriate boot image (rather than the 4.4 boot image), and so flashed that, and Voila,

everything is hunky dory again.

I seem to have lost ability to use nvflash (APX mode) after original 4.3 flashing (which I could access

on the device doing the same dance as above but pressing both volume up and volume down keys before power).

My USB driver Vender ID and Product ID's below, I seem to have two Fastboot Id's, presumably one for stock recovery

and the other for TWRP (I blanked last 5 digits with x's just in case they could be used for nefarious deeds).

Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\052101410714600xxxxx
TegraNote-Premium Google Galaxy Nexus ADB Interface Vid_18d1&Pid_d001
Tegra NOTE TegraNote-P1640 Vid_0955&Pid_cf02
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\15C4110C904000000100xxxxx
Advent Vega Tegra Note 7 Vid_0955&Pid_cf00&MI_00
Tegra NOTE Advent Vega Tegra Note 7 ADB Vid_0955&Pid_cf00&MI_01
Tegra NOTE USB Composite Device Vid_0955&Pid_cf00
APX NVIDIA USB Boot-recovery driver for Mobile devices Vid_0955&Pid_7535

Anyway, perhaps above is all known to you old salts, but for a newbie like me, is perhaps of use.

Also, thanks for the link :)
[Nvidia Tegra Note 7] hacktrix2006:
You can access APX by pressing Power plus Volume down and Volume UP at the same time and holding them.
[Nvidia Tegra Note 7] StainlessS:
Thanx hacktrix, I could access APX OK (was stuck with power on, ie could not power off, the dance described allowed me the access both fastboot and APX).

The problem was nvflash via flash_signed.bat.
[Nvidia Tegra Note 7] hacktrix2006:
Normally if your already in APX mode it just means you can skip the first section of the flash_signed.bat . Glad your back up and running though.
[Nvidia Tegra Note 7] StainlessS:
The 1st section of flash_signed.bat (to write serial to SN.txt worked OK, the stuff afterwards showed a device not found error message ((EDIT: Brainfart, perhaps it was the wrong nvflash (as fastboot) ID it was looking for, ie I had installed TWRP and it was for some reason looking for the recovery (non mod) image ID, as I said, I had two Fastboot id's).

I can't re-check at moment, in pub,, but I think is correct.

I see you are very active,saw your posts on nvidia developers forum, glad you had your prob sorted.

Anyway, also sorted here so no reply necessary, thanx.
[Nvidia Tegra Note 7] StainlessS:
I guess this could be important, so I repeat EDIT: from post #22 here,

(EDIT: Brainfart, perhaps it was the wrong nvflash (as fastboot) ID it was looking for, ie I had installed TWRP and it was for some reason looking for the recovery (non mod) image ID, as I said, I had two Fastboot id's).

In relation to the nvflash stuff in flash_signed.bat.

Again, no reply necessary, but might be of interest to sombody that has some idea of what they are doing., ie not me.

(I had originally left in the kitkat boot.img when trying to re-install JellyBean with TWRP).
[Nvidia Tegra Note 7] share_needles:
Hi Guys. I'm having a hell of a time with this.

I can access APX mode and "ADB Devices" tells me "XX00Serial Number00XX Host"

Any command I use to try and use NV flash doesn't work. How exactly do you do it? What commands are entered to start the process? Sorry I am very new to this.
[Nvidia Tegra Note 7] StainlessS:
APX will need yet another driver installed, point it at the VegaNote7\usbpcdriver\ directory.

Mine is (from USBDeview), APX NVIDIA USB Boot-recovery driver for Mobile devices Vid_0955&Pid_7535.

After that is installed, you use 'Flash_signed.bat' to install, I would not suggest you try to use the nvflash command yourself.
[Nvidia Tegra Note 7] slick97477:
Any idea how long this process takes, Trying to use this to un brick my tablet and just has a blinking cursor for a few minutes now. Nothing is displayed on the screen. Got the APX drivers installed correctly

A message says Cant start to flash Serial number is invalid. and flashes pretty quick and closes. Any idea how i would fix this thanks
[Nvidia Tegra Note 7] xda-Daviz:
The same issue. Entered APX mode, installed driver (NVidia USB boot-recovery driver for Mobile devices) and tried to run flash_signed.bat.

But it just printed "Can't start to flash. Serial Number is invalid!!!" and that's all. :(

Could anybody please help with this? Thanks in advance
[Nvidia Tegra Note 7] hacktrix2006:
There is a way. Pm me might be able to help. Will need device serial number, OEM maker name as well. Make sure you have tried another cable too.
[Nvidia Tegra Note 7] hacktrix2006:
I have started to notice that a few members have managed to get their tablets into APX Mode. Normally i would do an APX Flash for you to 4.3 to get the tablet working. Now i am going to be uploading a Advent 4.4.2 OTA 2-5 APX image set for you.

Now there is a few changes in the flash_signed.cfg to where it calls a NCT File directly (Where the Serial is stored) which will need modding.

Currently there is a line in the NCT_gp file with the following.

<name:serial_number; idx:0; tag:0x80; data:TEGRANOTEGP00A123456>

This will need to be changed to your devices serial number which should be on your box that come with the device so for example the change will look like

<name:serial_number; idx:0; tag:0x80; data:0521309919939>

When you run the flash.bat it will then look for the nct_gp file and then flash the serial number directly instead of trying to get the serial number dumped to a text file and it not always working.

Should be available some time next month and i will post a link to the New 4.4.2 APX image.
[Nvidia Tegra Note 7] Sparh4wk:
so if I dont have a box with SN and I cant get it via that Vega Script, Im doomed?
[Nvidia Tegra Note 7] hacktrix2006:
PM me the serial number for your device bud if you can find it on your box it would be great. I take it your device is bricked ?

I have a Dedicated thread for APX HERE

Which once certain images are available will be placed in the OP.

Also if you can't get your serial number all it means is that you can not download OTA's directly from nVidia you'll only be able to download from websites such as here with the files uploaded.
[Nvidia Tegra Note 7] microb77:
Hi guys,

The tablet (evga tegra note 7) just wouldn't start this morning. But it looks like it enters APX mode. I downloaded the above. When I try, I get the following:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

F:\Temp\tegra\VegaNote7>flash_signed.bat
Nvflash 3.09.1700 started
Using blob 3.09.1700
chip uid from BR is: 0x600000015c3de2032400000009008080
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: 0x000000015c3de2032400000009008080
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
board id: 0
warranty fuse: 1
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
Limited Power On - nothing to do
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) messag
e: nverror:0x3 (0x3) flags: 0
Partition table does not exist on device
Skipping backup of partitions
Continuing create using flash_signed.cfg
setting device: 2 3
deleting device partitions
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: RBL
creating partition: BMP
creating partition: LBP
creating partition: CHG
creating partition: EKS
creating partition: FB
creating partition: NCT
creating partition: GP1
creating partition: SOS
creating partition: DTB
creating partition: LNX
creating partition: FRD
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: MDA
creating partition: LBH
creating partition: FCT
creating partition: UDA
creating partition: GPT
failed executing command 17 NvError 0x120002
command failure/warning: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
9 (0x9) flags: 0

"Flash done"
F:\Temp\tegra\VegaNote7>

Any idea what could be causing this and how to resolve the issue?

Thanks!
[Nvidia Tegra Note 7] hacktrix2006:
That looks to be down to the bootloader. Which pack did you use the Advent Branded or Unbranded?
[Nvidia Tegra Note 7] microb77:
That was with the pack directly from advent. Maybe I should try the unbranded?
[Nvidia Tegra Note 7] hacktrix2006:
Give the unbranded version and see if that works. Else it can only be down to a failure somewhere in the nand.
[Nvidia Tegra Note 7] microb77:
Also failed. I get "bad data" with the unbranded. Should I understand I'm out of luck?
[Nvidia Tegra Note 7] hacktrix2006:
can you do a printscreen of the directory please bud. It would seem its something to do with partitioning by what i can read up on the error codes.

However there is other device's using APX mode with the same error codes being a NAND failure outright.

How long did you have the tablet for?

Also another question are you using Windows ? if not give Windows a try.
[Nvidia Tegra Note 7] hacktrix2006:
Check PM bud
[Nvidia Tegra Note 7] kossie12:
Thanks for linking to this guide. Got stuck on boot after messing up root on lollypop.
[Nvidia Tegra Note 7] smalldog123:
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:
[Nvidia Tegra Note 7] Cesar97:
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.
[Nvidia Tegra Note 7] 1eyedmonster:
Unless you can get into bootloader Only nvidia has apx drivers to restore your tablets bootloader

Getv in contact and hope nvidia do rma
[Nvidia Tegra Note 7] arhogroovy:
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
[Nvidia Tegra Note 7] saurabhsaini:
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
[Nvidia Tegra Note 7] arunbiju969:
Hey does it boot into boot loader (power+vol up)
[Nvidia Tegra Note 7] hacktrix2006:
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://xdaforums.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.
[Android Q&A, Help & Troubleshooting] mohammedmetto:
i lost official cwm from my phone and i lost but bassband plz any one backup cwm for me and upload it for me
[8125, K-JAM, P4300, MDA Vario General] db on cbr100xx:
I was perusing the forums of the two main protagonists in the PIM market [IMHO]

I noticed that the Agenda Fusion forum from Developerone has changed format to make for rather stilted discussion of issues there, as opposed the rather more open [and busier as it happens] Pocket Informant forum at WebIS.

D1 now moderate all posts [after some pretty terse threads when there was a hiatus in development late v7] with a range of read only FAQ threads.

I was wondering which PIM you use and whether you had switched from AF to PI

I did but I'll spare you the long story..............until after some poll results are evident anyway.... :)

BTW the first two options mean you use this PIM and always have.......
[8125, K-JAM, P4300, MDA Vario General] JwY:
i use informant and have never tried af

so far pi works well (it could still be faster though) so i don't plan to try af anytime soon
[8125, K-JAM, P4300, MDA Vario General] sk0t:
I've always used PI, since it was installed on my hx4705. When i purchased the upgrade, and I got rid of my hx4705, I installed it on my 8125.. Don't use it too much though on the 8125.. Not comfortable with the way it does a few things.. Might play around iwth it again though..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Any devs looking into this? Looking into making a modified recovery TWRP that supports F2FS file system?

I just got it all up and running on my nexus 7. And the speed increase is insane.
[Verizon Samsung Galaxy S 4] Wifilevel3:
Hi,

I went through all the form to root my S4 verizon(unlocked) but nothings related to MG7 baseband??

my baseband version is MG7 is it different than others?? i coudnt find any post related to this version

Main problem is KNOX security is installed in my phone in system directory,

KNOX preventing me from root access(when i tried super user app i am getting a notification ""An application has been forced to stop for an unauthorized attempt to access system in your device"),

so i tried to uninstall the KNOX but I need a root privilage to uninstall it. I stuck in the loop.

after I found to bypass the KNOX I should use the certified application to get into root. (i may be wrong i am not sure) is their any way for me to root and install cynagenMod ?? or if helped in uninstalling KNOX i can root it.

Thanks in Advance.

FYI: BaseBand version is I545VRUDMG7 its verizon and unlocked now using AT&T
[Verizon Samsung Galaxy S 4] riker147:
Are you sure it's MG7 and not MJ7? I did a quick Google search for I545VRUDMG7 and the only thing I found were the posts you created on this and other sites.

Maybe you could post a screen shot of your phone info.
[Verizon Samsung Galaxy S 4] Mistertac:
Even Google says...

Did you mean MJ7???

Lol
[Verizon Samsung Galaxy S 4] Wifilevel3:
Yes it is MG7, ya I even google a lot about about it and coudnt get any info, so last resort I posted here, I attached the screen shot info please go through it.

Thank you.
[Verizon Samsung Galaxy S 4] Mistertac:
[

[/COLOR]Grab this app

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

Take a screenshot for us since I don't see the one you say you've posted here
[Verizon Samsung Galaxy S 4] Wifilevel3:
Hi, I attached the another screen shot using that app u mentioned, please go through it. and what I am thinking is KNOX is the only think which is not allowing me to root my phone, is there any way to remove the KNOX??
[Verizon Samsung Galaxy S 4] jamesd1085:
Weird...its 4.2.2. ...is this pre mdk?anyone know what this is lol...never seen this version...if it is surge may want a good look at it
[Verizon Samsung Galaxy S 4] phobia09:
Maybe some sort of test build? Did you purchase the phone used? Generally S4 build numbers have followed a pattern. The second letter generally indicates a date, I believe. That's why MDK was most likely a May 2013 build, ME7 was a June 2013 build, etc. So this may be somewhere in between ME7 and MI1. I would say this device could be a rare gem and may even provide more information towards a BL exploit.
[Verizon Samsung Galaxy S 4] Mistertac:
Its very strange I could only find i9500 with similar build number but clearly that shows as an i545. Someone here will know. He says he has Knox on there though?
[Verizon Samsung Galaxy S 4] Wifilevel3:
Yes, its a used phone. Is there any way to root or to Uninstall KNOX which prevent root ?? to install CyanogenMod.!!
[Verizon Samsung Galaxy S 4] phobia09:
I would think it could be rooted with Kingo. I would try that first.

http://xdaforums.com/showthread.php?t=2473747

Please let us know if that works.
[Verizon Samsung Galaxy S 4] Surge1223:
Wait you dont have root on this? Try saferoot or any of the root methods we have they should work. Next it would be helpful if you sent me your bootloaders would you be willing to help us? Also please refrain from installing Cyanogenmod for a little bit until I can get some of the partitions from your device. Also don't upgrade the baseband yet either please.

There was a reason they didnt release this build. It would be helpful to know why I need to analyze the bootloaders from this build. I hope you read this soon and above all else do NOT update your phone!
[Verizon Samsung Galaxy S 4] decaturbob:
I hope he listens to you surge
[Verizon Samsung Galaxy S 4] Mistertac:
Hey did you happen to root the phone yet? And how about helping out the community and sending Surge what he mentioned... That'd be huge
[Verizon Samsung Galaxy S 4] Hashbang173:
Bumping this thread so maybe WiFilevel3 sees it
[Verizon Samsung Galaxy S 4] Mistertac:
I sent the OP a message. Hopefully something comes of it.
[Verizon Samsung Galaxy S 4] Wifilevel3:
yes , I can root my phone and I can help surge NP in it.
[Verizon Samsung Galaxy S 4] phobia09:
Any contribution is MUCH appreciated. Thanks for helping.
[Verizon Samsung Galaxy S 4] Hashbang173:
I guess [MENTION=4939386]Surge1223[/MENTION] can send you pm's on how to extract the needed files to find more about your bootloader. He could probably write a script for you.
[Verizon Samsung Galaxy S 4] Mistertac:
[MENTION=4939386]Surge1223[/MENTION] he had asked me couple hours ago how to pm you. So if you guys arent already in contact maybe shoot him a message.
[Verizon Samsung Galaxy S 4] Surge1223:
Yep he contacted me, we are in the process of getting the files. Thanks everyone for getting his attention. Ill post what I find in the bootloader thread.
[Verizon Samsung Galaxy S 4] Hashbang173:
Hope everything goes well
[Verizon Samsung Galaxy S 4] Hashbang173:
Can anyone point him in the right direction for getting a custom recovery
[Verizon Samsung Galaxy S 4] cbmggm:
Custom Recovery not possible, go to Safestrap thread.
[Verizon Samsung Galaxy S 4] meechy704:
Google "VROOT" on your computer...install the app....hook your phone up to the computer...(green is "root" in chinese). Once you have root access, go to the file manager on your phone (preferably a root file manager) SEARCH FOR ALL FILE NAMES WITH "KNOX" IN THEM, AND DELETE....KNOX WILL NO LONGER BE ON YOUR DEVICE, but will void warranty....HAPPY HACKING!
[Verizon Samsung Galaxy S 4] k1mu:
As you have only one post, clearly you're not very familiar with Vroot.

Please don't recommend that people use that. There are far better ways to root that don't deliver unknown data to who knows where, and don't install shady superuser programs. Oh, and don't set the Knox Warranty Void flag.

Sorry if you've already used Vroot. You should have looked further. For example, http://xdaforums.com/showthread.php?t=2565758

That'll root anything vroot can, without voiding your warranty. Yes, that's a rooting technique that I built specifically to avoid vroot/kingo.
[Galaxy S 4 Q&A, Help & Troubleshooting] Amarach:
Dear all,

I've been trying to solve the following problem for three weeks on my own and have made no progress, and have probably made things worse. So, I figured it was time to get some help at long last.

I bought my S4 I9500 in Bangkok, and I was not aware that Samsung was region locking their phones now, as I had an S2 that I used in Thailand, China and Cambodia without any problems.

So, I bought the S4 and loved it. However, I moved back to China last month, and upon arrival I bought a SIM card. It didn't work... At this point, my firmware was 4.3, as it had auto-updated from 4.2 while I was in Thailand.

The folks at China mobile couldn't figure out the problem, so I did some research and found out that my phone was region locked. I went to 3 Samsung stores here, and none of them knew what to do, nor would bother to figure it out.

So, I had to try to fix it on my own. I read about entering service mode and tried it, but it didn't work. From what I read, it would have worked in 4.2.2, but not 4.3. I tried finding a place to download 4.2.2 to flash it back, but Hotfile is dead, so I got 4.4. I figured it couldn't hurt, right?

Well, it didn't help.

So, basically, my I9500 is at firmware version 4.4, and my phone is still locked. I am in desperate need of some help. I do not care about the warranty, as I am pretty sure I screwed that up already.

BTW: I did try some sites for the unlock codes, but either they didn't have what I needed, the IMEI code was not accepted, only accepted Paypal, or would not accept a UnionPay credit card. -_-

Thanks for your time.