OK I just got my tablet last week and updated to ice the day it got released. I wanna root and I see a couple of threads that say pics root and I see a couple that say hc 3.1 or 3.2 root now I know my tablet came with honeycomb but I don't remember if it was 3.1 or 3.2 now my question is which of these threads should I follow if I wanna root my device that has pics 4.0.3 because idk if those threads were to give people ics or to root their pics tabs because it was posted in feb
root for ics
This worked for me, root with recovery
http://forum.xda-developers.com/showthread.php?t=1622425
READ THE INSTRUCTIONS
Very important
Choose the apx package with full root.
Good luck.
Ive read the guide but what I'm not clear on is should I be downloading all the files to my PC or do it from the tablet
rcraig617 said:
OK I just got my tablet last week and updated to ice the day it got released. I wanna root and I see a couple of threads that say pics root and I see a couple that say hc 3.1 or 3.2 root now I know my tablet came with honeycomb but I don't remember if it was 3.1 or 3.2 now my question is which of these threads should I follow if I wanna root my device that has pics 4.0.3 because idk if those threads were to give people ics or to root their pics tabs because it was posted in feb
Click to expand...
Click to collapse
1) plug to a computer.
2) to carry firewood Acer USB
3) unplug the tablet from the company, disable debugging on the usb, turn off the tablet
4) Reinstall the wood acer USB, while plate must not be connected to a computer
5) turn on the tablet wait for full load
6) turn on debugging via USB
7) Connect the tablet to a computer, ask if the installation of wood for Acer MTP, press the cancel
8) runs ICSRoot and all should be able to
rcraig617 said:
OK I just got my tablet last week and updated to ice the day it got released. I wanna root and I see a couple of threads that say pics root and I see a couple that say hc 3.1 or 3.2 root now I know my tablet came with honeycomb but I don't remember if it was 3.1 or 3.2 now my question is which of these threads should I follow if I wanna root my device that has pics 4.0.3 because idk if those threads were to give people ics or to root their pics tabs because it was posted in feb
Click to expand...
Click to collapse
here you go, there is a youtube video as well so it should be much easier to follow through.
http://forum.xda-developers.com/showthread.php?t=1520469
AstroMag said:
1) plug to a computer.
2) to carry firewood Acer USB
3) unplug the tablet from the company, disable debugging on the usb, turn off the tablet
4) Reinstall the wood acer USB, while plate must not be connected to a computer
5) turn on the tablet wait for full load
6) turn on debugging via USB
7) Connect the tablet to a computer, ask if the installation of wood for Acer MTP, press the cancel
8) runs ICSRoot and all should be able to
Click to expand...
Click to collapse
what is firewood acer usb?
rcraig617 said:
Ive read the guide but what I'm not clear on is should I be downloading all the files to my PC or do it from the tablet
Click to expand...
Click to collapse
Down load to your computer and extract them to a folder on c:
rcraig617 said:
what is firewood acer usb?
Click to expand...
Click to collapse
Apologies for the Russian slang, I mean drivers for Acer.
I finally did it. Didn't have to unlock, rollback the firmware, ADB, or anything too drastic. So happy.
I used this method here.
http://forum.xda-developers.com/showthread.php?t=1706588
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers. Can download it here if you're as incompetent as me (Under Utilities). Exit out Asus Sync in your system tray before attempting the method above. And I'm probably not the guy to ask for any help if you got problems or questions.
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
I installed OTA RootKeeper afterwards.
Thanks XDA. Thanks sparkym3.
I think you should give yourself more credit.
GJ
thanks man!
-Bang
supersoulfly said:
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers.
Click to expand...
Click to collapse
This works indeed, but you must stop ASUS sync if it's running. If you don't, the version of ADB packaged with ASUS Sync is different from the one in the zip file and you'll get a whole lot of lines with "adb server is out of date, daemon started successfully" which mess with the script.
Once I stopped the Sync thing from systray and verified in task manager, the script ran like a charm.
So, another TF300 with .29 WW rooted, thanks to the people involved in making this possible
all this confused me way too much but luckily for me i had help (well i say help he did it all via teamviewer lol) from thing o doom he is a star
I used this method too on my 29.WW,thx guys
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
jakelikescake123 said:
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
Click to expand...
Click to collapse
Ummmm.....I think I confirmed it, in the first post.
supersoulfly said:
Ummmm.....I think I confirmed it, in the first post.
Click to expand...
Click to collapse
im the idiot
thanks
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
lightiv said:
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
Click to expand...
Click to collapse
May not be the issue, but it's happened to me several times rooting & ROMing phones - plug the cable into a rear USB port that's on the motherboard. The USB ports on the front of the case don't always work for some reason. The front of my case has 6 ports and I can only get reliable phone connections on 2 of them. Down right squirrely!
ID10T Error on My Part
Turn out to be an ID10T error on my part. I had DroidExplorer running from when I rooted my cellphone. I finally ran across a post that made reference to it and killed the process. It took all of 30 seconds to root once I killed the process.
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
If anybody bricks his/her device and has only the APX mode available or is trying to get an nvflash utility for a Tegra Note 7, now the solution can be found: the Advent company has published a full package including a nvflash working with the Tegra Note 7. Moreover, the package contains a signed bootloader and bct and all the other parts of the entire storage (including the system partition for a 4.3. JellyBean).
It can be downloaded from their website of adventcomputers.co.uk in the downloads section (I can't post links yet), select Product range: "Advent"; Product type: "Tablet"; and then choose "ADVENT Vega Tegra Note 7", do not be mystified by the "driver" type and download the "Advent Vega Tegra Note Factory Image (4.3)" (about 641 MB package)
Many thanks to the dev and support guys at Advent (Dixons retail plc), because they have put the final cherry on the top of the cake. The Nvidia Tegra Note 7 is now not only a top of the top devices regarding its power, but this package renders it into an unbrickable device.
(note: I'm NOT affiliated with any of the companies, I just bricked my device and had no other mode available than the APX mode. I'm posting this post due to the abovementioned reasons, because I find this quite and important source for further hacking(orig. meaning) of the devices. In fact I regard this as an utlimate source for development on this platform.)
I have tried the package (including the batchfile, that does the automation), it works for me on my Advent Vega Tegra Note 7, however Im not sure if it will work on others (EVBA for example), so please feel free to test and post your experience underneath here.
Link: http://adventcomputers.co.uk/product-download-select/296
Sent from my TegraNote-P1640 using Tapatalk
thx
Thanks for the heads up. I tried it on my bricked dodgy manufactured tablet and I was able to get the device to a new level but it still crashes trying to boot the system partition. Least now I have fastboot.
With the nvflash recovery tools you can replace the images to suit say bat-recovery or latest boot.img with menu options the older version doesn't have.
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
HEhehee. This nvflash recovery is only new to the scene so I didn't get time to check it out then inform you Shaky.
In my opinion our community can rehash these tools and make a better recovery.
Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below), but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if this forum platform and its admins do not provide support for this.
With regards
------ Original message ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
rheingold said:
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below)., but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if the platform and its admins do not provide support for this.
With regards
------ Original mail ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
Click to expand...
Click to collapse
Hi i dont have an issue with this, mistake on my part, I thought this was my thread lol. Ive reopened my thread and its moved to Q&A. Will work on a newer things, I have new files. Will test few things first.
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
After finding out after a long time about this guide,I managed to reflash the stock firmware and reset the tablet,so hurray and much thanks for sharing this guide
Sent from my HTC One X using XDA Premium 4 mobile app
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia EVGA Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Hiro51 said:
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Click to expand...
Click to collapse
lizard-borys said:
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Click to expand...
Click to collapse
Can't use usb without power. The tablet will not stay turned off now and because of that, the battery won't charge enough to usb without power from usb.
I've even plugged in the charger and gone into boot-loader and clicked on shut down, but it still won't stay off or take a decent charge.
I have tried a different computer as well as different ports with the same results.
btw, thanks for replying.
As I reread the posts, I noticed rheingold's post at the bottom says he's not sure if this will work on the (I believe he meant EVGA) model. Can anyone verify it works on EVGA?
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Hiro51 said:
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Click to expand...
Click to collapse
Nice work mate. I am speaking with Nvidia too see if they will do factory images like the Shield but waiting on a response for that.
Also OTA 2.4 is now Live as of 5 minutes ago.
It seems the USB cables are not of high quality just like the ports.
lizard-borys said:
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
Click to expand...
Click to collapse
Having the same issue here.. anyone?
I have a copy if its needed still.
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).
Code:
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
You can access APX by pressing Power plus Volume down and Volume UP at the same time and holding them.
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.