I have a new tf300t with Android 4.1.1 on it and I have followed an older guide to unlock the device and it said to put clockworkmod on it and the Cyanogenmod forums indicate a problem with that, so I went TWRP instead. The twrp site said to pick the right version (-jb) and I did that.
I put 2.6.latest of twrp on and did a backup. Everything is going great. I rooted the device with SuperSU, Copied over CM 10.2.nightly and the right gapps version and it flashed fine. I booted in and I let it go for awhile and it just bootlooped. I went back into twrp and reflashed to ensure that wasn't an issue (same problem) and restored and I'm back to the beginning. I decided to try the 10.1 version on Cyanogen's site and had the same issue. I'm thinking it's the bootloader version doesn't match -- needs to be 4.2, but I want to be careful not to brick the device since a lot of people have done that.
Any guidance or pointing me at a thread would be appreciated. I have a feeling that letting the OTA update take place on the device kind of ropes me into a corner I might not want to be in. I'd really like to be on the latest Android OS *assuming* most of the tf300t features work. I can handle some odd things not working quite right.
Thanks,
Rich
Step1
It appears that my semi-direct path is to get to the newest [MINUS 1] version of 4.2.1 from Asus.
TF300T-US_epad-10_6_1_27_1-UpdateLauncher.zip
Many newer ROMS require this boot loader, and many people say to stick with the twrp 2.5.0.0 because 2.6.x.x is buggy. I can confirm that 2.6.x.x (latest), the mount feature does appear to be broken.
My only concern now is timing. Upgrade to 2.5.0.0 first, or upgrade using fastboot to the new Asus rom. It might not matter and I might need to put TRWP back on after the flash anyhow.
Also, I did root my current OS before doing this update, so it will be interesting to see if that remains intact.
Rich
Step3
I used fastboot to update and I thought I could apply the TWRP 2.5.0.0 update right after it, but it wouldn't take it. I was a little worried that I borked it. It booted and went into the OS and updated a bunch of things. I noticed my SuperSU was no longer root even though it was going to try and survive the update.
Also: I switched to the 4.2 Launcher... not sure I want my tablet to run just like my phone. I might switch back.
I'm still going to try and get to a CM 10.2 rom, it might not be an official rom though.
Rich
Step 4
I decided to see where things were at with a fully tweaked 4.2.1 rom before the 4.3 rom and picked
[ROM]★●[TF300T/G/L/201/301][CROMi-X 5.0.2][ODEX/DEODEX 10.6.1.27.1][SEP 8]●★
This looks very well done/well polished and has lots of people testing it. Will update as I head to 4.3.
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.
rreedy30 said:
First time poster, have been searching the forums the entire weekend so I'm finally going to break down and post a question.
History:
Purchased TF300T, came with Android 4.0.3
Installed OTA to get to 4.1.1, then it updated again to 4.2.1
MobileDock keyboard does not work, after calling ASUS they want me to send in for service.
So, I've decided to dive into the custom ROMs 1. because I want to learn how to, and 2. to see if I can get the mobiledock to work.
Unlocked via ASUS website
Installed CWM but it would never read my SD card
Installed TWRP 2.4.4.0
Backed up (thank goodness, I keep going back to it)
Installed CM10.1 ROM, it installs great but gets stuck on the ASUS image screen at boot
Installed AOKP_R5 ROM, it installs great but gets stuck on the ASUS image screen at boot
I've tried lower versions of TWRP with no luck.
I've tried wiping cache, dalvk, factory, system before, cache/dalvk after installing ROMs
What am I doing wrong? I feel like I'm so close!! Thanks in advance.
Click to expand...
Click to collapse
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108
cmendonc2 said:
The CM 10.1 and AOKP R05 are not compatible with your bootloader (4.2.1).
Sudru said he was going to release an AOKP version for the new bootloader, but you will have to wait for that.
Try flashing CleanRom: http://forum.xda-developers.com/showthread.php?t=2204166
Or flash
Energy: http://forum.xda-developers.com/showthread.php?t=2010108
Click to expand...
Click to collapse
Thanks so much I was able to load both ROMs. I really appreciate it. My mobile dock does not work with either of them but I think I'll search around for that before posting another question.
I got a little bit of a weird question.
I rooted my Tablet originally Cyangenmod's Root Guide:
http://wiki.cyanogenmod.org/w/Install_CM_for_tf101
Every single time I enter Clockworkmod Recovery, I get stuck in a boot loop until I rock between the newest version of Clockwork Recovery (v6.0.1.3) and back to the newest version of Clockwork Recovery Touch (v5.8.3.4.t) (rock as in move back and forth, not 'jam').
Clockwork Recovery Touch is the only version I've found that properly recognizes the sdcard while in recovery mode, so that always ends up being the version I keep on the tablet.
While I am always ultimately able to get the tablet back to functional AND install the rom, this remains something of a nuisance. As rarely as I update the tablet, I almost always forget about this quirk till I am knee deep into trying to update the ROM.
I wanted to see if anyone else has this problem and if there are any work arounds. I would like to not have to fight with this issue everytime and realistically, I'm nearing the point where I am going to upgrade to a new tablet and who I pass it on to will likely not be tech swavy enough to know how to deal with the problem.
Any thoughts?
Flash TWRP recovery - CWM is ancient and bricks the TF101 if you install JB and above ROMs
Easyflasher can do it
http://forum.xda-developers.com/showthread.php?t=1688012
So can Goo Manager from the Play Store
I'll give it a shot. Clockwork DOES do the job, its just, as I said, every single time I ENTER Clockwork, I have to rock the recoveries to make the tablet boot into Android again >.>
Based on the comments on the page TWRP, it seems to be similar problems there too, but at least I know how to get around it if it blows up!
LighthammerX said:
I'll give it a shot. Clockwork DOES do the job, its just, as I said, every single time I ENTER Clockwork, I have to rock the recoveries to make the tablet boot into Android again >.>
Based on the comments on the page TWRP, it seems to be similar problems there too, but at least I know how to get around it if it blows up!
Click to expand...
Click to collapse
TWRP (at least my builds) are working just fine with the tf101. My vfat formatted external microsd is recognized perfectly and the internal sdcard works perfect, too. Plus, you'll be able to flash newer ROMs. You could have an issue if your tab is already in some weird state, but otherwise TWRP should work fine unless you're using some other formatting besides what is standard for Android.
See here for download links and instructions:
http://forum.xda-developers.com/showthread.php?t=2434422
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
The phone with the red triangle is what you are supposed to see. When you see that, you need to hit Vol-Up + Vol-Down and Power and it will take you into recovery. With that, you should be able to do the OTA to 4.4.3. I'm not sure if you need to flash the 4.4.2 firmware first or not. You can give it a try. If it fails then go ahead and flash back to the 4.4.2 firmware from Tigerstown's thread and try it again.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
SCrosler has posted a stock rooted 4.4.3 ROM. If you flash that you will all up to date (or you could flash Viper 2.4 or NuSense 2.0) essentially flashing any 4.4.3 ROM will get you where you want to be.
Here is the link to the stock, rooted ROM: http://forum.xda-developers.com/ver...m-stock-rooted-vzw-ota-2-21-605-2-wp-t2874699. With your updated firmware and that ROM you will be stock, and up to date on 4.4.3
@BladeRunner & @jsaxon2, thank you very much for your replies and the help. Looks like this was covered to some degree, and has answered my questions.
Going to try dirty-flashing the ODEX rom. I want to flash Viper pretty badly, but don't want to have to wipe everything right now. When Android L comes out, that will be fully worth starting from scratch. I have just enough patience to wait.
Will confirm shortly that everything has worked.
FYI, dirty flash of the ODEX (just wiped cache/dalvik, left data alone) worked perfectly. Software is now reading 4.4.3. Thanks to @scrosler for the stock ROM!
Brief back story goes like this. Working TF300T running JB, was running slow and laggy so it seems a good time to flash something new. I'm no android/linux pro but I have a good base knowledge (you may question this statement later) . Successfully unlocked and flashed CM12 and TWRP. Tablet ran ok, sometimes significant lag, updated to a few different nightlies, then eventually decided to go back to stock. This is where it all went wrong. I followed the instructions here on XDA by d_crossfader. The flash seemed to go as expected, wiped cache/dalvik, rebooted. Loaded up to stock JB but no wifi, rebooted, all went bad. Stuck at the silver ASUS with spinning dots screen.
here's what working at this point.
I can load to fastboot, recovery etc, and have re-installed TWRP, the latest 2.8.1 failed install, but 2.6 is working (since I've read that this rev has issues).
I went back to the CM12.1 ROM I had working and it seems to flash fine but GAPPS fails, gives 'E: error updating binary in zip' for /boot and /recovery.
I think I've exhausted my abilities so it's time to call in people with actual skills.
What should my next move be? I'd be happy with stock or custom ROM's just like to get it back to functioning.
Thanks