Related
I got home on Friday and my Transformer told me there was an update available and it would take about 10 minutes to install. I followed the instructions and the tablet just hung on the boot screen. I left it for an hour and nothing changed. The only way I could get things working again was to wipe all data and restore it to factory settings. I did this and then went to the update screen where it once again told me there was an update available.
I followed the instructions and the exact same thing happened, so I wiped it again and started from scratch.
Anyone have any ideas here?
TIA.
Well first off it's not a brick. A brick is where you cant even get into APX mode. Secondly were you seeing an android image with an exclamation point on the screen? Or what did the screen look like that it hung on?
Are your rooted with CWM recovery installed?
stuntdouble said:
Well first off it's not a brick. A brick is where you cant even get into APX mode. Secondly were you seeing an android image with an exclamation point on the screen? Or what did the screen look like that it hung on?
Click to expand...
Click to collapse
It's the standard Eee Pad boot screen - the one that appears when you turn on the pad. No Android image.
Sounds like you need to hunt out and remove the .zip file on your device for the update that seems to remain after a hard reset, using ADB and the usb cable to your pc.
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?
musicfreak said:
Till this morning my Infinity I was on CleanROM Inheritance 3.4.7 with TWRP 2.5.0.0 Recovery, this worked fine. However I wanted to switch to CROMi-Xenogenesis 4.4.1 so I flashed 10.6.1.14.4 WW Bootloader and TWRP 2.5, as said in the OP. Unfortunately after the flash my device is dead, maybee bricked? I can't power on my tablet, with power on - volume down I can't get into recovery anymore.
I can't remember exactly what I saw after the flash. There should be an blue bar but I can't remember I have seen it. I saw this bar before when I flashed another ROM. The tabled had enough battery power, 90 or 95%.
When I put the tablet to my laptop I saw the word APX under other devices. Windows and Windows update doenst't seem to have the drivers present, luckily i found modified Universal naked driver at this blog. So now I have APX, but no fastboot.
When I read this thread, there is not much hope for me. Or is there a way to boot in fastboot modus? Any suggestions?
Click to expand...
Click to collapse
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
I would figure the tablet is on somehow if APX is noticing it. Have you tried holding down the power button until it vibrates to force shut it down then hold the power and volume down to get back into the boot loader?
Just wanting to make sure because APX is useless unless you have you NVFLASH blobs.
Click to expand...
Click to collapse
I thought I couldn't make my Transformer to power down. I hold the power button till it vibrates as you suggests. When I press volume down - power button nothing happens, the screen remains blank...
Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.
musicfreak said:
Maybee Nvflash is an option for me?
If I read http://rootzwiki.com/topic/35086-gu...rs-guide-unbrickrecoverdowngradeupgrade-tf201 correctly you can flash Nvflash in APX mode.
Click to expand...
Click to collapse
For this procedure, you must have obtained a blob.bin file by installing the hacked bootloader while you were still on a 9.4.5.26 or older bootloader.
If you don't have this file, and you don't know your tablet's unique SBK (Secure Boot Key), which nobody outside Asus knows, then you can't use nvflash.
Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...
musicfreak said:
Ah, so Nvflash is no option...
I contacted Asus support today by mail. First they came with the option of reinstalling the operating system for about 75 euro. Is that realistic? Or is an motherboard swap necessary? In that case the cost are about 160 till 200 euro. Quit a lot of mony. Then Ebay seems a better alternative...
Click to expand...
Click to collapse
If you can't get into recovery and you're using the correct side of the volume rocker (left!) and it really, really doesn't react to holding the power button for eternity - then you're probably bricked
The question is why? And how?
This hardly ever happens on the CleanRoms...
Did you reboot into system after flashing the bootloader and before flashing CromiX?
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
I don't know what happened after I flashed the 10.6.1.14.4 WW Bootloader and TWRP 2.5 recovery. After a while the tablet didn't react anymore...
In a Dutch forum I get the suggestion to check Easyflasher (http://www.youtube.com/watch?v=BxNmK6uXfFE&list=PLudvvIZ2s2oHbCK2Gb8aZHIoPpABzwthA). But om http://forum.xda-developers.com/showthread.php?t=1688012 I read WARNING: IF YOU USE THIS ON YOUR TF201/TF300/TF700 YOU WILL BRICK IT so this will be of no use I think.
I wouldn't use this -- it has been reported earlier to brick.
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)
berndblb said:
The question is why? And how?
This hardly ever happens on the CleanRoms...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I strongly suspect the Recovery, I also had issues attempting to flash a later version of Clean
Rom. It took a day of flashing to get the tab back to health. Along the same lines I have also had issues flashing my T'bolt and also my DNA. For the time being I am refraining from changes on the tab and DNA.
I have used both CWM and TWRP
MartyHulskemper said:
Have you tried to get into the bootloader -- that's what Tylor rightfully suggested, but I find your reply ambiguous -- press and hold down the left volume button ("volume down") and while you do so, keep the power button pressed until you feel it vibrate. Release the power button, and when/if you see some icons, release the volume button.
Click to expand...
Click to collapse
I've done this, but I see no Icons.... For me it's hard to see if my tablet is on or off. But when I hold the power button for a long time it vibrates so I assume it's off then.
You're based in Amersfoort -- do you visit Utrecht with any regularity? (I live in Hoorn, but work shifts in the UMC Utrecht so might take a look at it for you.)
Click to expand...
Click to collapse
What a great offer! Sometimes I visit Utrecht, and the UMC so this would be nice. When I'm planning to visit Utrecht I will give you a sign.
OK, so I went over and despite musicfreak having good ideas along the way, we haven't been able to revive his 700, and I'm not feeling too optimistic it can be done. However, I don't want to pass up the opportunity for _that to show off his immense skill once more (feel the pressure? ) and help musicfreak out.
In short:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
- the procedure for reflashing stock doesn't work at all, obviously, because there was a custom recovery (TWRP) -- still, grasping every little straw, we tried -- everything -- but the screen stays black.
My own 700 is detected properly in fastboot mode, so it seems unlikely we have a cabling and/or USB port and/or OS error (tried both WinXP 32-bit and 7 64-bit).
After the usual hassle of getting the drivers in place -- musicfreak's saving the day of installing the patched drivers (I though the patch had gone mainline by now) -- we haven't been able to get any further.
Is there a command we can get to the device in APX mode to detect what is causing this?
Is this recoverable? RMA?
Thanks for the help and insights, guys and girls.
MartyHulskemper said:
- unit doesn't actually boot into the bootloader at all, apparently. Screen stays black, no white lettering anywhere. Not a single one. Dead as a dodo.
Click to expand...
Click to collapse
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
MartyHulskemper said:
- only APX mode is available, by booting with VOL_UP pressed-- nothing else works (screen is oof, so I cannot tell if anything else is loading; Windows detects only APX device connected). No fastboot.
Click to expand...
Click to collapse
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
MartyHulskemper said:
Is there a command we can get to the device in APX mode to detect what is causing this?
Click to expand...
Click to collapse
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.
_that said:
Dead/broken/missing bootloader (or broken eMMC), or dead screen.
If you tried to enable fastboot mode blindly and the PC didn't detect it, then we can rule out "dead screen".
The only way to do anything in APX mode is NVFlash. Without the SBK (aka "unobtainium") or the "wheelie" tool and the matching blob, that mode is useless, as far as I know.
Click to expand...
Click to collapse
Yup, the two options you call out here were in my head, too. I got over to musicfreaks' thinking that the bootloader was actually working, but it soon turned out to be dead. Since the only mode Windows can detect is APX and neither adb nor fastboot give any reaction or meaningful reply, I guess musicfreak's 700 is deceased.
@OP: given the fact that even our guru knows not how to save your 700, it comes down to either salvaging the parts and selling them on their own, or selling the broken unit and dock together subtracting the repair cost.
Anyone having specific ideas which is better? (I'd veer towards selling it in whole, which at least makes sure you're not going to get stuck with loose parts...)
Yes, there seems no hope for my TF700 anymore....
I also think that selling the whole set (tablet and dock) is the best choice.
Unfortunately looks like a brick to me. Without nvflash the only option is to send it off to Asus if you want it fixed. Otherwise sell it for parts (Screen, digitiser, case etc)
I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.
musicfreak said:
I will, ýesterday I've put my Infinity on sale, see this at on Tweakers.net (in Dutch). Anyone interested here?
One thing comes to my mind: why can't the SBK be generated? Can't it be extracted somehow from the processor?
@MartyHulskemper: Have we tried to flash the stock rom from MicroSD card? I'm not sure.
Click to expand...
Click to collapse
Nope. If it were unencrypted, we could've tackled it ages ago and use it to unlock the bootloader without ASUS knowing. I have no doubt that the processor serial number or some other identifier does figure into the process, but we do not know the rest of the algorithm used.
As to your specific question: there is no use in trying to flash anything from the microSD card since we couldn't get into the bootloader at all, and therefore have never even seen a recovery of whatever description or denomination.
As I said when I was at your place: I was udner the impression you at least had the bootloader and fastboot access. Although it's probably hard working even then, it would not be without hope. Not having a bootloader, and not having Nvflash at hand, well... I fear it is without hope.
It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.
musicfreak said:
It has been a while since I post the last update to this thread.
In short: I sent my tablet tot Asus, they charge me 310 euro. After an email discussion with them without notice they sent the tablet back to me. I asked the shop where I bought it for repair, and now I nead some information for my email to them.
All this goed wrong when I flashed CROMi-Xenogenesis 4.7.0. Is flashing this ROM more risky then flasting CleanROM Inheritance 3.4.7? If so, why?
I hope somebody can explain this to me.
Click to expand...
Click to collapse
No it is no more risky than flashing any ROM. Flashing a ROM is not very risky cos even if you brick you will be soft bricked and usually that is recoverable. Your issue may have been related to the bootloader and recovery flash. Did you interrupt it - it should have rebooted on its own after the blue bar went to full?
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.
Hi
I read this forum for a long time, but for this one I didn't find the answer and had to register to explain exactly mu problem and hopefully someone can help.
My TF300T runs android 4.2.1 official. I unlocked it with the official app from their support page. The problem is with the digitizer, which I replaced, but still doesn't work after sleep and that's how I ended up doing all this.
Anyway, long story short, my TF300T is stuck at ASUS logo (the first one, the white one). And I mean STUCK. I can't even get into bootloader. Power + vol down will get me to the asus logo again, no RCK/android/wipe screen for me. And of course, I cannot connect it to windows, it doesn't see it. Yes, I have everything installed, all drivers ok, I have sdk, adb, fastboot, all were working before this happened with the tablet.
Any help would be appreciated.
Thank you
Did You already tried this? If You can't get to fastboot this is almost hopeless case.
psyalot said:
Hi
I read this forum for a long time, but for this one I didn't find the answer and had to register to explain exactly mu problem and hopefully someone can help.
My TF300T runs android 4.2.1 official. I unlocked it with the official app from their support page. The problem is with the digitizer, which I replaced, but still doesn't work after sleep and that's how I ended up doing all this.
Anyway, long story short, my TF300T is stuck at ASUS logo (the first one, the white one). And I mean STUCK. I can't even get into bootloader. Power + vol down will get me to the asus logo again, no RCK/android/wipe screen for me. And of course, I cannot connect it to windows, it doesn't see it. Yes, I have everything installed, all drivers ok, I have sdk, adb, fastboot, all were working before this happened with the tablet.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
I have the same problem. But what I did is I flashed a recovery from inside the TWRP terminal command thing (big mistake BTW) and now it will just stay at that Asus logo forever.
A friend of mine is trying to fix it... so far he managed to see the tablet in windows (as unknown device, but still) and now he is trying with nvflash...
I will keep you up to date if something comes up.
psyalot said:
A friend of mine is trying to fix it... so far he managed to see the tablet in windows (as unknown device, but still) and now he is trying with nvflash...
I will keep you up to date if something comes up.
Click to expand...
Click to collapse
Don't you need the blobs for nvflash? I think they are device specific too
yes. everything nvflash related.