Database Info

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

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

TF101 in boot loop

Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move

This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.

TomTcom said:
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
Click to expand...
Click to collapse
The ICS to JB isn't the issue as the issue started happening randomly with a ICS Rom that has been working for 4+ months when it has never had anything put ICS (well HC when I got it last year). Trying the JB rom was a near last ditch effort
I tried Revolutions superwipe several times, didn't help.
I probably completely screwed it up now in frustration. Tried to load the stock rom and now Recovery is screwed and it is boot loop so I don't think I can connect it to the computer now.
Hosed you think?

So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.

Firehawkns said:
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Click to expand...
Click to collapse
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop

Firehawkns said:
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
Click to expand...
Click to collapse
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium

morphuex said:
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Click to expand...
Click to collapse
Yea, I can do the power + vol down and then up and get the recovery android guy, then he goes on his back and a red exclamation comes up (which I believe means no recovery mode installed
I can also do the pwr + vol down and then wait 5 seconds and get the wipe device or android options, but it won't let me choose anything, 10 seconds later it reboots.
clouse2013 said:
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Will try tonight, but I believe all of those involve the computer having time to recognize the device, which it doesn't stay on long enough for the computer to recognize is and it won't seem to connect USB when the android guy is up.

nice rom! going to check this out tonight, thanks!

So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?

Firehawkns said:
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Click to expand...
Click to collapse
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go

pops106 said:
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
Click to expand...
Click to collapse
Thanks for the info, truly! I had searched for Drivers, but not naked.
That worked and it allowed me to use Easyflasher to get CWM back on.
Now I am back where I started, I have tried loading several Roms. Everyone hangs up about 15 seconds into first boot while the setup splash screen is on (for example the dotted circle on stock Asus rom or the simon says color circle like the JB rom or what ever it was in the ICS rom I was using. Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.

Firehawkns said:
Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Click to expand...
Click to collapse
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.

grgmre said:
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
Click to expand...
Click to collapse
Yea, I tried that first. Sorry forgot to mention.

Are you able to flash the stock firmware using Easyflasher?

cabraswell said:
Are you able to flash the stock firmware using Easyflasher?
Click to expand...
Click to collapse
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWOP and delete everything you see on the system and then reflash?

Firehawkns said:
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWRP and delete everything you see on the system and then reflash?
Click to expand...
Click to collapse
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?

Firehawkns said:
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Click to expand...
Click to collapse
Have you tried using nvflash that blasts everything, takes you back to as clean as clean can be.
I am starting to think hardware though but if you can sit in recovery of adb / apx mode without issue then maybe it is a software thing.
No probs wiith the drivers by the way, its not really the right website for searching for the word naked.... dam don't can't won't imagine what you could of found with the members in here...

SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.

Firehawkns said:
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Click to expand...
Click to collapse
I'm glad you finally got it fixed. I had some issues a while back (two weeks after I bought it) and I panicked and caused more trouble. Finally after stepping away from it for a day or two and a wife encouraging me I was able to get it going again...but my gut was in knots for that day or two.

Tablet after redoing the original root does not go over the system.
Not have access to ADB DEVICE or by Windows or the Linux Ubuntu, no longer accepts update totally blocked.
Ask help for those who have been through this problem.

[Q] only booting into recovery after updates/more please help

Hi all I've been an idiot and am hoping I haven't done any permanent damage to my unlocked/rooted tf300 so before I continued doing anymore I wanted to make a post here asking for any help possible.
I hadn't updated to the 4.2.1 build yet and finally decided to bite the bullet an hour or two ago since I wanted to try out the newest version of cromi. I was using the patched 2.4 twrp and initially updated to the 10.6.1.8 update using fastboot, then decided I might as well do the 10.6.1.15.3 using the fastboot again and finally updated to the 2.5 twrp using fastboot. As the jb updates were happening I would get the message that the tablet wasn't rooted and to install SuperSU, and because I'm a dumb creature of habit both times I just instinctively swiped to install, only realizing what I had done after the fact.
After all of this I was still able to at least turn on my tablet and get to the home screen, but unable to do a factory reset in recovery (the log would say "unable to" on every task, but the final message would still say successful?) or have any options to install a rom within it. I had also noticed that I wasn't rooted anymore. I used motochopper and was rooted again for the time being and used a couple apps that required root just to make sure that was the case. At this point I rebooted the tablet and holding down the power button/volume down, I think this is the point where my tablet would just boot straight into recovery, unable to boot into anything except recovery since even if I hold down the power button/volume down.
I've tried to do a factory reset and get the same response as earlier and I get a "failed" message when I try to do a data format. I know there will be at least a couple glaring red flags within this message to anybody who knows much more than I do, but I'm hoping this isn't the end of my tablet and would greatly appreciate any assistance provided. If you need any extra information please let me know I'll do the best I can with providing whatever would be useful, thank you in advance for your time and help.

did you install the 4.2 recovery version?

if you have TF300T (not TG or TL), you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob which you can download from the TWRP official website.
On 10.6.1.15.3, to enter fastboot mode, you need to reboot your tablet and hold volume down button until you see 3 icons (RCK, Android logo, and Wipe). At this point, release the volume down, but do not select any option and do not press volume up. Without doing anything, you are now in fastboot mode.
Do the usual thing you did... connect your tablet to PC via your USB cable, run cmd.exe and change your path to where you have fastboot and the "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" file. Type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
wait until you see a blue progress bar on your tablet. When that completes without error, type:
fastboot reboot
Enter TWRP recovery, Wipe dalvik and cache, try flashing the official ASUS 10.6.1.15.3 stock ROM again. Do not swipe to install SuperSU to root at this point. Just tap "Do not install." If installation goes well, reboot, and re-flash "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob", as installing the official stock ROM may have overwritten your TWRP recovery.
To root, use motochopper like you did. Or alternatively, flash a custom 10.6.1.15.3 stock-compatible kernel and let TWRP install SuperSU (Swipe to install) when prompted before you reboot system. You will get a SuperSU installer app on your launcher. Run that app and choose "Play" or "install from recovery" option. I can confirm that both method works without apparent issues. Choosing Play would be easier and faster than having to go to recovery to flash SuperSU binaries.
I hope this works for you.

matt95 said:
did you install the 4.2 recovery version?
Click to expand...
Click to collapse
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.

peerpressure said:
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
Click to expand...
Click to collapse
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time

matt95 said:
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
Click to expand...
Click to collapse
That's too bad I'm leaving for a month and was hoping to be able to use it while I was gone, oh well nobody to blame but myself looks like I'll be without a tablet for a while. Thank you guys for your time and help I really appreciate it, hopefully the fix will come at some point soon in the near future.

I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?

peerpressure said:
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
Click to expand...
Click to collapse
probably this will be fixed, i don't know why but we are working onto it... i won't sell it just for few dollars.... it's not worth it

One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.

c0ded said:
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
Click to expand...
Click to collapse
Thank you so much for the response, would there be a way to go about getting the 4.2 version onto my tablet though if it only boots into recovery, even when you hold down the power button/volume down? When I plug the tablet into my computer it isn't able to be recognized (I'm assuming just because it only gets to the recovery screen).

Try running "fastboot devices" on your computer while in the bootloader. Does it show anything?
Correct me if I'm wrong, but I remember reading somewhere the when in the bootloader, fastboot automatically launches on 4.2.
---------- Post added at 08:48 PM ---------- Previous post was at 08:31 PM ----------
It IS possible to flash recovery while you're in recovery. Here's how (from tobdaryl; twrp can be gotten from here: techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob):
adb push openrecovery-twrp-2.4.4.0-tf300t-4.2.blob /sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
adb shell
su
dd if=/sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob of=/dev/block/mmcblk0p4
adb reboot
An then to flash stock (once again, from tobdaryl; roms can be gotten from here: forum.xda-developers.com/showthread.php?t=1697227):
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot

Oh, well it hasn't been letting me go into the bootloader on the tablet, just boots into recovery regardless, but for what it's worth the options/commands still show up as shown in the attachment. I don't know if that's something they do anyways though.

What about "adb devices"?

c0ded said:
What about "adb devices"?
Click to expand...
Click to collapse
The list of devices attached doesn't show any it looks like it can't find it

Have you tried flashing 4.2 within TWRP?

How would I be able to go about doing that? (sorry for the inexperience and delays in response, have to wait five minutes between posts)

Download the 4.2 rom (http://www.androidfilehost.com/?fid=22926241640219416), extract it, and put the extracted zip file on to a MicroSD card. Boot into TWRP and install it from the external MicroSD (I don't know how to go about that since I don't have TWRP).
Also, you shouldn't be waiting 5 minutes between each response. You are over 10 posts.
---------- Post added at 09:12 PM ---------- Previous post was at 09:06 PM ----------
Oops. I just read the statement carefully and realized that you have to be verified by a moderator, not have over 10 posts.

I tried it out but sadly it looks like the external microsd is unable to mount so I can't pull anything off of it
edit: It gives me the option to mount a system when the ext. microsd is in but not when it is out, I don't know if that is of any help? Every other option isn't possible though.

What type of MicroSD card are you using?

A sandisk 32gb class 4 microsdhc, it's the same one I had been using with the tablet previously before this all happened

[Q] [Hardbrick fixed!] Bricked Device after installing 4.2 bootloader

Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!

you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.

bloodyshyt said:
you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.
Click to expand...
Click to collapse
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:

Unfortunately putting cwm on it means it is now bricked. Sorry

midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
You got twrp 2.5 to flash?
I am running openrecovery-twrp-2.6.0.0-tf300t-4.2.blob on 4.2.1 and having no issues.
Try it you have nothing to loose! Most people never get rid of cwm but it seems you did.

midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
Go home, splitscreen TWRP. You're drunk.
Go back to the TWRP thread and reread it again. It specifically says you'll need a particular version of the TF300T's firmware flashed before using TWRP 2.5.x, otherwise you'll have the dual display problem. To be safe, I'd flash the firmware (you can do it through fastboot) and then reflash TWRP. Worked fine for me, although I'm not touching it until more ROMs are safe with 4.2.

It lives!!!
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.

Next time (if you still want to upgrade to 4.2 or downgrade, etc) please read carefully!!
i attempted it once (just for the lolz) i succeeded upgrading to 4.2 and downgrading back to 4.1
Sent from my TF300T using xda app-developers app

midgetman7782 said:
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.
Click to expand...
Click to collapse
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
Click to expand...
Click to collapse
Once my pc detect it on ADB mode i can slove it as well

jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
Once my pc detect it on ADB mode i can slove it as well
Click to expand...
Click to collapse
It was the animated one. Good luck dude!

midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
There's the difference. I don't even get that far. My tablet doesn't flash anything in fastboot, and I have no access to adb. My tab only boots to the splash screen and NO further.
______________________________
HTC Evo 4G LTE

midgetman7782 said:
Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!
Click to expand...
Click to collapse
here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
Now flash recovery.....

midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
That's not a hardbrick, 99% of the time that can be fixed. A Hardbrick is when it doesn't get past the bootloader.

[Q] Bricked - please help!

Hey guys,
I managed to f*** up my phone and don't know exactly what went wrong. I'm worried it's a hard brick, but don't know for sure. It won't turn on though, which is freaking me out. I hope one of y'all can help.
So I was running CM10.1 for a long time and everything was great. I eventually installed an update through the built-in CM updater app, decided I didn't like it, and attempted to re-install through the .zip I still had on my sdcard. I'm still not sure why, but doing so put me in a boot-loop. I was pretty busy at the time so just flashed back to stock. Wasn't ideal, but worked fine.
So now I have some free time and decided I'd try to re-install CM. Prior to the install attempt, I was running 4.1.2 stock, rooted and with an unlocked bootloader. Here's what I did:
1: Flashed the VRALEC bootloader, as recommended by the CM wiki, through Odin.
-At this point, everything still worked OK. I think this next step is where I went wrong.
2: Flashed the VRALF2 kernel through Odin.
-This is what I think I did wrong. After I flashed it, instead of booting up the phone got past the Galaxy S3 graphic then the LED just slowly changed from blue to light blue and back. Either way, I still was able to do the following steps.
3: Flashed CWM 6.0.1.2 through Odin.
4: Installed CM10.2 and gapps from recovery.
5: Rebooted, stuck in a boot-loop showing the CM logo.
So hindsight being 20/20, this is where I should have stopped and asked for help. Instead, I decided that I'd try to fix it myself and tried to flash back to stock. When I tried to do so, Odin said it failed. I then reflashed the VRALEC bootloader, again through Odin. This was successful, but after it rebooted, it showed the Galaxy S3 graphic for a bit and then went blank. Since then, I can't get the phone to turn on or enter download or recovery modes.
Can anyone help? I'm really worried I hard-bricked my phone. What do I need to do / where can I go from here?

Update - Maybe not hard-bricked!
berichardson13 said:
Since then, I can't get the phone to turn on or enter download or recovery modes.
Click to expand...
Click to collapse
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?

berichardson13 said:
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
Click to expand...
Click to collapse
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
*your internal storage will be wiped with a factory reset (obviously).
I'm pretty sure they recommend flashing the newer CM's from the MF1 base. I might be making that up though.

Sounds like you forgot to flash something, check the thread you used again
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
If you have a blue led light after the Samsung galaxy s3 screen when it goes black then you don't have the proper drivers for your screen which would be in the file you didn't flash
Sent from my SCH-I535 using XDA Premium 4 mobile app

BattsNotIncld said:
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
Click to expand...
Click to collapse
Tried the factory reset, ended up in the same spot. So, next I'll try flashing back to stock.
I've done this before, but after the scare earlier I'm being overly paranoid - am I going to need to flash a different kernel? Or is it gonna be enough to just flash something like the VRBMF1 image?

Flash back to stock 4.1.2, use Casual to root and unlock, and get a recovery.
http://forum.xda-developers.com/showthread.php?p=42791826
Sent from my Last Ever Samsung Device.

0331 said:
use Casual to root and unlock, and get a recovery.
Click to expand...
Click to collapse
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick.

berichardson13 said:
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick
Click to expand...
Click to collapse
If it still doesn't work, try the slightly older version of Casual: http://rootzwiki.com/topic/44201-★-casualroot-unlock-recovery-1-click-all-otas★/
Sent from my SCH-I535 using Tapatalk 4