Related
Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.
So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!
It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.
well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.
DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.
okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.
Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.
DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?
Thanks for that important tidbit, solarnz. I'm going to file it away for future use.
OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!
Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk
I got my TF yesterday, I rooted today, and everything has been working marvelously.
That is, until I got ambitious. This is the fifth android device I've installed a custom ROM to, so I figured it would be smooth sailing. I did a nandroid backup in CWM, and then installed the newest version of Prime, which then refused to boot. Ever the optimist, I restore my backup. Which also won't boot. Then I get frustrated. Moving on, I try out Revolver, which then boots just fine. I download Revolver Parts, and it tells me there is an update (I installed 3.5.2), which I confirm for install. The tablet reboots, and never makes it into CWM..
Every time it boots, I get to the initial screen, that says Eee PC, Asus, and NVidia. after two or three seconds, it goes black, and starts again. If I tell it to enter recovery, it reboots and never gets to CWM. The only way I found to get it to boot is to hold volume down, and then NOT hit volume up to enter recovery, and cold boot android from there.
The tablet is still functioning, but without being able to get into recovery, I'm feeling paranoid about something happening that would need recovery to... recover from.
I wasn't able to find any answers after looking for most of the day; I thought perhaps NVflash would help (I can get into USB mode by holding volume up), but the download link isn't working. Does anyone have any suggestions, or have heard of anything like this before? Any answers at all would be appreciated, thanks in advance.
nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6
sert00 said:
nvflash and only nvflash...if the link is dead,try here..
btw nvflash links here in xda works well
linux
http://www.mediafire.com/?vyci8t4i5ayg2t1
windows
http://www.mediafire.com/?004a8n53arbc5o6
Click to expand...
Click to collapse
yea, this happen somtime, not sure why, especially with prime for me. use nvflash and push revolver 3.5.2 with cwm, busybox, and su. then make a nand and try and restore it.
you could always try holding low vol + pwr for 6 secs then let go of owr but still hold low vol untill promt tells you to hit high vol to load cwm. that should work as well....
Thanks for the replies, both of you. Nvflash fixed it, works like a charm now. I love this device
Hello Guys:-
I am hoping somebody can and is willing to help me?
Problem---My TF101 Will not boot in to recovery!
Symptoms---When I try to boot in to recovery with the volume + power button combo the small white writing comes up in the upper left hand corner, it writes that it is booting in to recover but does nothing at all just stays there motionless on the Asus load screen. The only way I can get out of this is by doing the volume + power button combo again but this time NOT pressing the volume up button and it gives me the opportunity to erase all data or cold boot back in the OS.
It's the same if I try to boot in to recovery from CWM or via any of the boot to recovery one click apps available in the play store.
I never had any problems until Megatron parts told me there was an update and would I like to install it? I clicked on 'Yes' The update never worked and MY MACHINE CRASHED, THUS GIVING ME THIS BIG PROBLEM ALSO!
I am running CM9.
Any thoughts or assistance would be much appreciated.
Thanks in hopeful advance
Dodge.
Try Thing O Doom PERI and see if yo ucan get a working recovery back on it.
http://forum.xda-developers.com/showthread.php?t=1681155
baseballfanz said:
Try Thing O Doom PERI and see if yo ucan get a working recovery back on it.
http://forum.xda-developers.com/showthread.php?t=1681155
Click to expand...
Click to collapse
Looking at it now but dont understand it yet. Thanks any way mate
What's not to understand
1) Download and extract PERI to it's own folder.
2) Plug in transformer.
3) Run the .bat file.
4) Follow it's instructions.
5) Root
6) ???
7) Profit!
Thing O Doom said:
What's not to understand
1) Download and extract PERI to it's own folder.
2) Plug in transformer.
3) Run the .bat file.
4) Follow it's instructions.
5) Root
6) ???
7) Profit!
Click to expand...
Click to collapse
Thanks. I worked it out, it was not difficult as you said.
Alas! It did not work. I have a crazy, crazy problem it seems.
If I use your system for some reason my pc just can NOT see my TF. BUT
If I try to boot to recovery with my already installed CWM, I just get stuck on the EeePad boot screen as before but now your system sees my tf and knows its there but still can not work because it says, although it sees it is there it is off line and thus can not communicate with it or push to it.
How crazy is that?
Should I just give up and keep using my breaking down CM9rc0 untill it dies for ever or do you think there may be a way?
Cheers fellas
Dene.
PS. I tried to do a factory reset. I clicked on 'Reset Tablet' then 'Erase Everything' but it just boots back to start up screen and sticks there again, I cold boot and everything is still there and nothing is deleted.
HTC Sync on my TF is greyed out and will not do anything either.
As you Americans say.........'This is way above my pay grade'lol
Thanks again
Hey guys! Been playing around with the transformer pad 300. unlocked it. rooted it. all while on 9.4.3.29. but then the update 9.4.3.30 came out so i installed the update. lost root. tried the same process to root via these links. could never get the recovery.img to load this time around. i uninstalled drivers and reinstalled drivers. always got stuck on "booting recovery kernel image". eventually i pissed it off. now when i try to go into fastboot mode, i dont get the 3 options "wipe date" "usb" "android cold-boot". all i get is booting recovery kernel image" and it sits there. if i dont hold down the volume down button during reboot. it sits on "the device is unlocked".
Is there an adb way to push files and get this puppy running again?
h*t*t*p://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
h*t*t*p://theunlockr.com/2012/05/25/how-to-root-asus-transformer-tf300t/
Please help!
Exactly what happened?
-i tried to install CWM on 9.4.3.30 from link above.
-it showed successful in cmd window on pc
-tried to boot into recovery, that sat there on "booting recovery kernel image". sat there for at least 20 minutes.
-held pwr button to reboot. it did and tablet started up fine.
-reboot with vol+dwn to go into fastboot. choose usb for fastboot.
-fastboot recovery img, which failed with error "Too many links".
-rebooted tab normal just fine.
-turned off tablet.
-tried fastboot erase recovery
-sat on "waiting for devices"
-rebooted just fine.
-checked drivers, all installed just fine. uninstalled, reinstalled to be sure. no problem.
-went through attempt to install twrp.blob. was successful on pc.
-but got stuck on booting recovery kernel image again.
-reboot normal just fine.
-decided to pwr + vol dwn, then choose wipe data.
-gave normal "data wipe complete". then boot recovery kernel image message i keep getting stuck on.
-stayed there for hours.
-finally i pressed and held power to attempt normal reboot. and get stuck on ASUS screen with "device unlocked" message.
-try pwr + vol dwn and get stuck on
"the device is unlocked."
"android cardhu-user bootloader <2.10 e> released by 'us_epad-9.4.3.30-20120604' A03"
"Checking for android ota recovery"
"Booting recovery kernel image"
-cannot adb devices at this point or fastboot devices at this point
HELP!?
http://forum.xda-developers.com/showthread.php?t=1680570
Try this thread.
MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Try this thread.
Click to expand...
Click to collapse
Thanks. i reviewed the whole thread. tried the external SD card idea with firmware update and with recovery.img just for kicks even though it didnt suggest it. no dice on either.
what os u using? I saw a few thread about booting into unbuntu off a live cd and being able to push to the sd card
paedz718 said:
what os u using? I saw a few thread about booting into unbuntu off a live cd and being able to push to the sd card
Click to expand...
Click to collapse
it's running 4.0.3 Asus build firmware 9.4.3.30. unlocked but not rooter (anymore). Could you sahre link to steps about the ubuntu and CD idea you have?
baldypal said:
it's running 4.0.3 Asus build firmware 9.4.3.30. unlocked but not rooter (anymore). Could you sahre link to steps about the ubuntu and CD idea you have?
Click to expand...
Click to collapse
here's the link to the posts that i saw about using Ubuntu. not sure its applicable to your situation, but hey give it a whirl as a last resort
http://forum.xda-developers.com/showpost.php?p=28407803&postcount=253
http://forum.xda-developers.com/showpost.php?p=28477279&postcount=204
Hey I wrote a tutorial for this, it happened to me and its real easy to fix! hope this helps FIX
Seems to me that something went wrong while flashing CWM or maybe you flashed a CWM that is for the Prime.
Had something similar going on with my Pad: This video helped:
http://www.youtube.com/watch?v=Iy-Sbq4JmdQ&feature=player_embedded
If you can´t get ADB to work, try this unbrick tool:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
Just execute the bat in there. Than choose option 5 for ADB shell.
Then use this comand:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
If it runs through this command:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
Then turn off your Pad. Now you should be able with - and Power to get to the screen were you can change to fastboot and then you can fastboot your Recovery again. Try to download it from here for CWM:
http://forum.xda-developers.com/showthread.php?t=1668173
or from here for twrp:
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps. Got mine unbricked like this.
d_crossfader said:
Hey I wrote a tutorial for this, it happened to me and its real easy to fix! hope this helps FIX
Click to expand...
Click to collapse
Thanks! but in my situation i cannot get into ClockworkMod. Also, i can't get into fastboot either. Screen is stuck on first screen with message "Booting recovery kernel image" but just sits there until the battery dies.
mikaole said:
If you can´t get ADB to work, try this unbrick tool:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
Just execute the bat in there. Than choose option 5 for ADB shell.
Then use this comand:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
If it runs through this command:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
Then turn off your Pad. Now you should be able with - and Power to get to the screen were you can change to fastboot and then you can fastboot your Recovery again. Try to download it from here for CWM:
http://forum.xda-developers.com/showthread.php?t=1668173
or from here for twrp:
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps. Got mine unbricked like this.
Click to expand...
Click to collapse
This looks to be the most promising so far. i'll give it w whirl when i get the tablet back.
I sent it to ASUS on Friday to see what their charge is going to be to fix it for me.
Well well well!
Got a notification back from ASUS today that they are sending my tablet back to me fixed and good as new. Funny thing is, they never charged me for any work? Unlocked bootloader tablet fixed under warranty? How often does that happen?
baldypal said:
This looks to be the most promising so far. i'll give it w whirl when i get the tablet back.
I sent it to ASUS on Friday to see what their charge is going to be to fix it for me.
Click to expand...
Click to collapse
baldypal, how did you send it to them it turns out, that same thing happened to me, and I think I would have to send it to Asus Also
osiris5180 said:
baldypal, how did you send it to them it turns out, that same thing happened to me, and I think I would have to send it to Asus Also
Click to expand...
Click to collapse
I called them to get tech support over phone. they couldn't assist. I asked if they could RMA it for fix (even though unlocked). They did. I just got lucky and they didn't charge me even though they should have since i unlocked it. WARNING: when i got it back, it was locked again.
I had some probs with mine as well and it seems asus just put up that legalese for its legal dept. I've talked to a guy there wheni asked for my pad and they basically repair all atm. Dunno if that will continue when their new line is out but so far they don't care much and focus on repairing their flagship and making their customers happy.
Cheers
Sent from my A700 using xda app-developers app
baldypal said:
I called them to get tech support over phone. they couldn't assist. I asked if they could RMA it for fix (even though unlocked). They did. I just got lucky and they didn't charge me even though they should have since i unlocked it. WARNING: when i got it back, it was locked again.
Click to expand...
Click to collapse
Guys I think I'm on the same boat as you now... did you have any progress on this?
JohnerH said:
Guys I think I'm on the same boat as you now... did you have any progress on this?
Click to expand...
Click to collapse
The process you quoted in your reply got my tablet fixed and returned but locked. i wasn't out any money, just about 1 weeks time without a tablet.
Hello,
I loaded the wrong version of TWRP on my TF300T. When it rebooted it loaded CM10.1 just fine. I then rebooted a second time in recovery mode and I have been stuck at the ASUS screen with the "device is unlocked" message. I am able to get into APX mode but my research has shown that mode doesn't do me any good if I haven't ran a nvflash backup. I am stuck and I would appreciate some advice or suggestions. I wonder what the factory reset fee would be from ASUS.
Thank you for your responses!
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
macgyver40 said:
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Thanks for the speedy response =)
Version History: Stock 4.1 -> CM 10.1 Nightly 0503 or 0429. I had CWM on it before trying to load openrecovery-twrp-2.5.0.0-tf300t-ICS.blob using the terminal emulator method. I think I should have loaded the JB blob but the warning on the TWRP site said to use that if you ran the offical OTA update, which I never did so I stuck with the ICS. It installed fine, then rebooted into CM 10.1 just fine. I then rebooted from there into recovery and have been stuck at the ASUS screen since.
The Vol + - button keeps me in the ASUS screen. Reset button keeps me in the asus screen. Vol + + puts me in APX mode.
I try running fastboot in APX mode but it hangs stating "waiting for device" so I don't think it'll work in APX mode.
Thanks.
T
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
c0ded said:
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
Click to expand...
Click to collapse
I bled it last night. I'll try booting it this evening. Thanks!
racet said:
I bled it last night. I'll try booting it this evening. Thanks!
Click to expand...
Click to collapse
No luck. I bled it twice and I'm still stuck at the ASUS logo with "the device is unlocked"
Am I looking at repair here?
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of eBay and replace it with the one in your tablet. Also, to save other people's tablets from bricks, you may want to look into this petition.
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
c0ded said:
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of
Wow 200$ what a load. To what degree of difficulty are we talking with replacing the mobo? Ifixit makes it look doable, yet at the end he messed up his LCD screen.
Click to expand...
Click to collapse
macgyver40 said:
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I would def like to try it if you can find it.
T
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
http://forum.xda-developers.com/showthread.php?t=2041528
found it. Hope this helps you like it helped me out of my broken recovery. once you download and add the files you want its pretty easy. the script in english makes it pretty easy to understand what your doing and hope it works since I know my TWRP was broken I couldn't even sit at the recover,android wipe screen for more then 3 mins without it bootlooping. I put it on that screen while connected to laptop ran the recovery flash and all went well installing TWRP 2.5 which I then recovered my backup and that even restored my 2.4.4 patch TWRP like nothing happened at all. tablet runs great and have made 3 backups that work after all this.
Good luck
macgyver40 said:
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Please take your time. I have no problem waiting especially if the only solution is to drop 75$ on a replacement mobo.
You could send me the file via email or drop box if it's easier. I was going to use the TWRP 2.5 JB with CM 10.1 nightly. I appreciate all the help!
T
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
macgyver40 said:
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I tried running through your tread but none of the commands worked on the script. Probably because I can't get fastboot to work. When it tries to load a recovery it just states: "waiting for device" and sits there. =/
c0ded said:
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I am unable to get fastboot to recognize the device. The only way the PC recognizes it is via APX mode. Download mode just sits there at the ASUS screen and windows doesn't see any devices.
Still no love. Am I bleeding out the battery correctly? I am just running the boot screen until it dies then I try to power it on again.
I popped the back open today to see how difficult it would be to replace the mobo, doesn't look too bad. Just having difficulty finding a good online guide.
Also, just so I have the terminology straight, when the tf300t goes into a "boot loop" does it ever leave the asus screen and go black or does it just hang? Mine never goes black, just sits at the ASUS screen with "the device is unlocked" message. The only time I can get it to leave this screen is when I do a reboot and hold the + sign. then it goes black and APX is detected on windows.
Just wasn't sure if any of that information was useful.
T
One other solution is to unplug the battery for 30 minutes, then plug it back in.
c0ded said:
One other solution is to unplug the battery for 30 minutes, then plug it back in.
Click to expand...
Click to collapse
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
racet said:
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
Click to expand...
Click to collapse
Usually, the volume button does not fail. Remember the volume button connects to, but is NOT part of the mother board. If it feels stuck when you push it, that's because you snapped the back cover in wrong. You need to slide it in at the corner where the buttons (volume & power) are, then pop in the rest of it. Take it out and do it again.