Ok.....i hope i can explane my problem..
Today i wanted to update my tf300t to the latest firmware with new bootloader and in fact....it works fine.....so i thougt..
But after i flashed the new firmware with twrp i am unable to mount the internal and external sd cards in recovery....
Tried the latest patched twrp and cwm......in both recovery's i am unable to mount int/ext storage.
Tablet boots fine and works fine to, but i am unable to flash files in recovery now.
I can't wipe cache/dalvik/ etc.
i can't mount/format etc.
in fact, my recovery's are totally worthless at the moment
So.......i started up fastboot and pushed the stock asus firmware again.......who knows, maybe it works.....but no, still no luck
I think it has something to do with the new bootloader and the new partitions but i'm not sure.
Anyone any clue what this might be?? maybe a kind of softbrick?
Unfortunately you have flashed an incompatible recovery with the new bootloader. This has probably bricked your TF300 with no known way to fix......
Are you able to get fastboot to accept a blob file?
sbdags said:
Unfortunately you have flashed an incompatible recovery with the new bootloader. This has probably bricked your TF300 with no known way to fix......
Are you able to get fastboot to accept a blob file?
Click to expand...
Click to collapse
Yes i can.....
Reflashed the rom, reflashed the correct recovery.....still can't mount anything in recovery.
FIXED!!! Did a wipe....in the fastboot screen (not in recovery since it didn't work)
And now the internal sd is visible and mounted, so next step flashed supersu......aaaaaaand i'm done
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!
I have read many posts around about the problem with wiping my tablet within the bootloader menu but unfortunately it was after the fact of doing so. I know my post is similar to most but what I found odd was that my bootloader was listed as 10.4.4.25. Am I in the same boat as everyone else having basically a bricked tablet? I can access adb mode, fastboot which says it successfully has written a file but does nothing when rebooted just hangs. I can send files to my tablet but when I go to install it states it failed. I have TWRP 2.4.1.0 which states unable to mount cache...etc. The device is unlocked. Is there any way to fix partitions or allow it to mount a file system, I did update to the newest Cleanrom, can't remember what I didn't like about the flash before I wiped it. Any help would be great and if you want to just state I messed up thats more then welcome too. Thanks
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .
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!