I've been running CM10 nightlies on my Asus TF101 (B60) for several months and haven't really had any problems until last night. It was running fine and then I got a random reboot. Something must have went bad because during the reboot process it stalled on the CM10 boot animation (not a boot loop). I can get into CWM recovery just fine, however, I cannot mount either /data or /sdcard. During the CWM restore it runs for a little while and finally spits out an error that it can't format /data. It will mount /system just fine and I can wipe/factory reset successfully. I can even reinstall the latest ROM I have on the external sdcard but it still will not boot.
Without being able to mount the /data and /sdcard partitions directly in CWM, is there any way I can run anything like chkdisk, fsck, or badblocks on it? I've got both Windows and Gentoo Linux at my disposal and I'm not at all shy with the command line.
kaneohe said:
I've been running CM10 nightlies on my Asus TF101 (B60) for several months and haven't really had any problems until last night. It was running fine and then I got a random reboot. Something must have went bad because during the reboot process it stalled on the CM10 boot animation (not a boot loop). I can get into CWM recovery just fine, however, I cannot mount either /data or /sdcard. During the CWM restore it runs for a little while and finally spits out an error that it can't format /data. It will mount /system just fine and I can wipe/factory reset successfully. I can even reinstall the latest ROM I have on the external sdcard but it still will not boot.
Without being able to mount the /data and /sdcard partitions directly in CWM, is there any way I can run anything like chkdisk, fsck, or badblocks on it? I've got both Windows and Gentoo Linux at my disposal and I'm not at all shy with the command line.
Click to expand...
Click to collapse
Had a lot of problems but not this one.. Anyways I think starting from scratch with easyflasher would be the best solution to make it functionnal again. Most of the problems I had have been solved by returning stock and reflashing a rom.
I haven't been able to get it to boot into APX mode yet. I saw it once but I didn't have the drivers installed. Since then I haven't been able to get it to go into APX mode again. Have tried several times.
After digging around on my laptop for a while, I finally figured out the drivers issue and was able to get into APX mode. This got me far enough to allow the tablet to boot using the stock Asus 4.0.2 ROM. I lost everything in /sdcard but I didn't have anything terribly important in there that wasn't being synced with Dropsync. After quite a bit of trouble, my own misunderstanding, I got EOS4 #89 installed and loaded as I've read that it's really stable/solid. I'll go back to try CM10 again after it stabilizes. Let the long recovery/configuration process begin...
When you say you can't get it to boot into apex does your screen turn off at least? Because if it is turning off the screen you are in APX mode, you might just needs new cable sadly. Same thing happened to me a while ago.
Sent from my Transformer using xda app-developers app
Related
I have a Transformer TF101 US and I have rooted it, I installed recovery, but whenever I try to install a ROM it just sits on the splash screen and loops forever. I was able to install a rooted stock ROM and I just left it at that, but the launcher crashes and I have to restart. It reboots randomly and I was having problems with the market not processing my requests. I had an old recovery so I thought that might be the problem so I installed roach's recovery 5.5.0.4 r2 and it installed but no change on the status of the ROM when I reflashed them. Now I can only access the internal SD card with the recovery but only have access to the external SD card due to the looping ROM. What's my next step?
The ROM I've been trying to install is the new CM9 nightly. I have tried to install other in the past but the looped too. Other people have had success with installing it. Why doesn't it work for me?
Thanks
-Munchi3s
If you need access to the internal SD, plug your TF into the computer and use 'adb push' to send the files you need to flash to it, or if you can get far enough into usb mode just drag and drop.
Also make SURE to 'wipe cache' when flashing anything, and factory wipe/wipe script if the Rom requests it.
You can also try flashing a custom kernel or a rom which includes one with fixes to help with reboots. Guevor's test kernels and the Tastymehics kernels are good for this.
Minor problem with that
Thanks for the reply, but that's what I tried first too. On windows ADB dosn't see my device in recovery mode and the drivers from ASUS wouldn't fix it. Next I tried ADB on my ubuntu machine and it shows something on the ADB devices but it says
??????????????? no permissions
If I try to push anyways it tells me there is a problem with permissions
Ok. You were right. Wiping the cache fixed up everything. The ROM booted normally and no other problems to date. Thanks for your help.
-Munchi3s
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
jordanjay29 said:
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
Click to expand...
Click to collapse
Reconnect tablet into APX mode, if u have installed all drivers laptop should recognize your tablet in APX mode... once in apex, use easy flash
Sent from my Transformer using xda app-developers app
You didn't read, clearly.
No worries, I got this unbricked by following this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
Hello Forum! I've come here for a little help! Here's My Story.
After running Cyanogen 10.1 Nightlies on 4.2.2 for quite some time, I decided to do a factory reset because my TF300T seemed to be running a little slugish. I DID NOT back it up (mistake #1), DID NOT have USB Debugging on (mistake #2), and, while CWM was wiping /data, I shut off the tablet (STRIKE THREE). Prior to my bonehead move, I had everything else squared away. The unit was fully functional. Now, I'm stuck in this infernal boot loop on the ASUS screen.
I can reboot into recovery, so CWM is not compromised. I have tried to push a new ZIP of the ROM via ADB (unsuccessful, thinking the drivers are nerfed) and through CWM (also unsuccessful).
If anyone has any ideas, please feel free to comment.
P.S. Please don't kill me Mods, I'll be good after this
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Kazman101 said:
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Click to expand...
Click to collapse
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
ricco333 said:
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
Click to expand...
Click to collapse
It Unbricked!
Step 1: Flashed TWRP 2.4.4.0 blob file to overwrite CWM (Check)
Step 2: Factory Reset and Wipe Entire Device (CHECK!?!?!)
Step 3: Flash CM.zip!?!?! (Not So Check ... PLAN B!)
Downloaded Chinese Stock system blob (don't ask, I know it was stupid, but go with me here)
Flashed the system blob (after 3 minutes ... SUCCESS!)
No more boot loop and back to stock ... now to root it again to get my sweet CyanogenMod back ...
Thank you Erik, your help was much appreciated!
So one fine day my TF101G runs out of juice and shuts down. I did the usual, plug in power cable, wait for a while before powering on.
However this time the TF101G is stuck on the loading screen.
I'm on No-Name CM10.1 4.2.2 by josteink with CrossBreeder.
I also have TWRP installed, so I booted up with TWRP and tried to see what can be done. I noticed that there was an error message saying unable to mount /data regardless of what i try to do.
I supposed that would be the root of my failure to boot into the OS itself?
If so, what can I do to recover back into 4.2.2 without losing data?
Many TIA!
ok it appears that I'm unable to mount internal storage also.
I can enter TWRP but I cant do anything because i cant mount internal storage and /data
adamtan said:
ok it appears that I'm unable to mount internal storage also.
I can enter TWRP but I cant do anything because i cant mount internal storage and /data
Click to expand...
Click to collapse
I know nothing about the G model but at that point I'd say you have to give up on whatever data was on there. Just start over, reflash a new rom. If it doesn't work, go back to stock then reflash.
Lethe6 said:
I know nothing about the G model but at that point I'd say you have to give up on whatever data was on there. Just start over, reflash a new rom. If it doesn't work, go back to stock then reflash.
Click to expand...
Click to collapse
Thanks Lethe, but I tried flashing CM10.1 but it failed due to unable to mount /data and also internal storage.
So I tried to flash stock firmware, but it failed also. Now I do not have TWRP/any recovery nor can I boot into CM10.1
I supposed the only way is through ADB.
But i'm not too sure how to go about doing it.
ok managed to get this working.
thankfully i still managed to boot into TWRP, and flash stock ICS firmware.
It didn't really went well because of unable to mount /data and internal storage.
But somewhere the flash in TWRP managed to take place and the tablet went to do some sorting out by itself and viola! it managed to boot into stock ICS.
run PERI and got everything up and running again. at the expense of losing all data but at least i dont have to get a new tablet
p/s: i look through the forums and it appears that the TF101 have a thing of building itself back up after a soft-brick
adamtan said:
ok managed to get this working.
thankfully i still managed to boot into TWRP, and flash stock ICS firmware.
It didn't really went well because of unable to mount /data and internal storage.
But somewhere the flash in TWRP managed to take place and the tablet went to do some sorting out by itself and viola! it managed to boot into stock ICS.
run PERI and got everything up and running again. at the expense of losing all data but at least i dont have to get a new tablet
Click to expand...
Click to collapse
Glad you worked it out!
So here is the full saga. I have a asus tf300t and I was able to successfully unlock it. Then I installed twrp, rooted it and put on CM 10. I wanted to update to cm11 but it wasn't working. Someone suggested I update twrp so I tried that, problem is I used the blob file for the tf300tg (not tf300t). After I did that it still booted just fine and I was able to use cyanogenmod, but then I tried to update cyanogenmod which shut down the tab and now when I boot it goes straight into twrp and I cannot get it out of twrp. (NOTE: I didnt realize that I had used the wrong blob file until just a few minutes ago).
ADB fails and when I try to re-flash cyanogenmod I get a 'could not mount internal storage' error. I have been trying to mount anything and nothing will mount. It is strange to me because if nothing will mount, how was it able to make changes in the first place so as to dis-allow me from booting into cyanogenmod (It is as if it wiped cm and just couldn't install the new cm). I hope this made sense. Please help!