I just bought a TF700T and immediatelly decided to install a Custom ROM. I had a Motorola Xoom before, so I recognize that was a monster hard to brick, but in my first hours with this new child, I'm suffering quite a lot, so I decided to ask for help.
First, the tablet was at Android 4.1. I unlocked the booloader, then I installed a new Recovery Menu. From what I read, it seems that TWRP is the recommended one recently, so I took it (version 2.6.3.1).
In there, I tried to install a Custom ROM, PAC-man, I downloaded a non nightly image, a little over 170MB (So I guess it's full and not just some random update), wiped the tablet (Full), flashed, restarted and the custom loader started, but soon it froze and restarted. It was the first infinite loop.
Then I decided to get the nightly image. Did the same thing, wipe, flash, restart, got the same results.
Then I gave up from PAC-man, and got BAM Android. Got their RC version, wipe, flash, restart, loading screen, freeze, and restart loop.
So am I forgetting something that should be done for the TF700?
ssj4maiko said:
I just bought a TF700T and immediatelly decided to install a Custom ROM. I had a Motorola Xoom before, so I recognize that was a monster hard to brick, but in my first hours with this new child, I'm suffering quite a lot, so I decided to ask for help.
First, the tablet was at Android 4.1. I unlocked the booloader, then I installed a new Recovery Menu. From what I read, it seems that TWRP is the recommended one recently, so I took it (version 2.6.3.1).
In there, I tried to install a Custom ROM, PAC-man, I downloaded a non nightly image, a little over 170MB (So I guess it's full and not just some random update), wiped the tablet (Full), flashed, restarted and the custom loader started, but soon it froze and restarted. It was the first infinite loop.
Then I decided to get the nightly image. Did the same thing, wipe, flash, restart, got the same results.
Then I gave up from PAC-man, and got BAM Android. Got their RC version, wipe, flash, restart, loading screen, freeze, and restart loop.
So am I forgetting something that should be done for the TF700?
Click to expand...
Click to collapse
Your on 4.1, thus you have 4.1 bootloader. Those roms require a 4.2 bootloader. My recommendation would be to read through CROMI-X thread from sbdags for detailed instructions for upgrading.
JoinTheRealms said:
Your on 4.1, thus you have 4.1 bootloader. Those roms require a 4.2 bootloader. My recommendation would be to read through CROMI-X thread from sbdags for detailed instructions for upgrading.
Click to expand...
Click to collapse
Oh, what a relief, thanks for the extra note, I didn't knew even the bootloader has versions, but it seems that now I understand another doubt that I had, though unrelated to this case.
I'll give it a look, at first I was looking at the latest Xenogenesis 5 thread, but I just saw the previous version (4.7.0 - http://forum.xda-developers.com/showthread.php?t=2223492 ) and seems like I found my answer in the first post. I'll try it tonight.
Thanks for fast answer
Yeah, it worked, thanks.
Just installed the bootloader, and the ROM worked.
Related
Hi guys,
I just bought a new Coby Kyros MID8127 tablet (A8, Android 2.3) for my friend.
Now, I want to flash a custom ROM with JB on it, but I just did not find any ROM, CWM or tutorial for that here at XDA (or elsewhere).
Is it possible, that there is no custom ROM for that tablet to have?
Thank you in advance.
Greetings,
sYCO
I have the same tablet and I bought a custom ROM from the people at KTZ, however, I could not install this ROM successfully, in order to install it I had to take the tablet to factory reset state and then delete a bunch of system applications to make room for the new ROM because the ROM does not allow you to install it from a formatted system partition (it's more like an upgrade). But when I finally installed the ROM it wuold not boot a second time; what that means is that, after installation the ROM boots normally but if I reboot it gets caught in a loop where I just see a blue disk spinning and it doesn't do anything else and the only way to get it out of that loop is to connect the USB cable and boot to recovery via adb and restore the backup that i did before flashing the new ROM. I tried to get help from the guy who makes these ROMs but he wasn't very helpful. I followed all his instructions and always got the same result.
I managed to install manually most of the components of this ROM through a long process of trial and error and left out the components that make the tablet misbehave and now I have a hybrid on my tablet which works pretty well with the exception of the wifi. The wifi works but at times is painfully slow.
I tried other ROMs from Android Tablet forums (check here). There is an ICS Rom there (or more than one, I don't remember) and also a JB ROM for the 8127 but I could not make them work on my tablet. The ICS ROM installed fine and runs very fast but it keeps freezing so I uninstalled. The Jelly Bean did not install properly and it was very hard to get the tablet to a working state after it bricked.
That was a while ago and I haven't checked lately if there is something else out there.
leunam12 said:
I have the same tablet and I bought a custom ROM from the people at KTZ, however, I could not install this ROM successfully, in order to install it I had to take the tablet to factory reset state and then delete a bunch of system applications to make room for the new ROM because the ROM does not allow you to install it from a formatted system partition (it's more like an upgrade). But when I finally installed the ROM it wuold not boot a second time; what that means is that, after installation the ROM boots normally but if I reboot it gets caught in a loop where I just see a blue disk spinning and it doesn't do anything else and the only way to get it out of that loop is to connect the USB cable and boot to recovery via adb and restore the backup that i did before flashing the new ROM. I tried to get help from the guy who makes these ROMs but he wasn't very helpful. I followed all his instructions and always got the same result.
I managed to install manually most of the components of this ROM through a long process of trial and error and left out the components that make the tablet misbehave and now I have a hybrid on my tablet which works pretty well with the exception of the wifi. The wifi works but at times is painfully slow.
I tried other ROMs from Android Tablet forums (check here). There is an ICS Rom there (or more than one, I don't remember) and also a JB ROM for the 8127 but I could not make them work on my tablet. The ICS ROM installed fine and runs very fast but it keeps freezing so I uninstalled. The Jelly Bean did not install properly and it was very hard to get the tablet to a working state after it bricked.
That was a while ago and I haven't checked lately if there is something else out there.
Click to expand...
Click to collapse
Hey Guys,
Just found this link. Maybe you can try it out and tell me if it works for you.
http://www.androidtablets.net/forum...lly-bean-stock-lite-mid8127-rooted-gapps.html
jpapadami said:
Hey Guys,
Just found this link. Maybe you can try it out and tell me if it works for you.
http://www.androidtablets.net/forum...lly-bean-stock-lite-mid8127-rooted-gapps.html
Click to expand...
Click to collapse
Sorry, I gave that tablet back and cannot test it anymore. I rather recommend to buy an Ainol Novo 7 Crystal. It is cheaper, better and ****ing fast with a nice custom ROM support like CM 10, CM 10.1, Paranoid 3.0, Crystal-Fuse, ...
Btw, KTZ sucks totally.
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 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.
I have a tf300t us sku.
I unlocked it about a year ago. I was running pacman, when in April, my lcd cracked. So, I bought a new lcd and replaced it. In the process of replacing the lcd, the digitizer cracked! So, I ordered a new digitizer. I installed it, and seems pretty solid, and looks good, but touch still does not work.
So, I thought maybe I had to update the touch firmware. Tried to run a command to fix that with the updated firmware, but my rom returned that the update_fw was not found.
I think I need to be on stock to fix it. So I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2) from the asus website. I tried to put it on an sdcard, and transfer it over. It found the sdcard the first time and seemed to install the sku no problem. But it bootlooped! So i tried again, same thing! I keep bootlooping. Before all of this happened, I was already on 4.2 bootloader and all that, so i should be fine, but it's not working. I don't know how to exit this bootloop...
Edit:
I just tried to flash twrp. Seemed to flash fine, but when I try to boot into twrp I don't have a recovery....
Edit 2:
Got twrp installed. seems that I have 5% battery life. so I'm gonna charge it all the way up then try to flash the firmware.
Edit 3:
I did a cold reset, which fixed the bootloop. After I could boot I flashed philz recovery. Problem was, I had ghost touches. So it was hard to get root. Finally got root and successfully updated touch screen fw. Its running very well now, bout to slap pacman on this guy.
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