Related
Hello guys,before with the rom hidro ponic 4.4 all was well.After i want change my rom and i've brick my asus after flash rom unofficial cm10..because the camera apk not found, and dispay is total green..I suppose the problem is the rom but after another flash rom the problem is same.On again the display is lock on the logo Asus and upstar on the little: the device unlock..stop.My asus there's no way to get it to recognize at pc and the driver installed not found..are't fastboot logo in Controll Pannel.I've not possilìbility to choce android--usb--wipe data.Help me please thank you sorry for my English
What about booting into recovery? Or fastboot?
As far as I understand your post Android isn't booting, but what if you hold volume-down when you turn on the tab?
I have almost the same problem. I flashed a bad boot blob (vanilla linux, not android) and now I'm stuck at the first Asus logo if I boot normally. But I still have fastboot and CWM recovery so I'm confident I can get it back into shape (even though a restore in CWM didn't help)
I think there's no way to unbrick the device,because I have the same problem.
I flash my device to official 4.1 and I found I lost root of my device
So I try to downgrade my device,but I failed...
Then I try to enter recovery and I failed again...
At last I try to wipe data of my device but it had no respond...
Of course,I had to reboot my device...
The result is:It bricked...
The symptom is just like the thread starter
What should I do???
I tried to contact the customer service of ASUS,but they said the device which unlocked by yourself couldn't get any warranty,even I willing to pay for it
(I think the customer service of ASUS is too bad,especially their attitude)
(I'm also sorry for my poor English...)
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
e...Thanks anyway
But my problem(the same as the thread starter) is:I couldn't enter either fastboot nor recovery
If I could enter one of it,I think I can fix it...
(Maybe I misunderstand what you mean?)
seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
Thanks guys Today i can try the guide..we ope in God:angel:
I try twrp jb recovery but not function because the teerminal it's impossible go in download mode (down+power)....The Jig Usb forf Asus exist?
Hello guys, but for this type of brick no one has an answer? Method with nvflash can 'operate according to you ..? But I'm trying to appear APX and install the drivers as a guide is a company because it makes them install it
As far as I can see nvflash is coming to TF300T, it has been developed for T201 (http://androidroot.mobi/t3_nvflash/). But at least for TF201 they have to have fastboot first, so that may not help you.
If I understand you correctly nothing is booting and you have neither ADB nor fastboot access. In that case I don't think there's anything to do except wait and hope for a working nvflash or to try to have Asus fix it, but since the tab is unlocked they probably won't do so for free.
It seems this tab bricks easily.
I have the same problem, and I hope nvflash too. But I don't know nvflash in dev or no. This my best device which die first. Cry
Having the same problem here also. Only had the tf300t for less than a week.
Here is a sticky to a thread I made. I'm just waiting for people to put in a bunch of ideas. Hopefully NVFLASH doesn't need fastboot.
http://forum.xda-developers.com/showthread.php?p=31465583#post31465583
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
surdu_petru said:
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
Click to expand...
Click to collapse
...Tried it about 1000 times, not possible, but thanks anyway. No fastboot possible, NVFLASH won't be working either...
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck!
Same problem. Stucked at Asus Logo but i can go into recovery. What can I do? Help me please
My PC finds it as Fastboot.
Seem I'm no alone...
Seem I'm not the only one.
This morning I bricked my tablet, 5 minutes after I bought a wall charger on EBay... :crying:
As for now the only answers seem to be from people that don't read post good.
We can't get to use the recovery...
Again, if someone knows how reset the tablet prior booting...
I beleive that its the only other way.
The last possibility, buy a new one...
I believe the problem started before.
- I unlocked my tablet more that a month ago, at the Jelly Bean release.
- Rooted
- Installed the official release
- Everything went well, up to this morning
- I noticed that my Rom Manager Premium start to show adds
- Goo manager refused to install recovery script
- Then I tried to go in recovery, it fails.
- I said to myself that it was better to start from scratch
- I tried a Factory reset using setting menu.
- After this step the tablet started to show This device is unlocked
-After the last step the device wouldn't boot no other way...
I don't know what happened but it seem a bit strange that everything worked fine before this morning.
For sure I'll keep exploring ways to get out of this mess.
But if I have to buy another tablet, there's a chance that I'll go to a Nexus 7...
Good luck to all the other unfortunate that that are in the same boat.
Alain
Hi back,
After I bricked my device i sended back my tablet to canadian customer service.
At first the didn't wanna fix the proble and the service told me that he needed to change the motherboard.
I argue a while and after an email discussion whit the customer service agent, they told me that they would fix the problem for me THIS TIME.
This morning I received my tablet and everything seem to work fine, as it was reset to factory.
BUT, after I started to investigate, seem that in no time the cover removed.
And maybe the motherboard change is a trick to suck more money from the users.
In fact I can't understand why you'de have to change the motherboard after the tablet is bricked.
Maybe I'm wrong, but I find this way of doing thing awefull, and I consider lucker that I got outa this mess...
Good luck to the others unfortunates
Alain
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Bricked TF300GT (please help)
Hello developers,
I have a bricked Transformer the goes in a loop flashing ASUS every 5 seconds or so. That was after having unlocked and then reset to factory default.
I have been reading a lot of articles at various forum for a solution. I have never seen something so confusing. Please is someone can point to me a page where the un-bricking is described step by step for that aparticular model?
Many thanks in advance
Yves
NB: I have tried the -volume and power button trick or the +volume power button that just make a USB connection on my PC
---------- Post added at 11:01 AM ---------- Previous post was at 10:53 AM ----------
tobdaryl said:
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Click to expand...
Click to collapse
I have the same problem and done what you described without success. What must I flash with fastboot and where will I get fastboot. I believe my machine is in JB 4.0.. Many thanks,
Yves
i got my tf300t bricked to.
got my tablet this weekend wanted to install cyanogenmod.
just did a week early'er a other one (the one for my mother)
that went well
my tablet installed de orginal 4.2.1 from asus.
Today wanted to install cyanogenmod.
run first de unlocker v8
the installed fastboot twrp421.blob
when i went to the twrp menu the cyanogenmod wont install, but the orginal wont start also not, it want nothing to start.
tryed with external sd.
ok i thought i want cmw so i run the recovery-clockwork-5.5.0.4-tf300t.img
went wel also.
i can only go to cwm but they are no file rights and still can install a zip or mount a sd internal or external.
now fastboot is not working
when i turn the tablet on it is going to cwm
wat i can do?
edit:
cmw version = v6.0.2.3
Me too! asus ask 230$ for replace new mainboard. I think they want eat money, because they already have nvfash to fix. 230$ can buy new item from amazon. I hate asus and never buy any thing of asus. Very bad support.
FIXED!
Can anybody help me? I had hoped to get some cash for it and now it just hangs.
I had rooted it, I think it was the one click root. I had cwm recovery manager. It was working perfectly, I used root apps with no problems.
This afternoon I went into settings and clicked Factory Reset. The pad rebooted and I got the image of the Android with some moving hexagon in front of it. This kept running for a long time and I clicked the on/off button. Then it tried the normal boot but that hangs too.
I have tried hard reset RCK, "Wipe Data", "Android" but it won't do anything it just hangs.
I had WW_epad-user-9.2.1.27.zip on it and I have tried adding that to a micro-SD card with a copy also named update.zip and then doing hard reset but I won't get anywhere. I tried APX mode but my computer does not register it.
Is there anything I can do or was this the final faceplant for my pad?
Thanks in advance!
CWM is the problem almost certainly
Try unbricking with Easyflasher and install TWRP recovery
http://forum.xda-developers.com/showthread.php?t=1688012
*Detection* said:
CWM is the problem almost certainly
Try unbricking with Easyflasher and install TWRP recovery
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Thanks, you saved my weekend! That was surprisingly easy (thanks whitekidney). Apparently I had APX connection all along. I thought I'd get some unknown hardware prompt when the tab entered APX mode but as the drivers already were there...
I now have TWRP installed. Now considering if I am selling this to a total n00b, how can I get it 100% stock? To leave no custom stuff on it. So this situation won't happen to him/her if they make a factory reset. :good:
jrkr said:
Thanks, you saved my weekend! That was surprisingly easy (thanks whitekidney). Apparently I had APX connection all along. I thought I'd get some unknown hardware prompt when the tab entered APX mode but as the drivers already were there...
I now have TWRP installed. Now considering if I am selling this to a total n00b, how can I get it 100% stock? To leave no custom stuff on it. So this situation won't happen to him/her if they make a factory reset. :good:
Click to expand...
Click to collapse
If your TF is B6O or earlier serial number, you can use NVFlash (Some B7Os work too, not all)
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Just stick it in APX mode again, and run download.bat
Otherwise I think using Easyflasher again with a stock ROM from ASUSs site should do it, but not 100% on that as I haven't gone back to stock for a long time
I think you can also flash official ASUS updates in TWRP which will return everything back to stock too
http://www.asus.com/Tablets_Mobile/Eee_Pad_Transformer_TF101/#support_Download_32
You might need to extract this stock update once and flash the extracted .zip
I got the stock ROM into it and I did a "Factory Reset" and it worked. So I will sell it like this. Thanks for you help!
Just for anyone else having similar problems I will write down what I did to unbrick my tab yesterday.
I had the APX drivers alread installed from previously (Win 7 Pro 64 bit).
Connected the tab via USB to PC, went into APX mode by holding VOL UP + PWR ON. It registered itself under [Control Panel\System and Security\Administrative Tools] -> Computer Management -> Device Manager -> Universal Serial Bus Controllers. It said NVidia something and that the device was working properly.
I downloaded EasyFlasher-0.8.3b-STABLE & WW_epaduser9_2_1_27UpdateLauncher.zip
Placed WW_epaduser9_2_1_27UpdateLauncher.zip into the EasyFlasher-0.8.3b-STABLE\asusupdate folder
Started EasyFlasher and flashed TWRP 2.2.1 onto my TF101 and then rebooted the device and went into APX mode again
From EasyFlasher clicked "Flash Asus stock zip / Unbrick" and then rebooted the device
Started the TF101 with VOL DOWN + PWR ON. Pressed VOL UP (RCK) which brought me into TWRP
From there I wiped all data and installed the WW_epaduser9_2_1_27UpdateLauncher.zip
This is how I did it and it worked, may be some stages weren't necessary I don't know. Just wanted to document them if it could help someone else. After starting the TF101 I clicked through the configuration wizard and went to settings and did a Factory Reset to make sure I didn't end up in the same situation (hanging/bricked).
jrkr said:
I got the stock ROM into it and I did a "Factory Reset" and it worked. So I will sell it like this. Thanks for you help!
Click to expand...
Click to collapse
Great news, good luck with your sale !
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.
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
Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data
same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Currently I am not able to switch on my phone !!!
AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!
Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.
The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.