Related
Well I haven't been on XDA in over sixth months but in my times of trouble I require help. Awhile back I flashed one of the first experimental ICS ROMs to my Xoom, it was non fuctional in many aspect but I liked it and kept it. Now, I'd like to get rid of it but I can't install ADB on my new computer (It's a Java JDK thing that I can't solve for the life of me) I tried flashing a new ROM over it but it fails half way through. So how can I get back to stock without being able to flash or use fastboot? Thanks guys.
P.S. Sorry that my terminology is rusty.
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
I already tried flashing different ROMs but it won't let me, I just get an error after it tries to install, no matter what SD card or ROM I'm using.
I'd recommend flashing this in recovery: http://goo.im/roms/TeamRogue/Xoom/Recovery/rogue_XM-recovery-1.5.0-rc3.zip
It's an updated touch recovery for the xoom, then reboot and go back into recovery and flash a new rom with that recovery, should work but let us know if you have more issues
Ok so i've finally decided im ready to unlock and flash. My question is this: whats the deal with returning to stock and redoing everything on certain roms? Can anyone explain to me the variables here?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
once you have your device rooted and have a recovery installed, make a nandroid back up your stock rom, flash whatever rom you want, then if you need to go back to stock rom, just flash the nandroid back up you made. If you want to go 100%, then you will have to find the stock recovery image, and flash that over your custom recovery as well, then just use OTA Rootkeeper... and temp unroot your phone... and viola, your 100% stock again.... but if you plan to go back to 100% stock then DO NOT UNLOCK YOUR BOOTLOADER!! there is no way to lock it again once you unlock it.
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
If you flash a stock ROM using CWM you will lose all data on your device, including any backups you made using CWM. So be sure to backup those files to your PC (they're located in the clockworkmod/backup folder of your internal storage) before flashing the stock Asus ROM.
I've been changing my ROM's throughout the day and have basically memorized the process of flashing CWM, root, and ROM's by now
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
TWRP can flash stock. I've done it.
Sent from my SGH-I897 using xda premium
Ive read about problems reflashing ROMs when youre on the CM or AOKP. Need to return to stock, then flash other ROMs, dunno why exactly. So is it enough just to restore my stock nand backup or do I need to do something differently? :good:
This is exactly what im talking about. What are the rules when coming from cyan to a stock flavor?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
So lets say right now im ready to unlock and root. I would want to unlock the device, then root, then flash CWM (not twrp) so i could still retrain (and boot in to without reinstalling) my original rom? Because i still want to titanium my apps.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
not sure if I understand your question right, but yeah you can use your stock rom when you root or flash cwm. Untill you wont wipe anything within CWM, theres no reason you coulndt use it. But dont forget to do backup of your stock mate.
I think part of the confusion is defining what "stock" means, and I've got two different views on it over the past few days:
COMPLETE STOCK means flashing ASUS' original stock firmware, which completely wipes out everything on your tablet (including your nandroid backups) and CWM and takes you back to a fully stock tablet (except it will still have unlocked bootloader). From here, if you want to install ROM's like CleanROM or Hydro you have to re-flash CWM each time, then flash the appropriate ROM.
MODIFIED STOCK would be making a nandroid backup of your stock settings as soon as you flash the stock ROM, install CWM, then back it up and you can revert to it accordingly. I don't know if this would break things when you tried to flash Clean/Hydro and so maybe someone can clarify.
I wanted to try both hydro and cleanrom so I spent many hours yesterday flashing between stock/modified stock. Its kind of a pain, but all part of the learning process.
And one thing I want to note both for myself and for anyone else: if you flash stock without removing CWM it'll give you the broken bootloader logo (android on his back w/ exclamation point), and my solution has just been to do a 'wipe data' from the fastboot menu and the stock will work fine. What I mean by this is I've done this at least three times, where I flash STOCK from within CWM and when I try to boot into recovery, I'll get that android. That's because STOCK completely erases everything including CWM so in order to restore the normal operating procedure, you just need to 'wipe data' from within the tablet.
Hope my understanding of these situations is correct, if not anyone can feel free to correct me
People like to experiment with their tablet, they get easily bored with the same thing.
So they go back to stock and flash another rom like Hydro which is stock based because when you flash CM or AOKP it won't let you just flash to Hydro.
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
NOT TRUE!
It should be noted that TWRP is now more functional than CWM. TWRP can now flash stock ROMs just fine. It can now restore complete nandroids, including /boot, and it can now flash from and store to the external SD card. It was just recently updated for this, which is why all the information until now has said to use CWM to flash the stock ROM. So, go ahead and use TWRP. It's perfect now.
I was on locked on stock OTA JB.
I unlocked a few days ago, then last night flashed TWRP. Created a nandroid, then rooted.
Today I've spent several hours downloading ROMs, doing Titanium backups, surfing forums, backing up my personal files etc. i.e. using my tablet normally without problems.
I decided it was time to flash a ROM so booted in TWRP to create a fresh nandroid. Then when it finished I rebooted the system with the plan to copy the nandroid to my pc.
The tablet booted, but then after 30s or so rebooted. It's now stuck in this boot loop. So I tried a cold boot, and then restoring the latest nandroid and the problem persists. I'm currently trying to restore the pre root nandroid I made.
To recap - I am on stock OTA JB, with TWRP v2.3.1.0 recovery. Any thoughts?
Ok just to update - the pre root nandroid seems to be stable at the moment. So... What to do?
Should I reflash the recovery? Try a different recovery?
Any ideas why the nandroid would be borked when the system seemed stable when I created it?
Sent from my Galaxy Nexus using Tapatalk 2
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
No it doesn't, it just replaces stock recovery and allows you to gain root.
You could start your own thread. Or, you could read the thread in Android Development that gives clear instructions for noobs to gain root and install TWRP or CWM.
Sent from my Galaxy Nexus using Tapatalk 2
which ROM were you trying to flash? was it a JB rom?
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
After you install TWRP, you just need to flash a root zip file with TWRP to gain root..
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
Flash a rooted custom rom. ull gain root + rom easily
mike-y said:
which ROM were you trying to flash? was it a JB rom?
Click to expand...
Click to collapse
Since this thread got immediately hijacked i'm not sure but I'm going to assume this part of your post was aimed at me...
I wasn't trying to flash a ROM at all. I hadn't even got that far. All I'd done was flash the recovery, root it and then create a nandroid. It was creating the nandroid that seemed to trigger the boot loop, even though that makes zero sense.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
can you get back into fastboot connected to your PC?
I'd try to re-flash TWRP. Also make sure you are using the JB version, not the ICS version.
http://teamw.in/project/twrp2/97
I just unlocked and flashed TWRP on my tf300 (with the OTA JB update) this morning, and everything is working fine. I also flashed a root file without any issue.
I reflashed TWRP and re-rooted it seems to be OK.
Then I found I couldn't get any ROMs to work - they all froze at the boot screen. The solution to that problem lies in flashing the US update of JB rather that the WW. Now I'm running Hydro with Untermensch's kernel.
One thing I did notice with TWRP 2.3 is I get the error "can't mount /storage" in the log whenever I do anything. A bit of research suggests this might be an issue with TWRP 2.3, not present in 2.2. I wonder if that is what was causing the boot loop issue I had previously.
I can't seem to find a blob of 2.2 to downgrade to so I'm living with it for now and hope it's not going to cause problems down the line.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Good that TWRP always using the same names for a DL Link. So here is the 2.2 for JB Bootloader
If you are looking for ICS just edit the dl link .
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300tg-JB.blob
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.