yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] ViViDboarder:
Ah, then yea. We can try to have someone flash the blob before we upload to goo.
[Eee Pad Transformer Android Development] hunkyn:
Guys

How do I use thi? I am on stock ICS and want to see if i can install CM10 to get the JB flavor. I have not been in android world since i last my HTC Aria and seems like things have changed drastically.

Been looking in transformer tf101 forums last two days and there are so many options and so many ROMs but dont know where to start.

I downloaded this from play store what else do I need besides the CM10 Nightly rom and this app?

Any help is greatly appreciated.
[Eee Pad Transformer Android Development] bfmetcalf:
If you mean you downloaded ROM manager from the play store, DO NOT USE IT!!!

Use one of the one click methods you see floating about around here to install a custom recovery, then use that to flash the ROM after wiping data/delvik/cache.
[Eee Pad Transformer Android Development] ViViDboarder:
This does not root your device. You can only install this to install a rom after rooting.
[Eee Pad Transformer Android Development] hunkyn:
Thanks that explains it. Which one is best for rooting and the one that works with CM10 or Raymans rom? I saw some of the threads saying use this if you install the rom but some did not.

Thanks in advance.
[Eee Pad Transformer Android Development] ViViDboarder:
There is probably a rooting thread stickied. Once rooted, come back here and we can get twrp and a rom installed.
[Eee Pad Transformer Android Development] hunkyn:
I just did the root finally. I used the 1-click root and it seems to have rooted my TF101. How do I use this TWRP now that I have rooted? I tried using the app and I did the open recover script option it say rebooting but it just restarts the tablet does not go into recovery.
[Eee Pad Transformer Android Development] thatlonedude:
Power off the tablet, hold the power and volume down buttons, when the screen turns on press the volume up button and it should boot into recovery
[Eee Pad Transformer Android Development] ViViDboarder:
Yea, do this. You may have to reboot normally first while it installs the recovery system.

After that you can reboot and to the volume down + Power then Volume up at the screen prompt to launch Twrp.

Once launched, make a backup of your current system.

With a backup you should be fairly safe with doing any kind of modifications to your device. After backing up and rebooting to Android you can download any rom you want and install it with twrp.
[Eee Pad Transformer Android Development] jkieffer46:
flash

how the heck do i flash the recovery without installing goo manager? i'm stuck right now with cwm recovery and can't get past the eee pad screen.
[Eee Pad Transformer Android Development] thatlonedude:
What cwm are you using? Some versions would make people get stuck in a boot loop that would only boot into recovery. the only way to fix it is to power down, hold the volume down and power, leave it alone for 5 seconds and select cold boot into Linux. If thats not the case though, than you'll have to search xda for a flashable zip that'll install twrp
[Eee Pad Transformer Android Development] ViViDboarder:
GooManager is by far the easiest way. Any reason you don't want to/can't use it?
[Eee Pad Transformer Android Development] thatlonedude:
I think he's stuck in one of those recovery boot loops which is why he can't download goo manager :/
[Eee Pad Transformer Android Development] ViViDboarder:
Try the directions at the bottom of the page here: http://www.teamw.in/project/twrp2/109

You download the .blob file and flash it with adb. That should do it for you.
[Eee Pad Transformer Android Development] PMcHargue:
You can also re-install the open-script recovery from the setting section of goo manager. This will D/L the latest version of TWRP, and install it - updating TWRP on your system.
[Eee Pad Transformer Android Development] JerryGNYC:
He said he can't do that. He's stuck with fruit loops... :eek:
[Eee Pad Transformer Android Development] maxjk:
When updating my ROM via GooManager, I don't see an option to place Nandroid backup on external SD card. As the backup is usually around 1.7GB large (some large games), I would very much like to do so; is there an option I'm missing somewhere?

Or should I just manually perform the steps in recovery?
[Eee Pad Transformer Android Development] hunkyn:
Actually i did that also and for some reason it did not work then. I had to try this like 10 attempts and then the 11th attempt took it. Now i am in and everything is fine now and great and buttery smooth.

Thanks for all the help guys.
[Eee Pad Transformer Android Development] ViViDboarder:
No, Goo Manager doesn't do that. I know s0up is working on a new version though. I'll try to see if he has any plans to let users select a default location.

Glad it's working!
[Eee Pad Transformer Android Development] JerryGNYC:
IMHO, best to do manually. You'll know exactly what's happening... :silly: :good:
[Eee Pad Transformer Android Development] atn0716:
Hello, I just installed v2.3.1.1 and installed liquidsmooth rc7 without gapps. I rebooted to the recovery, however, it said E:unable to mount /data, internal storage, data/media during gui startup, /data when trying to read settings file. I don't have any gapps so I don't have access to play store. When I plug in to my computer, all the files in the internal storage shows up. What can I do? Please help. Thanks
[Eee Pad Transformer Android Development] peacekeeper05:
edit: double post
[Eee Pad Transformer Android Development] peacekeeper05:
Whenever I flash something It always says at the end:

what does it mean and how do I fix it? I was able to boot the rom(EOS v.81) that I flashed though. .

and everything seems to be working well.
[Eee Pad Transformer Android Development] Taomyn:
I see the same thing and have just been ignoring it. Maybe that's a bad thing but I've not noticed any issues.

---
[Eee Pad Transformer Android Development] chumboy:
help, help !!!

had goomanager install twrp 2.3.1.1 and now i can't make backups or restore any previous backups.

twrp keeps saying:

e: unable to mount /data

e: unable to mount /internal storage

i had a major problem before updating to 2.3.11 when i used Revolution HD Super Wipe (i never use scrips...and now i know why!)...after that, tab wouldn't boot past asus logo. the i tried using Oneclickrecovery-0.4 and NVFLASH_ICS_9.2.1.27_US_NOROOT. both process screwed up until oneclick finally worked.

I have paranoid-android installed now and can't restore previous roms or my stock backup.

i have nothing on this tablet that needs saving (other than external sd card)

i'd just like to get back to 9.2.1.27 stock and start over fresh. i don't care if i nuke everything. what program should i use to restore everything to stock?

can someone point me in the right direction?

------------------------------

edit: wait....i restored permission in twrp and wipes went fine...restoring previous backup of teameos now....will let you know.

-------------------------------

edit: nevermind...dunno what happened, but fix permissions solved it. backup and restore on 2.3.1.1 works fine.
[Eee Pad Transformer Android Development] ViViDboarder:
Cool, the way to restore otherwise would be to use nvflash and reimage the device.
[Eee Pad Transformer Android Development] chumboy:
hmmm....seems like i need to fix permissions everytime i get into twrp or i get those mounting errors.

maybe i just need to nvflash/reimage.

i'm a nvflash idiot...is there a good guide for nvflash/reimage?

i have the latest .27 image from asus website.

and i have a zip called NVFLASH_ICS_9.2.1.27_US_NOROOT...guess i turn off tab, connect to pc, hold vol up and power, then run the .bat?
[Eee Pad Transformer Android Development] Yank555:
Hi guys,

I've just made a kernel flasher with option using Amarullz Aroma Installer (latest v2.56), but I just can't get it to work on TWRP recovery... I choose the zip, it loads Aroma installer binary, starts it but never gets to my splash screen.

I've searched the thread for "Aroma" and got 0 hits, so I hope the question hasn't been asked before... I've let my TF101 alone for quite a few months and concentrated on my S3, but I started working on my kernel for it this WE, so I do have some catch up to do on the TF on xda in general...

I've read here that Aroma is only supported in CWM 5.5.x or more, but I'd rather stick with TWRP. On the other hand I've seen on amarullz thread in the changelog for EDELWEIS - 2.55 - BUILD 121003-030 that amarullz gives "Thanks to agrabren from TWRP", so I guess it should be supported...

The same Aroma installer (more or less) for my S3 kernel works just fine on TWRP 2.3.1.0...

I've flashed CWM 5.5.0.4 by Roach and tested my zip, flashed fine. If you want to check my zip file, you can get it from here (OC not yet implemented, Aroma settings for OC will always default to 1.0GHz).

Any clue very welcome !

Thanx, JP.
[Eee Pad Transformer Android Development] ViViDboarder:
Take a look at the recovery log. Are there any errors? I can check next time I boot my tf.
[Eee Pad Transformer Android Development] Yank555:
Hmm .. how do I access the logs when flashing the zip hangs the device ? Is adb available in the recovery ? Never though of using it there so far...

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4a Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Eee Pad Transformer Android Development] ViViDboarder:
Yea. Adb is available. I think it's in /tmp/recovery.log and you can grab it with adb pull.
[Eee Pad Transformer Android Development] Yank555:
Will check that tonight and report back !

Thanx, JP.
[Eee Pad Transformer Android Development] Yank555:
Hmm, strange, all I get is a MTP USB device "failed" in Windows when connecting my TF once it has booted TWRP ... if I boot ARHD, USB debugging enabled, USB connects fine, but adb still isn't working :(

I will test at work as I have ASUS drivers installed there ... at home I have SGS3 device drivers installed, thought that wouldn't be an issue, but looks like it ?!

JP.
[Eee Pad Transformer Android Development] Yank555:
OK, sorry for not having had the time to do this any sooner :(

I've pulled the logfile (attached), but I can't see anything really conclusive in there :rolleyes:

Maybe you can see something I don't...

JP.
[Eee Pad Transformer Android Development] ViViDboarder:
Interesting. I'm seeing aroma start debugging and saying Starting Interface, but I see no errors from aroma. The only thing that seems weird is that it shows Starting AROMA INSTALLER twice. Does the log from CWM show that?

Also, I'm not totally sure how you build aroma installs, but I know Aroma works just fine on all other devices.
[Eee Pad Transformer Android Development] Yank555:
Absolutely agree on your last statement, hence my surprise when it didn't work on the TF101 :eek:

It only works on Roache's 5.5.x.x non touch CWM, all other CWMs I've tested gave the exact same behaviour, Aroma seems to start, but the splashscreen won't come up.

You can test it with Amarullz "default and empty" Aroma, won't work either :confused:

Can I pull the very same log (location and filename) on CWM ? If yes, I'll reflash Roach's working CWM, flash the kernel and get and post the log here...

JP.
[Eee Pad Transformer Android Development] Yank555:
Ok, I've just reflashed Roach's 5.5.0.4 recovery, and flashed my kernel. Unfortunately there is no adb support, so all I can offer at this stage is a picture of what is shown when you go in advanced menu and choose 'show log' :

If I can help in any other way, just let me know...

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4c Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Eee Pad Transformer Android Development] djlenoir:
How can I get a .img version of this recovery? Can I convert the .blob file?
[Eee Pad Transformer Android Development] Yank555:
You need to get hold of the blobtools, either the sources, or the compiled binaries ...

The sources can be pulled from here : https://github.com/AndroidRoot/BlobTools

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4c Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Eee Pad Transformer Android Development] Nu11u5:
I'm getting pretty much the exact same issue.

TWRP refuses to mount the /data directory and internal storage no matter what I do. With a little bit of fuss I can get it to mount my external storage to /sdc.
[Eee Pad Transformer Android Development] Yank555:
Hi,

I've started comparing Roache's CWM with TWRP trying to find why Aroma would work on his CWM and not TWRP.

Could it be due to the lack of "/sbin/setprop" or "/sbin/edify" symlink to busybox in the recovery ramdisk ?

Both are present in Roach's CWM, and missing in TWRP ? I Aroma is most likely using setprop as it stores user responses in .prop files.

But I'm just guessing here...

JP.
[Eee Pad Transformer Android Development] chazzdjr:
When do you think we'll see an update to this so we won't run into the sdcard /0/0/0/0 issue with 4.2 roms?
[Eee Pad Transformer Android Development] ViViDboarder:
I can try to compile the new version this week. Incidentally, how are the 4.2 roms?
[Eee Pad Transformer Android Development] chazzdjr:
TeamEos just released their early early early 4.2.1 build. I'm holding off until Twrp is ready. I'm sure it's buggy anyway.
[Eee Pad Transformer Android Development] ViViDboarder:
Just an update.

Tested a new build last night that resolves the issue we are seeing with CM10.

Here is the breakdown:

Twrp reads the drive format from fstab (ext4)

Twrp then generally checks the ACTUAL format from blkid

Since blkid should be more accurate, we go with that since our fstab is generic

All other roms report ext4 from blkid, CM10 reports ext3

This causes Twrp to try and mount /data as ext3 which fails

This is definitely something CM10 is doing to the partition on boot

We are "resolving" the issue by telling twrp to ignore blkid for /data and therefore mounting as ext4

Release should be sometime today when I get it uploaded.

I should also mention that since this is a build on the latest version of twrp, all 4.2 changes are included. That means formatting /data doesn't mess up your multi user support.
[Eee Pad Transformer Android Development] josteink:
That's fantastic. This /data-bug has been one of the few remaining annoyances I have with my TF101.

I guess this also fixes the similar issue with /staging and /cache ?
[Eee Pad Transformer Android Development] ViViDboarder:
I could be applied the same way to those partitions if they are causing issues as well.

I'm not seeing errors from either of those two in my recovery.log though like I was with /data.
[Eee Pad Transformer Android Development] ViViDboarder:
New build uploaded. Check Goo later today and it should be there.

It's up on techerrata now and will be mirrored to goo soon:

Techerrata: http://techerrata.com/browse/twrp2/tf101

Goo: http://goo.im/devs/OpenRecovery/tf101

EDIT: And it's up! Time to update the OP.
[Eee Pad Transformer Android Development] josteink:
Im also getting those issues with both /staging and /cache, at least presented in the on-screen log, but if I attempt to mount the partitions from a shell afterwards without specifying FS-type, it all seems to go well.

Basically things like the following works fine:

$ mount /dev/block/blkmmc0pX /staging
[Eee Pad Transformer Android Development] ViViDboarder:
What does blkid report?
[Eee Pad Transformer Android Development] josteink:
I was about to go check that when I discovered that my recovery now works perfectly without any need for manual mounting of anything. I guess the latest ROM + kernel I installed (RaymanFX/Gierdo's CM10 builds, 2012-11-29 w/KAT kernel 70 lidpatch) finally got that issue fixed, just in time for me not to notice.

I'll be back here reporting stuff if I ever encounter the issue again :)
[Eee Pad Transformer Android Development] catfishbilly:
installing from goo.im still shows 2.3.1.1
[Eee Pad Transformer Android Development] clouse2013:
You can download it and install it through the terminal. Just google install recovery blob tf 101 and its one of the first links. Worked fine for me.
[Eee Pad Transformer Android Development] ViViDboarder:
I'm looking into it, but the directions on a .blob install are here:

http://www.teamw.in/project/twrp2/109
[Eee Pad Transformer Android Development] ViViDboarder:
Fixed in Goo. Flashaway!
[Eee Pad Transformer Android Development] Sziehr:
I installed 2.3.2.3 through Too manager on my Glider, and it is completely unusable, my screen touches are not detected. Now I have to figure out to flash CWM without a working recovery. Any solutions?

Never mind, used the apk from Gnufabio
[Eee Pad Transformer Android Development] ewingr:
Boot not backed up...

I don't know how this happened. But I have a TWRP backup I want to restore, and Boot is not there. So, when I restore, I am restoring System and DAta. What I appear to end up with is as if I had done a hard reset.

I'm guessing I need to reinstall everything. Just wondering what anyone can tell me about boot not being there, and any thoughts to share.

BTW...I lost my IMEI too. I did do a backup of it. I'll see if I get it back.
[Eee Pad Transformer Android Development] Nu11u5:
Data and the internal SD are readable in the new version but cache is still inaccessable.
[Eee Pad Transformer Android Development] ViViDboarder:
What's a Glider?

Did the backup include boot? I don't think we did until the last update in October where it was added in. Also, do you mean to say your data partition did not restore? Do you have a recovery.log that I could review?

Have a recovery.log I can review? I'm not seeing errors in my log regarding Cache.
[Eee Pad Transformer Android Development] *Detection*:
Is it a bug or am I just not understanding correctly, when I choose Backup, it tells me my data partition is 2.3GB and System something like 400MB but I have just about filled my 16GB, only a few hundred MB remaining of free space

Just checking before relying on the backup and then finding out it didn't back everything up :)

Amazing recovery though, thanks for the hard work :)

Latest 2.3.2.3 installed
[Eee Pad Transformer Android Development] ewingr:
I've done 3-4 attempts at restore since posting. ONe was with a different image backup. Does the log get overwritten with each recovery?

I can say that the backup did NOT include boot. Although I don't know why. All I can think is that somehow I touched the boot X mark and inadvertantly unchecked it. I typically have done 2 different backups, but didn't this time. One thing for sure, I'll be double sure all appropriate things are X'd when I create new ones.
[Eee Pad Transformer Android Development] Nu11u5:
Attempting to wipe cache:

http://pastebin.com/tRjuSrbM

Updating CM10 (successful but some mounting errors):

http://pastebin.com/mPLyVUvy
[Eee Pad Transformer Android Development] droyd4life:
Hey everyone, when I turn on my tablet it just boots into my CM v3.1.0.1 recovery (I know, it's an old recovery) and I tried putting Rayman's Android 4.2 ROM on my tablet and then my tablet just kinda got screwed up. Can I flash TWRP through CM v3.1.0.1? My Tablet won't get past the boot animation (boot loop) but I do have a microSD card that I could put stuff on and flash through CM. :confused: any help is greatly appreciated :good:
[Eee Pad Transformer Android Development] chazzdjr:
TWRP for the galaxy Nexus just got updated to 2.3.3.0

Sent from my Mmuzzified Verizon Galaxy Nexus on Tapatalk 2
[Eee Pad Transformer Android Development] sttovo:
Follow the steps from this site: http://teamw.in/project/twrp2/109

Edit: so sorry! Those instructions are for w/o goo.im. Hmmmmmmmm, I don't know how to flash from cwm. Again, sorry for not helping.
[Eee Pad Transformer Android Development] Nu11u5:
Since you can still boot into CWM, just revert to a ROM that you know works. Then use GooManager to install TWRP.

Don't ever mess with your Recovery if your System install isn't working. If you get both into a state that can't boot you are getting ever closer to bricking your device.

Afterwards you can try your new ROMs safely.
[Eee Pad Transformer Android Development] droyd4life:
thanks ill try an older ICS rom
[Eee Pad Transformer Android Development] Sziehr:
Sorry, typo. Meant to say Slider (SL101)
[Eee Pad Transformer Android Development] droyd4life:
Hey guys. I'm still tuck on CM 3.1.0.1, and I installed ARHD 3.6 ROM to my imcroSD card through my computer. I couldn't get the superwipe script because the link was down so I just wiped data/cache/dalvik cache instead. After I installed the ROM I hit reboot now and it just reboots back into recovery. So then I turned off the device and tried to cold boot. But it won't even cold boot, it just gets stuck at "cold-booting linux". Am I bricked? I don't think I am, I can still access recovery. Is there any way I could flash a stock ROM or something? I can't even get to a boot logo :(
[Eee Pad Transformer Android Development] grgmre:
If you can get into recovery, try to factory reset/ wipe, then re-flash the rom. It's been a while since I used CM recovery (TWRP has a format /system option that would work). The idea being that you need to clean where the rom would be, and re-install to get it to boot. If you can get to recovery you're not bricked, you're just working with a borked operating system that needs fixing.

It sounds like you have a bad rom zip. The upside is you're working from your SDCard. I'd suggest grabbing the ICS rom (I like Revolver) as your CM recovery is kind of old, Download it to your computer, transfer it to your SDCard, then try to flash that again.

My main point is your shouldn't need to go to 'stock' to fix this problem. You just need a working rom in your /system folder and the one you have doesn't seem to want to boot. Revolver, for me, was the best ICS rom out there, and pretty much a stock rom with root access, so I'd try that. If you can get that running your next step would be to upgrade your recovery to either TWRP (recommended) or RaymanFX's CWM Recovery v6.0.2.1.

The newer recovery software does a way better job of keeping your system clean. I'm suggesting you get to a working operating system first, then upgrading that right away
[Eee Pad Transformer Android Development] droyd4life:
Thank you SO much I really do appreciate people like you helping me :)
[Eee Pad Transformer Android Development] droyd4life:
Nothing is booting. Not ARHD or Revolver. I can't do anything except be in recovery. Even when I hit reboot system now it just reboots into recovery.
[Eee Pad Transformer Android Development] JerryGNYC:
Have you tried booting normally by holding volume down and power when the tablet is off, and on startup, NOT selecting the option to load recovery?
[Eee Pad Transformer Android Development] ViViDboarder:
Try flashing a rom again. Maybe restore a backup of boot if you have one. If your normal boot got corrupted, you can restore or re flash.

I had the opposite issue as you back when porting twrp. I had it give me a booting Linux message but it was booting to Android every time. Cause was a bad kernel.
[Eee Pad Transformer Android Development] Nu11u5:
Search for "TF101 recovery boot loop" and see if that's your problem. It happened to me once and the fix took care of things.
[Eee Pad Transformer Android Development] kenshin1388:
Any plans to update to 2.4?
[Eee Pad Transformer Android Development] josteink:
Since when was there a 2.4? I just installed 2.3.3 on my gnex :D
[Eee Pad Transformer Android Development] frusso21:
Very easy and I love the keyboard for naming backups and such!
[Eee Pad Transformer Android Development] simo.scorpion:
I can flash if I have already the rogue 1.3.0 recovery ?
[Eee Pad Transformer Android Development] ViViDboarder:
This will replace Rogue, but yes.

The only cost to switching is that your old backups will be incompatible. I recommend keeping the old recovery handy just in case you need to go back to rogue to restore an old backup. That is until you've redone your backups in Twrp.

That's what I did with all my devices. Thankfully I've never HAD to restore a backup other than my most recent.