Related
I have a sl101. I only get eeepad screen. My son did something to the machine. I can get it to say booting recovery but nothing happens. I also can get a text that says cold booting Linux. Again nothing happens. Nvflash says USB write fail. But when I check adb the device is recognized. Is there a way for me to adb push a recovery in there for me to boot too, so I can reflash a rom. I have a little dilema here. I also was wondering if I can flash rom thru adb. I read once that's how they used to do it on g1. I don't know if I am speaking accurately though. Any kind of light shed on me will be greatly appriciated
Sent from my SAMSUNG-SGH-I997 using xda premium
not sure about the slider but i had a customer return yesterday with this exact issue on the tf101 and i couldnt get out of it. the tf just kept switching itself back on and getting stuck on the splash screen.
found this set of instructions but im not sure if its what you need or if it will work:
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
good luck
That is exactly what is going on with mine. The slider is basicly the same thing. I plug it in and I tries to boot. I thought you had to be booted into recovery or the rom for adb to work? That's why I believe this method you just revealed to me. Or some variation of it will work. I will be trying shortly.
Sent from my SAMSUNG-SGH-I997 using xda premium
not working transformer
i have asus tranfrormer 9.x.x.x, recovery 5.8.x.x, after i did superwipe , every thing is gone and i cant flash any rom through adb/nvflash saying cant write to sdcard (read only). any suggestions?
HELP : Same problem, no apx, recovery strange, no boot
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
densleonis said:
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
Click to expand...
Click to collapse
nvflash if your TF101 is compatible model.. (must B60 and below).
Or read Wolf's thread HERE. It might helped everyone here..
Thanks but everything needs adb connexion and as apx is not working, i can't connect ADB..
I have a B50 model
Nobody have a clue ?
well, I have to send it back to my reseller that will change it but before that I need to delete clockwork mode or brick it, how can i do ?
I tried every thread here, update rom does nothing, looks like it does not write anything on the tablet
Thanks in advance
try to follow this procedure...
http://forum.xda-developers.com/showpost.php?p=25636698&postcount=5
let me know
Hello, thanks, but as I can't get to apx mode, I can't use nvflash, so still stuck with my recovery, I tried to modify super Wipe package to do things but can't get through...
If someone can make a package to delete recovery, then I can try it on my tablet, I really yneed it to be bricked cause now it load with Rogue's recovery on and on, so the reseller will new it has been modified and I will have to pay to get it back ...
Thanks in advance
with the procedure posted in the previous link you don't need APX mode and don't need NVflash...
Just boot your TF in recovery mode and plug it to your pc...
remove all previous drivers and install the new one that you can find in the post
ciao
ps... at the end of the procedure you will have your TF101 with stock rom and stock recovery
I will try but even when I am on recovery, nothing appears in Hardware management, no recognition from My computer, still strange... And when I power + vol down key, It never says to presse vol up in the text in the upper left corner, just says booting linux kernel...
When I try to boot pressing vol up + power, nothing happens, not even the clics that can be heard when it powers up...
I had a similar issue when I used SuperWipe and discovered my ROM on the external SD Card could not be accessed by CWM
I tried pushing the file with adb but kept receiving errors - protocol, etc. I suspected it was a driver issue along with the fact that 64 bit systems don't always play nicely with drivers. I actually dug up an old hard drive and did a very basic install of 32bit Win7. I booted the Transformer into CWM and when I connected it to my PC - I pointed it to the universal naked driver. I was then able to successfully push the rom to internal storage and used CWM to flash it
Hello,
I tried to connect my tablet to an old Windows 2000, but still nothing happens
Hello every one, I finally sendt back my transformer to my reseller, now I can buy a new one...
Thanks again
Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.
Hi,
I've got a huge problem - i've been using Megatron ROM on my TF101, but sth has f****d up and i couldn't switch off WiFi/3G dongle and connect it to PC by USB. So i've decided to come back to original ROM by ASUS. A here is a bummer- after cleaning data/cache/system/delvik original system is not working. So i tried to use easy flasher - same thing. Nothing happened, tablet just boot to recovery. I thought it might be the system, so I wanted to install Revolution, and then Megatron again - but nothing! Every time I turn on the tablet, it boots to recovery, as no ROM was installed. Any ideas? THX a lot for answers & hints....
There is sometimes a problem after flashing a recovery where recovery gets stuck in a loop. Even if a ROM was properly flashed afterwards. There is a workaround and a fix hanging around.
I'll have to look for where the fix was posted, but it was somewhere on these boards. Basically, you have to connect the tablet up to a computer with ADB while it is in recovery and open an adb shell on the computer (or you can do this from the terminal shell in the recovery if you have the latest OpenRecovery TWRP 2.2.2.1) and you issue an environment variable to be written and it permanently fixes it.
The work-around, which is temporary, but gets what you need done, is to do a hard restart. Press and hold both the Power button and the Down-Volume button until after it reboots. You'll see some text on the screen (don't press up-volume) and then be given a choice of factory-reset, or Cold Boot Linux (Android in this case). Do the cold boot. That should get you into your ROM.
Sent from my Transformer TF101 using Tapatalk 2
Thanks a lot - i've been able tu get into ROM now. I've tried to fix bootloop (because it causes some more problems - in Revolution HD WiFi is not working) with thread {Guide}ClockWorkMod recovery bootloop fix (Tested on my c10) Windows (sorry, i cannot insert any links yet) but i've stopped @ point 8. ADB push is working fine, files are in folder "Download", but from CWM i am not able to install zips from internal memory, only from microSD. And then when CWM is on, ADB is not connecting with tablet. Why?
Hi !
I've also experienced a bootloop with some version of CWM Recovery (I was running CM9 and ROM Manager messed up everything ). The only way to start Android was to "cold boot Linux" every time, like you.
The solution I used was to start Android, activate USB debugging mode and authorize root access from shell, connect the tablet to the computer and then start an ADB Shell.
Then, you have to enter "su" in this shell to get the root access. The last command to enter is :
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Which is basically setting the BOOT flag on the Android partition.
If you need more to do this, like screenshots... I'd be happy to help.
I would much appreciate that!! And could be useful for the others...
[Edit]
Made it! Thanks a lot both of you!
Great
Sorry, I didn't have time to make screenshots yesterday evening (it's 9:50 am here), so if someone wants it, just ask !
Sent from my Transformer using xda premium
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck
I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?