Flashed JB Stock Rom via CWM 5.8.2.0 Touch - Transformer TF300T General

Hey folks,
once there was a little boy who was glad to own a new Transformer, but after he made a mistake, the little boy thought his beloved Transformer transformed into a pretty pricey paperweight (Oh, by the way the "little man" was me :crying.
The following lines are telling the whole story.
DISCLAIMER
I am in no way responsible for what you do with your Transformer, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
(Because it worked for me, I dont guarantee it will work for anybody else.)
Precondition:
- TF300T
- unlocked
- rooted
- CWM Recovery 5.8.2.0 Touch
- Stock ICS
What I did:
Flashing the stock rom from ASUS via CWM.
What happend:
My Transformer was stuck in a recovery loop, which means it started, the asus logo appeared on the screen and instead of starting Android, CWM started.
The Problem:
- The Transformer wasnt able to start...
- Fastboot didnt work. If I tried to get into fastboot mode the message:
"The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "ww_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image"
appeard.
- ADB didnt recognized my device
- Wipe, format, etc in CWM didnt work.
So I managed to get out:
- Installing Transformer Prime drivers. Universal Naked Driver 0.7 http://forum.xda-developers.com/showthread.php?t=1766220 and/ or TransformerPrimeDriver http://downloadandroidrom.com/file/TransformerPrime/drivers Choose one or take both (worked not the first time, but after a few tries Windows recognized my TF300T as ASUS Prime ADB device.)
- ADB still didnt work.
- I found & downloaded "WSG_UnBricker_TF300T_V1.0.2.zip" http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html to my PC(Google will help. You also can choose and try the original one from MasterZen88, but I chose the other one)
- after extracting I started the WSG_Unbricker.bat on my PC and started the ADB Shell.
- There I did the commands from DiamondBacks' Option 1a and rebooted the Transformer.
- After doing so my Transformer stucked on the ASUS Screen.
- I pressed Power till the screen went black.
- Then I hold Power + Volume Down. Then I chose Fastboot Mode. On my PC I started WSG_Unbricker.bat again. Here I started "Install Menu" and tried to install recovery, boot, system, all... Did a few restarts with my Transformer and repeated this step. After a few times I was able to start into CWM Recovery 5.5.0.4 instead of the 5.8.2.0 in the beginning.
- Transformer in CWM Recovery I opened cmd out of the WSG_UnBricker-folder and did the command: adb devices. My Transformer was RECOGNIZED!
- I downloaded cm9.1.0-tf300t.zip http://get.cm/?device=tf300t, renamed it into update.zip (after all maybe not necessary )
- put this update.zip into the same folder you started your cmd out of.
- Then I did the command: adb push update.zip /sdcard/update.zip
- After the transfer was finished I was able to flash the update.zip via CWM Recovery.
- Now I rebooted and watched my Transfromer booting into Android! :highfive:
I m not sure ir this story really helps anybody.
I m not sure if even anyone reads this lines, but maybe I could help another little boy

Ok, I don't test, because I already use TWRP, but it will be good if you could insert the links for all of your different files so that the members can use your method correctly.
Thanks.

What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?

timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
don't think he has since he was able to install CM

timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )

Droid_1 said:
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )
Click to expand...
Click to collapse
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx

0din said:
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx
Click to expand...
Click to collapse
Hello,
when my transformer was stuck on asus logo I was able to go to bootloader so... at the moment I dont have an idea.
But this thread may help http://forum.xda-developers.com/showthread.php?t=1514088 if you didnt read already.

Just want to say thank you.
I Bricked the tf300 by flashing a JB rom and still using a ICS bootloader.
Flashing the cm-9.1 version was a good advice, now i can boot again.
Tank You!

Related

[Q] ZTE Blade not starting, maybe bricked...

I think my phone is bricked
When I start up my phone it just stops when it says "ZTE"
Tried to reboot but wont work, its fully charged...
Please help
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
NO
matt4321 said:
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
Click to expand...
Click to collapse
No. No. and none.
I weren't running any roms or anything, but i have tried to root it with z4root and gingerbreak (etc..) a million times...
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
if he installs stock rom and unroots then it should be fine and he will keep his warranty
Sent from my Blade using xda premium
Ehhh..
matt4321 said:
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
I dont quiet know how to do that
I was on 2.3.5 have 2gen stock rom
how do i get into fastboot then?
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
matt4321 said:
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
Still looks way to complicated for me :/
Do u know any videos that can show me how to do it?
hi is it bricked or what?
hi all xda members, im new on this forum and i really don know were to post or something like that, sorry, and i have searched on every singel page in google and on a lots of forums, and i dont find anything that can help me with my problem..:crying:
So now to my poroblem, i have a zte blade II 2.3.6 gen3 un-rooted, i tryed but no luck... and now i think its really bricked...because i cant boot it at all, not in FTM, not in bootloader mode, not in recovery, the only thing i can boot it in is DFU but i cant flash from there, it is bricked or can this be fixed easily? Thanx in advanced guys!
ZTE Blade does not respond at all
My ZTE Blade does not respond at all.
I have tried to install the official update from android 2.1 - 2.2 using this official application from ZTE
( ztedevices official site -> downloads -> Greece -> smartphone ->Blade)
It stopped in the middle of the process and after that I cannot use neither Power&volume(+) nor Power+volume(-) nor Power.
It looks completely dead.
Battery is fully charged,
When connected to charger, back button does not get red.
When connected to computer does not show android logo.
I have copied gen1 to gen 2 image folder to sd... nothing
gen2 to gen 1 the same.
I have also tried the AIO-BLADE application no respond to any action.
I have been searching this forum and the internet for 2 days now. No one answers cases whith hardbricked phones.
I think the phone is out of warranty.
PLZ it is my only smartphone and there is no money for a replacement, I am unemployed.
:crying:

tf101 bootloop, corrupt recovery, apx inaccessible. lend me a hand?

ok so i have a pretty big problem and very minimal experience with flashing and rooting. Reading and studying many many forums i have peiced together what i have done wrong to do brick my tablet. So to begin a few days ago i managed to wipe my stock recovery and flashed a non existant one, reason being is i didnt download a recovery and unzip it in the required folder. the following day i had it rooted, that was successful. i installed an app from the android market which required root access and a reboot. It is now in bootloop on the "Asus Inspiring Innovation Persistant Perfection" Recovery results in the "Dead Andriod" screen. i have tried flashing using easy flasher but i cant get into APX mode to do so. if i exicute apx mode and plug the usb into the pc i dont get a response, but if have the cable already plugged in and exicute apx i hear chimes and i get "win 7 apx drivers not installed" i tried easy flasher and successfuly flashed WW_epaduser9_2_1_27UpdateLauncher asus stock rom however it still stuck in bootloop. i tried the recovery feature that came with easy flasher but that still result in bootloop when i boot from recovery. i have tried many recovery mods and none seem to work. im doing something wrong i just need someones help getting me out of this i dont want to make anymore mistakes. i have done enough damage. im taking this as light as possible, im a noob i watched the xda noob video and i read a t101 guide on a thread here on this website. many thanks for caring about a strangers issues.
asus tf101 S/N :B60KASO41231
ICS 4.0.3
9.2.1.27
rooted stock rom
audiphur said:
ok so i have a pretty big problem and very minimal experience with flashing and rooting. Reading and studying many many forums i have peiced together what i have done wrong to do brick my tablet. So to begin a few days ago i managed to wipe my stock recovery and flashed a non existant one, reason being is i didnt download a recovery and unzip it in the required folder. the following day i had it rooted, that was successful. i installed an app from the android market which required root access and a reboot. It is now in bootloop on the "Asus Inspiring Innovation Persistant Perfection" Recovery results in the "Dead Andriod" screen. i have tried flashing using easy flasher but i cant get into APX mode to do so. if i exicute apx mode and plug the usb into the pc i dont get a response, but if have the cable already plugged in and exicute apx i hear chimes and i get "win 7 apx drivers not installed" i tried easy flasher and successfuly flashed WW_epaduser9_2_1_27UpdateLauncher asus stock rom however it still stuck in bootloop. i tried the recovery feature that came with easy flasher but that still result in bootloop when i boot from recovery. i have tried many recovery mods and none seem to work. im doing something wrong i just need someones help getting me out of this i dont want to make anymore mistakes. i have done enough damage. im taking this as light as possible, im a noob i watched the xda noob video and i read a t101 guide on a thread here on this website. many thanks for caring about a strangers issues.
asus tf101 S/N :B60KASO41231
ICS 4.0.3
9.2.1.27
rooted stock rom
Click to expand...
Click to collapse
i finally got easy flasher to work, installed apx drivers manually updated device booted into apx mode ran easy flasher and got me out of bootloop, thank you.
audiphur said:
i finally got easy flasher to work, installed apx drivers manually updated device booted into apx mode ran easy flasher and got me out of bootloop, thank you.
Click to expand...
Click to collapse
Can you post the steps please?
mstrblueskys said:
Can you post the steps please?
Click to expand...
Click to collapse
Try this:
Open page with EasyFlasher
Download EasyFlasher
Restart your device into APX (power off than power on while holding volume up - screen will turn black and it will look like off)
Connect your tablet to windows computer. If you already have APX drivers just continue with next step. If don't, windows probably show you info that they didn't find proper driver. Just download APX driver (link on Easy Flasher page), open device manager on windows, right click on APX (it will have exclamation mark next to it) and choose update driver and select manual location to location where you extracted apx drivers.
Download the latest ASUS stock firmware (link also on Easy Flasher page)
Choose Flash Asus stock zip / Unbrick and select location of downloaded stock
When finished, click on flash button in Recovery area.
reboot and pray

asus tf300t bricked

kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.

[Q][SOLVED] A500 bricked, stuck in bootloader. Won't boot kernel or recovery.

I am sorry to start a new thread but I have been reading threads and trying things now for over 7 hours straight. I have bricked my mothers A500.
I installed Skrillex V8 bootloader to my own tablet with Thor 1.7.3 recovery and a CM10.2 rom, everything worked fine. My mother liked how my tablet had way more battery and seemed faster then her own so she asked me to do it to hers.
I did everything the same except I had deleted the files and had to find a different bootloader so I found the "lightspeed" version of Skrilex V8 and as it seemed to just be a re-skin figured it was fine.
I downgraded to the unstable 3.0.2 build then installed iconia root and a Thor recovery via acer recovery. I then installed the lightspeed bootloader via thor with intentions of then installing the newer thor and rom after.
This is where im stuffed, after installing the new bootloader it is screwed. I cannot enter recovery or boot the primary kernal. I attempt to enter fastboot and although the tablet goes into fastboot it outputs errors and has random lockups and freezing on the tablet which the computer identifies as it being disconnected.
I have tried searching the forums for an answer and have tried everything I can understand but I am truely boned. As I am writing this I am installing packages to my Ubuntu laptop so that I can obtain the UID through the terminal in hopes it will work with APX and blackthunders tools.
If I cannot get it working I will simply wipe and give my mother my tablet, But I would really like to try and get this son of a ***** working again. I am currently incredibly annoyed at it and am probably missing something obvious. Please help me.
[UPDATE 1]
I have managed to obtain my CPUID and thus my SBK through the method described here -> http://forum.xda-developers.com/showthread.php?t=1751978
I am still unable to use any tools as my PC will not recognize it in APX mode, I have reinstalled the drivers, restarted, tried multiple USB ports, uninstalled the failed unrecognized device and started from scratch a few times and I just cant seem to get it to detect them. Also tried other USB cables incase it was iffy, checked contacts on ports. There also cannot be any env variable or reg conflicts as I used my diagnostic machine to check it and it booted into its clean OS.
the APX seems to work with my linux unit though, but the blackthunder tools are for windows...
[UPDATE 2]
Using the tutorial here ->http://forum.xda-developers.com/showthread.php?t=2444187
I made it boot into the APX mode with the yellow acer logo and the APX mode text at the top, however I left it for a while and it didnt seem to finish flashing, using lsusb I can see its still connected to the linux box but it is clearly not flashing properly.
I am going to leave it for a bit then try unplugging from linux and plugging into windows while in the yellow acer logo screen with verbose output and see if blackthunders tool detects it.
[UPDATE 3]
DO NOT try what i did in update 2, I believe i removed it when it was formatting the partition, it wont even boot to the bootloader now. black screen with white light on power button and cannot be detected as APX.
[UPDATE 4]
I treid a few more times at getting it into APX mode and it turns out its just being dicky and freezing randomly, however, by trying a few times (this is dangerous but i had nothing to lose at this point) to run the Nvflash script on my linux box eventually it run through and installed the v9 bootloader. This bootloader allowed me to go into Fastboot without the freezing or crashing or loss of communications i was experiencing before. I then using fastboot flashed a recovery appropriate to the v9 bootloader and am now using that to flash a 4.3 rom. This should completely fix all the problems.
I am now sure (as previously I could only guess that the problem was caused by a dicky install of the lightspeed bootloader (a custom variant of skrilex v8 designed to match the theme of the lightspeed rom).
[UPDATE 5]
Working
Adding solved to title as I know the feeling when you come across an old thread that talks about your problem and has no replies or help.
-V0L4T1LE
Been using XDA for years never bothered to post as have never had to spend more then a few hours to solve a problem, this one took me a long time though so I decided to ask for help. Nevermind, didnt need it.
Awsum and well done getting yrself sorted, thanx for posting
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
Can you extract the partition 4 using nvflash --rawdeviceread to a file and share to me? My A500 is bricked and cannot download to it. only --rawdevicewrite works.
Thanks!

[Q] Bricked Advent Vega Tegra note 7 no usb debugging

My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
icdeamons said:
My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
Click to expand...
Click to collapse
Hi mate as you can get to the bootloader all is not lost.
Download the following files
The Restore to Factory via nvflash: http://www.adventcomputers.co.uk/download-select/nojs/3255
Recovery Guide: http://www.adventcomputers.co.uk/download-select/nojs/3260
Follow the guide to the letter apart from if you have the drivers already installed for ADB and Fastboot you also have the driver installed for APX.
This should get you booting again hopefully.
I have this problem but im on completely untouched device. No root no recovery all official roms.
What can i do?
LightInDark said:
I have this problem but im on completely untouched device. No root no recovery all official roms.
What can i do?
Click to expand...
Click to collapse
Do the above my friend that is your only hope.
Doing it via NvFlash doesn't require root as your flashing via a special mode called APX.
my problem is I don't think my computer even picks it up because the USB doesn't kick in until after the TEGRA NOTEtm screen as far as I am aware.
Follow the PDF it will place the device into apx mode for flashing via nvflash. The guide shows how to install drivers to flashing the device.
Apx mode is to recover from complete bricks or issues like the op. If you can't boot in to android give apx flashing a go. Trust me on this one. I have already done this myself.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
icdeamons said:
My son has this tegra note which he dropped and it is stuck on the the "TEGRA NOTE" boot screen i can get the bootloader up and have tried factory reset and side loading a update with sd card but non of these have made any difference. I have watched all the un bricking vids and help files and tried everything i can but nothing works as the usb debugging was never enabled, is there any way i can re-install the complete OS without this enabled ?
Click to expand...
Click to collapse
When i root my slate 7 extreme i never knew that i need to enable the usb debugging mode but somehow i am able to get root access by unlocking the boot loader and installed the cwm(which is usefull to install stock/custom rom)..heck i only know that option was actually available and hidden by default after rooting the device.
the step i followed is from this link:
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
and watching all rootjunky videos at YouTube might be helpful too..
You can unlock the bootloader, flash recovery the root that way but the aio scripts use adb and fastboot not just fastboot on its own.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
hacktrix2006 said:
Hi mate as you can get to the bootloader all is not lost.
Download the following files
The Restore to Factory via nvflash: http://www.adventcomputers.co.uk/download-select/nojs/3255
Recovery Guide: http://www.adventcomputers.co.uk/download-select/nojs/3260
Follow the guide to the letter apart from if you have the drivers already installed for ADB and Fastboot you also have the driver installed for APX.
This should get you booting again hopefully.
Click to expand...
Click to collapse
Hello.
Does this also work for other brands of Tegra Note, like Homecare?
Cheers,
Jaro
Doesn't work, I tried this and it just gets stuck on the Advent Vega logo instead of the TEGRA Note logo.
Ok have you tried going into the bootloader and getting into recovery?
If you get a android with a red triangle just press Vol-Up and power then clear the cache then do a factory reset and then reboot and see what happens.
If after the reboot your still in the same boats as you was before the apx flash then i think it could be due to a messed up partition somewhere (bad block on emmc) i am still looking for other ways of recovering the devices that have bricked but Nvidia has decided not to reply to my messages (Thats the mobile team support for ya!)
I retried the flash and it got to the spinning nvidia logo for a few secs, then it froze and the screen messed up and jumped around pixelly. Then shut off and started getting incredibly hot and wouldn't stop. Seems like bad manufacturing to me.
Sent from my LG-G2 using XDA Free mobile app
It sure looks like that as my first on did this as well. Seems its a hit and miss. My first one died due to the battery getting way to hot and killing the tablet the second one i stopped at 4.3 and i haven't had any issues. So not sure whats causing the issue out right.
Take its out of warrenty?
I hope advent will replace it even while in another country, I got it while under warranty but I'm currently in Belgium. It didn't even last 1 month before dying.
If no luck you could try Nvidia directly via their support
Posting an update. Whenever I try the fix from the advent flash it finishes, reboots and gets stuck at tegra note again.
LightInDark said:
Posting an update. Whenever I try the fix from the advent flash it finishes, reboots and gets stuck at tegra note again.
Click to expand...
Click to collapse
Hi mate, OK how many times have you flashed via the APX ???
Can you get back into fastboot?
If you can try a fastboot -w and then try booting again.
Well I decided to try a full dead battery then left it to full charge)(charging screen still shows fine) then run the flash and now it still hangs, not sure how to enter fastboot with this tablet.
Sent from my LG-G2 using XDA Free mobile app
Press and hold Volume Up + Power Button till a black menu comes up then go to fastboot protocol.
Then issue the fastboot command!
---------- Post added at 03:18 AM ---------- Previous post was at 02:37 AM ----------
If doing the fastboot -w hasn't fixed it the last thing you can try is the following
Download this: https://mega.co.nz/#!3R1GTAxY!ZeQRTsZdP0xVHP8fl4ImsEQK6Wc0br-8BeeWWuKhd94
Extract this to where fastboot is then type the following.
fastboot flash staging blob
fastboot flash dtb tegra114-tegratab.dtb
then reboot and see what happens!
Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.

Resources