Bricked Tegra Note 7

share_needles

Member
Oct 24, 2014
15
1
0
EVGA Tegra Note 7
4.3 jelly Bean

Used the Super Tool to flash drivers and unlock bootloader.
Installed TWRP Recovery
Rooted using SU

Everything is working great, at this point.

Failed to back anything up
Flashed Shaky's custom Kernal and I couldn't get past the tegra note 7 screen. - at this point I probably could have saved it but doing anything other than what happens next.

Flashed 4.4 stock Rom which has to have reset the Recovery and Debugging is now off.

Do not do what I did. Brick. Any ideas? I can still get into bootloader which is unlocked but my computer no longer recognizes it. Pretty much lost hope on this one. Surprise me if you feel inclined.
 
Last edited:

share_needles

Member
Oct 24, 2014
15
1
0
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful. :confused:
 

kapil.git

Senior Member
May 12, 2013
154
44
0
delhi
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful. :confused:
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .

Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.

You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).


Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.

I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)
 

share_needles

Member
Oct 24, 2014
15
1
0
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .

Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.

You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).


Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.

I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)

Yea I jumped in the deep end without doing enough research. I have rooted and installed custom ROMs on my android phone without issue but I've never messed around with kernals or had to dig myself out of a device stuck in boot-mode. Instead of learning about a device then modding it, I forced a situation where I modded now need to learn how to fix it.


As novice as I am, still working on getting the correct drivers installed to sideload a backup. My computer will not recognize the ADB device in the stock bootloader but when I boot into recovery it does recognize it so there is definitely a driver issue there.
 

StainlessS

Member
Oct 25, 2014
21
3
0
By kapil.git
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
I think more like a dozen brands of TN7.

You should at least tell your brand, would make it less mysterious.
Advent has a stock 4.3 install install via APX mode (although you seem to be only able to use it once, then it locks
the nvflash stuff).
 

share_needles

Member
Oct 24, 2014
15
1
0
Hi Guys. Tablet is working fine now. I used multiple files from multiple sources to get this going. Here were the commands to get me back to stock. Obviously there was a lot of playing with commands etc that I cut out. I truly believe this device is unbrickable. I was just stuck in a bootloop.

in short, the issue was with the boot after a kernel flash. The TWRP recovery was flashed back to stock.
Got the drives from SDK download because I'm not slick enough to be able to do it myself.

In fastboot, make sure you have the fastboot file in the folder with your boot.img , recovery.img

fastboot boot boot.img ----got me out of the bootloop temporarily without flashing anything unnecessary

fastboot flash boot.img, flashed the boot.img from Vega Note 7 source files that are out there, I recommend every download those now.

fastboot boot TWRP_recover.img -----messing around be led me in a good direction

From there, I installed the below file from XDA User e8hffff
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip

I believe that was a full backup of a 4.3 Evga Tegra Note 7 stock. This really helped me out a lot.


Thanks everyone for the help. You can see by the very few command that got this device up and running I am a total noob but I'm figuring it out little by little.

If anyone is in a similar circumstance in the future send me a PM and I may be able to assist you.