Database Info

Stop flashing until usb problem is fixed...

Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!

Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?

Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.

It could be any ROM.
Sent from my HTC Desire using Tapatalk

socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.

I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably

My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.

It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...

The problem is APPS2SD related.

DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?

Could this be most of the issue happened to be with people with .80 bootloader??

kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.

abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.

socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.

I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now

Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm

millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?

you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms

millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky

Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.

[Q] A question about my brick

I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.

jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.

MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.

Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.

jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).

_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!

jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.

I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.

MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.

_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...

okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.

Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] No way back? (magic ring)

Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.

In that case I'll give ya $100 for it.
Sent from my Galaxy Nexus using Tapatalk 2

zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unfortunately, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thread that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before via HOT LINE but without any response!) This tablet is really a piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Well my friend not exactly the best words to start with if needing help from the many fine members of this forum.
The unlock tool will eventually work if that's what you want to do.
Personally your being "really ugly" to Asus thru e-mail could be why they remain unresponsive.
If you could perhaps take the calm approach those trying to help would be much more willing.

absurd paradox
Unfortunately I can understand where all these negative feelings derive from.
I am the rightful owner of a tf700 too.
To be quite frank (and I won't surprise anyone), I am not pleased.
There is no reason why I can't enjoy a smooth and flowing experience.
There is no reason why in order to make the best out of the tf700 it is recommended that I flash a custom rom.
I refuse to unlock my tf700 because there is no reason why I should void my warranty, trying to fix it - this is an absurd paradox!
It is about time someone filed a class action in order to stop this "tf700 incident",
so Asus will start to make their excuses in court or maybe solve this unfortunate condition,
once and for good.
cheers.

Nothing stopping you from filing a class action lawsuit is there?
Or you could just take control and unlock and flash a custom ROM and be done with it....
Choice is yours as Asus are not going to help you.

wish it was that simple
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
For example, I read a guide which explains how to unlock and install a custom recovery using an "adb tool",
but there is no explanation how to install the newest version of TWRP, which is required for cromi 3.4.X.
Anyone know a plain and full guide for 10.4.4.25 build?

http://forum.xda-developers.com/showthread.php?t=2088176

No very ugly
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks

zrebec said:
OK, that wasn't very ugly mail, just I wrote to ASUS that I tried contact HOTLINE two times and nobody response me I was very frustrated that I cannot unlock my tablet
Can someone explain me, why doesn't exists alternative way around unlock?
The processor is encrypted or what?
Thanks
Click to expand...
Click to collapse
A work around for the unlock isn't available.
Seems as though the key for the bootloader is encrypted very well.
Until someone leaks the key to the internet we're stuck.
My understanding is:
Asus wants the embedded serial for any tablet requesting a bootloader unlock.
The serial is registered with Asus from an outside server database.
Asus voids the warranty then shuts off OTA's because they don't want to push updates over any customisation to the tablets firmware.
This would most likely result in a bricked\non-functioning device.
Asus knows people inherently re-code devices with non-manufacturer firmware and risky applications.
The manufacturer is saying to the buyer we can't be responsible for user induced damage.

zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Another woe-is-me post! Someone please get me a hankie, quick!

zrebec said:
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
Click to expand...
Click to collapse
First of all you could use the search button
Here is a thread where I specified how I got my tablet unlocked: http://forum.xda-developers.com/showthread.php?t=2146543
Just keep in mind that the Asus Support employees are not personally responsible that the MDM-server in Taiwan does not know your tablet. Don't act like a jackass and don't act like mister-know-it-all, then they will help you, like they helped me.
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
Click to expand...
Click to collapse
These forums here provide all information one needs to unlock/ root/ install custom ROMs. I got all information from here and I did not have any problem whatsoever.
You know, people here are willing to share their experience and to help out each other, but the burden to do the work is on you. Also the risk of bricking your device is on you.
Just don't expect anybody to do your work.
As a matter of fact, installing custom ROMs on the TF700 is not trivial. You do need ADB and Fastboot to flash a recovery first. Also you have to have some basic knowledge about how computers work in general and about Android devices.
Even as complete noob, you can find all needed information here. So either you take your time and educate yourself - like I did - or you use the stock ROM or you hire somebody who does the work for you.

Root it but keep it locked! I was loosing sleep at night because I thought I was suckered into believing this was a quality machine and its got tons of glitches, no doubt. But they are mainly lack-of-RAM related. If you root, and disable most of your startups, you can get a clean 500MB after boot, and that makes all the difference in the world, trust me. I was in you boots and was actually dreaming about getting an iPad (please forgive me guys). Honestly, I was sick to my stomach then the rage set in. I decided to learn and root before throwing this POS on ebay or craigs list, and starting over with another brand, probably an Apple, I was so hurt by lack of quality and testing/debug.
Like day and night! Now I love this thing. Hasn't had a random reboot, app crash, etc. in nearly a month now. Before I was getting 5 per day. Its an amazing difference attributed to the OS and apps having room (RAM) to run in. Whoever decided that 1GB RAM for a 4-core droid tablet was enough should be tarred and feathered then shot in the head twice!!! If it had been 2GB instead of 1GB we wouldn't be having this discussion at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Unlocked! Yay!
Hello dears,
so I have my tablet Unlocked now... I forgot.... You must register account and then register tablet here https://vip.asus.com/login.aspx?. So maybe this can help to someone... OK, I have installed Clean Rom Inherited now and it looks and works fine Thanks to all.
So steps to reproduce:
1) Create account on https://vip.asus.com/login.aspx?.
2) Register device after that
3) Download Unlock Device App: Unlock boot loader from Android -> Utilities from http://support.asus.com/download.as...Pad Infinity TF700T&hashedid=fq2B3oq64av1O95u
4) Run the application
5) Tick the you understand that your warranty is now VOID
6) Type your google account login and password
7) After restart you should see in up-left corner message "Device is unlocked"
8) Enjoy

Update: Fixed my last known problem which was wifi streaming movies to the device from external source (wifi HDD or network connected storage). Got Dice Player, that's all I have to say. Now EVERYTHING is working perfectly. No more random reboots, app issues, conflicting apps, got plenty of RAM, got all my desired startups loaded including System Tuner with a few tweaks added, Browser2RAM, RAM booster, etc. and device runs fast, smooth, and without any "glitches". I finally have achieved rooted stability and will now take a rest and enjoy this tablet a bit before I do anything more to it because this has been a hair-puller to get to this point. Finally very happy with this device but I had to venture far from stock to get here and it was worth it.
By the way, what day of the week is it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

[Q] What if NVFlash got updated

Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.

I think you can only install nvflash on not-yet bricked devices!
Sent from my Transformer Pad TF300T using xda app-developers app

vahid_shirvani said:
Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.
Click to expand...
Click to collapse
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/

tobdaryl said:
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/
Click to expand...
Click to collapse
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.

graphdarnell said:
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.
Click to expand...
Click to collapse
Once nvflash is installed what you present is correct (at least that is my understanding - I have only done a simple restore for testing purposes). Look at my signature for a guide to restore with nvflash. The second method presented is what you suggest for the tf101.
The situation to install is different because Asus has locked the tablet to exclude installing nvflash.
I am in the dark as you are. I only know what I can and can't do on my tablet. Otherwise I can pass information provided by others.
My reference is the Nook Tablet. I can delete every partition and rebuild the drive from a blank state this is possible because the tablet can boot from an sdcard.
I had a pm request to provide an nvflash installation guide. I complied but did not present it on xda. The member making the request was pleased and successfully used it to install nvflash. I have since used it to install nvflash on one tablet. Honestly my guide is no better than the guide provided, just a different presentation and can be done by anyone who wishes go step by step through the guide already presented. Just copy and paste the info and do some minor rewording.
I wish I could truly help but I honestly can't. I have come to accept some related info as fact since I have not been able to prove otherwise and have grown tired while chasing dead ends. I don't have the expertise, experience, or hardware to move forward.

Installing TWRP per instructions and now phone DOA...

Hi all,
I've been ROM'ing since 2013 on multiple devices so I am somewhat familiar with adb/fastboot flashing and commands, what to do, what not to do, etc.... I just picked up a used pixel and first thing I did was unlock the bootloader - no problem. Next I go to root, so I began following this tutorial https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/ , as instructed I DL the required drivers, image files, patch file etc...and follow this tutorial for installing TWRP https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ , I get to step 8 and instruct via the command window to fastboot boot twrp.img, just as instructed. Everything appeared to be going the way it should as it started to boot to TWRP but almost as quickly the phone just died. I mean dead as a door nail. It won't do a thing. It won't even charge now. I have never had a phone just die like this. I fear I have met my first true full on brick.
I mean, yeah, I have soft bricked phones many a times but always had a backup to restore or was able to dig my way out one way or another but that was explainable by messing with questionable ROM's or something similar. Here I was just booting to the phone specific most recent version of TWRP by a solid well known tutorial with solid links, no indication that these could be the wrong images or zip's at all....but I'll be damned if this phone is dead as hell. I'm hoping someone can shed some light as to what happened or even miraculously tell me that it can be fixed.
Guys, is this a worst case scenario full on brick with no hope or getting it back to life? If so, why? Where did I go wrong? If this is going to be what I fear it is I hope to at least understand how it happened so I can avoid it in the future. This was a very expensive F-up on my part. I am beside myself with grief and disbelief that I could have done this with as many times as I have unlocked bootloaders, rooted, installed TWRP, flashed ROM's, etc.. I mean I 'm not the best but I am not a noob by any means. I feel like such a dumb ass right now!
Appreciate any help or explanation anyone can offer. Thanks.

We don't flash avb or any other patches anymore and haven't for like an android version and a half. For future reference look for more current information when modding a phone and for simple things like root guides go to xda don't just ask Google.

@kerryh420,
Those are some pretty old tutorials!
After plugging in the charger and wait for say 10seconds, can you boot into bootloader with button combo?
(Power + volume down or power + volume up for recovery as alternative)
Cheers
Sent from my Galaxy Tab S2 8.0 using XDA Labs

No offense, if you've been ROM'ing since 2013 you'd know not to go to other websites for tutorials! XDA is your best friend to follow instructions on Rooting, Flashing a recovery, and etc! Sorry that happened to ya. If it's literally dead you're probably out of luck and I know that's not what you want to hear. My best advice is to not follow tutorials on other websites. Good luck on your next device!