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!
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
My Asus TF300T is currently not working. I had a port of Paranoid Android 3.1 installed on it, but I wanted to go back to stock Asus firmware. I flashed the firmware like any other custom ROM, having unzipped the file I downloaded from Asus once. My tablet then went into a bootloop, and i have been trying to fix it a few ways.
I have tried these:
a) I flashed the system blob, through fastboot, from the asus file (this causes the TWRP recovery to be lost)
b) I reflashed TWRP through fastboot. I am asked for a password, even though i never ever ecrypted the tablet (This causes me to lose access to all the files on the tablet, i think it has something to do with the files being in ext3 instead of ext4)
c) I tried to flash the asus firmware through twrp, as i stated above, this failed, giving me the error of being unable to mount /system and /cache, among others.
I really don't have a clue about what to do now... Any ideas???
Edit: Never mind, the problem was fixed when i did a factory reset. This thread can be closed.
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!
[SOLVED]
So after having my Transformer for some time now (unlocked, rooted, and running CROMI) it began to get sluggish. I wanted to upgrade to something else, and decided to try PA HALO http://forum.xda-developers.com/showthread.php?t=2376927
I missed something somewhere, prob the fact that I installed TWRP over my CWM that I had from long ago, instead of upgrading to the new CWM, or the fact that I'm still on the 10.4.4.25 bootloader. I rebooted into recovery, flashed the PA zip, rebooted into recovery, flashed the new GAPPS, and wiped the cache and Delvik. When I went to boot it up the "ParanoidAndroid3+" text and neon jellybean/fish thing show up, then nothing.
I (stupidly) did not make a new backup before doing this change (though there is one from my CWM, but TWRP doesn't seem to recognize it).
ADB does not seem to be working. When I select the USB icon, while using the power+volDown, I get the message "starting fastboot usb download protocol" and ADB does not see the device. If I let the device try and boot (when it gets stuck at the neon jb/fish) ADB sees the device, but gives the error <waiting for device> when I try and flash the new CWM. I seem to be able to access the terminal from TWRP, so I know there is a way to load the old CWM restore files, I just don't know how.
Help is needed.
found a way to do it, but I guess it took away my root when I flashed the new rom. Now I get "su is not recognized" from the terminal..... I'm downloading http://forum.xda-developers.com/showthread.php?t=2107271 and will try to get the os to boot. I can always re root the device, but I kinda need the device to boot into something first.
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
berndblb said:
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
Click to expand...
Click to collapse
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
datboyc said:
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
Click to expand...
Click to collapse
The "kick" was really meant as a friendly slap upside your head which was probably unnecessary since I hope you did that yourself already extensively - so I apologize
Glad you got it working :thumbup:
Hello guys.
Last time I rooted and installed a Custom ROM was like 7-8 years ago with CM5 or so. So I'm not really up to date.
On my K1 tablet, I wanted to install the CarbonROM. Tablet runs Nougat.
The Root was successful, used fastboot for TWRP recovery. (Version 3.1.1 and 3.0.2, tried both). As in many tutorials described I wiped data/cache before installing. Installed CarbonROM (latest version) + gapps micro for 7.1 then wiped cache/dalvik and rebooted.
System then was stuck in bootloop forever, waited about 20mins but nothing happend.
Managed to backup by hard-reboot into recovery/adb and flash twrp again. Tried this time with twrp version 3.0.2, same issue.
I know about the presence of "blob", whatever it is. But since a few guides use it, and few dont, I tried with once with it but managed to land in bootloop again.
Tried with CWM but it didnt even recognize my SD card, or confused the internal storage as sd card. Moved the CarbonROM to the internal storage then and tried to install it. After boot image there was an android with a red "!" and "no command". Vol up + pwr -> recovery. rebooted. Still had the firmware from before, nothing happend at all.
I don't know anymore what to do to get CarbonROM installed and actually started.
Anybody got ideas or a actually a solution?
Greetings
Try a different ROM, or try another gapps (I've often had to mess with different gapps on AOSP ROMs on previous devices).
As for just getting the phone working again, you should have made a TWRP backup before trying to flash a custom ROM. Then you could have just restored the backup.