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

[SCRIPT] Safe Bionic Path Saver + .901 + Liberty3 2.0 - VERSION 2

Yesterday afternoon I attempted the Bionic Path Saver update with 901 and Liberty 2.0. Due to issues with flashing the Webtop image and some flaws in the script I wound up with a dead phone. After hacking up a charger and over 12 hours of experimentation I was able to get the phone and and was able to update it. I do not want anyone to have to go through what I went through so I am posting this. I do not take credit for the files, I only came up with the combination. All download links lead to the creators. Let me know how this works out and of course always create backups before performing this.
**Things you will need**
A FULLY charged battery
My SafeBionicPathSaver_v2.rar - http://www.filesharesite.com/files/201201/1327968223SafeBionicPathSaver_v2.rar.html
RSDLite 5.5 - In this package
Motorola Drivers - In this package
flashme.zip - In this package
Liberty 2.0 (.901 OTA Compatible) - http://rootzwiki.com/topic/13096-901-radio-working-with-custom-rom/
bionicbootstrap.apk - http://droidmodderx.com/bionic/bootstrap-recovery-for-the-bionic/
**Instructions**
1.) Install RSDLite 5.5 and Motorola Drivers (32-bit or 64-bit accordingly).
2.) Extract flashme.zip to any location on your computer.
3.) Extract SafeBionicPathSaver_v2.rar (ME) files to any location on your computer.
4.) Copy bionicbootstrap.apk and copy the Liberty 2.0 (.901 OTA Compatible) ZIP to the root directory of your SD card.
5.) Connect phone to computer, set phone to USB Debugging Mode, and set it to Charge Only. You will also need to allow "Unknown sources" in your application settings.
6.) Go to the directory from Step 3 and run SBPSscript.bat. Let it run and wait for Phase 1 to complete.
7.) Phone should now be at the bootloader. Open up RSDLite and browse to the XML in the directory from Step 2. Flash this and the phone should reboot, it will take a while.
8.) The phone should now be at the Android setup screen. *The phone has been reflashed and reset, you now need to follow STEP 5 again to continue*. You may now contune following the prompts in the SBPSscript.bat script. Watch for any errors as directed. The phone should end up booted into stock recovery.
9.) At the recovery menu you are going to install updates manually. First do update893.zip, then do update901.zip. Make sure there were no errors then reboot the phone.
10.) You are now at version .901 and should still be rooted. To test root you can try and update Superuser by going to Superuser's menu and updating the binary. If it fails with a permission issue, you do not have root and have to start over.
***IF YOU WOULD LIKE TO REMAIN ON THE STOCK ROOTED .901 ROM YOU CAN STOP HERE. THE REST OF THE STEPS ARE FOR GETTING LIBERTY3 2.0 INSTALLED.***
11.) Now install bionicbootstrap.apk, open the application, and press the "Bootstrap Recovery" button (grant any SU access). This will install the Clockwork Recovery ROM and would fail if you were not still rooted.
12.) Now click the "Reboot Recovery" button. You will now be in the Clockwork Recovery Mod.
13.) At this menu you will need to wipe data, cache, dalvik cache, and format /system.
14.) Now you will select "install zip from sdcard" using the volume and power buttons and choose the Liberty ZIP you uploaded in Step 6.
15.) After this is done you can reboot the phone and you will have a Liberty3 2.0 / .901 Radio Bionic!
-Mark DePalma | MNetwork

I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.

utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
You're welcome, a user just notified me of a typo "fixme = flashme" and I have updated that in my ZIP and in the post. The same user also told me that the flashme.zip file isn't available for download at the moment. I would host it myself, but I know that within 30 minutes my pipe would be saturated. Hopefully this link comes back up soon, if not I will find a way to host it somewhere.

utcu said:
I will be trying this later tonight. I'm hoping it goes well and I'll be sure to let you know. Thanks for taking the time to make the write-up. If it works properly, it's exactly what I've been looking for.
Click to expand...
Click to collapse
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.

utcu said:
Worked like a charm. Greatly appreciated. Nothing like being on Liberty with 901.
Click to expand...
Click to collapse
Great! Good to hear. I have updated the post with a 2nd link to download the flashme.zip file since that went down last night. Very happy XDA is finally back online.

can this be used to go back to 5.5.839 from .901?

waffleb051 said:
can this be used to go back to 5.5.839 from .901?
Click to expand...
Click to collapse
I believe you can, but you MAY have to flash a .901 CDT image after you flash back to .839. I came back from a failed root attempt on .901, but I was also playing with different CDTs. If you try it out you can definately get it working, may or may not have to flash that .901 CDT.

I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4

Stealth36 said:
I haven't able to have any success with this. I tried it twice but it keeps hanging on the Motorola screen. This is after I flash flashme (step 9) and when it goes to reboot. I've waited both time for 15-20 minutes but nothing. Is there something I'm missing? I have RSDLite 5.5 and Drivers 5.4
Click to expand...
Click to collapse
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...

so I'm taking this doesn't work... files aren't even there
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.

Slie said:
all i need is the last one... BPS_Safe_Scripts
plus there is a safe strap now... whats' going on.
Click to expand...
Click to collapse
My web server runs on an old P2V'd box in my ESXi cluster and I've been meaning to port all my web sites over to a new web server VM, but haven't had the chance. I have to restart this VM every once in a while... I just rebooted it and the web site is back up. You can download this file now.

mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!

Stealth36 said:
I went to try it again and it worked this time. It ended up on the Android welcome screen. Thanks for the script!
Click to expand...
Click to collapse
Good to hear!

I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?

Stealth36 said:
I have one more question. Right before I installed the Liberty(.901).zip my system version said 901 but after installing Liberty it now says 886. So is that telling the truth?
Click to expand...
Click to collapse
I am in the same boat. I believe since the ROM is built on .886 that is what it is going to report. The radio, however, has already been updated and Liberty doesn't contain a radio and therefor would not roll it back. The version of Liberty used in here is only patched with libraries to handle the .901 radio. Since the upgrade I have not had the contant data drops and 3g/4g switching that I had before. The only time the data really drops now is when I'm going through a tunnel or something like that.

Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.

treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
The governement is getting out of control with the piracy protection... I can make one complete package that would be much smaller than all of them combined, but if I host it I know I will be out of bandwidth in 30 min (it would still be fairly large).

treefrog20012003 said:
Unfortunately it seems that all of the servers for these files have been stopped or are now unavailable. Anyone got the files or a new location for the files? This situation has gotten out of control with the sites.
Click to expand...
Click to collapse
Which files did you find were missing? I was able to download two of the larger ones with no problem.

The flash me zip was not available and one other file was blocked on two of the sites and on a third it called for four hours to download. I want to get off the 901 system and downgrade so I can run the ics ROM. I tried once and was bricked for 24 hours until I found the bin swap method to get back to 893 from the motorola files using rsdlite.
Sent from my DROID BIONIC using XDA App

Same Problem -- Need Help
mnetwork said:
Well since you have rebooted you now have to manually get it into the fastboot mode. Turn the phone off, hold both volume buttons down, then hold the power button down for a second or two and the phone should enter fast loader mode. At this point you can connect it to the computer and RSDLite will see the phone and you can resume. Let me know if this works for you...
Click to expand...
Click to collapse
I am running into the same problem. I have re-ran the RSDLite script, it finishes but the phone never goes to the Android Welcome Screen. It stays on the Motorola Dual Core start-up screen

[Q] ICS update failed

Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan

I had the exact same problem. Got it fixed. Use the method from this thread: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html

Thanks for your reply. I noticed on that page that it says that if the serial number is BD70 or above (which mine is) do not use the tool. Has there been an update that allows this to be used on the newer units?
Thanks,
Ryan

Hi there!
I got a similar problem yesterday and the error was that a file inside the DATA partition could not be deleted. I noticed when doing a factory reset from CWM.
If you have CWM and you can flash the "super wipe tool" you can fix the problem. Then you re-flash the ROM. I got it working and now I'm on a clean clean clean clean.... clean shiny install
check my threat if you want:
http://forum.xda-developers.com/showthread.php?t=1516204
Hope it helps!

I'm guessing I do not have CWM as I do not know what it is?
Thanks,
Ryan

sh.assassin said:
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
Click to expand...
Click to collapse
Ok, I'm going to help you unbrick your device. But you need to forget everything other people in here have told you. Ok? And just do. Don't question. Just follow the steps.
(1) Go to the following asus webpage, choose android as OS and download your version of the 21 firmware. WW, US, TW, etc.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
(2) Rename the downloaded zip file to "EP101_SDUPDATE.zip"
(3) Move zip file to a micro sdcard.
(4) Insert microsdcard into the TF.
(5) Turn off TF.
(6) Power on by pressing power button and volume down buttons at the same time. When white texts appear on upper left hand corner, release power button and volume down buttons and press volume up button.
(7) Watch your TF unbricking itself.
(8) Leave it alone to do its thing.
(9) Write me a check for 2,000 yen.

Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan

british.assassin said:
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
Click to expand...
Click to collapse
Download is corrupted. Have you tried again?

Yes I have, about 10 times and it always comes up with that error.

I had the same failure and had to install .13 and update 3times to get to ICS. Got it from the Unlockr link. Worked great and then rooted with ViperMod.
A clean install is seemingly not having as many issues. Plus I already have an AOKP ICS rom on my phone, so I already know most of the ICS features.

I did try downloading .13 and installing it the same way as I did .21 (putting in on the micro sd and powering on with power & vol - to get into recovery mode), however when I try this I get the yellow triangle and black exclamation mark again, only this time it does not stop my tablet from booting back in to .21.

british.assassin said:
Yes I have, about 10 times and it always comes up with that error.
Click to expand...
Click to collapse
This error comes up when you have a corruption in your stock recovery.
You won't be able to "downgrade" to .13 the way you did with this. Unfortunately, there's no easy way for you to go about this. Here is what you need to do. Yeah, it will be a little long.
(1) Root via nachoroot.
(2) Install CWM via recovery installer. Can be found in the app portion of this forum.
(3) Download the repacked .13 version from the following link.
http://dl.project-voodoo.org/transformer-roms/3.0.x/
(4) Download stock recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=606402&d=1306284085
(5) Flash the repacked .13 version via CWM.
(6) Restart the TF.
(7) Flash the stock recovery.
(8) Restart TF.
(9) Upgrade via OTA. One of the updates will give you the appropriate stock recovery.
Failure to follow my instructions precisely will result in brick.

[Q] Bricked?

Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark

mmanis said:
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
Click to expand...
Click to collapse
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad Infinity TF700T&p=28&s=1
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.

berndblb said:
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here:
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
Click to expand...
Click to collapse
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark

mmanis said:
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
Click to expand...
Click to collapse
Hmm, still bootlooping.
Next thing I would try is to boot into the bootloader, select 'Wipe Data' with the Volume Down button, hit Volume Up execute.
And actually, before even booting back to system (that would be choosing the Android), I would reflash the firmware - just for good measure after the data wipe.
Can't wait to hear if that solves it!

So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark

mmanis said:
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
Click to expand...
Click to collapse
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.

berndblb said:
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
Click to expand...
Click to collapse
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark

mmanis said:
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
Click to expand...
Click to collapse
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491

berndblb said:
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark

mmanis said:
Hi, how do you capture a logcat
Click to expand...
Click to collapse
This was at the top of the xda portal http://forum.xda-developers.com/showthread.php?t=2274119
best bookmark it for future reference its a really good tutorial

mmanis said:
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
Click to expand...
Click to collapse
At this point only a bootloop logcat can shed light on this. Check the tutorial JTR recommended. It's truly good - thanks for the link!

Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark

mmanis said:
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

berndblb said:
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Right try booting without the microsd card in. Something is wrong with it. Also turn off the Bluetooth, what ever it is trying to connect to is adding lots of entries to the log.

[Q] rebooting TF700T..... first ever problem

Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol

PaulCopel61 said:
Constant reboot suddenly appeared today
Can you stop it rebooting?
Message come up when using on and vol button
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?

TF700T first ever problem
berndblb said:
So it boots to the bootloader, you see the three icons - and then what?
It bootloops again?
Give us more info: Are you on stock? Rooted? Locked/unlocked? What did you do/install prior to this happening? Did you drain the battery so that it suddenly shut down?
Click to expand...
Click to collapse
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Trust that helps ...I am newbie at this worked perfectly up to now

PaulCopel61 said:
Hi
Thanks for reply
The pad has never touched,altered,rooted,etc.... ,after reading a book on pad ..shut down in evening ...next morning problem occurs
Loads up main screen for about 6 seconds freezes the starts rebooting
By pressing on/vol button I get messages
With flashing RCK it says
bootloader 1.00 e released by "US epad-10..6.1.14.10-20130801"AO3
Key driver not found ..booting OS ?
Starting fastboot USB download protocol
Click to expand...
Click to collapse
That's ok and healthy. You are in the bootloader menu and seeing exactly what you're supposed to see here.
Moving along to Android symbol
it adds booting recovery kernel
signature match
Starts to install update ..
then gives me "error" android symbol
Click to expand...
Click to collapse
Mhh, this doesn't quite make sense...
If you say: Moving along to Android symbol - you are pushing Volume Up?
You toggle between the icons with Volume Down and execute them with Volume Up.
"Booting recovery kernel" would indicate that you pushed Volume Up on the flashing RCK icon which would fire up your recovery, and since it doesn't find a valid update file you get the Android on his back and the error message.
Since you are on stock your options are very limited. My guess is somehow your system partition got corrupted and your tablet can't boot into Android anymore.
You can give it a shot by using Volume Down to get the Android icon to flash and then pushing Volume Up, but I doubt that it would help since the tablet refuses to boot your system in the first place.
So if the above fails, go the Asus support website, the download section, enter "Transformer" in the search box, select the TF700t, choose "Android" as OS and from the resulting page choose the firmware for your SKU. If you are in Europe it would be WW, US for North America, JP for Japan - you get my drift...
Download the file and then unzip it ONCE, the result being another zip file. Rename that zip to EP201_768_SDUPDATE.zip and copy it to a microSD.
Turn the tablet off and insert the microSD.
Boot into the bootloader with Volume Down and Power.
Push Volume Up on the flashing RCK icon to boot into recovery and it should recognize the firmware zip and start to flash it.
You will probably loose everything you have on the tablet if it is not backed up. But I don't see any option for you to save your data if you want to get the tablet working again. I just hope you knew and lived by my mantra: Data not backed up is data not yet lost....
Good luck.

Tried advice
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul

PaulCopel61 said:
Thanks for advice
Took a week to get micro card reader !!, however downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)
Booted up as per instructions, it recognized the firmware zip and started to flash it.
Loaded as normal .. however same problem still exists ... noticed it the few seconds before it rebooted that not much had changed on desktop ?
Definitely says Android US Epad 10.6.14.10-20130801
Should desktop have changed ?
I am missing anything ?
Getting desperate
Any help appreciated
thanks
paul
Click to expand...
Click to collapse
I think you are going to have to wipe the device mate.

wipe
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul

PaulCopel61 said:
Thanks
Will do anything to get it working
As I am new at this could you guide me to best thread which gives clear instructions how to wipe and re install?
Pad is out of warranty never been altered ...
paul
Click to expand...
Click to collapse
When you are in the bootloader menu, choose the third icon 'Wipe Data'. You navigate there by pressing Volume Down twice, then it should be flashing. Press Volume Up to wipe your device.
You will have to re-install the firmware (same procedure I described already)

Thanks...
Everything working !!
Finally...
So I don't have similar problem again should I unlock?
What program should I use ?
Could you point to thread to show me how too ?
Paul

Glad you got it going!
Check this out: http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html