[We Need] Working Nvflash.... :( - Asus Eee Pad Transformer Prime

I rooted the galaxy tab using nvflash when it first came out in the US. With nvflash we can flash rooted roms and do full backups. I am trying the same process with the TP but I have ran into some issues. First issue was the drivers would not install. I added the TP device id then I installed the drivers. I tried nvflash --sync command but get a unkown device message. We need a updated nvflash that supports tegra 3. If anyone has an updated version of nvflash please pm me.
Thanks
Shep
Edit: I checked online and dev package for tegra platform from nvidia but could not find a updated version of nvflash that supports TP. Are device does have APX & nflash support(Vol+ then power button then hold both 15 secs then release).

---

might be interesting to try the sbkcheck from rayman
http://forum.xda-developers.com/showthread.php?t=1290503
(note: IIRC there was a modified version at androidroot.mobi that could check for a "v3" SBK as well).

---

its not a driver issue. the drivers that come with the latest version of NVflash are the drivers supplied by ASUS, BUT the PID/VID
try adding these lines to the NvidiaUSB.inf under the x86 and amd64 lines
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
then force uninstall any drivers (you may even go as far as installing old google ADB drivers) and then try installing the nvflash drivers (with the new lines added)
i was trying to do this, but i cant find my device in hardware list. like literally its not that hahah

---

This will give us the ability to flash roms right?
Sent from my Transformer Prime TF201 using Tapatalk

---

biggem001 said:
its not a driver issue. the drivers that come with the latest version of NVflash are the drivers supplied by ASUS, BUT the PID/VID
try adding these lines to the NvidiaUSB.inf under the x86 and amd64 lines
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%USB\NvidiaUsb.DeviceDesc% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
then force uninstall any drivers (you may even go as far as installing old google ADB drivers) and then try installing the nvflash drivers (with the new lines added)
i was trying to do this, but i cant find my device in hardware list. like literally its not that hahah
Click to expand...
Click to collapse
I already got the drivers working. Nvflash says unknown device whe you try to use the sync command. We need new version of nvflash.

---

Wordlywisewiz said:
This will give us the ability to flash roms right?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Yes you can edit system partition and flash with root or custom rom but flashing recovery & boot loader is the main goal.

---

shep211 said:
Yes you can edit system partition and flash with root or custom rom but flashing recovery & boot loader is the main goal.
Click to expand...
Click to collapse
Yes! Can't wait to root! I had root then it forced the update on me!
Sent from my Transformer Prime TF201 using Tapatalk

---

So if you have root then apply the OTA, it hoses root?
Sent from my Galaxy Nexus using XDA App

---

Superguy said:
So if you have root then apply the OTA, it hoses root?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yep, it wipes the /system/ directory

---

I have same issue it says unknown device, we need a new EXE. Hope to get one soon.

---

I went into NVFLASH and saw that it takes the USB PID of the device, and that tells how the device is what it is. so the TP needs to be added to NVFLASH.. im seeing if i can do it be playing with the exe

---

here is an nvflash that supports cardhu(tegra 3), this is for linux, its all use so all i have, i just issued the --sync command and have not gotten an unknown device error, just getting nvflash started, then it just sits there.
i havent used nvflash really at all, im just used to fastboot and adb, but hopefully this helps and i dont have much time today or tomorrow at all to mess with it.
Linux users- in your rules.d(android-rules-whtever you want to make it) first line will get ADB working with the prime, second should allow it to be seen in APX mode:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
Edit after messing with some nvflash commands I get a "USB write failed" error, which after Googling tells me Asus has used an SBK(secure boot key), rendering nvflash useless(unless asus gives it to us-128 bit encryption). Basically locked, encrypted bootloader and were f#$ked.
I really hope I'm wrong.

---

You are not wrong unfortunately. It's the same with the first Transformer. The first SBK was leaked, but they changed it and the second one is still unknown as far as I know. It's a real shame, because nvflash provides a lot of safety (you can reflash even almost bricked device).

---

Dammit! Isn't this against Google s open source license or something?
Sent from my Transformer Prime TF201 using Tapatalk

---

di11igaf said:
Edit after messing with some nvflash commands I get a "USB write failed" error, which after Googling tells me Asus has used an SBK(secure boot key), rendering nvflash useless(unless asus gives it to us-128 bit encryption). Basically locked, encrypted bootloader and were f#$ked.
I really hope I'm wrong.
Click to expand...
Click to collapse
If this is true, I will return it on principle. I don't buy locked devices, which is why I will never buy Motorola

---

Wordlywisewiz said:
Dammit! Isn't this against Google s open source license or something?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Lol, no. Heck, HC source is still private.

---

Well when it becomes ICS's won't they have to let us do whatever we want with it?
Sent from my PC36100 using Tapatalk

---

Wordlywisewiz said:
Well when it becomes ICS's won't they have to let us do whatever we want with it?
Click to expand...
Click to collapse
No, Asus dont have to release the source to their proprietary software unfortunately. You can have the source for ics from google, but doesnt mean you can get it on your device!

---

I cant imagine this being a problem for long. Even iphones get jailbreaked after some time and Apple is known for their locked system. They probably have a whole department just for locking up and preventing jailbreaks.
I really cant imagine that Asus is doing a better job than Apple in that matter and making it impossible to do some magic with it.. It'll probably take some time though.
Is there a good channel to reach Nvidia or Asus with our demands? Crying loud enough worked with HTC after all

---

clouds5 said:
Is there a good channel to reach Nvidia or Asus with our demands? Crying loud enough worked with HTC after all
Click to expand...
Click to collapse
+ 1
Sent from my Transformer Prime TF201 using xda premium