You can try to flash the offical recovery ,and then do the factory wipe by the recovery.
[Super Tool][Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root
- Thread starter Tomsgt
- Start date
-
- Tags
- development
The best part of the new bootloader is that it charged powered off ? with custom charger fixes (wireless or solder directly on the io board)
Sent from my GT-I9300 using Tapatalk
Sent from my GT-I9300 using Tapatalk
Well I tryed to restore to kitkat with version 2.7
everything was ok, but after completed all steps, display is black and pc sees it as APX :/ cant turn it on etc...
any tips? thanks
everything was ok, but after completed all steps, display is black and pc sees it as APX :/ cant turn it on etc...
any tips? thanks
Last edited:
Did you flash the Twrp recovery and did a factory wipe?
you can try to flash the stock recovery and do a fasctory wipe again.
Just wanted to say this is a fantastic tool and works great for both Android 5.0 and 4.4.2.
Only glitch appears to be when trying to root, it looses connection to the tablet when you get into TWRP and you have to manually root but outside of that, it works great.
Only glitch appears to be when trying to root, it looses connection to the tablet when you get into TWRP and you have to manually root but outside of that, it works great.
Dont understand why i cant get the unlocking bootloader to work, drivers are installed says everything is ok but seems nothing happens as it should after it reboots the tablet to recovery mode.. mailed the creator but he dont seem to be willing to help anything.. id say this program is buggy and don work 100% for all tablets for some reason....
I have a similar situation.
My tablet (EVGA Tegra Note 7) seems bricked; nothing will turn on. But I can get it recognized as APX in Windows. So I tried the Advent flashing tool and the one laying around "Nvidia Branded" and both are failing when getting to creating the GPT. I want to thanks Hacktrix2006 for giving it a try yesterday.
Tablet was working fine, next morning was dead.
We came to the conclusion that either the Nand is fried, or the USB connection is loose in the tablet (it does feel loose, but it's been like that for a long time).
Unless anyone else has a suggestion, I think the next step is to try to re-solder the USB port, and if it still fails, it's a dead one.
:crying:
Before you start breaking into your Tab and blaming the USB port, i'd also make sure you try a new USB cable. Often times what looks like a loose USB port is just a worn out USB cable or a badly designed cable (like the one that came with my LG G3, stupid super long end that is easy to put pressure on.).
I had what sounds like a similar incident as you a while back. Make sure the tab has had some time to charge, then try a few extended power button presses as well as some combos of power+volume to see if you can get to the bootloader at all. Though if the tab was working fine the night before, it sounds like something may have run away and burned your battery all the way to 0 which sort of does exactly what you are describing. (not even the charge on screen icon)
I had what sounds like a similar incident as you a while back. Make sure the tab has had some time to charge, then try a few extended power button presses as well as some combos of power+volume to see if you can get to the bootloader at all. Though if the tab was working fine the night before, it sounds like something may have run away and burned your battery all the way to 0 which sort of does exactly what you are describing. (not even the charge on screen icon)
@IM0001 if it was battery it wouldn't of entered APX mode which is what has happened to microb77's TN7, The USB cable was swapped and even changed USB Ports to make sure. The only reason why i mentioned about the USB port on the TN7 was due to microb77 saying it was loose which might be causing the issue of being unable to push the APX image to the device.
Due to microb77 device being in APX mode the bootloader is not available at all even if you combo press Volume Up and power.
Due to microb77 device being in APX mode the bootloader is not available at all even if you combo press Volume Up and power.
Stucked in recovery after attemp to downgrade to 4.4.2
Hi guys,
I was very disappointed with less performance after upgrade to android 5.1. I decided to downgrade back to 4.4.2. I used for it super tool 2.5 (because it is the latest for android 4.x). But something wrong was happened during the flashing procedure. Maybe was bad idea use older tool to device with adroid 5.1, and I should change only ROM file... Anyway the flashing failed. After that I did wipe data/factory reset and wipe cache partition. System didnt reboot, was stucked in boot loop. By volume+ button and power it is able to get to recovery (KOT49H. 19090_427.9267) - it looks that it is stock recovery to android 4.4.2. I tried to flash several ROMs (4.4.2 and 5.1) from zip file and also update by ADB sideload. Every attemp ends with message that E: footer is wrong and signature verification failed. I also tried recovering by "Recovering your Advent Vega Tegra Note 7" but I have WIN7 and is probably necessary to have different driver, because this guide is writen for WIN8 - so I wasnt able to instal appropriate driver. Last issue is that I am not able to turn the device off. When I try it, it always start booting very soon after she screen is blank.
Do you have any suggestion how to solve my issue? Thanks in advance.
Hi guys,
I was very disappointed with less performance after upgrade to android 5.1. I decided to downgrade back to 4.4.2. I used for it super tool 2.5 (because it is the latest for android 4.x). But something wrong was happened during the flashing procedure. Maybe was bad idea use older tool to device with adroid 5.1, and I should change only ROM file... Anyway the flashing failed. After that I did wipe data/factory reset and wipe cache partition. System didnt reboot, was stucked in boot loop. By volume+ button and power it is able to get to recovery (KOT49H. 19090_427.9267) - it looks that it is stock recovery to android 4.4.2. I tried to flash several ROMs (4.4.2 and 5.1) from zip file and also update by ADB sideload. Every attemp ends with message that E: footer is wrong and signature verification failed. I also tried recovering by "Recovering your Advent Vega Tegra Note 7" but I have WIN7 and is probably necessary to have different driver, because this guide is writen for WIN8 - so I wasnt able to instal appropriate driver. Last issue is that I am not able to turn the device off. When I try it, it always start booting very soon after she screen is blank.
Do you have any suggestion how to solve my issue? Thanks in advance.
What brand do you have? Also is you bootloader unlocked? If not unlock it and then try using fastboot to flash the files again. The driver for Recoverinh your Advent will work in Window XP to Windows 10 however if you have a 64bit OS you need to disable driver enforcement.
Sent from my MotoG3 using Tapatalk
Sent from my MotoG3 using Tapatalk
I have Homecare (bought in china). When I had adroid 4.x bootloader was unlocked. I am not sure if bootloader wasnt rewrote by upgrade to 5.1 via OTA. I did disable driver enforcement before booting OS. Maybe the problem is that I cant see my device on device manager before I choose "Apply update by ADB". And after that it is recognized as Tegra Note 7 and windows wont to replace driver (message: windows was not able to find driver). How can I unlock the bootloader without supertool?
Use the command fastboot OEM unlock you'll need to find the fastboot driver and adb driver from nvidia. You can use the nvidia shield driver which is digitally signed to do this.
Sent from my MotoG3 using Tapatalk
Sent from my MotoG3 using Tapatalk
After command fastboot OEM unlock, I see "waiting for device". Because computer see my device only in "adb sideload" mode I cant confirm unlocking on device. I also tried restart device during waiting, but it ends with Failed (Too many links).
Last edited:
I have one success, after using nvidia shield driver I was able to flash ROM via guide "Recovering your Advent Vega Tegra Note 7". Everything passed succesfully, but the booting is stopped on the screen where you can choose language and device start shutting down. I think it is caused that recovery tool was done for android 4.x and in my device is probably some mess of android 5.1. My question is, is a good way to find system.img file for android 5.1 and change it in booting folder?
@deahlie the only way to upgrade to 5.1 at the moment is via Recovery and the OTA zip file. As of yet Only the 4.4.2 Image is available via nvidia.
As for the fastboot OEM unlock command not working did you install the driver for fastboot as it needs to be manually done via the Device manager on Windows. Glad that you got it working again.
As for the fastboot OEM unlock command not working did you install the driver for fastboot as it needs to be manually done via the Device manager on Windows. Glad that you got it working again.
Last edited:
It is DONE! I replaced images for recovery, system and boot in flashing folder. Device is back on slow android 5.1, but it is working 
Thanks a lot hacktrix!
Last question, what it the safest way how to do a downgrade to android 4.x?
Thanks a lot hacktrix!
Last question, what it the safest way how to do a downgrade to android 4.x?
Safe way to downgrade would be to fastboot flash a 4.4.2 boot recovery system images. So for example fastboot flash boot boot.img fastboot flash recovery recovery.img fastboot flash system system.img then just do a factory reset in recovery after
Sent from my MotoG3 using Tapatalk
Sent from my MotoG3 using Tapatalk
I noticed your super flashes the xolo version of the files. can you upload a version that has the stock evga so i can send it in and get my speakers fixed.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone