yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] simo.scorpion:
Ok but i can click install open recovery script ?

Inviato dal mio GT-N7100 con Tapatalk 2
[Eee Pad Transformer Android Development] sidneyk:
Yes and allow it to finish downloading the blob and automatically boot back to Android.
[Eee Pad Transformer Android Development] simo.scorpion:
Thanks, last question's : there are a important bug ? Read the micro SD ?

Inviato dal mio GT-I9000 con Tapatalk 2
[Eee Pad Transformer Android Development] sidneyk:
MicroSD should be formatted as FAT32 with a special software tool that you can Google for formatting sdcards. It may also be necessary to use Windows to check it for errors.
[Eee Pad Transformer Android Development] simo.scorpion:
And what about the bug ?

Inviato dal mio GT-N7100 con Tapatalk 2
[Eee Pad Transformer Android Development] sidneyk:
What specific bug are you referring to? If you are talking about the bug on JB 4.2.1 where it sometimes says the card is corrupted then that is what I was talking about, you have to check it with Windows chkdsk or something and fix it.
[Eee Pad Transformer Android Development] a***nc83:
This is i imagine a pretty noobish question, but how would go about going from Clockworkmod recovery to this recovery?

Thanks
[Eee Pad Transformer Android Development] RED ZMAN:
Easiest way is to download goo manager from the market, hit menu and install open recovery script. Follow the prompts and then profit.
[Eee Pad Transformer Android Development] a***nc83:
Thanks, do i have to removed clockworkmod or anything...or just by installing TWRP, it sort of overwrites that, and that's gone...or am i overthinking this and therefore sounding...fantastically stupid....im sort of new to this stuff on Android
[Eee Pad Transformer Android Development] thatlonedude:
Lol it'll just overwrite it so your good bro
[Eee Pad Transformer Android Development] a***nc83:
LOL thanks, btw, is there a preferred ROM? There just seems to be so many, each of them slightly different, with different "bugs", is there one that stands out among the rest?
[Eee Pad Transformer Android Development] Jayster0966:
+1 I'm exactly in the same boat. I bought this tablet already loaded with CM10 and CWM. Seems to be laggy.
[Eee Pad Transformer Android Development] a***nc83:
So, going the Goo manager route seemed to work well, except when i open goo manager and i select reboot recovery, the usual prompts come up, and it simply reboots, right back up, not into recovery, the only way i was able to reboot into recovery and check that the recovery was actually installed, was using the Reboot2recovery app that i used with clockworkmod....did i miss or do something incorrectly?
[Eee Pad Transformer Android Development] thatlonedude:
Oh yeah, goo cant reboot into recovery for a reason i cant recall so you have to manually boot into recovery :/

And when it comes to ROMs, i would suggest raymanfx's cm10 if you want a jellybean ROM that's pretty stable or if you just want a ROM with little to no bugs than you can try one of the ICS ROMs
[Eee Pad Transformer Android Development] cbrox:
Goomanager supports rebooting to recovery and open recovery I have been using it since TWRP was made available for the TF101

Goo manager supports rebooting to recovery from within goo but it has to be with a rom that has a power-menu selection(means the menu supports reboot to recovery) that is compatible with goo like EOS. It also supports open recovery from recoveries(TWRP) that are compatible with goo's open recovery script. Open recovery is the ability to make your recovery selections(flashing your rom, kernel, gapps, and mods) from within your rom without having to reboot to recovery to select them. You select them in the goomanager flash rom menu which is linked to where your images and mods are stored(on my external microSD in the goomanager folder for me) then select the order you want to flash them then select wipe cache and dalvik or wipe data(factory reset) then select enter and it reboots to recovery flashes your selections then reboots back up to login. You just have to take the time to do a little reading and searching to learn how to fully utilize goomanager and TWRP; once you do you will be glad you did!
[Eee Pad Transformer Android Development] a***nc83:
Ahh i see, well i guess i can just keep the reboot2recovery app, since it allows me to do without having to do it manually(my volume up button seems to have a mind of its own, and chooses when to function and when not to)

---------- Post added at 04:10 PM ---------- Previous post was at 03:47 PM ----------

Ok, just so to ensure i understand this fully....and don't mess up anything (as i mentioned i'm a noob at this, years ago i did alot of this stuff with psp, but since then not much, and i'm not exactly a techie guy...i'm a medical resident)....so please bare with me here...i can basically do everything from GooManager...select the ROM I want to flash from "browse compatible ROMs", download the gapps (If i'm suing an ASOP ROM), and then select wipe case and dalvik...and then it reboots, and executes all those tasks in the order i selected it?

Just a few other questions, is there a particular thread that discusses how to do this?

Which EOS rom would you suggest? I looking under the EOS roms in the Compatible ROMs section of GooManager, and there were several. Also i am hoping to overclock, are you aware if the EOS ROM's built in overclocker is any good, or would you recommend a different overclocking kernel?

Thanks for any help :)
[Eee Pad Transformer Android Development] cbrox:
This is where the part of reading and searching comes in. If you use the xda search box at the top and type in the key words such as "noob guide for flashing a tf101" or "Kernels, Governor, and mods" it will bring up all the threads relating to it on xda. ;)

Video TWRP 2 and Goo Manager Tutorial & Review

http://xdaforums.com/showthread.php?t=1625010

Asus Transformer EPIC NOOB GUIDE

http://xdaforums.com/showthread.php?t=1494230

Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs

http://xdaforums.com/showthread.php?t=1369817

Most any question that you have for flashing a tf101 and maintaining it(within normal reasoning) has probably been asked and answered in the Q&A thread for the TF101

http://xdaforums.com/forumdisplay.php?f=1104

Last but not least i have found that no two TF101's are the same I have 2 B60's and they both run totally different on the selected custom roms and kernels I choose to run on them. What works for me may not work for you and your hardware. There is no magical one size fits all rom and kernel and recovery combo. You will have to find the rom and kernel and recovery that performs the best for your hardware and your preferences.

Just remember search is your friend whether it's Google or XDA:)
[Eee Pad Transformer Android Development] a***nc83:
Thanks i appreciate it...trust me i've been searching...lolol idk if i'm getting old or what...or i'm just getting stupider...i just seem to get more and more confused, every evening, i come home and spend an hour or so on here....or if i have some time between rounds, i would be prowling the forums on here at 1 and 2 in the morning...lol

Thanks again i really appreciate it.
[Eee Pad Transformer Android Development] cbrox:
No problem!

You can send me a PM if you run into any issues or need any further help on your setup. That way we don't high-jack ViViDboarder's thread anymore than we have.
[Eee Pad Transformer Android Development] banditsw:
No recoveries found for your device

Hello,

I am running Android Revolution 3.6 and am planning to try out EOS 4.2 JB MR1. The instructions for the EOS rom say that I should be using the latest compatible JB recovery.

I am currently on an older version of TWRP, and have tried to use Goo Manager to install the latest recovery. However, when I hit the three dots on the upper right of the app, and choose "install open recovery script", I get the following message:

"No recoveries were found for your device."

If anyone can provide any assistance on this, I would appreciate it. I don't want to push the recovery via adb because I always seem to run into problems with adb.

EDIT: My wifi connection was down so that apparently was the problem...Duh

Thanks
[Eee Pad Transformer Android Development] jardan:
EDIT: Never mind, I installed RaymanFX's Android 4.2 V0.8.0 using CWM recovery and then installed goo manager and it worked just fine.

I have the exact same problem but my wifi is on, still no recoveries found. any ideas?

BTW I tried also with megatron and get the same result.
[Eee Pad Transformer Android Development] rbird2:
Goo Server Problems - Can not download with Goo Manager.

I really like TWRP 2.3.2.3 but not being able to flash via recovery (like 2.2 and earlier) is a real pain in the ...

Today I am updating my TF101 using Easy Flasher and can not get TWRP 2.3.2.3 loaded back on ny TF101 again since the Goo servers appear to be having some serious problems.

Since I can not get TWRP back on my TF101, I can not restore any backups so I'm now stuck.

Can we get a version of TWRP 2.3.2.3 that can be loaded from recovery. It would help so much.

Thank you,

Rodger
[Eee Pad Transformer Android Development] ViViDboarder:
You can flash it with adb using the blob instructions from the link in the op. Link even has a mirror apart from Goo.
[Eee Pad Transformer Android Development] rbird2:
I saw that it was not recommended so I was not willing to risk it.

I still think that flashing a recovery from recovery is much easier.

I trird to use the Goo Manger program to flash ROMs and quickly found scripts get screwed up quite often so I gave up on Goo Manger.

It appears the Goo server is now fixed so I used Goo Manger to get TWRP 2.3.2.3

Rodger
[Eee Pad Transformer Android Development] akyboy:
Hi

I need image (,img) 2.3.2.3 file to flash with Tubuntu, but i cannot find it in op.

Can i use blob file in Tubuntu instead?

Thanks
[Eee Pad Transformer Android Development] arun_7:
Track, thanks it works
[Eee Pad Transformer Android Development] Globespy:
Won't Reboot into recovery? Is TWRP compatible with ICS?

My TF was running sluggishly after 2 years of flashing, so I decided to NVFlash back to stock Asus ICS ROM.

I then rooted (confirmed using Root checker, plus SU was installed during the 1-click root process), and installed GOO Manager from the Play Store.

I granted GOO Manager root access in SUManager and then installed the recovery script from the menu option as described in the OP.

My device rebooted and I went back into GOO Manager and clicked on the 'recovery' button, expecting it to then boot into the TWRP recovery.

But the device just rebooted back into the OS?

Is TWRP only compatible with JB ROMS? If so, do I have to go through the process of installing CWM instead if I want to have the option to go back to an ICS ROM (Revolver) if I want to? I like to switch between ICS and JB as JB ROMS are just not quite there yet IMO, but I do like to try an updated version from time to time.

Or am I missing something here?

Thanks.

EDIT - I powered down my TF and booted holding volume down and power, then volume up when the screen started and it booted into TWRP - question is, why won't it boot from GOO Manager?
[Eee Pad Transformer Android Development] sidneyk:
My understanding is you have to be on a ROM that has 'reboot to recovery' support in it's power menu.
[Eee Pad Transformer Android Development] Jayster0966:
There is also a app on the play store called (transformer reboot to recovery) that we can use for ICS based ROMs.

Sent from my Transformer Prime TF101.
[Eee Pad Transformer Android Development] carhauler1969:
Just flashed 2.3.3.2 via GooManager. The recovery flashed fine. My concern is that I'm on Eos-Cornerstone 74 (ICS) & I was trying to make a nandroid in preparation to flash Eos MR1 4.2. The recovery appears to have frozen backing up /system, no apparent progress in the last 30 minutes. Did I make a mistake in flashing the newer recovery version on the older ICS ROM? Or its it just really slow when compression is used?

Sorry I haven't really done any flashing on my TF in about 6 months, I'm a little behind the 8 ball here... :o

Edit: apparently it failed to mount my microSD in recovery. I let it sit for four hours (taking a nap) and it never backed anything up. So I made a backup on the internal SD which worked just fine.

Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro
[Eee Pad Transformer Android Development] ViViDboarder:
Glad you figured it out. Were you able to get a log to see if the mount failure showed up?
[Eee Pad Transformer Android Development] carhauler1969:
No, actually I didn't think to do that at the time. When I rebooted into the system my microSD wasn't mounted, after removing & re-inserting the microSD it mounted just fine, & has been fine since. :cool:
[Eee Pad Transformer Android Development] chazzdjr:
Galaxy Nexus TWRP was just updated to 2.4.0.0
[Eee Pad Transformer Android Development] erickwill:
Any update on sight? ;)

Thanks!
[Eee Pad Transformer Android Development] mayurh:
Yeah, will we get the new update?
[Eee Pad Transformer Android Development] ViViDboarder:
Not that many changes for us on TF101.

That said, I can try to get a build up for it soon. I'm currently traveling and do not have reliable internet. I can also see if Dees_Troy can kick the build off himself though. We still don't have a Jenkins instance up...
[Eee Pad Transformer Android Development] Nu11u5:
I just upgraded to TWRP 2.3.2.3 and I am still unable to mount the cache partition. Flashing a .zip fails as TWRP can't create a log file residing on /cache.

This issue with failing to mount different partitions has been an issue for as long as I've tried using TWRP on my TF101. In a previous version, it failed to mount /data, preventing me from doing wipes and backups.

TWRP works great on my SGS2, but the significant issues with it on my Transformer is infuriating.
[Eee Pad Transformer Android Development] billouetaudrey:
Hi,

Goo don't want update my TWRP ... Download OK, but when want install, my tablet reboot ...

Any idea? Is it possible to flash the update in thr recovery?

Thx

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Android Development] frederuco:
It should reboot into TWRP during the Goo install, but I know some users with CWM it will not install properly.

You can try the terminal menthod listed on the TWRP TF101 site. I have used this in the past with great success: http://www.teamw.in/project/twrp2/109

Basically, download the file, name it twrp.blob and put it in the /sdcard/ directory.

Then, in terminal:

su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
reboot

PROFIT
[Eee Pad Transformer Android Development] billouetaudrey:
Very well, thx sorry much ;)

Envoyé depuis mon Transformer TF101 avec Tapatalk
[Eee Pad Transformer Android Development] rbird2:
TWRP 2.4 - Asus Transformer TF101 page

The website a few posts up (http://www.teamw.in/project/twrp2/109) shows TWRP 2.4. When I use Goo Manager to check for updated Goo Manager says no updates found. When I try "Install OpenRecopveryScript" in Goo Manager it tries to load TRRP 2.3.2.3 not 2.4.

How do we get Goo Manger to update TWRP 2.3.2.3 to version 2.4?

Thank you,

Rodger
[Eee Pad Transformer Android Development] just lou:
There is no 2.4 for the TF on there yet.
[Eee Pad Transformer Android Development] frederuco:
The title if the web page says 2.4, but it has not been ported for the tf101 yet.
[Eee Pad Transformer Android Development] maxidad35:
Hi just a question... is it posible to install this recovery on slider? Or tf 101 only has support

Enviado desde mi Transformer TF101 usando Tapatalk 2
[Eee Pad Transformer Android Development] chefp:
GooManager no longer finds a recovery for the TF101 ("check back later" or somesuch). Flashed manually in Terminal Emulator and it works great. Thanks for making TWRP recovery available to the TF101.
[Eee Pad Transformer Android Development] josteink:
Latest official is now on 2.4.1.0. Any news on if anyone plans on doing an updated build for the TF101? :)
[Eee Pad Transformer Android Development] chazzdjr:
Galaxy Nexus TWRP was updated today to version 2.4.2.0... The gap widens. :what:
[Eee Pad Transformer Android Development] thelangosta:
+1 for update.
[Eee Pad Transformer Android Development] MassStash:
Works fine. Update when it comes. For all you know, update could be buggy and everyone in here will be complaining about having to downgrade... Kna what I meanz?

~d2spr runnin' CarbonRom

cpu0/1: 1.7ghz | 192mhz | sleep 486mhz with latest ktoonsez kernel

Intellidemand

row

mpdecision: off
[Eee Pad Transformer Android Development] Taomyn:
I too would like to see 2.4 for our TF101s :good:
[Eee Pad Transformer Android Development] rbird2:
So would I...
[Eee Pad Transformer Android Development] Wdustin1:
Yep the multiple 0 folders are going to get annoying haha anybody gonna pick this up? I might have to start learning, anybody wanna teach? Lol ill learn if I need to.
[Eee Pad Transformer Android Development] josteink:
A start: http://xdaforums.com/showthread.php?t=1943625

Since I'm already building nightlies I've considered trying to build TWRP ss well, I've just never gotten to the point where I actually do it ;)
[Eee Pad Transformer Android Development] josteink:
Quick status report. Following that guide, I can build a CWM-image. I've yet to test it, so no idea if it's fully functional or not, but at least it builds.

Going by what's said in that thread, that means I should be able to switch out a few repos/sources and be able to build TWRP. And if we're lucky, it should work.

Anyone here willing to mess around with nvflash/wheelie, blobunpack, etc, to try out eventual images I make?

I ask because, I wont be able to verify that they work myself, so whoever tests this (and maybe ends up without working recovery) should be skilled enough to know how to flash (adb, dd, nvflash, whatever) a working recovery back in without assistance.

---------- Post added at 10:42 AM ---------- Previous post was at 10:14 AM ----------

Latest TWRP2.4 compiled against No name CM10.1 device-tree and sources:

http://nexfiles.kjonigsen.net/tf101/twrp/

It's completely untested and in IMG-format so that n00bs wont be able to flash it and ruin their device with it :)

Edit: Hint. From what I can tell this image is already blobunpacked and ready for nvflash. I'm at work and cannot test myself though, since my transformer is at home.
[Eee Pad Transformer Android Development] st0nedpenguin:
Any chance of a .blob?

I'm not by a USB cable but I can always give it a shot with a .blob.
[Eee Pad Transformer Android Development] josteink:
At burger king now, but give me 60 minutes and that should be up too.

---------- Post added at 12:09 PM ---------- Previous post was at 11:38 AM ----------

Blob is up.

Packed using blobpack as SOS partition.
[Eee Pad Transformer Android Development] st0nedpenguin:
Threw it on there but it looks like it just compiled a CWM image. No sign of TWRP.
[Eee Pad Transformer Android Development] josteink:
Uh. My bad. it seems for some reason the repo haven't been updated despite my TWRP override:

jostein@OFFICE:~/unbuild/tf101_4.2/bootable/recovery$ git remote -v
github git://github.com/CyanogenMod/android_bootable_recovery (fetch)
github git://github.com/CyanogenMod/android_bootable_recovery (push)

Will try again :)

Edit: on the plus side that means I have a setup which can compile a working recovery. That's certainly promising.

Edit 2: Now the build is running and I know it's a TWRP build, because it required loads of extra configuration. Hopefully my settings are OK (with regard to internal/external storage, etc)

---------- Post added at 12:57 PM ---------- Previous post was at 12:22 PM ----------

New files are up.

Same file-names but should have new content. Let me know how it works out :)
[Eee Pad Transformer Android Development] st0nedpenguin:
There we go, flashed and installed fine. :)

It's finding the internal storage, but it doesn't look like it's finding the external sdcard at all.

E:Mount: Unable to find partition for path 'sdc'
[Eee Pad Transformer Android Development] josteink:
Awesome. I just assumed /sdc was a valid mount point, since it is on my transformer for the MicroSD ;)

Just to be clear: Are you talking MicroSD or regular SD?

Once we have the kinks worked out, we can actually make this a CWM/TWRP flashable ZIP (or just ship the img off to the Goo-team).
[Eee Pad Transformer Android Development] st0nedpenguin:
Ahh yeah, it's the microSD, I'll stick a regular one in there and see what it says.

No luck with that one either, can't select it with the toggle at the top or find anything in the folder structure.
[Eee Pad Transformer Android Development] josteink:
Thanks for doing a test-drive.

I'll take a deeper look into this once I get home, try to figure out where all the partitions and mount-points are and do a new build.

If it all works well, I'll create a new thread and just post a TWRP/CWM-flashable zip and blobs there.

Edit: Btw. To save me time later on... You flashed these using "dd" or nvflash?

Edit 2: Obviously dd since you wanted blobs and didnt have a USB cable around :p
[Eee Pad Transformer Android Development] josteink:
Care to show me how you got it flashed, because now I've tried everything and I accidentally the whole nvflash :D

I'm back to square one and the initial problem though: I can dd the image all I want, but when I boot back into recovery I get the same old 2.3.2.3.

Nvflash also fails. I see my recovery is ... uhm some 6MBs and the recovery partition shouldn't really be more than 4.5 or so.

How on earth did you get this flashed? :)

I guess I'll need to go back and see what can be trimmed to make this image smaller. Change kernel, remove jars, etc.
[Eee Pad Transformer Android Development] st0nedpenguin:
I had issues with it not apparently working the first couple times, then after checking out the TWRP site realized I needed to do a normal reboot after flashing them with dd in terminal manager for it to finish the install.
[Eee Pad Transformer Android Development] josteink:
Well. Real world constraints says this shouldn't work unless you've modified your partition table. Not disputing your story, but I can't flash this and I suspect quite a few others will have troubles too :)

Sooo... Today I'm going to continue working on this and try to slim down the recovery image down to something which actually fits on a default recovery-partition.

I see I have lots of fat which can be trimmed out, and the kernel (full Lumpy-kernel, wifi, BT, everything) has a million more things than we need. Not to mention keyboard drivers etc.

I'll rip everything I can out and see if I can get his below the magic 5000000 byte limit.
[Eee Pad Transformer Android Development] MassStash:
Save keyboard support if at all possible please! Haha

~d2spr runnin' CarbonRom

cpu0/1: 1.7ghz | 192mhz | sleep 486mhz with latest ktoonsez kernel

Intellidemand

row

mpdecision: off
[Eee Pad Transformer Android Development] josteink:
Gdamn

error: /home/jostein/unbuild/tf101_4.2/out/target/product/tf101/recovery.img too large (5523532 > [5406720 - 54912])

Edit: Close though. Much closer than I was before. Only need to claim another 171 724 more bytes.
[Eee Pad Transformer Android Development] st0nedpenguin:
This tablet has seen so much abuse since I bought it that I'd really not be shocked if my partition table is a tad off, lol.