I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Not that its much help but if you are bricked like I was, it was quite easy to replace the main board with a used one from Ebay.
No chance you had NV Flash snapshots?
Good luck with it,
Feend
In all honesty it simply sounded at first to be a permissions issue for SystemUI.apk.
But if you can get to fastboot I would try Reformatting your system partition and flashing another ROM. Then factory reset your data partition.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
sbdags said:
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Click to expand...
Click to collapse
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow. Thanks a lot for posting this information. I had no idea. Would using the factory reset within CWM or in the settings be dangerous?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
So doing this completely hard bricks the device? meaning NO bootloader? It almost seems like the bootloader factory reset is touching the block that holds the recovery. Isnt there source code for this bootloader? Couldnt this be solved?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow i am very glad i stumbled across this.. there should be a sticky about this or something!! Thanks for the very helpful post
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have to agree, I'm REALLY glad I came across this. I'd noted that in a few of the "My tablet is bricked" threads that people had bricked after accidentally clicking something in the bootloader screen and had vowed not to touch anything in the original bootloader.
Thanks for the heads up on this.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Game over
sbdags said:
Game over
Click to expand...
Click to collapse
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
sbdags said:
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
Click to expand...
Click to collapse
That's a bummer for them but good to know nvflash can fix it. and f*** Asus for locking the jb boot loader to prevent nvflash... Maybe this is a stupid comment but I think they would sell more devices if they didn't do stuff like this... I know when I look into purchasing a device I come here first to make sure there is android development and unbricking procedures. ( I saw nvflash for tf300t and that's pretty much the reason I picked that tablet). Its a bummer that companies like Asus are much more concerned with making money by repairing bricked devices. (Although I do love Asus hardware. I own a tf300t and a nexus 7...its a love hate thing... Damn you Asus)
Sent from my Nexus 7 using xda app-developers app
D.MADROX said:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
Click to expand...
Click to collapse
I have worked with six or seven who used the wipe data on the bootloader; two recovered.
If you have any chance to recover you have to work at it. First apx mode is useless unless you previously flashed Nvflash.
We need adb, fastboot, or recovery working. Here is a thread for your use to get control of your tablet.
You mention rebooting into recovery. Stock, cwm, or twrp?
As you progress through this list the tablets have a way of evolving. This can happen even if you haven't gotten anything to function as you wish. That means you have to do them again; three times may be the charm.
I would like very much to know about your mention of recovery. Can you still get into recovery and which?
How about a current update before you begin using that link.
Related
I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.
Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk
It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App
Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App
Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2
That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.
I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.
No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.
dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?
Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.
Hello everybody. Bought slider101 us... 8.6.5.18 Successfully rooted with Razorclaw. Superuser installed.
Didnt have a chance to flash CWR.
Tried to update through asus notification that i got on my tablet. At the end of update it said something like "failure to update",but it changed to 8.6.5.21 on my tablet. After that tried to install recovery through" recovery installer", couldnt do it. I guess I lost my root on my tablet because of that update and Razorclaw doesnt work with .21 I did try to fix it through ADB commands which led my tablet to non stop rebooting. Cant load a screen after ASUS logo. It keeps rebooting.
The last try was this Nvflash "Unbricking and forever root" but when I hit download batch file it disconnects me from computer and looks like APX is disapearing on Device Manager place.
Cant load to recovery cause didnt install it. Tried to find sollution ,no luck so far. im not sure if its bricked. Thanks for any help in advance.
Update: problem fixed-- somehow could get into the screen where i could wipe data, I think it was system kind of recovery. And then installed nachoroot, cwm recovery, android revolution super wipe and ROM. Works perfect!
I belive you're not supposed to update when rooted.
Sent from my PG86100 using xda app-developers app
There are a few NVflash methods to unbrick devices here. You should read them all in general thread and development thread and see which one suit your slider101. And when you find one, please try different PC to do it. Some PC just act strange but some would give you profit..
farsight73 said:
There are a few NVflash methods to unbrick devices here. You should read them all in general thread and development thread and see which one suit your slider101. And when you find one, please try different PC to do it. Some PC just act strange but some would give you profit..
Click to expand...
Click to collapse
Thank u! Problem fixed. Somehow could get into wipe.data screen and that fixed the problem. Could load to normal screen.
root0660 said:
Thank u! Problem fixed. Somehow could get into wipe.data screen and that fixed the problem. Could load to normal screen.
Click to expand...
Click to collapse
Just for future reference, what steps did you take to fix it? It was my understanding that nvflash does not work for the Slider at all.
Solar.Plexus said:
Just for future reference, what steps did you take to fix it? It was my understanding that nvflash does not work for the Slider at all.
Click to expand...
Click to collapse
I think it wasnt really bricked, it just couldnt load main desktop screen. Its stucked on ASUS logo.I managed to get into system recovery screen where u can see "wipe data" and i think an image of droid man. So by pushing volume down and turning it on u can see that screen, and u need to point onto "wipe data" little green square by pushing volume up right after Ive read something like "cold boot" written with small white letters. And then it started to wipe all data. After that it could boot to the main desktop screen. From there I rooted with nachoroot since I have 8.65.21. Razorclaw can root up to I think .19.
hi guys my tf300 is bricked after flashing 4.1 B update from 4.0 , still on bootlog , i tried to restore a bakcup or install again the R1 rom but still on bootlog what can i do now ? i only can go in recovery CWM :crying:
your tablet is NOT Bricked, bricked means something different than your state. You can even access fastboot.....
Blubberor said:
your tablet is NOT Bricked, bricked means something different than your state. You can even access fastboot.....
Click to expand...
Click to collapse
ok , but what i must do now ?
I had the same issue( and so have others) but all have been able to be fixed one way or another. So no panicing, :fingers-crossed:you'll get your baby back in working order just going to take some reading. Get a cup of coffee, take a deep breath and read you'll find your answer. In my case I had flashed with CWM recovery, turnes out that almost always ends up being stuck at bootlogo . If you Power off with a long press on the power button then hold volume down and power button you'll get the bootloader menu, volume up on the RCK and you'll be back in recovery. For me I just had to fastboot connected to my computer and push TWRP then boot to that, then flashed, rooted version of Stock 4.1 (found else where in this forum) let it boot once, then when back into TWRP and flashed Hydro, let it boot up the first time, then the Update for Hydro 4.1. Now all is good. Your story might be different but you'll find it if you read.
Exact problem I had. Its cwm messing everything up. Flash team win from fastboot and everything will be OK.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Your definitely in the right place, and I agree that a little light reading will inlighten your path
Good luck on your quest
Sent from my ASUS Transformer Pad TF300T using xda premium
Hi,
I recently installed a deodexed Stock Rom, and I'm pretty sure I used CWM to do so. (I haven't touched this tablet in about a month). Today, I was in the process of doing a factory reset, through the actual OS Settings, and now it's stuck on boot. It gets past the ASUS start screen, and gets to the screen with the Green Android robot, with the Blue spinning cog thing, like when you do an update or wipe.... but it will not go past this screen. If I hold power and left volume, it just goes back to this same screen. Vol+Right, brings up APX on Windows when connected with USB, but I don't have any saved blobs. What are my options at this point? Is this truly bricked?
Any help would be greatly appreciated.
Maybe you just need to wait longer.
_that said:
Maybe you just need to wait longer.
Click to expand...
Click to collapse
My guess would have been he's stuck in the dreaded boot-to-recovery-loop after wiping from system instead of recovery...
Now that cryptic statement makes me curious! Could you elaborate on that, @_that?
berndblb said:
My guess would have been he's stuck in the dreaded boot-to-recovery-loop after wiping from system instead of recovery...
Now that cryptic statement makes me curious! Could you elaborate on that, @_that?
Click to expand...
Click to collapse
In another thread someone said he could get out of that wipe screen simply by waiting long enough for it to finish.
berndblb said:
My guess would have been he's stuck in the dreaded boot-to-recovery-loop after wiping from system instead of recovery...
@_that?
Click to expand...
Click to collapse
I think I might be stuck in this as well, is there any way to get out of it? I am able to do an ADB SHELL but I have no idea what to do next, ADB REBOOT BOOTLOADER does not work...
Thanks!
blaxer said:
I think I might be stuck in this as well, is there any way to get out of it? I am able to do an ADB SHELL but I have no idea what to do next, ADB REBOOT BOOTLOADER does not work...
Thanks!
Click to expand...
Click to collapse
Try fastboot reboot bootloader
sbdags said:
Try fastboot reboot bootloader
Click to expand...
Click to collapse
Doesn't sound as if he can get into the bootloader for fastboot.
_that seems to have it right (as usual).
Just read about someone who factory reset from settings with CWM installed and couldn't get out of recovery.
He solved it by letting it do it's thing "for hours".
berndblb said:
Doesn't sound as if he can get into the bootloader for fastboot.
_that seems to have it right (as usual).
Just read about someone who factory reset from settings with CWM installed and couldn't get out of recovery.
He solved it by letting it do it's thing "for hours".
Click to expand...
Click to collapse
I came here after searching "Android spinning cog TF300T" (and a lot of shouting at my tablet).
I have CWM installed and stupidly wiped from system instead of the bootloader (I have CM10 installed).
I got all p**sed off with my tablet after the spinning comatose Android r2d2 so I chucked the tablet on the seat of my van and went for a coffee. I read this while enjoying an americano at Cafe Ladro - I came back to my van and the tablet has restarted. It took about two hours of just "leaving the damn thing alone" for it to work.
As a side note - thank you to xda-developers for this and tonnes of other resources I've used. You guys make me, my Asus TF300T, and my multiple HTC Vision / Desire Z / G2 devices happy! :good:
hibernian said:
I came here after searching "Android spinning cog TF300T" (and a lot of shouting at my tablet).
I have CWM installed and stupidly wiped from system instead of the bootloader (I have CM10 installed).
I got all p**sed off with my tablet after the spinning comatose Android r2d2 so I chucked the tablet on the seat of my van and went for a coffee. I read this while enjoying an americano at Cafe Ladro - I came back to my van and the tablet has restarted. It took about two hours of just "leaving the damn thing alone" for it to work.
As a side note - thank you to xda-developers for this and tonnes of other resources I've used. You guys make me, my Asus TF300T, and my multiple HTC Vision / Desire Z / G2 devices happy! :good:
Click to expand...
Click to collapse
Great that you got your tablet back, but just for the record: Wiping from the bootloader would have had the same effect as wiping from Settings! [emoji12]
Use your RECOVERY and only your recovery once it is a custom one.....
Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977
burner1977 said:
Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977
Click to expand...
Click to collapse
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.
cmendonc2 said:
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.
Click to expand...
Click to collapse
thank you for your response. No I can't get in there. any suggestions?
thx for your advise
burner1977 said:
thank you for your response. No I can't get in there. any suggestions?
thx for your advise
Click to expand...
Click to collapse
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.
cmendonc2 said:
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.
Click to expand...
Click to collapse
I stupidly made no backups so what you are saying is that it is done.
burner1977 said:
I stupidly made no backups so what you are saying is that it is done.
Click to expand...
Click to collapse
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing
coppervines said:
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing
Click to expand...
Click to collapse
I'm on the same boat, this morning I was trying to install CyanogenMod following the instructions and wipped the tablet... I only have APX connection now with no backups...