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
Related
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.
Ok, so i've read up that your able to fastboot a new recovery, but i havnt been able to find a link with a stock recovery kernel.
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Bootloader (1.00 e) released by "WW_epad-10.4.4.20-20121026" A03
The story is i've bought it some while ago of course, and its been lieing around on the table for a few months.. Basically busy life and other ****. Yesterday i looked at it and was, oh right! Turn it on, and it bootloop on me, apparently common issue with a JB version. herpaderpa on android but fck that..
And when i use a update file on the sd card, i cant install that to update the stock firmware due to the dead droid with the triangle..
From what i can gather around, if i have fastboot option, then its unlocked ? Yes, no ?
If so, could anyone give a hint as to whut the duck i've missed when reading the big full guide thread on the infinity Im starting to become rather desperat. Never had this kind of behaviour with my android devices before, Sure a goofed usb driver for fastboot here and there.. But never a dead droid with triangle..
SOLUTION :
Follow this chaps guide http://forum.xda-developers.com/showthread.php?t=1755576
using his alternative method, and at step 2.
DO AS HE WRITES! Using upper case letters on the file your moving to the sd card, EP201_768_SDUPDATE.zip as such! It works!
My droid kept showing up dead, untill i changed to upper case letters... Then the darn thing came to life!
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
_that said:
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
Click to expand...
Click to collapse
In that case, how can i go about bringing my tablet out of this infernal boot thing? I've tried flashing the twrp kernel, but i dont see any change, when i sent the flash it dit get a blue bar on the bootloader indicated full. So i assumed it could send the loader..
Basically i just want to firmware upgrade with the latest stock firmware, But i tried dumping the file on an sd card, and then go into the bootloader But it did not recognize it and start an update. also i couldnt go into the RCK selection, due to the dead droid.
What exactly did you do, exactly which file(s) did you try to flash, and what exactly happened? And does "I couldn't go into the RCK selection" mean that you never see the bootloader menu, that it doesn't work, or that you don't know how to use it?
Ok, basically, when i start the pad, it never goes beyon the ASUS screen.
Im able to get into the bootloader, here i have 4 icons, RCK, Android, USB, Wipe Data.
When i select RCK it brings the dead droid after a droid thats working.
If i enter USB i can use fastboot. What i've tried here is to do the http://www.teamw.in/project Twrp recovery using http://forum.xda-developers.com/showthread.php?t=1833212 guide *** Custom Recovery Installation ***
However i dont think that it ever was sent to the tablet. Not sure.
I know how to move around in bootloader power + volume down = mennu, then tap the volume to switch between icons, and the other volume to select.
Power + other volume = AXP iirc in stead of bootlaoder.
Did not try to flash any files when the dead droid thing / bootloop started. I basically did an OTA update iirc to a newer version a good while ago. And then life became fcked for me for a periode so playing with the tablet wasnt really an option for enjoyment. It then drained of battery of course, and here now after having it charged up. i realise about this odd bootloop for one of the older droid software versions.
theorion said:
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Click to expand...
Click to collapse
_that said:
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on.
Click to expand...
Click to collapse
Do you already know if your device is unlocked?
_that said:
Do you already know if your device is unlocked?
Click to expand...
Click to collapse
No, it does not say unlocked any where
theorion said:
No, it does not say unlocked any where
Click to expand...
Click to collapse
OK, that explains why installing TWRP didn't work.
Now if you would describe in detail what you did to install the latest firmware, maybe someone could tell you why that didn't work.
Did you unzip the downloaded firmware update once (the result being another zip file)?
The unzipped zip is what you have to put on your sd card. Then the recovery should recognize it when you boot.
If that does not work, try to rename the unzipped zip: EP201_768_SDUPDATE.zip
and put that file into the root of you sd card.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
1. Downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.8 Only for WW SKU (Android 4.2.1) from the TF700F download page selecting android as os.
2. Have a 2gb microsd, i formated as fat 32, using all standard alocation and stuff with windows' own formatting tool.
3. I unzipped the downloaded ZIP file so i have a WW_epad-user-10.6.1.14.8.zip that now contains a meta-inf folder, and a blob file.
4. renamed the zip file to ep201_768_sdupdate.zip, however i did use lowercase... Could that be the issue ? Basically i presumed that the uppercase was only to make people aware of a change.
5. boot the device using the power + volume, and enter recovery mode.
6. Dead droid..
Update as i was writing this, i thought, though it wasn't said specificly, i renamed the EP201_768_SDUPDATE to uppercase, and decided to give that a go.. Now the droid is working its ass off...
F**** i feel like a complete bloddy retard! Gawd i hope it works now then...
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
theorion said:
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
Click to expand...
Click to collapse
Oh yeah, Linux is case sensitive alright. Get the case wrong and it has no idea what you talkin' bout Willis.
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.
ok, I probably am not using the correct lingo but I know one of you guys can help me out. I think I'm hung up on the recovery screen?
Have an unlocked tf700t that HAD a JB recovery image on it. Wife wanted to sell it so she did a factory reset before consulting me.
Now the thing is stuck on the attached screen. Is that the recovery screen? The guts are spinning & the "running" bar below that scrolls as well.
I can shut it down & reboot it but can't get into CWM and can't find it with fastboot on my PC (don't think I can even put it in fastboot mode).
When booted up the "device is unlocked" text and the "ASUS" center screen shows briefly, then the android & his innards take the screen and remain. I've tried booting while holding volume up & volume down and I can't get the 3 icons or CWM to show up.
Have I got a brick on my hands?
Help?
Tf701 for sale how much?
Sent from my SCH-I535 using Tapatalk
psouth said:
ok, I probably am not using the correct lingo but I know one of you guys can help me out. I think I'm hung up on the recovery screen?
Have an unlocked tf700t that HAD a JB recovery image on it. Wife wanted to sell it so she did a factory reset before consulting me.
Now the thing is stuck on the attached screen. Is that the recovery screen? The guts are spinning & the "running" bar below that scrolls as well.
I can shut it down & reboot it but can't get into CWM and can't find it with fastboot on my PC (don't think I can even put it in fastboot mode).
When booted up the "device is unlocked" text and the "ASUS" center screen shows briefly, then the android & his innards take the screen and remain. I've tried booting while holding volume up & volume down and I can't get the 3 icons or CWM to show up.
Have I got a brick on my hands?
Help?
Click to expand...
Click to collapse
Yep - that's the stock recovery....
I've read about this... If you do a wipe from the bootloader (maybe the same for a factory reset from Settings) with a custom recovery installed, it can happen that the bootloader writes a command to the misc partition to boot straight into recovery and it gets stuck there.
Do you have ADB access when you are in recovery?
Try 'adb devices' and see if it gives you anything. _that developed a file to solve this particular situation, namely clearing the misc partition so that you can boot to the bootloader.
I think I have that file somewhere. Check if you ADB and I look for it.
The other option would be (if the stock recovery is working) to download the Asus firmware, unzip it once, rename the resulting zip to EP201_768_SDUPDATE.zip, copy it to the root of a microSD, insert it into the tablet and let it boot to recovery. It hopefully would recognize the firmware file and flash it.
You would loose all data though.
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
stuck into recovery
Hi same problem,
after factory reset inside lates cyanogenmod
stuck into stock recovery
cwm not usable
no adb device visible
won't boot from image taken from
WW_epad-user-10.4.4.20.zip
any other idea?
thanks
g.
psouth said:
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
Click to expand...
Click to collapse
golemlist said:
Hi same problem,
after factory reset inside lates cyanogenmod
stuck into stock recovery
cwm not usable
no adb device visible
won't boot from image taken from
WW_epad-user-10.4.4.20.zip
any other idea?
thanks
g.
Click to expand...
Click to collapse
Sorry - I do not understand what you are saying.
---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------
psouth said:
Thanks Bernd,
Going with the stock firmware is something I've been trying but not having any luck with. I've tried downloading
ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update
from
http://forum.xda-developers.com/showthread.php?t=1946456
several times but I have yet to get anything that I can unzip??
Click to expand...
Click to collapse
That 10.4.xx is really old JB 4.1. The firmware you want to get a the source: Asus
Go here: http://support.asus.com/Download/Options.aspx?SLanguage=en&type=1
Enter "Transformer" in the search box
Choose your model
Select "Android" from the OS choice
....and you will be presented with a list of firmware file, freshest on top.
Scroll down a bit and you'll find the 10.6.1.14.8 firmware for US SKU. That firmware version is still rootable with Motochopper. The latest .10 firmware is not.
Merry Christmas everyone
Fantastic! Thanks Bernd.
DL'ing that file now.
Hope you and yours have a very Merry Christmas out on the west coast.
PS
berndblb said:
Yep - that's the stock recovery....
I've read about this... If you do a wipe from the bootloader (maybe the same for a factory reset from Settings) with a custom recovery installed, it can happen that the bootloader writes a command to the misc partition to boot straight into recovery and it gets stuck there.
Do you have ADB access when you are in recovery?
Try 'adb devices' and see if it gives you anything. _that developed a file to solve this particular situation, namely clearing the misc partition so that you can boot to the bootloader.
I think I have that file somewhere. Check if you ADB and I look for it.
The other option would be (if the stock recovery is working) to download the Asus firmware, unzip it once, rename the resulting zip to EP201_768_SDUPDATE.zip, copy it to the root of a microSD, insert it into the tablet and let it boot to recovery. It hopefully would recognize the firmware file and flash it.
You would loose all data though.
Click to expand...
Click to collapse
Bernd, tried the sd card with the firmware & no luck.
Checked adb and I do get
"015d2ea06d381211 recovery"
so I assume I have access that way. Did you have any luck finding the file you were talking about?
psouth said:
Bernd, tried the sd card with the firmware & no luck.
Checked adb and I do get
"015d2ea06d381211 recovery"
so I assume I have access that way. Did you have any luck finding the file you were talking about?
Click to expand...
Click to collapse
Dang! But at least you have adb....
I finally found the file and the corresponding thread:
http://forum.xda-developers.com/showthread.php?p=48773174
You can download bootit.ko from post 31.
That bloke's situation was somewhat different though and I don't know enough to tell you with confidence that this method would work for you.
The best would be if you could get @_that attention - he's the expert on this.
But read the thread - it should get you closer to a solution.
Good luck and report back please!
Well I'll be. Christmas just keeps on coming. I have a working tf700t this evening. I have no idea of what was taking so long or if it's just a Christmas miracle but I left my pad plugged up to the computer all day. Apparently it decided to get unstuck from the recovery screen all on it's own. Thing boots fine now, completed the reset and went through the initial setup with no problems. Wahoo!
Thanks for all the help Bernd.
psouth said:
Well I'll be. Christmas just keeps on coming. I have a working tf700t this evening. I have no idea of what was taking so long or if it's just a Christmas miracle but I left my pad plugged up to the computer all day. Apparently it decided to get unstuck from the recovery screen all on it's own. Thing boots fine now, completed the reset and went through the initial setup with no problems. Wahoo!
Thanks for all the help Bernd.
Click to expand...
Click to collapse
Santa did hear your pleading and the elves probably had some time to spare right after Christmas! Nice gift! :good:
Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
luisgarino said:
Hello Guys, Im new in the foro and I would like to have your help! Due to I called Asus Official Service in Argentina and they wanna charge me with a 100 USD for soft services out of warranty.
The thing is that my dad put a MicroSD card in his TFT700t and when he whipped it out (without proper procedure), the tablet showed the following sign "Encryption unsuccessfull" and when you press "reset tablet" button, Android start thinking (5 seconds) and then you receive the error screen.
"Encryption unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your tablet is not longer accessible.
To resume using your tablet, you need to perform a factory reset. Whn you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account"
And a "Reset Table button"
When you hit it... there is an Android Robot image that says "Installing system upgrade" and 2 seconds later you have a Dead Android Robot with a ! sign and it says "ERROR"
I have triyed the following things:
- Hard reset by putting a clip on "reset switch"
- VOL DOWN + POWER BUTTON and Android or Wipe Data option... neither worked out.
- VOL DOWN + POWER BUTTON and put Asus Official firmware on a SDCArd renamed "EP201_768_SDUPADTE.zip"... then choose RCK option (I do not have USB Sign button).... nothing happend... the tablet looks to reset, and then they start again with "Encryption Unsuccessfull"screen.
- Finally I tryed to use Minimal ADB and Fastboot, but I used some commands to load firmware from Asus and reboot it and nothing... still the same screen.
As I said it is my old man tablet... it is standard as hell! Stock firmware, not unlocked, not rooted!
When I get into bootloader it shows:
"Androi cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.8-20130514" A03
Key driver not found.. Booting OS
staring fastboot USD download protocol
Im freaking out!! Would you please help me? I really want to fix this problem for my dad.
Thanks dudes!
Click to expand...
Click to collapse
I am getting the same thing after a recent update to Cromi 4.4
bender_123 said:
I am getting the same thing after a recent update to Cromi 4.4
Click to expand...
Click to collapse
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
berndblb said:
CROMi 4.4??? That rom is quite old. What did you update from?
What recovery are you using?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
http://imgur.com/AABbF14
bender_123 said:
Sorry for not labeling it properly. It is the latest version listed in the Dev section. I have been on custom Roms since day one and have never had this issue with any device. The button commands to get to recovery or fastboot seem non responsive and it will boot through a splash screen for the OS and then give this screen (sorry stole the pic from someone else having the problem on a phone, but the text is the same). My PC can see the tablet when it is in this state, but adb commands to reboot to fastboot just loop back around to the same Encryption failed screen...
yEAP... That's the screen... I have a stock tablet,stock firmware, not unlocked, not rooted.
The buttons do respond... but nothing seems to work...
thanks.
Click to expand...
Click to collapse
Try to boot into fastboot: Hold Power and Volume Down buttons until you see three icons.
If you can get into the bootloader (see above) you have a fighting chance to get this solved. Although I have not tried the fastboot/adb commands I have in mind on a locked device. No idea if they would work but no harm in trying.
You can also try to get adb access while in recovery, but you need to set up fastboot/adb on your computer first.
Let me know if you need help with either.
Sent from my K00C using Tapatalk
Sound like you need to reinstall the os. You can find info here
http://forum.xda-developers.com/showthread.php?t=1946456