I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment
NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?
The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.
xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.
Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running
Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.
Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files
End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.
I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...
Related
firsth of all hi to everyone, im new here , so be patient.
i was searching on the forum and try to solve my problem, but no succes.
all the methods ive tried are a no go
my problem here is that im already rooted (razorclaw tool), superuser installed aswell, so i dont know what else do i need to enter on the recovery mod (i know i have to press down power button and volume - , at the same time), no succes either, the TF just restar as always or the little android with an exclamation sign appears and i have to restart the TF again
my problem is that i cant install custom ROMS, because it always skip to home screen or to the android with the exclamation.
i cant see all those options that lot of people tallk(install from zip, backup current rom, install X rom)because i never get to that part....
so my problem again, how to install some tool that will allow me to enter in clockwork mode (??) ??, and enable those option at the intial boot (power button & vloume - at same time ) to be abble to access the install from zip, backup current rom, wipe data , etc etc
please if someone can help me with another step by step i will be really happy
I am having the same problem
Sent from my Transformer TF101 using xda premium
i think i have this problem since i got the " FIX the problem with DOWNGRADE from .21 to .19", something along those lines, with the method someone posted before (add both files to SD card but rename one of those and then apply update)
jesesystem said:
my problem here is that im already rooted (razorclaw tool), superuser installed aswell,
please if someone can help me with another step by step i will be really happy
Click to expand...
Click to collapse
but have you installed CWM recovery?
User RecoveryInstaller to install CWM.
http://forum.xda-developers.com/showthread.php?t=1346180
/agree with @baseballfanz
Check that you have CWM installed. Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
AzureusPT said:
/agree with @baseballfanz
Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
Click to expand...
Click to collapse
OR you can install 'transformer reboot to recovery' from market
Pepecillo said:
OR you can install 'transformer reboot to recovery' from market
Click to expand...
Click to collapse
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
AzureusPT said:
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
Click to expand...
Click to collapse
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
neidlinger said:
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
Click to expand...
Click to collapse
Thank you¡¡¡¡¡¡¡
Thats the step i was mising , all the instructions are for ppl that actually had cwm recovery, and i was taking advices from posts about installing custom roms and not the 1sth root
Its solved now ,thank you all for your help.
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Bobsinclair25 said:
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In essence there is nothing wrong with asking for help. Heck even the smartest of android hackers started somewhere, asking questions the selves.
The problem lays in the fact that is is pretty common knowledge and a simple search would of gave you the answers you wanted.
Keep in mind nothing i say is meant to come across rude. Sharp maybe, rude? no. If you take what i say as rude. I'm sorry.
No problem. I have been trying very hard to learn on my own. The problem I had with this was trying to find information specific to the transformer. I have done quite a bit with my other android devices and the transformer is new to me and since I use it at work every day I am probably a bit more cautious about it. Thanks, I am working on it.
Sent from my Transformer TF101 using xda premium
I was wiping my tab getting ready to sell it to my cousin. I was in recovery TWRP 2.22 I think. I walked away when my 4 yr son got a hold of it. I came back to see he wiped everything meaning the system. So tried to recover from my nandroid back up but it was gone with everything on my internal SD. I tried mounting the tab to my PC to transfer the old ROM back on but it wouldn't see it with any drivers I've tried. I also tried putting it on my microSD that was in there and it's also not being seen by TWRP 2.22.
I tried to fastboot flash the OEM JB ROM on it when all else failed in TWRP recovery. That didn't work. I tried flashing a CWM recovery to see if it would work better than the old TWRP I had. But after flashing that, my tab won't boot to fastboot and goes in a constant boot loop lol. SMFH at this madness. When the until turns on, it shows the device is unlocked. If I hold the vol down, it will say it's going to recovery then restarts every time no matter what. All I want to do is see if this is even remotely possible to recover from. If not this joint is going on Feebay to game some cash back. So if anyone has any good idea's. I'm open to whatever. What's he worst that can happen. My tab becomes an even bigger bricked unit lol.
Anybody know what options I got? I've read through many threads and none seem to have the answer I'm looking for.
So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium
larryv1979 said:
So you extracted the blob file from the Asus official firmaware and flash system blob in fastboot? And that failed?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah I tried that about 40 times. On 3 PCs with the Asus transformer pad usb drivers on all. I could fastboot TWRP latest recovery then it caused my tab to go into a endless boot loop. I can't get into fastboot mode no more.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Does it get recognized by the PC? Check Device Manager and see if its recognized. If it is and it has an alert (meaning it needs troubleshooting) right click the device update driver and when it asks you select the option where you search manually through a list of drivers. In there try looking for android ADB driver should be one of the first, install it and try again.
It shows up as Asus ADB Interface. But as soon as I attempt to get the to get back to fastboot or even recovery it reboots. So I think the system is dead because nothing I've read seems to be related or can help this system out.
Don't know if this will help, but have you tried the hard reset button?
Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.
JayWheelz said:
Where's that? I know that's a potentially a [email protected] question but I didn't realize there was a hard reset button.
Click to expand...
Click to collapse
AFAIK its the small hole under the microsd slot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I tried that hard reset button and it doesn't help. But I managed to put the tablet in a state where it's recognized by my PC looking for a APX driver. Then I found a Asus APXusb driver but still don't know what I can do from here. After installing the driver. I still can't fastboot or adb to the device. So again I think this tab is a brick.
Hi, I've been experiencing this problem for a while now. Once the screen comes off, the tablet will never wake up. I've clean flashed, with/without gapps, and even right after flashing (EOS, CM, RaymanFX's & Gierdo's, ARHD...) once I turn the screen off (with either the lockpad button in the keyboard, the button on the screen, or after a display timeout) it will never light up again.
I also have trouble switching off the tablet, i.e. I hit shut down and it will never do (I had to go into recovery by power vol-) and hit shut down from there.
Buttons work, so I am thinking it might be firmware problem? Since all roms and different recoveries dont make a difference... I am currently downloading the latest ASUS official firmware from their website, but it'll take some hours since my internet connection here is rubbish.
thanks for any advice and help!
When you flash the different ROMs, are you wiping all the following:
Cache
Davlik Cache
System
Factory Reset (from recovery)
If you are skipping any of these, it can cause issues. The most important one is the Factory Reset to erase the system settings and can cause huge issues when jumping from one ROM to another ROM.
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
TheKaser said:
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
Click to expand...
Click to collapse
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
TheKaser said:
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
Click to expand...
Click to collapse
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
frederuco said:
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
Click to expand...
Click to collapse
Nothing worked. I indeed followed the insturctions you gave me but reading them in the TWRP site so I did it correctly. Still didn't work. I flashed using EasyFlasher the official ASUS firmware, and the tablet still behaves in the same way: Will never shutdown or reboot by software command, will not wake up when screen is switched off... this is frustrating, but it needs to be software, right? It can't be hardware, since the power button does work...
I dont know what else to do... I wiped my tablet clean and flashed the official firmware and the issue is still present...
the thing is that the tablet is working (PC reacts to usb) and it makes noises when I plug the keyboard dock... but the power button will just not turn the screen on...
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
TheKaser said:
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Go to the android development tab of this forum and use the katkernel. Works with EOS roms. I still had a screen freeze but better than the stock kernel. This may help you. Follow the flashing instructions.
Sent from my SGH-T999 using Tapatalk 2
Thanks Tom, I have already tried katkernel in the past, with the same result.
the tablet cant power off either, it stays with the powering down box for ever. I need to hard reboot it into the recovery and power it down from there...
It's all very strange, it happens like that with every rom i've tried, from 4.0 to 4.2.2, and every kernel.
Sent from my Transformer TF101 using Tapatalk 4 Beta
I have followed all the threads I have seen, flashed from roaches Prime 3.0 rom, to EOS 4.2.2, stock Asus/unbrick with easyflash, and using tubuntu installer.
I always find the same issue, cant reboot (it stays stuck), cant tunr screen on after turning it off, and TWRP recovery doesn't work (only the two others provided by easy flasher).
Might it be there is something partially bricked?
I once bricked my USB in my old nexus. I am desperate, the tablet works fine when turned on but can't reboot, power down, or turn the screen back on... it has to be some kind of bricking...
ps: from here: http://forum.xda-developers.com/showthread.php?p=42046184#post42046184
TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
I can corroborate that your commands work.
TomTcom said:
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
Let me know what happens.
Click to expand...
Click to collapse
Is there a way that some part of the hardware is bricked?
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
TheKaser said:
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
Click to expand...
Click to collapse
My commands from the previous postings were to do just that. Format_all and use the configuration file to load from but I could've edited it wrong.
You can try manually pulling all the files from fresh stock software. I don't use any of the tools out there so it's back to research on it.
Sent from my SGH-T999 using Tapatalk 2
once I do a format all, do you know what will I end up with? no OS, no SDCard files, no internal memory, but also no recovery? If so, I guess I have to do flash recovery via Easy Flasher on APX mode.
edit 1:
i couldnt make the --format_partition --format_all work, it gave an error on partition 0.
So, I run --format_partition 1 and its taking too long it seems, cant tell if it's hung up or what...
edit2.
from the config file you provided in the other thread, I can see the partitions are named 3-16. I manually formatted them with your androidpartition.cfg file. I will proceed to installing the stuff and report back. Thanks!
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Good for you! Glad you got it!
Sent from my SGH-T999 using Tapatalk 2
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Hi!
I have similar problem to you.
My tablet is not booting corectly. Stuck on the logo (look at the picture).
I have tried: Easy flash (a few soft), and when i click on the "unbric" my tablet is disconecting from PC.
I can't go into TWRP. I only boot into APX mode.
I can turn on my tablet by recovery mode, and chose there "android" option, but this is annoying.
I dont konw what to do ;(
Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!
Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.
1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app
Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]
Hello,
I loaded the wrong version of TWRP on my TF300T. When it rebooted it loaded CM10.1 just fine. I then rebooted a second time in recovery mode and I have been stuck at the ASUS screen with the "device is unlocked" message. I am able to get into APX mode but my research has shown that mode doesn't do me any good if I haven't ran a nvflash backup. I am stuck and I would appreciate some advice or suggestions. I wonder what the factory reset fee would be from ASUS.
Thank you for your responses!
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
macgyver40 said:
what version where you on? what version did you load that you think you shouldn't? Can you enter recovery mode? fastboot mode? I used fastboot to fix my recovery TWRP just can't find the thread I got my info from.
if your seeing the asus screen like you say I don't think it has anything to do with your recovery. I just went though fixing my mistake and breaking my install of TWRP 2.4.4 patched had to install 2.5 TWRP and when I restored my backup 2.4.4 was back and working again. anyway while the recovery was broken I could still run the stock rom that was installed at that time. I think if your on the asus screen your kernel has an issue.
I don't know where I read about issues like this but I know others have had em and recovered search or someone else should be able to point in a direction but have hope doesn't sound bricked yet.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Thanks for the speedy response =)
Version History: Stock 4.1 -> CM 10.1 Nightly 0503 or 0429. I had CWM on it before trying to load openrecovery-twrp-2.5.0.0-tf300t-ICS.blob using the terminal emulator method. I think I should have loaded the JB blob but the warning on the TWRP site said to use that if you ran the offical OTA update, which I never did so I stuck with the ICS. It installed fine, then rebooted into CM 10.1 just fine. I then rebooted from there into recovery and have been stuck at the ASUS screen since.
The Vol + - button keeps me in the ASUS screen. Reset button keeps me in the asus screen. Vol + + puts me in APX mode.
I try running fastboot in APX mode but it hangs stating "waiting for device" so I don't think it'll work in APX mode.
Thanks.
T
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
c0ded said:
Try waiting for the battery to die, then boot in CM10 and flash the correct recovery.
Click to expand...
Click to collapse
I bled it last night. I'll try booting it this evening. Thanks!
racet said:
I bled it last night. I'll try booting it this evening. Thanks!
Click to expand...
Click to collapse
No luck. I bled it twice and I'm still stuck at the ASUS logo with "the device is unlocked"
Am I looking at repair here?
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of eBay and replace it with the one in your tablet. Also, to save other people's tablets from bricks, you may want to look into this petition.
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
c0ded said:
If you send it in for repair, ASUS will charge you $198. I suggest you buy a replacement motherboard off of
Wow 200$ what a load. To what degree of difficulty are we talking with replacing the mobo? Ifixit makes it look doable, yet at the end he messed up his LCD screen.
Click to expand...
Click to collapse
macgyver40 said:
if you get stuck in fastboot mode then there is a zip file I will find the thread again and it has cmd files that run the fastboot stuff. I was stuck not able to use fastboot commands and then the zip I found worked like a charm.
its a zip file called adb-t.. instructions where to put the twrp.blob in the folder and the update in my case 10.6.1.15.3.zip and it flashed it even though i couldn't manually do it. really wish I could find that thread but I don't have my laptop right now
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I would def like to try it if you can find it.
T
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
http://forum.xda-developers.com/showthread.php?t=2041528
found it. Hope this helps you like it helped me out of my broken recovery. once you download and add the files you want its pretty easy. the script in english makes it pretty easy to understand what your doing and hope it works since I know my TWRP was broken I couldn't even sit at the recover,android wipe screen for more then 3 mins without it bootlooping. I put it on that screen while connected to laptop ran the recovery flash and all went well installing TWRP 2.5 which I then recovered my backup and that even restored my 2.4.4 patch TWRP like nothing happened at all. tablet runs great and have made 3 backups that work after all this.
Good luck
macgyver40 said:
please give me some time. laptop is home again but I need time to look thought my browser history to find the thread. I was searching TWRP 2.5 threads.
I could also find a place to drop the zip file its very small. you would just need the correct TWRP.blob file and a ROM if you want to do that also from this file set I found.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
Please take your time. I have no problem waiting especially if the only solution is to drop 75$ on a replacement mobo.
You could send me the file via email or drop box if it's easier. I was going to use the TWRP 2.5 JB with CM 10.1 nightly. I appreciate all the help!
T
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
macgyver40 said:
look at my please wait thread. found the link in 2 mins and added it above plus a little on why I used it and how bad mine was so to explain why I have hope for yours.
Sent from my Customized Transformer TF300T using TapaTalk HD
Click to expand...
Click to collapse
I tried running through your tread but none of the commands worked on the script. Probably because I can't get fastboot to work. When it tries to load a recovery it just states: "waiting for device" and sits there. =/
c0ded said:
Power up your tablet while holding down the Vol- button, then wait until a menu appears on your tablet. Within 10 seconds, hit the Vol- button.
On your computer, run "fastboot devices". If it finds your tablet, then download the correct recovery (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.5.0.0-tf300t-JB.blob), copy it to your fastboot directory, then flash it using:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-JB.blob
Followed by a reboot:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I am unable to get fastboot to recognize the device. The only way the PC recognizes it is via APX mode. Download mode just sits there at the ASUS screen and windows doesn't see any devices.
Still no love. Am I bleeding out the battery correctly? I am just running the boot screen until it dies then I try to power it on again.
I popped the back open today to see how difficult it would be to replace the mobo, doesn't look too bad. Just having difficulty finding a good online guide.
Also, just so I have the terminology straight, when the tf300t goes into a "boot loop" does it ever leave the asus screen and go black or does it just hang? Mine never goes black, just sits at the ASUS screen with "the device is unlocked" message. The only time I can get it to leave this screen is when I do a reboot and hold the + sign. then it goes black and APX is detected on windows.
Just wasn't sure if any of that information was useful.
T
One other solution is to unplug the battery for 30 minutes, then plug it back in.
c0ded said:
One other solution is to unplug the battery for 30 minutes, then plug it back in.
Click to expand...
Click to collapse
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
racet said:
Ok,
Tried disconnecting the mobo, no love. Ordered a new one for 75$ on ebay. Replaced the mobo and now the volume button doesn't work. Checked all the ribbon cables and they're snug. Probably broke something but I can't find what, so I am thinking of sucking that up. I can control volume with the settings. The only downfall is without a volume button I can't enter the boot loader, so no rooting/ cwm.
Least I'm back in business for now! And another positive is the mobo I received was 32 gig storage so it's like I got an upgrade... with a broken volume button =)
Click to expand...
Click to collapse
Usually, the volume button does not fail. Remember the volume button connects to, but is NOT part of the mother board. If it feels stuck when you push it, that's because you snapped the back cover in wrong. You need to slide it in at the corner where the buttons (volume & power) are, then pop in the rest of it. Take it out and do it again.