Related
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]
nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!
same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).
This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
only thing I can guess if you still have the stock Recovery is trying the reset button on the left side under the external sd slot. But this can make it worth.
What exactly to do with reset button ?
Sent from my Nexus 4 using xda app-developers app
petition
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
rhc94 said:
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
Click to expand...
Click to collapse
How did you take a blob.bin????
atoma1972 said:
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
Click to expand...
Click to collapse
yeah m8 same as me from 2 days now your soft briked and nothing else to do but w8t or send it to asus and be charged for the repair.
Sign the petition and maybe wer in luck some day not to far.....
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
from the loop,If you hold the power button for 10s when reboot and immediatly press the volume down button, what you have asus loop or the screen with the 3 icons (RCK ecc) ?
Claudisimo said:
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
Click to expand...
Click to collapse
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Sadly, the tablet came with Android 4.1.x :S
atoma1972 said:
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
Click to expand...
Click to collapse
Use of the bootloader information may allow access to recovery, adb, or fastboot. Access to any of the three may allow the ability to recover your tablet.
None of the ways worked for me.... can't access that menu...
Claudisimo said:
None of the ways worked for me.... can't access that menu...
Click to expand...
Click to collapse
If you still have no adb, fastboot, or recovery I don't know how to help.
Same situation
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Mynzer said:
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Click to expand...
Click to collapse
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
It Work
tobdaryl said:
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
Click to expand...
Click to collapse
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Great! I'm glad I could help.
help...
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Fullpoweradonf said:
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Click to expand...
Click to collapse
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Would be nice if you could use someone else's file to fix a brick. Has anyone tried it.
Mynzer said:
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Click to expand...
Click to collapse
Could You explain step by step which driver and how do you get up Yours TF300T?
I have the same problem, only recovery starts (TWRP2.5.0.0)
possible brick?...
After downgrade the console from the v. 4.2 to 4.1, following tutorials in this forum, because it would not let me install a Custom Rom (yes the recovery, not the root) I can think of to make a choice Wipe from the Stock 4.1 Recovery and restart WW I stand still Asus logo, white, and trying to restart pushing Recovery again, I go and I follow the fixed logo. I do not recognize the device SDK and have seen many posts and I can not find the solution ... buf! Someone has been the same? ... The strange thing is that lights ...
In case nothing else works (another fix) worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, don't forget to hit thanks button if it works =)
i have an odd question
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
racerocm said:
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
Click to expand...
Click to collapse
If you cannot access to fastboot, IMHO there's nothing you can do. I am in your same boat: no adb and fastboot access, my PC recognize the tablet only in APX mode but with NVflash I cannot do anything because I not have a backup.
Bye
EDIT: I am in this situation after a wrong recovery flash. I flashed a new recovery but I could not load it and I made the (big) mistake to try a wipe from the recovery menu. My Tf300t is now stuck at asus logo and I cannot access to the bootloader anymore. I do not know what to do, is the tablet definitely bricked or there's something I can try before going to ASUS service?
Thanks in advance.
Bye
Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.
vexille said:
Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.
Click to expand...
Click to collapse
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822
LetMeKnow said:
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822
Click to expand...
Click to collapse
Tried those - didn't work.
vexille said:
Tried those - didn't work.
Click to expand...
Click to collapse
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...
I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it
LetMeKnow said:
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...
Click to expand...
Click to collapse
Win 7 64.
Device originally detected as APX but with yellow !. Then Windows installed it as "unknown device".
Uninstalled that from Device Manager and rebooted. Connected tablet and get "unknown device" again.
When I try to update driver to those in link it says "best driver already installed"
Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked
vexille said:
Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked
Click to expand...
Click to collapse
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
sbdags said:
I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it
Click to expand...
Click to collapse
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:
LetMeKnow said:
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:
Click to expand...
Click to collapse
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.
vexille said:
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.
Click to expand...
Click to collapse
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...
LetMeKnow said:
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...
Click to expand...
Click to collapse
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Oh well, you can not boot into your bootloader and can not get adb running. I hope that someone or experts can jump in and give you some good advices... Maybe, _that, sbdags, lj50036, and berndblb are actively helping users around here... good luck...:fingers-crossed:
vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.
vexille said:
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.
Click to expand...
Click to collapse
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them
berndblb said:
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them
Click to expand...
Click to collapse
Well struck out on all accounts (I had left it plugged in at the Asus logo last night).
Appreciate all the help but I think it's eBay time for whatever I can get and sell the mobile dock and fancy leather case.
Then to decide what brand to get next....
berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
I've tried every suggestion and cannot get past the "device is unlocked" mice type and static Asus logo.
When using adb it doesn't find any devices. I'll be putting it up eBay tomorrow for whatever I can get.
Looking at the new Samsung Galaxy 8.4 Pro as a replacement.
LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL
berndblb said:
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL
Click to expand...
Click to collapse
I hope that you had a great time with your family... I am still looking and have not decide it yet.. I always backup my stuff before messing with the device. Plus, my nephew has a few hour of playing on the tablet per day any way.. So I can take it any time that I want, hehe....:laugh: I also have a higher authority as an uncle...:silly:
Hi there,
a friend of mine, gave me this tablet because was bricked. Now i have tried the famous easyflasher with his "flash default stock" ability.
I have already installed the naked driver on my pc, and the tablet in apx mode is correctly recognized by windows.
Via easyflasher i have already started the flashing of the recovery "RogueXM Touch v1.5.0-R1" and now i'm going to flash the stock rom.
All goes pretty well, but at this time the process is stucked on the screen:
"""""
Nvflash started
[resume mode]
"""""
The tablet is still recognized by windows (i can find them on hardware connected).
So the question is: it's normal that the Nvflash take long time, and don't give me any output on his work? Nor if it's going to do something?
Let me know.
Thank you...
costal said:
Hi there,
a friend of mine, gave me this tablet because was bricked. Now i have tried the famous easyflasher with his "flash default stock" ability.
I have already installed the naked driver on my pc, and the tablet in apx mode is correctly recognized by windows.
Via easyflasher i have already started the flashing of the recovery "RogueXM Touch v1.5.0-R1" and now i'm going to flash the stock rom.
All goes pretty well, but at this time the process is stucked on the screen:
"""""
Nvflash started
[resume mode]
"""""
The tablet is still recognized by windows (i can find them on hardware connected).
So the question is: it's normal that the Nvflash take long time, and don't give me any output on his work? Nor if it's going to do something?
Let me know.
Thank you...
Click to expand...
Click to collapse
sorry i have found that i have wrote this post on the wrong place. You can remove him. Thank you and sorry for the mistake.