Hi,
After a complete factory reset my kids tf300t starts automatically installing applications like 'adult browser', 'hot videos', ... even before I was able to select my language and connect to my wifi during the installation wizard. The device is also extremely slow and many windows are popping up all the time.
It is still the original stock ROM, the boot loader was not unlocked.
Now I'm trying to overwrite the (infected?) stock rom. I'm able to put the device in fast boot mode (I see a status line that fast boot is enabled after pressing vol-up + per) but when I connect it to my PC 'fastboot devices' doesn't list the device. I tried with another device to check my fast boot installation and that works fine.
After a long time I was able to enable debugging mode (i saw a popup 'usb debugging mode enabled') adb was neither able to connect.
I even tried another cable.
Anyone any suggestion how to recover my device?
XDA Visitor said:
Hi,
After a complete factory reset my kids tf300t starts automatically installing applications like 'adult browser', 'hot videos', ... even before I was able to select my language and connect to my wifi during the installation wizard. The device is also extremely slow and many windows are popping up all the time.
It is still the original stock ROM, the boot loader was not unlocked.
Now I'm trying to overwrite the (infected?) stock rom. I'm able to put the device in fast boot mode (I see a status line that fast boot is enabled after pressing vol-up + per) but when I connect it to my PC 'fastboot devices' doesn't list the device. I tried with another device to check my fast boot installation and that works fine.
After a long time I was able to enable debugging mode (i saw a popup 'usb debugging mode enabled') adb was neither able to connect.
I even tried another cable.
Anyone any suggestion how to recover my device?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. First, please have a look at your device's homepage here:
Asus Transformer TF300T
If you create an account with XDA, you can ask the experts in the Q&A forum located there.
Good luck and welcome to XDA!
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, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter
pepond said:
Hi, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter
Click to expand...
Click to collapse
Are you rooted with custom recovery or stock? After soft reset when the "M" first appears count to three and press the volume down button, hopefully you will see "android recovery". If you do press the volume up button to enter recovery and you could do a system restore from it. I'm thinking maybe you didn't have "usb debugging" turned on in developer settings, does it show a pop up on your computer when you plug in the xoom where you can browse it's file contents? If so save any photos or important docs and do a system restore like I explained earlier.
Same woes here
solved
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
thepenrosesteps said:
Hey everyone. I couldn't find an answer to this that I could follow and that worked for me as I'm not very technically inclined.
My HTC One X recently died after having a low battery and now whenever I try to turn it on (even when it is fully charged), it gets to the lock screen, but I can only access everything for about 5 seconds before it restarts again. I know I have USB debugging enabled, and I can get to the screen that shows up when I hold down the power button and the volume-down button.
What I want to do, before doing a factory reset and praying that ends the bootloop, is recover my photos which I stupidly did not back up anywhere. I can connect my phone to my laptop, which runs on Windows 8, but it is not recognized as it normally would be (ie: I can't access files directly). I've gotten to the point where I can see "FASTBOOT USB" on my phone when it is connected and I've restarted my PC so that it is able to identify it in the Device Manager. I have also gone through the steps of downloading a universal naked driver and choosing the driver under the Device Manager, so when I use a command prompt my phone shows up in fastboot devices. (I used minimal fastboot and ADB)
But what can I do now? I have never tampered with my phone, so it is locked or unrooted. I'd like to keep it that way if possible, but I'm having a hard time understanding how I can retrieve my photos. Should I use ADB commands, and if so, how do I get to the point where my PC recognizes my phone under ADB devices? Or is there a better way? I'm also not very familiar with custom roms, TWRP, CWM, etc.
I'd appreciate a brief walk-through if possible as, like I said, I don't normally do this sort of thing. Thank you!
Click to expand...
Click to collapse
Try Power the Device Up in Safe Mode - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
sd_shadow said:
Try Power the Device Up in Safe Mode[/URL] - HTC One®
Do you know the model number? Is it the AT&T or Rogers? s720e, G23, 720, 325...
Click to expand...
Click to collapse
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
thepenrosesteps said:
I tried going into safe mode and nothing changed! It didn't break the bootloop, so I guess it isn't an app that's causing the problem. It's with Rogers, but I don't know the model number... I got it in North America if that helps.
Click to expand...
Click to collapse
It's likely a s720e then, but
I will request that this thread be moved to AT&T One X Q&A, Help & Troubleshooting
Where you should be able to find out for sure.
Next step is likely flashing a custom recovery like TWRP or CWM then you could, mount sd card/storage and copy photos.
see AT&T One X Q&A, Help & Troubleshooting Frequently Asked Questions by Heisenberg
[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 5/8/14) by redpoint73
I have a Cherry Mobile Flare Lite which is unlisted on this site, unfortunately, that I tried unrooting because of reasons. After the unroot which I thought was successful, I reset my phone. When it turned on again, it showed me a screen that says "oot access is missing. Root devic" and below it "THIS CANNOT BE UNDONE." with two options right below that. One says "No" and the other "Yes - Root device (/system..." It happened a few days after the unroot and I can actually choose "no" without any problems and the phone would start up normally. But now it won't let me even choose, it's like it freezes the moment it shows the stuff said above and keeps resetting and resetting. I keep tapping on the options, pushing the volume buttons and power buttons but no response. It just freezes and resets. What did I do and what can I do to fix it?
Hello,
Welcome to XDA.
Can you boot to recovery or to download/fastboot mode or whatever flash mode your device has? Can you connect the device to adb?
Be prepared to use the tools I mentioned, get adb installed and set up on your PC, make sure you have your drivers installed on PC to connect your device, search for the flashtool that your device uses and install it if you don't already have it.
Have you tried rooting the device the way you did the first time?
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help.
Register an XDA account to post and reply in the forums. Good luck.