Database Info

[Q] Loaded Wrong TWRP on TF300T and can only access APX mode

Hello,
I loaded the wrong version of TWRP on my TF300T. When it rebooted it loaded CM10.1 just fine. I then rebooted a second time in recovery mode and I have been stuck at the ASUS screen with the "device is unlocked" message. I am able to get into APX mode but my research has shown that mode doesn't do me any good if I haven't ran a nvflash backup. I am stuck and I would appreciate some advice or suggestions. I wonder what the factory reset fee would be from ASUS.
Thank you for your responses!

what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD

macgyver40 said:
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Thanks for the speedy response =)
Version History: Stock 4.1 -> CM 10.1 Nightly 0503 or 0429. I had CWM on it before trying to load openrecovery-twrp-2.5.0.0-tf300t-ICS.blob using the terminal emulator method. I think I should have loaded the JB blob but the warning on the TWRP site said to use that if you ran the offical OTA update, which I never did so I stuck with the ICS. It installed fine, then rebooted into CM 10.1 just fine. I then rebooted from there into recovery and have been stuck at the ASUS screen since.
The Vol + - button keeps me in the ASUS screen. Reset button keeps me in the asus screen. Vol + + puts me in APX mode.
I try running fastboot in APX mode but it hangs stating "waiting for device" so I don't think it'll work in APX mode.
Thanks.
T

Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.

c0ded said:
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
Click to expand...
Click to collapse
I bled it last night. I'll try booting it this evening. Thanks!

racet said:
I bled it last night. I'll try booting it this evening. Thanks!
Click to expand...
Click to collapse
No luck. I bled it twice and I'm still stuck at the ASUS logo with "the device is unlocked"
Am I looking at repair here?

If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of eBay and replace it with the one in your tablet. Also, to save other people's tablets from bricks, you may want to look into this petition.

if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD

c0ded said:
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of
Wow 200$ what a load. To what degree of difficulty are we talking with replacing the mobo? Ifixit makes it look doable, yet at the end he messed up his LCD screen.
Click to expand...
Click to collapse

macgyver40 said:
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I would def like to try it if you can find it.
T

please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
http://forum.xda-developers.com/showthread.php?t=2041528
found it. Hope this helps you like it helped me out of my broken recovery. once you download and add the files you want its pretty easy. the script in english makes it pretty easy to understand what your doing and hope it works since I know my TWRP was broken I couldn't even sit at the recover,android wipe screen for more then 3 mins without it bootlooping. I put it on that screen while connected to laptop ran the recovery flash and all went well installing TWRP 2.5 which I then recovered my backup and that even restored my 2.4.4 patch TWRP like nothing happened at all. tablet runs great and have made 3 backups that work after all this.
Good luck

macgyver40 said:
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Please take your time. I have no problem waiting especially if the only solution is to drop 75$ on a replacement mobo.
You could send me the file via email or drop box if it's easier. I was going to use the TWRP 2.5 JB with CM 10.1 nightly. I appreciate all the help!
T

look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD

Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot

macgyver40 said:
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I tried running through your tread but none of the commands worked on the script. Probably because I can't get fastboot to work. When it tries to load a recovery it just states: "waiting for device" and sits there. =/

c0ded said:
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I am unable to get fastboot to recognize the device. The only way the PC recognizes it is via APX mode. Download mode just sits there at the ASUS screen and windows doesn't see any devices.

Still no love. Am I bleeding out the battery correctly? I am just running the boot screen until it dies then I try to power it on again.
I popped the back open today to see how difficult it would be to replace the mobo, doesn't look too bad. Just having difficulty finding a good online guide.
Also, just so I have the terminology straight, when the tf300t goes into a "boot loop" does it ever leave the asus screen and go black or does it just hang? Mine never goes black, just sits at the ASUS screen with "the device is unlocked" message. The only time I can get it to leave this screen is when I do a reboot and hold the + sign. then it goes black and APX is detected on windows.
Just wasn't sure if any of that information was useful.
T

One other solution is to unplug the battery for 30 minutes, then plug it back in.

c0ded said:
One other solution is to unplug the battery for 30 minutes, then plug it back in.
Click to expand...
Click to collapse
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)

racet said:
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
Click to expand...
Click to collapse
Usually, the volume button does not fail. Remember the volume button connects to, but is NOT part of the mother board. If it feels stuck when you push it, that's because you snapped the back cover in wrong. You need to slide it in at the corner where the buttons (volume & power) are, then pop in the rest of it. Take it out and do it again.

[Q] Dead droid, red triangle on recovery kernel

Ok, so i've read up that your able to fastboot a new recovery, but i havnt been able to find a link with a stock recovery kernel.
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Bootloader (1.00 e) released by "WW_epad-10.4.4.20-20121026" A03
The story is i've bought it some while ago of course, and its been lieing around on the table for a few months.. Basically busy life and other ****. Yesterday i looked at it and was, oh right! Turn it on, and it bootloop on me, apparently common issue with a JB version. herpaderpa on android but fck that..
And when i use a update file on the sd card, i cant install that to update the stock firmware due to the dead droid with the triangle..
From what i can gather around, if i have fastboot option, then its unlocked ? Yes, no ?
If so, could anyone give a hint as to whut the duck i've missed when reading the big full guide thread on the infinity Im starting to become rather desperat. Never had this kind of behaviour with my android devices before, Sure a goofed usb driver for fastboot here and there.. But never a dead droid with triangle..
SOLUTION :
Follow this chaps guide http://forum.xda-developers.com/showthread.php?t=1755576
using his alternative method, and at step 2.
DO AS HE WRITES! Using upper case letters on the file your moving to the sd card, EP201_768_SDUPDATE.zip as such! It works!
My droid kept showing up dead, untill i changed to upper case letters... Then the darn thing came to life!

The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".

_that said:
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
Click to expand...
Click to collapse
In that case, how can i go about bringing my tablet out of this infernal boot thing? I've tried flashing the twrp kernel, but i dont see any change, when i sent the flash it dit get a blue bar on the bootloader indicated full. So i assumed it could send the loader..
Basically i just want to firmware upgrade with the latest stock firmware, But i tried dumping the file on an sd card, and then go into the bootloader But it did not recognize it and start an update. also i couldnt go into the RCK selection, due to the dead droid.

What exactly did you do, exactly which file(s) did you try to flash, and what exactly happened? And does "I couldn't go into the RCK selection" mean that you never see the bootloader menu, that it doesn't work, or that you don't know how to use it?

Ok, basically, when i start the pad, it never goes beyon the ASUS screen.
Im able to get into the bootloader, here i have 4 icons, RCK, Android, USB, Wipe Data.
When i select RCK it brings the dead droid after a droid thats working.
If i enter USB i can use fastboot. What i've tried here is to do the http://www.teamw.in/project Twrp recovery using http://forum.xda-developers.com/showthread.php?t=1833212 guide *** Custom Recovery Installation ***
However i dont think that it ever was sent to the tablet. Not sure.
I know how to move around in bootloader power + volume down = mennu, then tap the volume to switch between icons, and the other volume to select.
Power + other volume = AXP iirc in stead of bootlaoder.

Did not try to flash any files when the dead droid thing / bootloop started. I basically did an OTA update iirc to a newer version a good while ago. And then life became fcked for me for a periode so playing with the tablet wasnt really an option for enjoyment. It then drained of battery of course, and here now after having it charged up. i realise about this odd bootloop for one of the older droid software versions.

theorion said:
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Click to expand...
Click to collapse
_that said:
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on.
Click to expand...
Click to collapse
Do you already know if your device is unlocked?

_that said:
Do you already know if your device is unlocked?
Click to expand...
Click to collapse
No, it does not say unlocked any where

theorion said:
No, it does not say unlocked any where
Click to expand...
Click to collapse
OK, that explains why installing TWRP didn't work.
Now if you would describe in detail what you did to install the latest firmware, maybe someone could tell you why that didn't work.

Did you unzip the downloaded firmware update once (the result being another zip file)?
The unzipped zip is what you have to put on your sd card. Then the recovery should recognize it when you boot.
If that does not work, try to rename the unzipped zip: EP201_768_SDUPDATE.zip
and put that file into the root of you sd card.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

1. Downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.8 Only for WW SKU (Android 4.2.1) from the TF700F download page selecting android as os.
2. Have a 2gb microsd, i formated as fat 32, using all standard alocation and stuff with windows' own formatting tool.
3. I unzipped the downloaded ZIP file so i have a WW_epad-user-10.6.1.14.8.zip that now contains a meta-inf folder, and a blob file.
4. renamed the zip file to ep201_768_sdupdate.zip, however i did use lowercase... Could that be the issue ? Basically i presumed that the uppercase was only to make people aware of a change.
5. boot the device using the power + volume, and enter recovery mode.
6. Dead droid..
Update as i was writing this, i thought, though it wasn't said specificly, i renamed the EP201_768_SDUPDATE to uppercase, and decided to give that a go.. Now the droid is working its ass off...
F**** i feel like a complete bloddy retard! Gawd i hope it works now then...

And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!

theorion said:
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
Click to expand...
Click to collapse
Oh yeah, Linux is case sensitive alright. Get the case wrong and it has no idea what you talkin' bout Willis.

[Q] Complete touchscreen failure

Hey Everyone,
Recently the touchscreen on my HTC Sensation stopped working, including the capacitive buttons. I pulled the battery to reset it (several times), but still the problem persisted. I then though that maybe I should do a full wipe and reflash my ROM (CM10.1 AOSP 4.2.2 Jellybean [KANG]) but I have CWM Touch installed and therefore can not achieve this from the phone. I then searched for ways to flash the ROM from the PC through adb, but haven't had much luck at finding a precise step-by-step guide on how to do this. I searched through XDA and found a thread outlining a 'foil trick' to fix a potential grounding problem, however this did not resolve the issue.
Question 1: Is this (most likely) a digitizer issue?
Question 2: If not, is it possible to flash CWM Recovery (not Touch) over the top of the Touch version FROM MY PC so that I can reflash my ROM?
Question 3: If not possible, can someone please outline the steps to be taken to wipe and flash a ROM FROM MY PC?
I have attempted to connect my phone to my PC and flash the ROM using UniFlash, but my PC does not recognise my phone as being connected. I have made sure that the drivers are installed and HTC Sync is uninstalled, but it still does not recognise the phone being connected. Cannot check if USB-Debuggung is turned on as I cannot use the touchscreen.
Anything else I should try?
Thanks,
Matt
Edit: the screen itself lights up, I can receive texts, calls, etc. but I cannot actually interact with the phone due to the touchscreen issue

Hi yh id say ul need new digitizer, they cheap on ebay. Anyway if ur s-off u can use fastboot commands to flash non touch recovery. go here
http://www.clockworkmod.com/rommanager
Download non touch recovery (rename file to recovery.img)
Then go here
http://forum.xda-developers.com/showthread.php?t=2317536
Setup adb & fastboot
Once uv setup everything, put recovery.img in the fastboot folder then boot ur phone into fastboot mode (turn off phone then press n hold volume down + power then select fastboot) connect to pc and now shoud say fastboot usb. Now open command window from fastboot folder (shift right click, open cmd window here) then type
fastboot flash recovery recovery.img
U now should have non touch recovery
If im honest, if ur digitizer is broke then a full wipe and fresh flash of rom wont make a difference, but u can try.
You can try this thread aswell for some other fixes
[FIX] [UPDATED] Touchscreen issues
These fixes didnt work for me, i actually put a small piece of rubber on mine and worked perfect. see pic
Sent From My HTC Sensation

soloman56 said:
Hey Everyone,
Recently the touchscreen on my HTC Sensation stopped working, including the capacitive buttons. I pulled the battery to reset it (several times), but still the problem persisted. I then though that maybe I should do a full wipe and reflash my ROM (CM10.1 AOSP 4.2.2 Jellybean [KANG]) but I have CWM Touch installed and therefore can not achieve this from the phone. I then searched for ways to flash the ROM from the PC through adb, but haven't had much luck at finding a precise step-by-step guide on how to do this. I searched through XDA and found a thread outlining a 'foil trick' to fix a potential grounding problem, however this did not resolve the issue.
Question 1: Is this (most likely) a digitizer issue?
Question 2: If not, is it possible to flash CWM Recovery (not Touch) over the top of the Touch version FROM MY PC so that I can reflash my ROM?
Question 3: If not possible, can someone please outline the steps to be taken to wipe and flash a ROM FROM MY PC?
I have attempted to connect my phone to my PC and flash the ROM using UniFlash, but my PC does not recognise my phone as being connected. I have made sure that the drivers are installed and HTC Sync is uninstalled, but it still does not recognise the phone being connected. Cannot check if USB-Debuggung is turned on as I cannot use the touchscreen.
Anything else I should try?
Thanks,
Matt
Edit: the screen itself lights up, I can receive texts, calls, etc. but I cannot actually interact with the phone due to the touchscreen issue
Click to expand...
Click to collapse
I had same problem..
remove the battery and give external voltage to battery pin on phone via usb cable from PC ... Mine one is works this way. coz USB port is broken I tried to charge my battery externally. Ultimately I got my touch screen back

jmcclue said:
Hi yh id say ul need new digitizer, they cheap on ebay. Anyway if ur s-off u can use fastboot commands to flash non touch recovery. go here
http://www.clockworkmod.com/rommanager
Download non touch recovery (rename file to recovery.img)
Then go here
http://forum.xda-developers.com/showthread.php?t=2317536
Setup adb & fastboot
Once uv setup everything, put recovery.img in the fastboot folder then boot ur phone into fastboot mode (turn off phone then press n hold volume down + power then select fastboot) connect to pc and now shoud say fastboot usb. Now open command window from fastboot folder (shift right click, open cmd window here) then type
fastboot flash recovery recovery.img
U now should have non touch recovery
If im honest, if ur digitizer is broke then a full wipe and fresh flash of rom wont make a difference, but u can try.
You can try this thread aswell for some other fixes
[FIX] [UPDATED] Touchscreen issues
These fixes didnt work for me, i actually put a small piece of rubber on mine and worked perfect. see pic
Sent From My HTC Sensation
Click to expand...
Click to collapse
Thank you for your reply, your instructions about installing CWM Recovery were incredibly straight forward and made the process of re-flashing my ROM very easy. Unfortunately, re-flashing my ROM didn't help (wasn't expecting it to, in all honesty) so it looks like I will have to replace the digitizer Hopefully this relatively cheap fix will solve the problem. The thanks button has been pressed
Matt

soloman56 said:
Thank you for your reply, your instructions about installing CWM Recovery were incredibly straight forward and made the process of re-flashing my ROM very easy. Unfortunately, re-flashing my ROM didn't help (wasn't expecting it to, in all honesty) so it looks like I will have to replace the digitizer Hopefully this relatively cheap fix will solve the problem. The thanks button has been pressed
Matt
Click to expand...
Click to collapse
Yh didnt think it would either. Did u try the last link to touchscreen fix? Theres a couple of things there u can try, also the pic i posted, u could try that too. It fixed my touch screen problem. Anyway i know off ebay u can get a digitizer for no more than 20 euro, i baught one off there for my desire s for 10 euro and its perfect, they fairly easy to change urself. I did my own with no problems, just make sure the seller gives 3m double sided tape with it so u can stick the digitizer to the lcd.

jmcclue said:
Yh didnt think it would either. Did u try the last link to touchscreen fix? Theres a couple of things there u can try, also the pic i posted, u could try that too. It fixed my touch screen problem. Anyway i know off ebay u can get a digitizer for no more than 20 euro, i baught one off there for my desire s for 10 euro and its perfect, they fairly easy to change urself. I did my own with no problems, just make sure the seller gives 3m double sided tape with it so u can stick the digitizer to the lcd.
Click to expand...
Click to collapse
Yeah I tried the things in the link and what you suggested in your picture but nothing worked. I pulled my phone apart and I'm going to pick up a new digitizer (and tape) tomorrow. Hopefully that'll sort everything.
Matt

I replaced my digitizer with no problems. Or so I thought. My phone does not turn on! Battery indicator shows that the battery is recharged, so this is not the issue. Everything seems to be plugged/clipped into place. Could I have placed tape (3m sticker) over something important without realising it?
Any ideas?
Matt

What happens when the phone is off then u press power button? Does it vibrate as if it turns on?
Take off the back battery cover n try turn it on without the cover, if nothing then i suppose ul have to take it apart again and check if everything is connected

jmcclue said:
What happens when the phone is off then u press power button? Does it vibrate as if it turns on?
Click to expand...
Click to collapse
+1.
How are you going with this? Does it vibrate, does it not make HTC boot music? I'm wondering if the screen is hooked up properly.

[Q] Bricked TF700

Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.

Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!

Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.

Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.

Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.

Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...

Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.

berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash

Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?

sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock

zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...

berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.

Unlocking and Rooting AT&T LG V10 H900?

Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out

T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?

I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.

sharky481232 said:
I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.
Click to expand...
Click to collapse
How'd you manage to do that? I've tried a combination of buttons, but nothing.

RobertVanHagar said:
How'd you manage to do that? I've tried a combination of buttons, but nothing.
Click to expand...
Click to collapse
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.

sharky481232 said:
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.
Click to expand...
Click to collapse
Really hope you find the work around. Alot of people say at&t isnt going to allow rooting of new devices.......if theres a will theres a way!good luck

no updates?

I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?

betovanbuuren said:
I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?
Click to expand...
Click to collapse
I have the same problem with my AT&T H900. I'm on 90009e and wanted 90010f. AT&T Tech support couldn't get it to upgrade either which I find very odd. We really need some phone mastermind to unlock the secrets of the AT&T LG V10 H900. I'm unable to get it into download mode or unlock the boot loader either.
Thanks,
Silver

professorpoptart said:
T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?
Click to expand...
Click to collapse
Hmmm that's wiered because mine has stayed checked since I got the phone,although I don't t think it matters since it isn't unlocked. What's funny is i don't know why you can check it if bootloader is locked, I'm still lost on that one .

kotafoxx said:
Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out
Click to expand...
Click to collapse
This has been asked and answered here

How to get into stock recovery
1) Enable USB dubugging
2) Plug phone into computer
3) Set USB connection type to MTP
-Now the "USB debugging connected" notification should appear.
4) Entering "sudo adb reboot recovery" into the terminal will reboot you into the stock recovery.
Note: Entering "sudo adb reboot bootloader" will only reboot your phone...
Using: at&t LG V10
Model Number: LG-H900
Android Version: 5.1.1
Build Number: LMY47V
Computer OS: Ubuntu 15.10

I was able to root an LG escape2 with this method. You can communicate and push files to your phone through the download mode without technically using adb. Any chance a method like this would work?
http://androidforums.com/threads/gui...2-2015.937446/

in case you are subscribed to this thread go here..... http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317/post65864734#post65864734

Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954

jiggajatt said:
Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954
Click to expand...
Click to collapse
Excuse me, what's flux?

manny18pr said:
Excuse me, what's flux?
Click to expand...
Click to collapse
http://techcrunch.com/2016/03/15/popular-blue-light-reducing-app-f-lux-arrives-on-android/